bongmanayon
04-02-2007, 06:29 PM
Marlon was bothered by the VPN problem with the K10D. Noli posted this elsewhere:
Hi. Don't have the K10 but I'm a depreview member also. Somebody (forgot who) stated it quite well when he said that yes- vpn can be observed sometimes but those who are experiencing it are pushing it beyond the limits of their equipment. This is the case for any camera (N or C). So, whichever gear you buy, everybody has to know the limits of their equipment and work within those limits. Just my borrowed 2 cents.
Nols
It does not seem to be a problem for PDML members and having occasionally used a Canon 20D & 350D, Noli is right that its not uniquely a Pentax or in particular a K10D problem (I got my hands on a D80 but did not get to use it in a low-light situation). On the scale of things, the K10D is relatively new, I remember Canon releasing an astronomy variant of the 20D mid-term to address that issue (I forgot what they called it...).
Early models of the *istDS suffered something similar and that was later addressed in the firmware updates. So that could be fixed as well.
Bong
Hi. Don't have the K10 but I'm a depreview member also. Somebody (forgot who) stated it quite well when he said that yes- vpn can be observed sometimes but those who are experiencing it are pushing it beyond the limits of their equipment. This is the case for any camera (N or C). So, whichever gear you buy, everybody has to know the limits of their equipment and work within those limits. Just my borrowed 2 cents.
Nols
It does not seem to be a problem for PDML members and having occasionally used a Canon 20D & 350D, Noli is right that its not uniquely a Pentax or in particular a K10D problem (I got my hands on a D80 but did not get to use it in a low-light situation). On the scale of things, the K10D is relatively new, I remember Canon releasing an astronomy variant of the 20D mid-term to address that issue (I forgot what they called it...).
Early models of the *istDS suffered something similar and that was later addressed in the firmware updates. So that could be fixed as well.
Bong