Bizarre EDIT Errors! (AREV Specific)
At 21 OCT 1997 12:09:12AM Matthew Jones wrote:
A client has suddenly started experiencing a break to debugger whenever they use the editor (AREV 3.12). The message "EDIT line 2 non-numeric data when numeric required" is displayed any time they use the editor from any of their workstations (after pressing return, before displaying anything). I have replaced the SYSOBJ file by DOS copying mine over the top of theirs, but this didn't fix it.
Any clues?
At 21 OCT 1997 07:52AM Maggie Woo wrote:
Was your client trying to create a new record, or edit something that was already there?
I noticed soon after getting my Windows 95 computer that I would get this error if I tried to edit a record that was pretty big (like over 50,000 bytes big), but if I booted up in DOS mode, I could function normally.
Just an idea.
Maggie
mwoo@tnc.org
At 21 OCT 1997 06:18PM Aaron Kaplan wrote:
You'll get this when memory is low or the record is just about 64K.
apk@sprezzatura.com
At 21 OCT 1997 09:22PM Matthew Jones wrote:
Strangely enough, memory is not low, and the item attempting to be edited is a four or five line VOC entry (although it seems to happen for any item tested).
At 22 OCT 1997 11:49AM Aaron Kaplan wrote:
Still seems like a memory thing though. What's the start-up command options? It should be /X /M4096 with 4M EMS allocated to the DOS session.
apk@sprezzatura.com
At 22 OCT 1997 09:38PM Matthew wrote:
We did use /M4096 some time back, but they were experiencing workstations hanging / freezing regularly at that time. We changed to /M2048 and the freezing stopped, so we've kept it at that. Maybe we should try /M4096 again, eh?
(Oh - AREV 3.12, NLM 1.10, Novell 3.12, Win95B on all workstations using Novell Client32)
(This is the same site that experiences random incidents of char(0):"OI" and a couple of other combinations of spurious characters embedded randomly in their files. You may have heard me discuss that problem some time ago as well. They still get that problem, although we have now eliminated the NLM as the cause, but we are still no closer to finding a cause or a solution)
At 23 OCT 1997 01:02PM Victor Engel wrote:
Some time back we had problems with random data corruption in files. It turned out there was a bug in the router software. After Southwestern Bell replaced the software, everything worked fine. I doubt if this is your problem, but it may open up some possibilities.
Victor
At 27 OCT 1997 09:19PM Matthew wrote:
A bizarre fix to the bizarre EDIT problem.
We found that if we use a different ".INI" file the editor works properly again! When I compared the "ini" file that works against the one that doesn't, the only noticeable difference was in the temporary path. If I change the setting on the one that works, it doesn't work any more. If I set it back to what it was, it works fine again.
This setting had been changed recently, as I noticed their sorts weren't being stored locally and were hence taking a long time across the network.
I have absolutely no idea why this would cause the non-numeric message and failure in the editor though!!