Hi Guys
I am hoping the great gurus here can help me with a problem that I have just encountered.
I have just updated a couple of machines on a clients site from Win98 to Win2000 SP3 (or SP1).
I am having problems with these machines when I try to run any DOS Application (including AREV) in Full screen mode. In a windows is sloooow but works.
In the case of AREV, the program starts up and "runs" until it looks for some keyboard input and then freezes.
I have installed Tame (from www.tamedos.com) and activated the monitor which reports CPU utilisation by running DOS apps and it appears that it is NOT "Windows" or the machine that is locking up. It appears to be that the AREV application just "stops".
The machines use a MSI 6533E motherboard with a Celeron 1.7 CPU.
And I'c wondering whether its got something to do with the keyboard buffer interrupts - or something like that ??
Any suggestions would be greatly appreciated.
Thanks
Tony Lillyman
F1 Data Systems
I had something similar running AREV on Windows XP in full screen.
After it started it would work for a few moments, then appear to lock up. Running in a window it worked fine - although much slower.
However, after upgrading the video drivers (for a GeFore MX440) it now works normally in full screen mode.
Thanks Charles
I'll try to see if there is a later video driver.
Regards
Tony
Hi Tony,
When we first ran our app on win 2000 or XP we sometimes got lock ups after it had been sitting waiting for keyboard input for a while, whether in fill-screen mode or not.
Turned out to be because on startup in some circumstances we were issuing a pdisk command and if no printer was connected to the local machine, or NET use to redirct printer output was in place, it would lock up.
Disabling the automatic PDISK solved our apparent "keyboard lockup"
Cheers
Warren Kinny
Exodus Systems