To All,
ewavr - found diskboot.bin vers 1 through 4.
jetzt - my guess is that you were saying what ewavr was about to tell me.
Found a zip file with bootable.exe 53kB from 21 jan 08, empty.dum 8,192kB from 31 jan 08 and four subdirectories with diskboot.bin of 1kB and 21kB from 31 jan 08.
Copied bootable.exe and empty.dum onto SD card.
Looked at empty.dum with ZTreeWin to confirm it was all zeros.
One at a time copied a version of diskboot.bin onto root.
Loaded camera. Turned it on.
Message: "Card Locked" displayed for about 1-2 secs.
Waited 15 secs & opened battery door. Repeated 4 times.
Put card in computer and used ZTree to look at empty.bin.
No change. Still all zeros.
After numerous tries as outlined above, I did some further testing.
During the time the card is in the camera, there is no influence on the operation of the camera. It does not disable the keyboard, nor the Power button, nor the Menu button nor any other function except the ability to take a picture on the locked card.
There is no difference whether I remove the battery or simply use the Power button to turn off the camera before removing the card. There is no indication of any activity such as a flashing or blinking LED. The Power LED stays lit until I open the battery door.
I don't know if there should be any other indications that the dump is proceeding as nothing is expressed in the instructions I have. Perhaps someone who has used this method successfully can provide additional insights.
Possibly the other four variants of diskboot.bin will hold the answers...?
As per jetzt, my previous method of creating a 0 byte empty.dum file is incorrect. (thanks for the heads up!)
The proper method is to use the 8.2 mB file contained in the archive listed below.
Any other ideas as to what's going on here and how we might obtain a dump of the TX-1 firmware??
TIA,