Dos95 and Windows 95 together

[os2fan2]

I am currently using DOS-LOGO.SYS (freedos),to load variations of LOGO.SYS

You can have multiple copies of doslogo.sys, but the corresponding bitmap has to be in the root directory.

Using a hex editor, replace the string \LOGO.SYS with some other name, eg LOGO.DOS, use different names for different files.

Put the LOGO files in the root directory

Make these modifications to the startup files.

This is part of the plan to see if i can fire up two different copies of Windows 9x from the same DOS menu. You could have Windows 95, Windows 98SE, and MS-DOS 7.1 startup screens, The DOS boot is fast, so you don't see it that long.

Code: Select all

-----MSDOS.SYS--------
bootgui=0
-----CONFIG.SYS-------

[Win95]
device=c:\fenster\winlogo.sys

[MSDOS]
device=c:\msdos7\doslogo.sys

------AUTOEXEC---------
goto %config%

:WIN95
cd c:\fenster
win

[computebrute]

Code: Select all

:WIN95
cd c:\fenster
win

It's funny how you (or someone else) named c:\fenster because "fenster" means window(s) in German.

[os2fan2]

Yes, I know this.

It's even funnier when you realise that 'defenestrate' means to kill someone by tossing them out the window (as the Czechs have done a few times). Defenestrating a computer means 'removing windows' for something more potent. (like OS/2).

Among the other names one has is 'legacy' as in 'this runs legacy software'. That's the second name.

But putting the OS early in the alphabet helps things like directory sorters do their job right.

[os2fan2]

I've updated the ms-dos version in Windows 95, to some commotion. Seems like Windows 95 only partly likes MS-DOS 7.1. Anyway, we fixed that. (vers 7.00 in autoexec.bat)

Still, the DOS path by default is c:\msdos7;c:\msdos7\command and the windows path is c:\fenster;c:\msdos7;c:\msdos7\command.

This turns out to be quite nice, because you can install the bulk of DOS in \msdos7\command, and anything you want to run in place of the default DOS runs in c:\msdos7.

Also, the winbootdir and windir entries are now different, and do different things. All fun and games.

Haven't got windows 3.1 to fire up yet.

[Battler]

- os2fan2: You need the IO.SYS patch to make Windows 3.x run. I forgot how it was called it but you need it and unless you apply it, IO.SYS will say you're attempting to run an unsupported version of Windows and halt the computer, requiring a reboot.

[os2fan2]

The patch goes by the name of start3x.

My msdos 7.10.2400 has this, and a number of other patches already built in.

In any case DOS 7.00.0950 runs it without the patch. I installed and ran Windows 3,1 from a DOS 7.0 session quite easily.

Windos itself needs a patch, and i might apply it to the binary tonight.

[Battler]

- os2fan2: Yes, 95's DOS can Windows 3.1 without the patch. OSR 2, however, already needs the patch.