Possible bug
Posted: Thu Sep 18, 2003 6:48 pm
I just discovered a way to make newspro make an internal error:
I was reading an binary article containing a .nfo file
I double-clicked on it, so it opens ultraedit to view the file (in my case i registered ultraedit to .nfo), but there was heavy HD activity at that time, so ultraedit launched very very slowly....
While ultraedit was trying to load, i pressed <esc> key to close the window and continue browsing the list of atricles in the newsgroup, and newspro told me that it had done an internal error, that i could reset or optimize database etc.....
I'm sorry i didn't write down the error message.
It's a little difficult to recreate the same situation, so i'm not sure i can reproduce this.
Just to let you know, if you think it's interesting, i can make further attempts to redo it
I was reading an binary article containing a .nfo file
I double-clicked on it, so it opens ultraedit to view the file (in my case i registered ultraedit to .nfo), but there was heavy HD activity at that time, so ultraedit launched very very slowly....
While ultraedit was trying to load, i pressed <esc> key to close the window and continue browsing the list of atricles in the newsgroup, and newspro told me that it had done an internal error, that i could reset or optimize database etc.....
I'm sorry i didn't write down the error message.
It's a little difficult to recreate the same situation, so i'm not sure i can reproduce this.
Just to let you know, if you think it's interesting, i can make further attempts to redo it