Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!bu.edu!att!att!occrsh!occrsh.ATT.COM!okcusr.UUCP!mjw From: mjw@okcusr.UUCP Newsgroups: comp.windows.ms Subject: Re: Enhansed 386 problems (DTK) Message-ID: <13300007@okcusr.UUCP> Date: 8 Nov 90 07:00:00 GMT Lines: 63 Nf-ID: #N:okcusr.UUCP:13300007:000:2709 Nf-From: okcusr.UUCP!mjw Nov 8 01:00:00 1990 /* Written 4:52 pm Oct 28, 1990 by mjw@okcusr.UUCP in okcusr.UUCP:comp.win.ms */ /* ---------- "WINDOWS 3.0 Enhanced Mode HANGUP " ---------- */ /* Written 4:43 pm Oct 28, 1990 by mjw@okcusr.UUCP in okcusr.UUCP:comp.win.ms */ ------ I am reposting this to prevent possible Orphaned Response. ------ /* Written 10:32 am Oct 22, 1990 by lopes@cogsci.ucsd.EDU in okcusr.UUCP:comp.win.ms */ In article <023%1&^@rpi.edu> curt@unix.cie.rpi.edu (Curt Signorino) writes: >>The DTK 386/33 I just purchased comes with its own DTK BIOS. >>Apparently, Windows 3.0 and the DTK BIOS conflict when Windows is run >>in 386-enh or standard modes. There is no problem when running >>Windows in real mode. I believe the problem (from the Windows side of >>it) lies in HIMEM.SYS. > What kind of PROBLEMS? > I own a DTK 386/33 running DTK BIOS and have no problems > running Windows in enhanced mode. I have had similar problems with the DTK 386/20 and the same BIOS. In running 386-enh mode, it would give a C> prompt at the top line of the Banner Page and hang up. I found out by reading the *.txt files that windows may have difficulty finding the VGA video ROM memory addresses. I found out that if using the STB VGA Extra boards, (perhaps others too), that the MS EMM Manager (HIMEM.SYS), failed to detect the STB ROM at locations C000-C5FF. In conclusion, if you have problems with this VGA card in your system, install the following command in your windows system.ini file: Find [386Enh] in the file and type below it; EMMEXCLUDE=C000-C5FF This should be edited before entering windows if possible. Start up windows in enhanced mode (win /3) and see if it works. If so, run windows (win) again. It should now work properly. Incidentally, if it runs too slow, don't forget to create a SWAP file. Instructions are in the *.txt files in C:\WINDOWS. ______________________________________________________________________________ "If you can't get ahead, then you're bringing up the rear" ______ ___ ___ /| /| ( // (_ | /| // Mike Wood - NAOC307670 //| //| \__//_// | //| // AT&T Switching Systems _ // | // | _ ____//__ | // | // Oklahoma City Works ( |// |// | / ( // | // | // Human Resources IM&M \// // |/ o \_// o |// |// o att!mwood!mjw attmail!mjw att!mwood!okcusr!mjw MEMBER $USR/OKC, Charter of $USR/Tulsa , D.P.M.A ______________________________________________________________________________ /* End of text from okcusr.UUCP:comp.win.ms */ /* End of text from okcusr.UUCP:comp.win.ms */