We are having a problem with certain Records being corrupted in the Read Write process. After the Record becomes corrupted it looks very strange when you try to edit the record manually (EDIT FILE.NAME KEY). Usually the first section of the data is moved to the first line and is separated by Field Marks. The rest of the original data is gone. After the data separated by field marks there is usually what looks like some type of compiled code. Almost like the PC is having some type of Memory corruption and then writing that out to the record.

Although I have not been able to isolate what code is corrupting this one record I have seen this in the past when I Read a Record, did some data manipulation on it and then wrote it back out. In this other situation it also did not get corrupted on a consistent basis, only sporadically. I eventually added a couple of delay()'s and that seemed to stop the problem.

We are running Arev 2.12 on NOVELL 3.12. Using mostly Windows 95/98 machines and some dos pcs. We are running the NLM, version 1.12. We have also checked the PC's to make sure they are set up correctly (ie Write behind caching disabled. EMS=4096. XMS=None. Always Suspend off.

Has anyone seen anything simmilar to this. Any info you could pass along would be greatly appreciated.

Thanks,

G Motter

We've seen this with bad versions of SETPTR or PDISK, which trashes the file handle and write data out to an different open file. Usually, the resultant file is SYSOBJ, but that's not a given.

Try upping the number of file handles.

The Sprezzatura Group

World Leaders in all things RevSoft

First, add a

FLUSH

GARBAGECOLLECT

to an insert and attach it to all programs at the start. Second, try using EXPENDABLE functions and subroutines wherever possible. Third, if you have a replacement network card lying around, try it.

EMS=4096. XMS=None. is the wrong way around - should be

XMS=4096. EMS=None. (AREV only uses expanded / XMS)

Setting file handles higher will reduce memory under 640kB, so be sparing with any increments.

Steve

I'm a little confused. Isn't EMS - Expanded and XMS - Extended. That's the way it is defined on the Window's shortcut settings.

G Motter

We saw a similar problem at a client site several years ago. At first we thought it was a bad network card. In the process of replacing the NIC, my astute tech thought that the NIC was a bit hot. We immediately saw that the computer fan was not working Thereby causing the temperature in the computer to exceed acceptable standards. Once this happens the memory in the computer can behave erractically. We left the computer open for the rest of the day and had a fan blow air over it. After doing this, everything was okay. We left it that way until the field engineer came in with a new fan. Problem solved. This may not be your situation, but you may want to check the fan.

Good luck,

rayc@symmetryinfo.com onmouseover=window.status=imagine … ;return(true)"

Symmetry Info

Ray Chan ~ Symmetry Info

Doh! - You're absolutely right - I've been working on NT for some months now and I rarely boot to Win 95 any more. Apologies for the error.

Steve

View this thread on the forum...