6 replies to this topic

[wendy]

The basis of this dos is the one at http://www.multiboot.ru/msdos8.htm and patch8.

There are three source sets, the boot diskette, the cab file, and the files created from patch8 under windows xp.

The boot diskette is largely upx-compressed, but version check is removed. Removing the version check is the plan for the full set.

The cab file is basically a mish of files from windows me, 98se, from dos 6.22, and a few other places. Some interesting utilities round this out.

The cab file is a mix of dos 5 files from Windows XP, a few dos 8 files from the diskette in diskcopy.dll, and some extra downloads. These are patched by a series of batch runs. The files used here come from inside core8.ima.

The help file in the cab is one of mine, released through mdgx's site.

The diskette files packed with upx are unpacked through upx dos version, and stored in the unpacked directory. Dosshell.exe is also upx'ed and is likewise treated.

Files are introduced into the final directory in the order

1. Files from the cab
2. Files from the cdrom
3. Files from the unpacked

command.com is extracted from the patch8 tape, to round the lot out.

edit,com and edit.hlp are replaced by msed.com and msed.ohp (my hex patches of edit)
fasthelp.exe and doshelp.txt (.hlp, renamed), become my doshelp.exe and doshelp.hlf

The result is then touched to date 2000.08.06 time 08.00.

We get, eg

[.]             [..]            ANSI.SYS        ATTRIB.EXE      AUTOEXEC.BAT

AUTOEXEC.HDD    BOOTICE.EXE     BOOTPREP.EXE    BOOTPREP.TXT    BOOTSECT.BAT

CDROM.SYS       CHKDSK.EXE      CHOICE.COM      COMMAND.COM     CONFIG.HDD

CONFIG.SYS      COUNTRY.SYS     CVTAREA.EXE     DBLBUFF.SYS     DEBUG.EXE

DELPART.EXE     DELTREE.EXE     DISKCOPY.COM    DISPLAY.SYS     dos710.com

doshelp.exe     DOSHELP.HLF     DOSKEY.COM      DOSSHELL.COM    DOSSHELL.EXE

DOSSHELL.HLP    DOSSHELL.INI    DOSSWAP.EXE     DOSTOWXP.COM    EGA.CPI

EGA2.CPI        EGA3.CPI        EXETYPE.EXE     EXETYPE.INI     EXT.EXE

EXTRACT.EXE     FC.EXE          FDISK.EXE       FIND.EXE        FORMAT.COM

HELP.COM        HELP.HLP        IFSHLP.SYS      INT19.COM       IO.SYS

ISO.CPI         ISO.TXT         JO.SYS          KEYB.COM        KEYBOARD.SYS

KEYBRD2.SYS     KEYBRD3.SYS     KEYBRD4.SYS     LABEL.EXE       MEM.EXE

MODE.COM        MORE.COM        MOUSE.COM       MOVE.EXE        MSCDEX.EXE

MSD.EXE         MSDOS.SYS       MSDOS8.INF      MSED.COM        MSED.OHP

NLSFUNC.SYS     OFORMAT.COM     PAGE.EXE        QBASIC.EXE      QBASIC.HLP

RAMDRIVE.SYS    READ.SCR        README.EXE      README.TXT      REBOOT.COM

REGDOS.EXE      SCANDISK.EXE    SCANDISK.INI    SETUP8.BAT      SETVER.EXE

SHARE.EXE       SKIPDSK.SYS     SORT.EXE        SUBST.EXE       SYS.COM

TREE.COM        VC.EXE          VC.INI          VESATEST.EXE    VESATEST.TXT

WINBOOT.HDD     WINBOOT.INI     XCOPY.EXE       XCOPY32.MOD

      3,406,425 bytes in 97 files and 2 dirs    3,645,440 bytes allocated

The files not from the original source are dos710.com. This sets dosver to 7.10 for the command on the argument line, eg dos710 fdisk etc.

Can we run Windows 3.11 under this? Supprisingly, yes.

We tried windoze 3,11 (which is vga), but this did not start. Even windows standard started, but progman also gpfed.

I used the ibmwindows tape (an unmodified OEM version), this had the ega mode, which did successfully start.

Here's windows file manager showing the root directory.



One sees firstly the date is 19;1. This is 2011 in the y2k form 19(x3B)1 where x3n is the digit n, x3A is : and x3B is ;. Otherwise, the file-manager.

[0ffer]

Windows 3.11 in enhanced mode?

[wendy]

Windows 3.11 in enhanced mode?

Windows in enhanced mode crashes before the GUI loads. The OS seems to load, though.



This is actually windows/standard mode, with an alternate prompt (copy \command.com krnl286.exe)

Windows crashes in enhanced mode, still.

[0ffer]

Windows in enhanced mode crashes before the GUI loads.
Windows crashes in enhanced mode, still.

Are you using IO.SYS from Patch8, size 130832 or 116736?
Last Patch8 include Win3xStart fix. I also run Word6 in standard mode from my Windows 3x Startup disk run Mini Windows 3.1based on mini.cab win98SE with KRNL386.EXE from it. I have no means of checking enhanced mode.

[wendy]

The pictures i took were with io 116736, which is what patch8 makes of IO.SYS from Windows XP sp3. This is the same set of files that live in the dos8 set i downloaded from multiboot.ru.

The io.sys 130832 + command.com 92992 were unable to start windows 3.10 in either standard or enhanced mode. When i replaced krnl286.exe and krnl386.exe with command.com ('92), Windows complained about an invalid command.com in standard mode, and an invalid xms driver in enhanced mode. Putting command.com 93040 in fixes this problem.

In general, i could run a very large number of apps from the standard mode of MiniWin, in vga (rather than ega mode). It ran nearly everything i through at it, including things like Praxim, tcmd, write. etc, You need to copy extra files into the setup, to make this happen, but in the main, (toolhelp, ole*.dll, ctl3dv2.dll), these just need to be there, no setup. I even got topdesk to load.

There's some comment about the miniwin setup in the Windows OAK on beta-archive, including utilities to mark files to run under this. I have not used these.



This is tcmd showing that it picks a number of resources from miniwin (the system menu is in russian). It is showing the dos version as 8.00.

One can feed extra files and things into Mini31 to make it start in enhanced mode. But the nest of Windows 9x and Mini31 seems to be causing more conflicts than say PC-DOS 7.1 and mini31.

Still, we are getting somewhere. I've worked through three or four bugs to get further with it. Win.com in the setup will run enhanced mode. typing win /? or win /3 shows this.

1. system.ini needs a [386Enh] section. I'm using a generic one at the moment.

2. winoa20.386 needs to be in the root directory of the boot device.

3. win386.exe needs to be present. This is the vxd library used by Windows. (it's the home of all of the *vxd files in system.ini [386Enh] section.

4. At the moment, we getting down to

Invalid VxD dynamic link call to device number 000A, service 0007.

Your Windows configuration is invalid.  Run the Windows Setup program

again to correct this problem. 

Still, we're getting somewhere.

[roytam1]

My Mini-Windows ( http://roy.hp2.jp/gp...mw16/mw16b2.zip ) runs well in 386 Enhanced mode in MS-DOS 7.1/PC-DOS 7.1, but not in MS-DOS 8.0 (IO.SYS = 130832 bytes).
I got "Error: Cannot install the 386 enhanced mode XMS driver."

[0ffer]

wendy & roytam1


Thank you very much for your answers