Post 4 made on Saturday August 17, 2002 at 16:26 |
CharlesPLM Lurking Member |
Joined: Posts: | August 2002 3 |
|
|
You are absolutely correct! I have just upgraded to NeoEdit 2.0.5 and the problem has gone away. There must be some interaction between the firmware update program and NeoEdit that caused the catastrophic errors to occur. This is not something you would expect, but I hope everyone is forewarned from now on. Update to the latest versions and save, save, save your configurations and data.
Charles
|
|
|