Article View: comp.os.ms-windows.misc
Article #3447Re: Can't get Windows 3.1 to run
From: Dean Sadites
Date: Sat, 18 Mar 1995 17:59
Date: Sat, 18 Mar 1995 17:59
46 lines
3169 bytes
3169 bytes
There are several reasons why Windows might terminate immediately following the startup logo. This problem will occur if you try to use a video driver that is incompatible with your display adapter. However, if you're using the default VGA driver that ships with Windows, it is unlikely that the problem is video related (unless you have something other than a VGA card installed). I've also seen this occur if an EMM conflict exists. If 'DEVICE=C:\WINDOWS\EMM386.EXE' is present, try commenting it out (by placing a semi-colon or 'rem' in front of it). If this solves the problem, you may need to specify memory range exclusions on the EMM386 line in CONFIG.SYS that correspond to address space that might be needed by adapters installed in the computer. If this is the case, you may also need to add an 'EmmExclude=' line under the [386Enh] section of your SYSTEM.INI file. In some rare instances I've seen the problem you're experiencing occur on machines where the "/TESTMEM:OFF" specifier follows the DEVICE=HIMEM.SYS line in CONFIG.SYS. There are numerous other possibilities. If this doesn't help, let me know. dsadites@mcd.on.ca (Dean Sadites) --------------------------------------------------------------------- In article <Pine.SUN.3.91.950317122708.15936A-100000@solar.sky.net>, novmondo@solar.sky.net says... > >I just bought a used computer with Windows 3.1 on it. when I went to >start Windows up, I got the Windows logo, then it returned to the DOS >prompt. I've tried wiping it clean, then reinstalling it, with the same >result. I took the installation files, and installed Windows on another >machine, and it worked just fine. > >I've tried: >1) transferring the autoexec and config.sys files from the second machine > to the first. >2) transferring the .ini files from the second machine to the first. > >Nothing has helped, I still get just the logo, then thhe DOS prompt on >the first machine. Anyone have any ideas? Thanks! >
Technical Details
Message-ID:
<3kf71p$cll@mindy.mcd.on.ca>Path:
arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!pipex!bnr.co.uk!bcarh8ac.bnr.ca!bcarh189.bnr.ca!nott!torn!news.uunet.ca!uunet.ca!mcd.on.ca!usenetReferences:
<Pine.SUN.3.91.950317122708.15936A-100000@solar.sky.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 15eb16,8551aa6c7b471195 X-Google-Attributes: gid15eb16,public X-Google-Thread: 1102f1,8551aa6c7b471195 X-Google-Attributes: gid1102f1,public X-Google-Thread: 1076d4,8551aa6c7b471195 X-Google-Attributes: gid1076d4,public X-Google-Thread: fb485,8551aa6c7b471195 X-Google-Attributes: gidfb485,public X-Google-Thread: fe6f8,8551aa6c7b471195 X-Google-Attributes: gidfe6f8,public X-Google-ArrivalTime: 1995-03-18 10:25:33 PST Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!pipex!bnr.co.uk!bcarh8ac.bnr.ca!bcarh189.bnr.ca!nott!torn!news.uunet.ca!uunet.ca!mcd.on.ca!usenet From: dsadites@mcd.on.ca (Dean Sadites) Newsgroups: comp.os.ms-windows.misc,comp.os.ms-windows.setup,comp.windows.misc,fidonet.windows,bit.listserv.win3-1 Subject: Re: Can't get Windows 3.1 to run Date: 18 Mar 1995 17:59:21 GMT Organization: Mindemoya Computing, Sudbury, ON, 705-523-2109 (data) Lines: 49 Message-ID: <3kf71p$cll@mindy.mcd.on.ca> References: <Pine.SUN.3.91.950317122708.15936A-100000@solar.sky.net> NNTP-Posting-Host: ss-65.slip.mcd.on.ca Mime-Version: 1.0 X-Newsreader: WinVN 0.93.14