Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Dual-Boot Win95, Windows 3.1

46 views
Skip to first unread message

Chris Bacon

unread,
May 19, 1995, 3:00:00 AM5/19/95
to

I haven't been able to boot into DOS 6.22 / Windows 3.1. Any help
would be appreciated.

1. I have a 486/50 with 8 megs of RAM, a Stacker 4.0
compressed hard disk, and a "regular" external drive.
Running MS-DOS 6.22 and Windows 3.1.

2. Tried installing Win95, but it wanted more space on
the uncompressed Stacker partition. Reconfigured
Stacker to increase the space, but it still didn't
work, so I removed Stacker.

3. Installed Win95 successfully into a new, separate
sub-directory, "WIN95", of course.

4. Made sure that MultiBoot=1.

5. Hit "F8" after "Starting Windows" message. Selected
#7, "Start previous MS-DOS", but it then just
brought up Win95.

6. Checked that my old AUTOEXEC.BAT and CONFIG.SYS are
now AUTOEXEC.DOS and CONFIG.DOS; they are.

Any clues? Hints? Advice?
Thanks in advance.

Lannie Schafroth

unread,
May 19, 1995, 3:00:00 AM5/19/95
to
In article <3pihrs$d...@worm.hooked.net>, cba...@worm.hooked.net says...

>
>
>
>5. Hit "F8" after "Starting Windows" message. Selected
> #7, "Start previous MS-DOS", but it then just
> brought up Win95.
>
>6. Checked that my old AUTOEXEC.BAT and CONFIG.SYS are
> now AUTOEXEC.DOS and CONFIG.DOS; they are.
>
>Any clues? Hints? Advice?
>Thanks in advance.

You need to press F4 on bootup. This will allow WIN95 to be bypassed
and load your regular DOS/Windows setup. When you are in WIN95, the
config files will be CONFIG.DOS and AUTOEXEC.DOS. When you are in
DOS/Windows they will be normal.

--

Lannie Schafroth

Pathworks Network Administrator Iowa Network Services, Inc.
Voice: 515 830-0443 4201 Corporate Drive
Fax: 515 830-0123 West Des Moines, IA 50266
Email: Lan...@ins.netins.net
Any statements herein are my own opinion and not that of my employer.


Chris Bacon

unread,
May 23, 1995, 3:00:00 AM5/23/95
to
I tried hitting F4 after the "Starting Windows" message, but got the same
results, it still started up Win95. Thanks, though.

Perry Reed

unread,
May 24, 1995, 3:00:00 AM5/24/95
to
In article <3pt0q4$c...@also.hooked.net>, cba...@also.hooked.net (Chris Bacon) writes:
> I tried hitting F4 after the "Starting Windows" message, but got the same
> results, it still started up Win95. Thanks, though.

If you installed Win95 directly over Win3.1, I believe you cannot dual boot.
Some of your old DOS files will have been deleted. In order to dual boot,
you MUST install Win95 into a new directory (of course, you'll then have to
re-install most of your software...)

>
> In comp.os.ms-windows.setup Lan...@ins.netins.net (Lannie Schafroth) said:
>
> >
> >You need to press F4 on bootup. This will allow WIN95 to be bypassed and
> load
> >your regular DOS/Windows setup. When you are in WIN95, the config files
> will
> >be CONFIG.DOS and AUTOEXEC.DOS. When you are in DOS/Windows they will be
>
> >normal.
> >
> >

--
----------------------------------------------------------------------------
___ ___ _
| _ \___ _ _ _ _ _ _ | _ \___ ___ __| | Perry Reed
| _/ -_) '_| '_| || | | / -_) -_) _` | re...@corp.hp.com
|_| \___|_| |_| \_, | |_|_\___\___\__,_| Hewlett Packard Co. - PGIS
|__/

Adam Peller

unread,
May 24, 1995, 3:00:00 AM5/24/95
to
I have dual boot working just fine on my machine (along with
LILO on my MBR), but I'd like to know how to configure it
so that, let's say Windows 3.1 comes up by default.

Did Mucrosoft provide any documentation on this feature?
Someone mentioned a while ago that there might be some
information in the April Windows Sources, but I can't find
it anywhere.

I know there's a file called msdos.sys that looks like a
.ini file. Does anyone know the settings?

-Adam

Bob Schuchman

unread,
May 25, 1995, 3:00:00 AM5/25/95
to
pel...@aloha.cc.columbia.edu (Adam Peller) wrote:
>I have dual boot working just fine on my machine (along with
>LILO on my MBR), but I'd like to know how to configure it
>so that, let's say Windows 3.1 comes up by default.
>
>Did Mucrosoft provide any documentation on this feature?
>Someone mentioned a while ago that there might be some
>information in the April Windows Sources, but I can't find
>it anywhere.
>
>I know there's a file called msdos.sys that looks like a
>..ini file. Does anyone know the settings?
>
>-Adam
>
>
the following is a fragment of MSDOS.SYS, as known when in WIN95
otherwise known as MSDOS.W40 when in DOS or WIN 3.X:

[Options]
BootMulti=1 ; provides multi boot
BootMenu=1 ; gives a menu to choose from
BootMenuDefault=8 ; defaults to item 8, my old MS-DOS 6.22
BootMenuDelay=5 ; gives me 5 seconds to press 1 and go to WIN95 instead

Bob


Kevin Davis

unread,
May 30, 1995, 3:00:00 AM5/30/95
to
In article <3qdnvt$8...@freeside.cls.de>,
wi...@freeside.cls.de (Wiljo Heinen) wrote:

>re...@pa.itc.hp.com (Perry Reed) writes:
>
>>In article <3pt0q4$c...@also.hooked.net>, cba...@also.hooked.net (Chris
Bacon) writes:
>>> I tried hitting F4 after the "Starting Windows" message, but got
the same
>>> results, it still started up Win95. Thanks, though.
>
>>If you installed Win95 directly over Win3.1, I believe you cannot dual
boot.
>>Some of your old DOS files will have been deleted. In order to dual
boot,
>>you MUST install Win95 into a new directory (of course, you'll then
have to
>>re-install most of your software...)
>
>Well... if you install over an old system, Win95 will delete quite a
few
>of your DOS files, but you can still dual boot.

My question is if you do a clean install to a new directory, can it be
on the same drive as your old MSDOS/Windows, or if it is on the same
drive (logical or physical) will it still delete/write over some of your
old files?

When I get Win95 I would like to install it clean into a new directory
on drive c: (which is where my MSDOS/Windows is now) without it messing
up my old DOS/Win. Is this how it works?

If it is possible to do it this way then Win95 must have a totally
different/differently named command interpreter and system files from
command.com, io.sys, and msdos.sys, right?


|---------------------------------------------------------------------|
| Golf Tip: Don't pick up a lost ball until it stops rolling |
|---------------------------------------------------------------------|
| Kevin Davis "Hoser" | Standard Disclaimer |
| | 1. aq...@yfn.ysu.edu |
| | 2. da...@patrick-pims.af.mil |
|---------------------------------------------------------------------|

Wiljo Heinen

unread,
May 30, 1995, 3:00:00 AM5/30/95
to
re...@pa.itc.hp.com (Perry Reed) writes:

>In article <3pt0q4$c...@also.hooked.net>, cba...@also.hooked.net (Chris Bacon) writes:
>> I tried hitting F4 after the "Starting Windows" message, but got the same
>> results, it still started up Win95. Thanks, though.

>If you installed Win95 directly over Win3.1, I believe you cannot dual boot.
>Some of your old DOS files will have been deleted. In order to dual boot,
>you MUST install Win95 into a new directory (of course, you'll then have to
>re-install most of your software...)

Well... if you install over an old system, Win95 will delete quite a few

of your DOS files, but you can still dual boot. This
is from

WINDOWS 95
FINAL BETA RELEASE NOTES

[look for readme.txt in your \windows directory]

[in it it says:]

GENERAL
=======
Dual booting using F4 is now turned on by default only if you install to
a clean directory. If you install to a clean directory, Setup will add
BootMulti=1 to the [options] section of your MSDOS.SYS file (hidden text
file in the root of your boot drive).

[... and further on...]

Previous MS-DOS Files
---------------------
If you upgrade over a previous version of Windows 3.x, Setup will
delete a number of files from your old MS-DOS directory to free
up disk space and remove utilities that have been replaced by
the Windows 95 versions in the Windows and Windows\Command folders.

The following files will be deleted from the old MS-DOS directory:
ansi.sys
attrib.exe
chkdsk.exe
choice.com
country.sys
debug.exe
defrag.exe
deltree.exe
diskcopy.com
display.sys
doskey.com
drvspace.bin
dblspace.bin
drvspace.exe
dblspace.exe
drvspace.sys
dblspace.sys
edit.com
edit.hlp
ega.cpi
fc.exe
fdisk.exe
find.exe
format.com
keyb.com
keyboard.sys
label.exe
mem.exe
mode.com
more.com
move.exe
mscdex.exe
nlsfunc.exe
scandisk.exe
scandisk.ini
share.exe
sort.exe
start.exe
subst.exe
sys.com
xcopy.exe
emm386.exe
help.com
help.hlp
msd.exe
networks.txt
os2.txt
ramdrive.sys
readme.txt
setver.exe
smartdrv.exe


Regards

Wiljo
--
commercial link systems, Wiljo Heinen WWW: http://www.cls.net/
Lise-Meitner-Str. 1-7 Internet Dienste
24223 Raisdorf BANZAI! ISDN

Wiljo Heinen

unread,
Jun 1, 1995, 3:00:00 AM6/1/95
to
aq...@yfn.ysu.edu (Kevin Davis) writes:

[...]

>When I get Win95 I would like to install it clean into a new directory
>on drive c: (which is where my MSDOS/Windows is now) without it messing
>up my old DOS/Win. Is this how it works?

Yes.

>If it is possible to do it this way then Win95 must have a totally
>different/differently named command interpreter and system files from
>command.com, io.sys, and msdos.sys, right?

And yes.

Stephen C. Smith

unread,
Jun 1, 1995, 3:00:00 AM6/1/95
to
wi...@freeside.cls.de (Wiljo Heinen) wrote:

>Well... if you install over an old system, Win95 will delete quite a few
>of your DOS files, but you can still dual boot.

Wrong! Read your own quoted text.

>This
>is from

> WINDOWS 95
> FINAL BETA RELEASE NOTES

>[look for readme.txt in your \windows directory]

>[in it it says:]

>GENERAL
>=======
>Dual booting using F4 is now turned on by default only if you install to
>a clean directory. If you install to a clean directory, Setup will add
>BootMulti=1 to the [options] section of your MSDOS.SYS file (hidden text
>file in the root of your boot drive).

The above states *if you install to a clean directory* (not on top of
an existing Windows directory), that this is true. I can verify that
this is NOT true if you install to c:\windows, even if you manually
add "BootMulti=1" to MSDOS.SYS. Any F4 keypress is ignored at
startup.


Steve
smi...@biocom1.bioc.uab.edu


M P Davison

unread,
Jun 2, 1995, 3:00:00 AM6/2/95
to


Strange - I installed over my previous installation of Windows, manually edited
MSDOS.SYS and now it mulit-boots fine (including the F4 to the old version of DOS)

True some of the DOS commands had been deleted (replaced by newer protected mode
versions in \windows\command) but after I manually re-installed the old DOS commands
I still wanted emm386, mem, xcopy etc etc everything works fine.

Maybe you should check your setup ;)

Mark


---
--
Mark Davison,
Department of Electronic and Electrical Engineering,
The University of Leeds, Leeds, LS2 9JT, United Kingdom

E-mail:een...@leeds.ac.uk
Tel: Int+ 44 (0)113 2332016 Fax: Int+ 44 (0)113 2332032
WWW Home-page: http://www.elec-eng.leeds.ac.uk/mpd/M.P.Davison.html
--

Nigel Samuel

unread,
Jun 6, 1995, 3:00:00 AM6/6/95
to
In comp.os.ms-windows.setup een...@sun.leeds.ac.uk (M P Davison) said:
dido the dual boot works fine for me also. I manually updated the msdos.sys
file and it works fine.

--
Nigel Samuel
nsa...@pipeline.com
The search for the perfect game never ends!

0 new messages