T.R | Title | User | Personal Name | Date | Lines |
---|
2857.1 | Me too! | BSS::PROCTOR_R | Sniffing the floral arrangement | Wed Mar 19 1997 15:54 | 4 |
| I have the exact same config and the exact same problem... The only fix
seems to be to start the DOS window in full screen mode, and [alt]
[return] to go to a DOS window.
FWIW.
|
2857.2 | alt-enter twice is a work-around | dhcp-client-13.mro.dec.com::levine | Randy Levine | Thu Mar 20 1997 08:40 | 9 |
| I discovered last night that what .-1 suggests does provide a work-around:
alt-enter to get to full-screen DOS then alt-enter to return to windows
restores the display properly.
I still don't know what's causing the original problem. It's an interesting
way to find out when your machine is executing in DOS mode, though. Some
things you expect (e.g., unpacking a self-extracting archive), and others you
don't (e.g., logging in to DIGITAL1, which executes a DOS script on your
machine locally).
|
2857.3 | Try adjusting MSDOS.PIF(LNK?) parameters | POBOXA::KEEFER | Craig PK03-1/R11, DTN:223-4902 | Thu Mar 20 1997 10:43 | 9 |
| >>> if I try to open a DOS window or run any DOS program
>>> the screen goes haywire.
I don't know if this will help, but if you alt-double-click on the MSDOS
Icon you can bring up the properties for the MSDOS Window. You can change
the mode, font, etc used by the MSDOS window. Perhaps, if you change one
or more of these parameters, you'll find a combination that will keep your
screen from going haywire.
|
2857.4 | try the correct driver? | ODIXIE::SIMPSONT | PC = world's biggest con job! | Thu Mar 20 1997 15:03 | 6 |
| Why aren't you using the driver for the video adapter that is in your
system? That might fix it...?
Regards,
Tom
|
2857.5 | A clue ? | WOTVAX::16.194.208.3::warder.reo.dec.com::sharkeya | Who am I now ? | Thu Mar 20 1997 15:14 | 5 |
| I had this with an Orchid Prodesigner IIs in 72Hz mode. When I used a II in
60Hz mode, it was fine
Alan
|