os2fan2

It's not included. What is found there is msvbvm60.dll W

PC-DOS 7.00 B (aka 2000), is a variety of DOS 6.x (you could think of it as PC-DOS 6.7, for example. It does not support long file names, fat32, etc. OEM versions of MS-DOS 6.23 and PC-DOS 7.10 were made, that did support fat32, but not long file names. Neither of these are complete DOS versions, just a few basic files with Fat32 support hacked into it. The thing about running PC-DOS 7.1 under Windows 98, or PC-DOS 7.0 under 95 is that it has built-in support for an external rexx processor, and so the batch files are more useful than what raw windows command.com can provide.

I had a look at VCRedist.inf and the extracted files, against Win2k with a slipstreamed SP5. The only file required is "msvcp60.dll", which goes into %windir%\system32. W

The way DOS, Windows and OS/2 allocate letters, is that the active primary partitions are given the first sweep of letters, and that partitions in extended partitions are allocated letters thereafter. If you are using two hard disks, it is best to use this sort of setup. Disk 1: primary: c (probably fat, does not need to be big, eg 256k) extended: e windows copy 1 (xp needs about 4 GB), f: copy 2 (also 4.1 GB) (other active data should go somewhere on disk 1 Disk 2: primary: d (swap and temp stuff: say, eg 8 GB) extended other spare partitions, and one for resources and iso files. Setting the swap file somewhere distant from the OS drive, but on the same disk, eg hda1 = swap, hda5 = OS, will make the system much slower than if the page file is in between, or on the same disk, as the OS's. It would be better to have the OS's on 4G partitions, separated by the common swap file. W

You can run the PC-DOS 7,0 version of command.com under Windows 95. If you get hold of PC-DOS 7.1 (eg Ghost 8 disks), you can run its command,com under Windows 98. The reason for doing this is to access rexx batch scripts. None the same, neither of these command.com support long file names, so it is handy to keep the microsoft version around too.

You could, i suppose, take a leaf from vista: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons] ; Download drive [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons\E] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons\E\DefaultIcon] @="%Systemroot%\\system32\\shell32.dll,106" ; Windows drive (idea nicked from vista) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons\H] [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons\H\DefaultIcon] @="%Systemroot%\\system32\\shell32.dll,39" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons\R] ; Ram drive [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\DriveIcons\R\DefaultIcon] @="%Systemroot%\\system32\\shell32.dll,12"

One thing dandy to add for a service pack is the vc6 run-time files. This is one or two files (since most of them are already there). The vc6redist program (which places them in Win98/NT), does not work under 2k, and the files are already present under Windows xp. W

I thought i saw a bug, i did, i did. Here goes. Visual c 6.0 drops a number of run-time files, normally accessed via vr6redist.exe in NT4 / Win98. However this proggie does not run under windows 2000, more because the installer is prevented from doing so. If you dismantle the installer, and write a batch file, it runs like a treat. Since there is no clear way of installing vc6 runtime files into win2k, i decided to see what it takes to integrate the stuff into the base install. Since i noticed this first in sp5, i thought it was a bug there, but neither the base install sp0, nor sp4 have the necessary files either, so i conclude it is a distribution-bug. None the same it is a legitimate space to correct this in sp5. W

Don't worry, i am working on yet an other bug. Ok. W

You can do it from the command line, ie format /fs:NTFS /q w

I actually did the setup from Windows NT4 sp6. DOS was not involved. The sp is 5.0, not the later 5.1 Still, when i made these corrections, it worked like a dream. W

I slipstreamed SP5 into a Windows 2k SP0 (ie release). There were a number of files that caused the install to stop or pause with an error message. So i decided to fix this. dosnet.inf You need to include the file disk1 into this copy. This file is required to be in the $winnt$.~ls directory, so that Windows will find things. [Files] ;... d1,disk1 ;..... Txtsetup.sif There are five files that someone is attempting to put into the dllcache, however it does not work this way. You need to remove or comment any line that contains the string ",44" (ie comma, 4, 4) [SourceDisksFiles] dmdiag.exe = 1,,,,,,,3,0,0 dmdiag.exe = 1,,,,,,,44,0,0 <--- delete this line W

Windows NT, even from 3.1 days, tends to be larger because it is sheilding the hardware from the apps, and doing a lot more downstairs. For example, the IO.SYS file in Windows NT is 6 MB, and the corresponding config.sys is something like up to 24 MB.

Calmira 3.x does make it look like Windows 9x. Workplace Shell for Windows makes it look like OS/2. Oh well, it's a matter of putting VW stickers on your trabbie to look upmarket. W

Win2k uses "ProductId", not "ProductKey". You may need to look at the windows 2k version of unattend.doc, which is on the cdrom. I think the params keys have the params at the end, not at the beginning, but i never used this. If you are doing it through a bartpe install, then you have to grant everyone rights to the root directory, because XP changes the way the root directory works. This is for both the c: drive and the drive that windows is installed on.

You can try something like: http://nt4ref.zcm.com.au/patch.htm This is always a good site, since it lists all of the relevant patches for NT, including some of the server -> ws mods you can do. I use a batch file to install all of these patches, eg this hfix.cmd It goes into the root of the cdrom. Note i unpack the service pack, and a few other files (eg the server updates). If you are dual-booting, as long as you get SP6a back on before booting into Win2k or XP, all goes well. That is, install Windows NT and its service pack before booting into 2k/XP. You will need to copy the 2k/xp ntldr/ntdetect.com to get these OS's to boot properly. I have all of these files on the same cdrom as Windows NT, and i install a number of other junk also, eg hhupd140, wmi/nt, Adeptic aspi, IE5.0, etc. set hfix=\HOTFIX if exist %systemroot%\system32\qhain.exe goto :fix2 if exist %systemroot%\system32\aspichk.exe goto :fix1 :fix0 %hfix%\nt4sp6a\update\update.exe -q -z -n %hfix%\Q299444\hotfix.exe -q -z -n %hfix%\Packed\Q304158i.exe -q -z -n %hfix%\Q810833\hotfix.EXE -q -z -n %hfix%\q815021\hotfix.EXE -q -z -n %hfix%\Q817606\hotfix.EXE -q -z -n %hfix%\Packed\Q819696i.EXE -q -z -n %hfix%\Packed\Q841373I.exe -q -z -n :: these are server updates modified for workstation. %hfix%\Q873530\hotfix.exe -q -z -n %hfix%\Q891711\hotfix.exe -q -z -n :: redist files. %hfix%\REDIST1\tweakui.exe %hfix%\redist1\aspiinst.exe silent copy %hfix%\REDIST1\*.cpl %SystemRoot%\system32 copy %hfix%\redist1\ntsubst.exe %systemroot%\system32 copy %hfix%\redist1\oeminfo.ini %systemroot%\system32 copy %hfix%\redist1\oemlogo.ini %systemroot%\system32 copy %hfix%\REDIST1\aspichk.exe %systemroot%\system32\aspichk.exe %hfix%\IE50\ie5setup.exe /q /R:N :: qchain makes a full package %hfix%\REDIST1\qchain.exe %hfix%\redist1\reboot.exe set hfix= goto :end :fix1 :: needs SP6 installed %hfix%\redist2\wmi-nt4.exe /q %hfix%\redist2\instmsiw.exe /q %hfix%\redist2\msjava86.exe /q %hfix%\redist2\hhupd140.exe /q %hfix%\redist2\jet40-kb837001-ENU.EXE /q %hfix%\redist2\WM320920_64.EXE /q %hfix%\redist1\qchain.exe copy %hfix%\redist1\qchain.exe %systemroot%\system32 goto :end :fix2 :: this is a failsafe :end

You need something like this batch file @echo off set winsys= if exist %windir%\system\regsvr32.exe set winsys=%windir%\system if exist %windir%\system32\regsvr32.exe set winsys=%windir%\system32 if %winsys%=="" goto :end copy *.dll %winsys% %winsys%\regsvr32.exe %winsys%\zipfldr.dll set regfile=%temp%\zipfolder.reg echo REGEDIT4 > %regfile% echo [HKEY_LOCAL_MACHINE\Software\Microsoft\Plus!98\Setup\ZipFldr]>>%regfile% echo "Installed"="1">>%regfile% echo. >> %regfile% echo [HKEY_CLASSES_ROOT\CompressedFolder\DefaultIcon]>>%regfile% echo @="%winsys%\zipfldr.dll,0">>%regfile% echo. >> %regfile% regedit /s %regfile% set regfile= set winsys= :end This creates the file, and associates the correct icon with it, too.

Wish people would be more specific in the title of the topic. "Need Help" is not clear enough! W

You could look for unknowndevices. at http://www.halfdone.com/Development/UnknownDevices It should be able to identify the real name of the modem, and you could download (from somewhere), its drivers. W

Sad, really. Xenix was the last of the 8-bit Unixes. W

While you can install Windows NT4 after Windows 2k, you should not boot 2k until you install sp6a. There are some details on how you can add some SP6a files to 2k, to get past the 8G hard disk issue, this requires replacing the default NTLDR, NTDETECT.COM, ATAPI.SYS and a few other files. You can replace the SP6a NTLDR with a more recent version (eg Windows 2k or XP or 2k3), in SP6a. but not in NT4. Really, it is a commercial decision of microsoft not to issue either a sp7 or to do slipstreaming of the service pack. You can indeed run a scheduled batch to upgrade the guff. Try http://nt4ref.zcm.com.au/index.htm for some info. W

Windows NT3.x supports both HPFS and the NTFS. However you should format the partition in NTFS unless you are upgrading from OS/2. It will read older style HPFS (ie 2.x, 3.x, 4.0), not sure of the new style. There are various proggies around that will upgrade pinball.sys (the hpfs driver) for use under Windows nt and 2k. W

if i recall correctly, microsoft sold off xenix to someone else.

ntkrnlmp.exe, i guess. That's the one that the BartPE windows logon screen is hacked in.

Total Commander is compiled into separate Win16 and Win32 versions. The win16 stuff is still maintained.