As any software designer/programmer knows, the user can always find a way to beat the system!

John Coyle
Brisbane, Australia
----- Original Message ----- From: "Tom C" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 12, 2004 1:43 AM
Subject: Re: *ist D Anomalies



It's interesting (I have close to 25 years in software design/development).

I wonder if I was triggering a bug. I was impatient to get the next shot and so occassionally would go spastic on the shutter release, hoping to fire it as soon as the camera would allow. Maybe this rejected input caused the software to branch unexpectedly and caused the mode to internally change to .jpg.



Tom C.




From: "Larry Levy" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Re: *ist D Anomalies
Date: Thu, 11 Nov 2004 08:57:43 -0600


Sounds like the typical computer engineer solution - reboot the system.

This could easily be a software problem. Try to keep track of what was happening when the camera ('s computer) got stuck. This information enables you to:

1 - Possibly avoid those situations in the future

2 - Provide the data to Pentax so that they can take corrective action for release in later versions of the software

For some strange reason, we all (including me) expect software to always work the way the designers and programmers intended it to. Always is a long time.

Larry in Dallas (with over 3 decades of system design)







Reply via email to