mf4f+@andrew.cmu.edu (Mark Fichman) (02/19/89)
I have the following problem. On a IBM PS/50, I am running desqview 2.2.
I run kermit and do a file transfer in window one, and run an editor (epsilon)
in window 2. While in window 2, the machine crashes, such that
I can type anything in, exit epsilon or desqview. The keyboard is essentially
locked. I have to turn off the machine (I can not Ctrl-Alt-Del reboot) and
turn it on. I get an error code
301
8602
error which is a keyboard error, I think. I then reboot and the system is
back to normal. This system crash is pretty reliable and
quite annoying. I got it, but far less frequently, I think, with Desqview
2.01. I have all the standard and appropriate settings on my windows (no
swapping communications out and so on) and have removed all TSR's to
minimize other problems. STill no luck.
Thanks for any help
Mark Fichman
Carnegie-Mellon Universitybarry@dgbt.uucp (Barry Mclarnon) (02/23/89)
From article <AXzSW4y00WB84XRF4h@andrew.cmu.edu>, by mf4f+@andrew.cmu.edu (Mark Fichman): > I have the following problem. On a IBM PS/50, I am running desqview 2.2. > I run kermit and do a file transfer in window one, and run an editor (epsilon) > in window 2. While in window 2, the machine crashes, such that > I can type anything in, exit epsilon or desqview. The keyboard is essentially > locked. I have to turn off the machine (I can not Ctrl-Alt-Del reboot) and > turn it on. I get an error code > > 301 > 8602 > > error which is a keyboard error, I think. I then reboot and the system is > back to normal. This system crash is pretty reliable and > quite annoying. I got it, but far less frequently, I think, with Desqview > 2.01. I have all the standard and appropriate settings on my windows (no > swapping communications out and so on) and have removed all TSR's to > minimize other problems. STill no luck. One possibility that occurs to me: go into the DESQview Setup program and see if you have "Optimize communications" turned on. If it is, try switching it off and then running your programs again (you may have to restart DV for the change to take effect). The "optimize comms" function rearranges the interrupt priorities so that the interrupts attached to the serial ports have higher priority than the others. I'm not sure about the PS/2, but in the XT and AT at least, this means that the serial port interrupts will now have higher priority than the system timer and keyboard interrupts, which could potentially cause some nasty side-effects. If this doesn't pan out, check some of the settings in the "Change program" menu for your programs. You can try such things as increasing the protection levels, increasing the window sizes, and checking that "Uses the serial ports" are set properly. Good luck! Barry -- Barry McLarnon Communications Research Center Ottawa, ON Canada UUCP: ...utzoo!bnr-vpa!bnr-rsc!dgbt!barry INTERNET: barry@dgbt.crc.dnd.ca Compu$erve: 71470,3651 Packet radio: VE3JF @ VE3JF