Quote:
Originally Posted by willgordon
I ran the firmware update last night, from a Windows machine. Is it worth running again? Any special tricks I should try?
|
If the firmware update ran okay, I assume that the reader itself, including the "invisible" part of its internal memory where the operating system resides is okay.
In your very first post of this thread you wrote that you already tried to format the PRS-505's internal memory as FAT16. That may actually be the root of the problem. I just checked with my own PRS-505 how the internal memory is exposed when connecting the reader to my notebook. As a Linux user I cannot verify how it looks on OS/X or Windows, but here the situation is somewhat unexpected. When looking at the properties of the three USB devices, all three are shown as "msdos" filesystem. This should translate to FAT16.
I tried to verify this by taking a closer look at the three volumes with the partition editor. Both, the SD-Card and the Memory-Stick where indeed shown as FAT16, just as expected. The internal memory, however, was shown as "not assigned", as if not initialized or not formatted.
The reader appears to have a particular way of handling the internal memory. At least differently compared to the storage cards. This means, you probably cannot simply partition and format it like a regular storage device attached via USB such as an external hard disk, SD-Card or other removable storage media.
What I would try is this: use a partition editor (either windows or mac) and delete the reader's internal memory partition altogether. Do not format or partition it, but remove any partition altogether. The idea is to have the visible part of the internal memory as a totally uninitialized blank slate. I hope that this triggers the reader's operating system to automatically initialize/partition/format it.
After you have done this do a hard reset of the reader. There is at least a chance that at this point the reader becomes usable again.
Further info:
When I got my PRS-505 a few days ago, the first thing I did was to update its firmware. I noticed that all the example content of the reader was still there, untouched. That makes me believe that a firmware update in itself does not modify the visible part of the internal memory at all. Thus it makes sense if that a firmware update does not help to remove a corruption in that area.
Hope that helps and good luck!