ed@qtc.UUCP (03/11/87)
What a mess...I've had nothing but problems finding a good combination
of EGA cards which will work with codeview correctly to include the mouse.
It seems that most of the EGA clones uses parts from CHIPS. I've had
some no-name brand that would not work at all (blank the screen stuff).
I recieved a series of patches from Microsoft which did not work on
this EGA card. I took the card back (fortunately) and now have a
EGA card from Ahead Systems (American made, right...) Codeview now works
only if the mouse is not enabled. Codeview worked great other than that.
Microsoft windows in EGA mode worked great, including the mouse.
It may be possible that the EGA firmware has problems. This particular
EGA card does autoswitching to EGA/CGA/MA/Hercules,...I tried disabling
the autoswitching but still had problems. I tried both the Microsoft
Bus and Serial mouse(s). Now I'm not sure if I can get my money back or what.
A friend of mine has a Quadram EGA w/NEC Multisync montitor and
Codeview did run, amazing. I'm hoping that I can get my card fixed
or replaced with something else. I tried running Kings Quest I on
my friends machine and it just blanked the screen, Running Kings Quest II
runs fine. On my machine, Kings Quest I blanks the screen too and
Kings Quest II only shows half the screen.
I guess the bottom line is that Kings Quest I/II/III and codeview with the
mouse are good tests for true compatibility if there's such a thing.
Does anyone else have better luck than I?
+------------------------------------------------------------+
| Ed Lisle | ogcvax! |
| Quantitative Technology Corporation | verdix! qtc!ed |
| Beaverton, OR (503) 626-3081 | sequent! |
+------------------------------------------------------------+lotto@wjh12.UUCP (03/12/87)
Keywords: > (summary) cannot get Microsoft CodeView to work with Microsoft mice > and second party EGA cards... Well, I am using IBM's EGA card and Mouse Systems optical mouse (with updated drivers) and the thing works fine. Perhaps the problem is not the EGA card, but compat. between the two Microsoft products (mouse and swre)? I have seen problems with EGA cards in machines with Microsoft mice too often (Word/Codeview bugs with IBM or clone EGA cards when a Microsoft mouse is present that go away when the mouse goes away). Some number of software revisions have been made since and I have not kept up with them.
perkins@bnrmtv.UUCP (03/13/87)
The story as I understand it is that MicroSoft tries to code around
some "interesting features" (read bugs) in IBM's EGA BIOS. As a
consequence, they get bizarre behavior on those cards which don't
have the same bugs. MicroSoft in general has a very weird view of
the PC world: they sell MS-DOS to OEMs of all sorts of machines,
but their applications programs expect True Blue hardware. (Example:
MicroSoft Word looks for "IBM" in the right location in the EGA BIOS
to determine if you're using an EGA card.)
--
{hplabs,amdahl,3comvax}!bnrmtv!perkins --Henry Perkins
It is better never to have been born. But who among us has such luck?
One in a million, perhaps.zarifes@bnrmtv.UUCP (03/14/87)
> What a mess...I've had nothing but problems finding a good combination > of EGA cards which will work with codeview correctly to include the mouse. > > Does anyone else have better luck than I? I have a Paradise Autoswitch EGA Card running on a Fountain 286-AT clone. Codeview would only work properly in 43 line mode. In 25 line mode the now-classic garish display would come up (magenta on yellow I beleive) and the display would blank completely at the first keystroke. The mouse appeared to work, the Paradise only had display problems (actually, Codeview has the problems!). After obtaining a free patch from Microsoft, Codeview works perfectly, including the mouse. You are, of course, using the new mouse.sys included with MSC 4.0 right? -- {hplabs,amdahl,3comvax}!bnrmtv!zarifes --Ken Zarifes
cramer@kontron.UUCP (03/14/87)
> What a mess...I've had nothing but problems finding a good combination > of EGA cards which will work with codeview correctly to include the mouse. > It seems that most of the EGA clones uses parts from CHIPS. I've had > some no-name brand that would not work at all (blank the screen stuff). > I recieved a series of patches from Microsoft which did not work on > this EGA card. I took the card back (fortunately) and now have a > EGA card from Ahead Systems (American made, right...) Codeview now works > only if the mouse is not enabled. Codeview worked great other than that. > Microsoft windows in EGA mode worked great, including the mouse. > It may be possible that the EGA firmware has problems. This particular > EGA card does autoswitching to EGA/CGA/MA/Hercules,...I tried disabling > the autoswitching but still had problems. I tried both the Microsoft > Bus and Serial mouse(s). Now I'm not sure if I can get my money back or what. > A friend of mine has a Quadram EGA w/NEC Multisync montitor and > Codeview did run, amazing. I'm hoping that I can get my card fixed > or replaced with something else. I tried running Kings Quest I on > my friends machine and it just blanked the screen, Running Kings Quest II > runs fine. On my machine, Kings Quest I blanks the screen too and > Kings Quest II only shows half the screen. > > I guess the bottom line is that Kings Quest I/II/III and codeview with the > mouse are good tests for true compatibility if there's such a thing. > > Does anyone else have better luck than I? Yes. The Everex The Enhancer EGA card (see my remarks a few days back) definitely works with Codeview V1.1 (just shipped by Microsoft to me after I complained that V1.0 didn't work with EGA and IBM Monochrome Display), and with the Logitech Mouse, which supposedly emulates a Microsoft Mouse. The Everex card uses the Chips & Technology chip set. Clayton E. Cramer