Bruce, thanks for the note back and perhaps some of your sympathy rubbed off because I just successfully upgraded the Firmware to v.1.3. Here is how I did it, I copied over the ProntoEdit v.3.4 and the 1.3 upgrade executable to my laptop - running Windows 2000, not W98 and followed the upgrade firmware instructions within PE3.4 and sure enough in about 3 minutes I was up and running. I am not sure whether it was a win.ini issue or what it is on my home pc, but it is now upgraded and I hope not to have to do any more of these firmware upgrades for awhile (lets hope v.1.4 comes out in about 100 years.) Thanks for your help. JStom

See... you should have believed me on the phone last Sunday..LOL!

I am more than pleased to see this work out for you.

To others... the lesson learned here is that if the upgrade fails when executed from the menu in ProntoPro edit, try it with just the tool.

In this case with JStorm live on the phone last week, ( I was NOT the person who sold this Pro to him. I was just helping out.) I had him try that. The tool screen indicated a problem almost immediately that appears to be masked by executing the upgrade from ProntoPro Edit. My suspiciion at the time was that something hidden in his Win system was causing this.

-Bruce
alpha2data
on eBay

This message was edited by alpha2data on 11/21/01 21:04.03.

Bruce, win.ini (while still present) is not used any more (by Windows). If it is affected by a system setting, it is more than likely in the registry.

We already know of one setting that can affect the emulator (I think) and that is to turn off support for files having equivalent 8.3 filenames.

Peter...

Thank you for the technical correction. I realize you are absolutely correct, but as an OS/2 user, ( see www.carbonbased.com.au )to me, everything is "win.ini" more as an expression than a statement of accuracy. I did realize it was a registry entry, but I was taking literary license.

However, I see that that is not really what one can do with things like this on a public post. Actually, Peter, I am having a really bad day... :-( Sorry for the inaccuracy.

I had given JStom my 800# last Sunday and he called me prox 10-11P. As I stepped him through the process only using the tool, the error occured and was immediately visible. Yet, when he later tried it through the ProntoProEDIT system, the error was masked and it was just an endless wait.

-Bruce
alpha2data
on eBay

This message was edited by alpha2data on 11/21/01 22:11.37.