nelson@sgi.com (Nelson Bolyard) (11/16/90)
In article <1990Nov14.051545.21285@odin.corp.sgi.com> I wrote that I had a
problem with my serial mouse (on COM2) not working at all well after I ran
a full screen application and then went back into windows, either by
exiting the application, or by typing ALT-ENTER. The problem would occur
with ANY full screen application; just firing up the DOS COMMAND prompt and
typing exit immediately would cause it.
I only got one e-mail reply 8-( from someone who said that he'd had the same
problem and had fixed it by running the MOUSE.COM program before firing up
windows. I tried that and it worked, but it bugged me. I was SURE that I
had read in the Windows manual that you should remove all mouse drivers and
TSRs, so I went into the manual and looked for those instructions. When I
found those instructions, explicitly telling me to get rid of MOUSE.SYS from
my CONFIG.SYS and MOUSE.COM from AUTOEXEC.BAT, I discovered on the same page
a note that if running DOS 3.3, I should add a line to my config.sys that
reads: STACKS=0,0
I was surprised that the Windows INSTALL program had not done that for me.
It had certainly made lots of other changes to my CONFIG.SYS file.
So I added the STACKS line to my CONFIG.SYS, and re-booted. Then I tried
Windows again, without loading MOUSE.COM or MOUSE.SYS.
Voila' The problem was gone!
Now, if I could just get a non-Windows EGA graphics program to run in a
window (instead of full screen) I'd be a happy camper. I think the problem
is that EGA 16 color modes are fundamentally incompatible with VGA 256
color modes, and Windows either doesn't give the EGA program its own
virtual memory to use for graphics space, or Windows doesn't know how to
translate the EGA virtual memory into VGA 256 color graphics. When I try
it, the EGA graphics in the window appear to have been matrix transformed.
I see the graphic image in black and white on the left side of the window,
and lots of bars of colors on the right side of the window. Sigh.
-----------------------------------------------------------------------------
Nelson Bolyard nelson@sgi.COM {decwrl,sun}!sgi!whizzer!nelson
Disclaimer: Views expressed herein do not represent the views of my employer.
-----------------------------------------------------------------------------leoh@hardy.hdw.csd.harris.com (Leo Hinds) (11/16/90)
In article <1990Nov15.192401.17396@odin.corp.sgi.com> nelson@sgi.com (Nelson Bolyard) writes: > I discovered on the same page >a note that if running DOS 3.3, I should add a line to my config.sys that >reads: STACKS=0,0 I have been plagued with this for a while ... and was starting to get VERY annoyed ... I tried what you said ... MAGIC ... it's amazing what can happen if one reads RTFM (which I obviously did not do :-) ) ... thanks for reading it for me. leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr
leoh@hardy.hdw.csd.harris.com (Leo Hinds) (11/16/90)
In article <1540@travis.csd.harris.com> I wrote ... >I have been plagued with this for a while ... and was starting to get VERY >annoyed ... I tried what you said ... MAGIC ... it's amazing what can happen >if one reads RTFM (which I obviously did not do :-) ) ... thanks for reading >it for me. Well, looks like I will have to take all that back ... I (cockpit error :-) ) tried to run pc-nfs' telnet from the windowed command.com ... I was "thrown out" of windows and was forced to power re-boot ... not it's back to the same troubles ... ARGHHH !!! leoh@hdw.csd.harris.com Leo Hinds (305)973-5229 Gfx ... gfx ... :-) whfg orpnhfr V "ebg"grq zl fvtangher svyr lbh guvax V nz n creireg ?!!!!!!? ... znlor arkg gvzr
bryan@intvax.UUCP (Jon R Bryan) (11/17/90)
From article <1543@travis.csd.harris.com>, by leoh@hardy.hdw.csd.harris.com (Leo Hinds): > tried to run pc-nfs' telnet from the windowed command.com ... I was "thrown > out" of windows and was forced to power re-boot ... not it's back to the same > troubles ... ARGHHH !!! > Frankly, I am amazed that you can get the PC-NFS telnet to run at all from Windows. My experience was that it is _exceedingly_ ill-behaved on anything other than a plain vanilla DOS setup. I switched to the Beame & Whiteside implementation and have been much, much happier. -- Jon R. Bryan <=> bryan@intvax.UUCP Sandia National Laboratories Intelligent Machine Principles Division Albuquerque, New Mexico