AREV/Win95 Lockup (AREV Specific)
At 14 APR 1999 03:55:44PM Steve Waite wrote:
I have 17 machines running Advanced Revelation 2.1. Half of them operate under Windows 3.1 and the others operate under Windows 95. All of the windows 95 machines that have been upgraded from windows 3.1 all have a lockup problem. If you leave AREV and go to another program (Internet, Windows Word 7.0, Micosoft Excell, Autocad or other loaded programs in the background) for a period of time and then return to the AREV application it will seem locked up. The cursor will blink once every 8 seconds. If one could wait long enough you could log out normally by pressing the 'L' key and Enter then come back in the next day and it will be logged out. Right now we have to close the application by picking the Icon, wait 8 seconds
for the pull down to appear click Close then wait another 8-16 seconds to close the application. I have spent alot of time and money to develop a good Application that fits our business and am now considering going another windows based application unless I can figure out why this happens. I'm not sure if it's a hardware problem or a Windows 95 problem or an AREV problem.
At 14 APR 1999 04:29PM Stephen Revelation wrote:
Steve,
Are you using one of our networking products? Because ARev is a DOS-based program, it does not behave normally under Win95/98/NT due to issues such as write-behind caching and opportunistic locking. For more information on our networking products you can call our Customer Care Dept. at (800) 262-4747. If you are using one of our networking products, right click on your shortcut -] Properties -] Misc. and make sure that your Allow Screensaver and Always Suspend are unchecked on your Win95 workstations.
Hope this helps,
Stephen Revelation
Regards,
Stephen Revelation
At 15 APR 1999 12:21PM Michael Slack wrote:
You might want to check your shortcut settings as well. There should be a document in the Knowledge Base area that tells you what needs to be set to what to make Win95 and Arev play better together. I don't remember where to set it but you may whant to check that your write behind chaching is turned off. That a few other things that I don't remember right off hand is what we had to do to overcome the same problem. You should find several discussions on this very subject within this discussion area, you'll just have to do a little searching for them. I believe part of our solution was using the right NLM.
Mike Slack
At 15 APR 1999 01:30PM Maggie Woo wrote:
I noticed this same effect (not on all Windows 95 workstations, but just the ones that had been upgraded from Windows 3.1). We resolved it by deleting the file c:\windows\_default.sfx. The Windows 95 resource book states that this file is just from Windows 3.1 and that Windows 95 doesn't need it. However, for some reason, if this file exists, windows 95 will use its attributes as the default for any DOS window–and these attributes include "always suspend"–if you get rid of this file, then the actual shortcut attributes will apply instead.
Good luck!
Maggie Woo
mwoo@tnc.org