os2fan2

There are some things to note about UMBs on modern machines and Windows. 1. You should avoid using UMBs under Windows, since this slows it down somewhat. Have a look at UMBPCI on the web on this. 2. Modern machines use more UMBs then the average 486, so there's less for DOS. UMBPCI will find out what's available. I generally try to avoid WFW311, sticking with Win311. Still, i don't think there's a lot of changes.

Some of their utilities are neat. They have ctm, a console-mode task mamager, and the freedos command.com (cmd.exe) and edit.com (edit.exe) recompiled to Winnt. You can get things like the device manager and user manager to function without all that other MS legacy attached to it.

I had a look at the IBM thinkpad disks (which are basically recovery disks, but the process can be done from PE). The base copy of Windows is an unmodified source tape. The modifications come between the text-mode install and the gui. You install windows in some sort of other mode from PE., using the switches in winnt32 to point to the correct boot drive. Once the source is in place, you copy over files as needed (usually oembois.*), and then on the reboot, the install happens normally. Usually the OEM toys are added after the setup, which is why you don't find things like OEM bitmaps in Windows or DOS setups.

Compress v 1.02 and 1.11 will create KWAJ files. These date from 1990 (the WLO10.ZIP file for OS/2 is compressed in these). It's used in DOS 6, and Windows 3.11, it's hard to find. Vers 1.11 is the go, because the default rename is to edlin.ex_ rather than edlin.ex$. I got 1.02 from the fox pro 2.6 redistribution, and 1.11 in the msdos 6 source code package. Compress v2.0 is available in the Windows 3.1 SDK and many other things, that produce SZDD files. The compress in the Windows NT 3.10 reskit produces this file. Compress v2.5 in the resource kits, etc, by default, produce MSCF files (MSZIP), with varying degrees of compression. Look for CABPACK v 1.1 for a DOS version of this. Expand 2.1 (windows 3.11), expands both KWAJ and SZDD, but not MSCF. Other expand utilities work with some subset of SZDD, KWAJ and MSCF. The DIAMOND utility even in the earliest packages, are Win32. You could look for cabpack 1.1 for a DOS version. Needs to have the Runtime 200 fix applied, though.

Here are some things ye might like to try. CONFIG.SYS files=50 buffers=30 STACKS=9,256 device=c:\dos\himemx.exe /max=64512 /x REM device=c:\dos\emm386.exe noems i=b000-b7ff /verbose dos=high,umb,NOauto device=c:\dos\cdrom.sys /d:satadvd lastdrive=z You don't really need AUTO here, because you're loading stuff through config.sys Try UMBPCI, http://www.uwe-sieber.de/umbpci_e.html it gives UMB's (ie dos=umb), without loading EMM. AUTOEXEC.BAT @echo off path c:\dos;c:\windows set temp=c:\temp SET TMP=c:\temp PROMPT $p$g lh mscdex /d:satadvd /l:x REM lh ctmouse REM idle If you are just testing whether windows will load, try removing the mouse and idle. Add the line 'pageovercommit=1' to the 386Enh section of System.ini in your windows directory Try using vga driver or vga30 driver, to see if this cures problems. SYSTEM.INI [386Enh] ... PageOverCommit=1