Hi All,
I just thought I'd let you know of a pitfall I encountered with my 300 recently.
I am running Boroda's f/w V1.05a, and recently have been trying out the
http://ebookapplications.com/ overlay, V1.6.
Last week whilst on holiday, a combination of Sun, Sand, and San Miguel caused me to have a brain fart.
My battery was showing 2 bars remaining, when the screen froze. Now my 300 is quite reliable regarding the battery meter (its about 10 months old and has been discharged fully several times), so I was surprised to see the screen freeze. My beer enhanced brain decided that a restart was needed rather than a recharge, so I tried to turn the machine off and on, which failed. Brain then decided that a reset was needed, which failed. Another pint of S.M. later, and Brain decides that a recharge, followed by the "10 times reset" is required, as the firmware was obviously corrupt

.
Have I mentioned that I was using a USB wall charger (500mA with a PSP USB lead), and my recharge lasted the length of time to walk to the fridge, pour another SM, and walk back to the 300?
I started pressing the reset button/power switch cycle, and could only watch in horror as a minute or so later the screen froze with "updating firmware now" with a flashing amber LED. I could not reinstate the 300 back to a working conditon, and being without a PC there was nothing I could do. Fully discharging/ recharging/ resetting the machine failed. I spent the last week of the holiday borrowing tatty old paperbacks from the reception, and drowning my sorrows in more San Miguel. And Sangria.
Arriving home last night, I plugged the 300 into my PC, and fired them both up. Still nothing. All I could get was one external drive showing up in "My Computer", with a 44Kb file called "Protected!!". After several hours of attempts (although sober, I was now tired after travelling home), I eventually remembered that Kartu had
helped me out previously with a firmware issue. Running the 300 updater from Kartu's link, I succesfully reflashed my reader with 505 firmware, and then Boroda's 1.05a. This was my last attempt at a fix, I was seriously starting to wonder if I had bricked the reader.
I believe that the issue I had was likely caused by the reader attempting to run the ebook application firmware mask as an update rather than a 'proper' firmware.
Regardless, I have now restored my reader back to a fully working condition. I post this tale in the hope that it may help others avoid my mistake.