Name: arisoue Date: June 18, 2005 at 07:21:01 Pacific Subject: DOS 7.00 and Win 3.1 OS: Win 3.1 Greek + Calmira 3 CPU/Ram: 486/33 Mhz
Comment:
Hi, again! I wonder whether it is possible to load Windows 3.1 on top of DOS 7.00 (version sgipped with Windows 95a, e.g. ver. 4.00.950). I know there is a patch to use with DOS 7.10 (shipped with Windows 95 OSR2, e.g. ver 4.00.1111). What about DOS 7.00? Does there exist any similar patch? I am currently using old DOS 6.22, but would like to "jump" to DOS 7.xx.
No patch is needed, it will run as easily as in MS-DOS 6.22
MS-DOS 7.01 which underpins W95/95A is essentially MS-DOS 6.22 There are some differences (both in core and in external programs): * 1st- it will refuse to run on 286 or below * 2nd- You may have a logo that will be shown while booting * 3rd- All MS-DOS programs shipped with MS-DOS 7.01 (C:\Windows\Command) support LFN's, as long as the API is implemented (through DOSLFN or Win95) * 4th- MS-DOS Editor shipped with Win98 upwards can open up to 9 files at the same time. * 5th- I think it automatically tries to load/run (because DOS 7.10 does) HIMEM.SYS (extended memory), DBLBUF.SYS (Double buffering), SETVER.EXE (Compatiblity), IFSHLP.SYS (Instalable file systems) and WIN.COM (guess what... - this one I'm sure it tries) in the path specifies in the "WinDir" line in MSDOS.SYS. * 6th- It has a built in Start Menu (F8 while starting up) allowing to start Normal (if the WinDir setting is specifies, it will boot windows), Safe mode (ignores autoexec.bat and config.sys, Windows will boot, but, as /D:M command line switch is not recognized, it will boot normally), Command Line (windows will not start) and Safe mode command line (Ignores startup files and do not boot windows) * 7th- Direct disk access is disabled by default, to protect LFNs. LFN aware programs that use direct disk access automatically locks the disk. To allow LFN unaware software (ex.:win3.11 trying to create a permanent swap file) you'll have to lock it (see LOCK /?) * 8th- Better memory management: COMMAND.COM, BUFFERS, FILES, STACKS, FCBS, LASTDRIVE and part of the DOS Kernel will be automatically loaded in UMBs if they are present
My advice: * Install DOS 6.22 if it is not installed * Use a DOS 7 Bootdisk and replace the kernel (SYS A: C:) * Copy all MS-DOS programs shipped with Windows 95 over DOS 6 programs (most of them are in the %windir%\Command, but some, as SMARTDRV.EXE, are in the windows folder) * Install Windows 3.11 if not installed * Move C:\DOS folder so it will be something like C:\WINDOWS\COMMAND, changing all the references in AUTOEXEC.BAT, CONFIG.SYS and any other configuration file (like the program groups in DOSSHELL/WINDOWS) * Copy MSDOS.SYS from an working Win95/98 machine and modify the WinDir and WinBootDir to match Win3.11 directory * Replace/Copy the following files in the Windows directory with the Windows 95 ones (you probably copyed most of them to your MS-DOS folder): SMARTDRV.EXE, HIMEM.SYS, EMM386.EXE and DBLBUFF.SYS. * use "mem /c /p" after restarting to be sure DBLBUFF.SYS is being loaded. If so there is no need to load "SMARTDRV.EXE /DOUBLE_BUFFER", as DBLBUFF.SYS will provide this. * if you Windows is not Win for Workgroups you will probably want to copy IFSHLP.SYS to your Windows folder for a Win95 folder, so DOS won't complain while startign up * search the net for a beautiful logo. as you probably know, Windows logo is a 320x400 256 color bitmap so you can do one by yourself (animation is obtained through a hack in the pallete, but it is not needed) * you will probably want to remove win.com from autoexec.bat (if it is there) as it will be loaded automatically (if the option BootGUI is set to 1 in your MSDOS.sys) * you may want to add "ECHO Y|LOCK C: > NUL" to the end of your autoexec.bat (or before win.com) so it will auomatically enable direct disk access
...for stripping out MS-DOS 7.0x to use with Windows 3.x, IMHO it becomes a little pointless as the Windows 3.x Program Manager and File Manager are available as alternative interfaces for W95.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE