Xref: utzoo comp.unix.sysv386:4240 comp.unix.msdos:305
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!uakari.primate.wisc.edu!crdgw1!sixhub!davidsen
From: davidsen@sixhub.UUCP (Wm E. Davidsen Jr)
Newsgroups: comp.unix.sysv386,comp.unix.msdos
Subject: Re: Problems running Windows 3.0 under Merge/386
Message-ID: <2952@sixhub.UUCP>
Date: 23 Jan 91 04:17:14 GMT
References: <0XV4V2w164w@mudos.ann-arbor.mi.us>
Reply-To: davidsen@sixhub.UUCP (bill davidsen)
Followup-To: comp.unix.sysv386
Organization: *IX Public Access UNIX, Schenectady NY
Lines: 19

In article <0XV4V2w164w@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:

| Has anybody installed Windows 3.0 under Merge/386?  How'd you do it?
| Is this even possible?  SCO, are you listening?

  There's a something call which windows is documented to use to
determine the CPU type. Sorry if I can't remember the details, I can
remember who to ask tomorrow. At any rate, MSoft documented this method,
but then used something else in W3 instead. The call works in VPIX, I
believe in merge, too, but it's not used.

  There is supposed to be a patch which makes this all work anyway. I'll
ask tomorrow for the details, I overhead this whole thing going on as a
discussion over lunch or somewhere.
-- 
bill davidsen - davidsen@sixhub.uucp (uunet!crdgw1!sixhub!davidsen)
    sysop *IX BBS and Public Access UNIX
    moderator of comp.binaries.ibm.pc and 80386 mailing list
"Stupidity, like virtue, is its own reward" -me