We installed our application on some Win 95 workstations and kept getting GPF's in REVDEBUG.DLL. Now we're pretty sure that in every case it was because OpenInsight wasn't allowed to access certain system or data files correctly (in one case some system files were left as read only, in another case the data files were corrupt).

What exactly occurs in REVDEBUG.DLL that would be sensitive to these issues? Why would a corrupt data file crash the system rather than not simply be able to be attached? We'd like to avoid any other occurances so it would help to know the broader range of issues that we have to deal with here.

Thanks,

dbakke@srpcs.com

SRP Computer Solutions

Don,

It sounds like an error occurred that activated the debugger, and the debugger was unable to load correctly because it depended on being able to access those files.

Cameron Purdy

Revelation Software

View this thread on the Works forum...