I have a customer who has just started to run a Rev G application on Windows Me. This application has been running on Windows 95 for at least 5 years. Rev. G seems to cause windows Me to run out of disk space. Shutting the system down and restarting frees the disk space. Any ideas or suggestions? Anyone have experience with Rev. G on Windows Me?

On what basis do you say RevG makes Windows ME run out of disk space? What have you done to verify this? The reason I ask is that if the available space to RevG is big enough, you can get an error in RevG indicating you have run out of space when, in fact, you have not.

There are other threads here about this topic and the 2 Gig or 4 Gig limit imposed by 16 bit applications. The solution, if this is the problem, is to limit the amount of free space on a drive that RevG has access to to 2 Gig max.

If this does not sound like your problem, can you provide more details?

When Revelation complained about low disk space, I had my customer toggle to Windows and check the disk space on the c drive. There was less than 100kb free on a 16 gb partition. Shutting down and restarting resulted in over 13gb of free space. Any ideas?

I have no clue. Does the same symptom occur if only applications other than RevG are used? RevG wouldn't even be capable of using up that much space except by using multiple files, since the limit of what RevG can address is 2 Gig or 4 Gig, depending on the operation. I'm thinking any problem you are having must be with Windows itself, some other program, or the hardware.

I suspect it is the swap file getting out of hand. PCMag has a little disk activity monitor utility (disk action) that you can download for free from their website (www.pcmag.com). You can set it to monitor a specific drive and it will show a log of program and time that the disk was accessed.

Why the swap file would grow so large due to REV G running is a mystery though. Could be memory leaks with the DOS setup. Are you running REV G with a PIF or desktop icon? What are the memory settings?

We are running the application from a desktop icon. I am in NJ and the machine is CA. I am going out tomorrow, and will check memory settings, swap files, etc. We seem to have narrowed this phenomenon to one operation in Rev. G. I will be running some tests this weekend. I will also try to run other DOS programs.

Thank you both for your suggestions. Any and all other suggestions would be appreciated.

FWIW: there was a MEMFIX program that was issued by RTI to fix some memory allocation problems with REV G. This was run prior to loading REV.EXE. The alternative was to send your REV.EXE to RTI and have it patched.

I don't recall the details from 11 years ago when this workaround was issued.

When I visited the customer's site, I discovered that the System Restore feature in Windows ME was the problem. In the root directory on the C: drive is a hidden folder named _RESTORE. In that folder is another hidden folder named TEMP. A particular operation in the Revelation application was causing Windows ME to generate file images of Revelation files. This was consuming gigabytes of storage space. I disabled the System Restore feature and the problem went away. Any ideas?

Interesting. I've never used ME, but probably it is recognizing the .LNK extension as an executable. Perhaps you can configure ME around this.

View this thread on the forum...