Tryphon

I tried the very first official version 4.00.950 with 14 disks. I tried 4.00.4111 versions (one of them was OSR2.5, and for the other I do not know). I will try to reach OSR1 and OSR2. I found himemx.sys and I will try. For Win98 I never tried. But 486SLC2 is not a true 486 (no math coprocessor, I have it separately). Well I can try to see if it brings new clues. This address http://ipfs.io/ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco/wiki/Architecture_of_Windows_9x.html tells : vmm32 process seems to pass successfully according to my bootlog.txt (this is only my opinion, not necessarily the truth). The next step is the protected mode. Is it possible that this switch to protected mode failed at the beginning knowing that I got no error message and that Windows nt4 works fine. I just ask. What do you think?

Steps I did: Format partition Install of Windows 95 ver. 4.00.950 (14 disks) Compact installation (no optional tools/programs) I let a boot disk in A: I rebooted to boot from A: I edited system.ini to comment all the 386Enh section I saved \windows\system\vmm32.vxd and the folder vmm32 vxdlib -l vmm32.vxd VxDLIB v1.01 (c) Copyright Tenth Planet Software Intl., C Turvey 1995-1996 All rights reserved. Non-Commercial use only Listing vmm32.vxd vxds: VMM 1 total vxd(s) I deleted VPD.vxd and VCP.vxp in \windows\system\vmm32 folder I rebooted from C: = first w95 start I asked for a bootlog file The start process claimed for VPD.vxd and VCD.vxd (expected since I did not delete the matching entries in the registry) W95 froze Here the obtained bootlog.txt [00162C27] Loading Device = C:\WINDOWS\HIMEM.SYS [00162C29] LoadSuccess = C:\WINDOWS\HIMEM.SYS [00162C29] Loading Device = C:\WINDOWS\IFSHLP.SYS [00162C2A] LoadSuccess = C:\WINDOWS\IFSHLP.SYS [00162C2A] Loading Device = C:\WINDOWS\SETVER.EXE [00162C2A] LoadSuccess = C:\WINDOWS\SETVER.EXE [00162CC5] Loading Vxd = VMM [00162CC8] LoadSuccess = VMM [00162CC8] Loading Vxd = nwlink.vxd [00162CCA] LoadSuccess = nwlink.vxd [00162CCA] Loading Vxd = vnetsup.vxd [00162CCB] LoadSuccess = vnetsup.vxd [00162CCC] Loading Vxd = C:\WINDOWS\system\VMM32\CONFIGMG.VXD [00162CCE] LoadSuccess = C:\WINDOWS\system\VMM32\CONFIGMG.VXD [00162CCE] Loading Vxd = C:\WINDOWS\system\VMM32\VSHARE.VXD [00162CCF] LoadSuccess = C:\WINDOWS\system\VMM32\VSHARE.VXD [00162CCF] Loading Vxd = C:\WINDOWS\system\VMM32\VWIN32.VXD [00162CD0] LoadSuccess = C:\WINDOWS\system\VMM32\VWIN32.VXD [00162CD1] Loading Vxd = C:\WINDOWS\system\VMM32\VFBACKUP.VXD [00162CD1] LoadSuccess = C:\WINDOWS\system\VMM32\VFBACKUP.VXD [00162CD1] Loading Vxd = C:\WINDOWS\system\VMM32\VCOMM.VXD [00162CD2] LoadSuccess = C:\WINDOWS\system\VMM32\VCOMM.VXD [00162CD2] Loading Vxd = C:\WINDOWS\system\VMM32\COMBUFF.VXD [00162CD3] LoadSuccess = C:\WINDOWS\system\VMM32\COMBUFF.VXD [00162CD3] Loading Vxd = C:\WINDOWS\system\VMM32\IFSMGR.VXD [00162CD7] LoadSuccess = C:\WINDOWS\system\VMM32\IFSMGR.VXD [00162CD7] Loading Vxd = C:\WINDOWS\system\VMM32\IOS.VXD [00162CDA] LoadSuccess = C:\WINDOWS\system\VMM32\IOS.VXD [00162CDA] Loading Vxd = C:\WINDOWS\system\VMM32\SPOOLER.VXD [00162CDB] LoadSuccess = C:\WINDOWS\system\VMM32\SPOOLER.VXD [00162CDB] Loading Vxd = C:\WINDOWS\system\VMM32\VFAT.VXD [00162CDD] LoadSuccess = C:\WINDOWS\system\VMM32\VFAT.VXD [00162CDD] Loading Vxd = C:\WINDOWS\system\VMM32\VCACHE.VXD [00162CDE] LoadSuccess = C:\WINDOWS\system\VMM32\VCACHE.VXD [00162CDE] Loading Vxd = C:\WINDOWS\system\VMM32\VCOND.VXD [00162CDF] LoadSuccess = C:\WINDOWS\system\VMM32\VCOND.VXD [00162CE0] Loading Vxd = C:\WINDOWS\system\VMM32\VCDFSD.VXD [00162CE1] LoadSuccess = C:\WINDOWS\system\VMM32\VCDFSD.VXD [00162CE1] Loading Vxd = C:\WINDOWS\system\VMM32\VXDLDR.VXD [00162CE2] LoadSuccess = C:\WINDOWS\system\VMM32\VXDLDR.VXD [00162CE2] Loading Vxd = C:\WINDOWS\system\VMM32\VDEF.VXD [00162CE3] LoadSuccess = C:\WINDOWS\system\VMM32\VDEF.VXD [00162CE3] Loading Vxd = C:\WINDOWS\system\VMM32\VPICD.VXD [00162CE4] LoadSuccess = C:\WINDOWS\system\VMM32\VPICD.VXD [00162CE4] Loading Vxd = C:\WINDOWS\system\VMM32\VTD.VXD [00162CE5] LoadSuccess = C:\WINDOWS\system\VMM32\VTD.VXD [00162CE5] Loading Vxd = C:\WINDOWS\system\VMM32\REBOOT.VXD [00162CE6] LoadSuccess = C:\WINDOWS\system\VMM32\REBOOT.VXD [00162CE6] Loading Vxd = C:\WINDOWS\system\VMM32\VDMAD.VXD [00162CE7] LoadSuccess = C:\WINDOWS\system\VMM32\VDMAD.VXD [00162CE7] Loading Vxd = C:\WINDOWS\system\VMM32\VSD.VXD [00162CE7] LoadSuccess = C:\WINDOWS\system\VMM32\VSD.VXD [00162CE8] Loading Vxd = C:\WINDOWS\system\VMM32\V86MMGR.VXD [00162CE9] LoadSuccess = C:\WINDOWS\system\VMM32\V86MMGR.VXD [00162CEA] Loading Vxd = C:\WINDOWS\system\VMM32\PAGESWAP.VXD [00162CEA] LoadSuccess = C:\WINDOWS\system\VMM32\PAGESWAP.VXD [00162CEA] Loading Vxd = C:\WINDOWS\system\VMM32\DOSMGR.VXD [00162CEC] LoadSuccess = C:\WINDOWS\system\VMM32\DOSMGR.VXD [00162CEC] Loading Vxd = C:\WINDOWS\system\VMM32\VMPOLL.VXD [00162CED] LoadSuccess = C:\WINDOWS\system\VMM32\VMPOLL.VXD [00162CED] Loading Vxd = C:\WINDOWS\system\VMM32\SHELL.VXD [00162CEF] LoadSuccess = C:\WINDOWS\system\VMM32\SHELL.VXD [00162CEF] Loading Vxd = C:\WINDOWS\system\VMM32\PARITY.VXD [00162CF0] LoadSuccess = C:\WINDOWS\system\VMM32\PARITY.VXD [00162CF0] Loading Vxd = C:\WINDOWS\system\VMM32\BIOSXLAT.VXD [00162CF1] LoadSuccess = C:\WINDOWS\system\VMM32\BIOSXLAT.VXD [00162CF1] Loading Vxd = C:\WINDOWS\system\VMM32\VMCPD.VXD [00162CF1] LoadSuccess = C:\WINDOWS\system\VMM32\VMCPD.VXD [00162CF2] Loading Vxd = C:\WINDOWS\system\VMM32\VTDAPI.VXD [00162CF2] LoadSuccess = C:\WINDOWS\system\VMM32\VTDAPI.VXD [00162CF2] Loading Vxd = C:\WINDOWS\system\VMM32\PERF.VXD [00162CF3] LoadSuccess = C:\WINDOWS\system\VMM32\PERF.VXD [00162CF5] Loading Vxd = vredir.vxd [00162CF8] LoadSuccess = vredir.vxd [00162CF9] Loading Vxd = ndis.vxd [00162CFB] LoadSuccess = ndis.vxd [00162CFC] Loading Vxd = ndis2sup.vxd [00162CFC] LoadFailed = ndis2sup.vxd [00162CFD] Loading Vxd = vnetbios.vxd [00162CFE] LoadSuccess = vnetbios.vxd [00162D00] Loading Vxd = C:\WINDOWS\system\VMM32\DYNAPAGE.VXD [00162D01] LoadSuccess = C:\WINDOWS\system\VMM32\DYNAPAGE.VXD [00162D01] Loading Vxd = C:\WINDOWS\system\VMM32\VDD.VXD [00162D03] LoadSuccess = C:\WINDOWS\system\VMM32\VDD.VXD [00162D03] Loading Vxd = C:\WINDOWS\system\VMM32\VKD.VXD [00162D04] LoadSuccess = C:\WINDOWS\system\VMM32\VKD.VXD [00162D04] Loading Vxd = C:\WINDOWS\system\VMM32\EBIOS.VXD [00162D05] LoadSuccess = C:\WINDOWS\system\VMM32\EBIOS.VXD [00162D05] Loading Vxd = C:\WINDOWS\system\VMM32\INT13.VXD [00162D05] LoadSuccess = C:\WINDOWS\system\VMM32\INT13.VXD I noticed a surprise : EBIOS.vxd successfully loaded where other Windows 95 versions I tested failed to load it. I restarted in step by step mode and I got the same result except EBIOS.vxd failed. I found SoftIce 4.05. I nerver used it. But it can hurt my limited knowledge. I will see. I could try different combinations of a limited set of vxds but it can be crazy to manage. If it is valuable to understand, I will need a strategy to narrow the sets of vxds to try. Arrrgh, no more clue yet! Thank you.

Ok, back to my computers. Specially the desktop : I opened it... Arghhh, not exactly a 386 SX as sticked on the box, but a 486 Cyrix SLC2 (50MHz). Thank you to all for your replies. @dencorso None really done yet, but I am still curious to do this manipulation. @jaclaz I applied the Win95FIX (sucessfull installation) to versions 4.00.0950 (14 disks) and 4.00.1111. The vmm32 got the new vxd files. With 4.00.1111, the new vxd are loaded successfully (instead of the old one found in vmm32.vxd). Unfortunatly, bootlog.txt ended with VPP.vxd as before. With 4.00.0950, the bootlog process is weird : bootlog.prv and bootlog.txt never change whatever I do. They remains the same as they were printed the first time after w95 install (stuck at the first reboot). If I delete them, after a reboot, the w95 start process restore them identically. Anyway they are not exactly same as the one of version 4.00.1111. The link you provided IS my "bedside book" !! Surely I need to read it again and again to be sure I am not missing something. @mercury127 "then u can replece ur system vmm32.vxd to extracted vmm..vxd from ur distr, and place all other vxds from ur distr to system\vmm32 folder. after this, u can start windows with win /d:m command and look, which part make problems...." I did this manipulation (even before I posted here, but I did not report). All the vxd files printed in bootlog.txt were \windows\system\vmm32\whatever.vxd saying that all vxd were loaded from the vmm32 folder and not from vmm32.vxd. However, bootlog ends by \windows\system\vmm32\VPD.vxd (sucessfull load), hence the boot process brings no more information about any failing vxd. The computer has an inport bus for the mouse : https://en.wikipedia.org/wiki/Bus_mouse The mouse works well under MSDOS (with driver), Windows NT 4 and Windows 95 during the setup process. vflatd is loaded sucessfully but I cannot tell if my hardware really support it. Is my hardware healthy? I cannot be sure at 100%. Windows NT 4 works fine (no blue screen) with the network features. I changed the memory card locations (4 banks) : after w95 reinstallation, same story. I changed the memory cards by other: idem. Well, I am searching anything that could help to just understand ... Thank you.

I will do. This is interesting, I did not have this idea. But it will take a while because I need to dismount the laptop frame (not easy) to access its HDD. Thank you.

I have Win95 4.00.1111 in both 386SX computer (useful to understand what is not functional). This version seems to be OSR2. I never saw stability issue on my 386 SX laptop but this true, Win95 is quite slow. I can let it hours connected to my network where another computer can read/write its shared folders. Ok, on both 386 SX I have math coprocessor. Remember I tried floppy set of win95 (4.00.950) on my 386 SX Cyrix 50 with exactly the same freeze at the first start. I tried this a long time ago. But if required ... I can do another try.

Then I did this next try. Only these vxd were not loaded according to the vmm32files list : vflatd.vxd, vmouse.vxd and vmd.vxd One of them is the next Vxd. I created 3 vxd files renaming EBIOS.vxd to vflatd.vxd, vmouse.vxd and vmd.vxd. I put these dummy files in \windows\system\vmm32 (as it did for the dummy VPD.vxd I tested before). Hence Win95 boot process will ignore these vxd in vmm32.vxd and should attempt to load these ones in vmm32 folder instead. After a reboot, bootlog.txt said: ... [000D0362] Loading Vxd = VCD [000D0363] LoadSuccess = VCD [000D0363] Loading Vxd = VPD [000D0364] LoadSuccess = VPD The boot process did not even try to load the dummy vflatd.vxd, vmouse.vxd or vmd.vxd files. I checked the bootlog.txt file in my other 386SX laptop where win95 boots fine. vflatd.vxd and vmd.vxd are in the wmm32files list in the registry BUT there are not notified in the bootlog.txt file. Hence, it seems the boot process simply ignores them for a reason I do not know. Then I could conclude it is normal some vxd are ignored. Back to my 386SX Cyrix 50, vflatd.vxd, vmouse.vxd and vmd.vxd files seems to be ignored. Perhaps vmouse.vxd (not ignored in my laptop) could be the issue ... but replacing it by a dummy vmouse.vxd file did not cure anything. The mystery remains.

I tried also to disable LPT port in the bios. Win95 froze again at the same point.

@MrMateczko I know how to add a vxd to vmm32.vxd but I do not know if it is possible to delete a vxd from a basic vmm32.vxd file. However, I did the following. EBIOS.vxd is a driver not required by my system and it does not block the boot process when the load fails. I extracted it from a CAB and renamed it VPD.vxd. I put it in \windows\system\vmm32 folder where the drivers are loaded with priority against the same one in the vmm32.vxd file. Hence this dummy VPD.vxd will be loaded and not the one in the vmm32.vxd file. After rebooting, the bootlog.txt file is: ... [000D0362] Loading Vxd = VCD [000D0363] LoadSuccess = VCD [000D0363] Loading Vxd = VPD [000D0364] LoadFailed = VPD after this win95 froze without warning. @rloew All drivers in the [386enh] section were commented and win95 froze at the same point (after LoadSuccess of VPD) I do not know if vmm32.vxd did not finished to load. When something goes wrong I expect the last bootlog.txt line to be "Loading Vxd = SOMETHING", then we understand this vxd stops the start process. Win95 first start could be exactly between the vmm32.vxd end and the beginning of SYS CRITICAL INIT where I do not know what's happening. But how to check this hypothesis ?

Thank you for your question. Since my 386 SX laptop is running Win95 fine, I would say yes. I do not know if it can be generalized to all 386 SX computers.

Hello, My issue is in the title. First time I did a Win95 installation on a old hardware which is a 386SX 25 MHz with the upgrade Cyrix 386 to 486 50 MHz, 16 MB RAM (this config accepts fine Windows NT4 so hardware seems to be healthy). After a fresh install of win95 (tried A, B, C versions), the first start led to a freezing. No error message was displayed; never. This is the Bootlog.txt produced by the win95 first start process: [000D024E] Loading Device = C:\WINDOWS\COMMAND\DISPLAY.SYS [000D024F] LoadSuccess = C:\WINDOWS\COMMAND\DISPLAY.SYS [000D0250] Loading Device = C:\WINDOWS\HIMEM.SYS [000D0252] LoadSuccess = C:\WINDOWS\HIMEM.SYS [000D0252] Loading Device = C:\WINDOWS\IFSHLP.SYS [000D0252] LoadSuccess = C:\WINDOWS\IFSHLP.SYS [000D0253] Loading Device = C:\WINDOWS\SETVER.EXE [000D0253] LoadSuccess = C:\WINDOWS\SETVER.EXE [000D0296] C:\WINDOWS\COMMAND\MODE.COM(Logo disabled) [000D0296] starting [000D029A] C:\WINDOWS\COMMAND\MODE.COM[000D029A] starting [000D02DC] Loading Vxd = VMM [000D02EB] LoadSuccess = VMM [000D02EB] Loading Vxd = C:\WINDOWS\SMARTDRV.EXE [000D02EC] LoadSuccess = C:\WINDOWS\SMARTDRV.EXE [000D02ED] Loading Vxd = nwlink.vxd [000D02EF] LoadSuccess = nwlink.vxd [000D02F0] Loading Vxd = vnetsup.vxd [000D02F1] LoadSuccess = vnetsup.vxd [000D02F3] Loading Vxd = JAVASUP.VXD [000D02F3] LoadSuccess = JAVASUP.VXD [000D02F4] Loading Vxd = CONFIGMG [000D02FA] LoadSuccess = CONFIGMG [000D02FA] Loading Vxd = VSHARE [000D02FC] LoadSuccess = VSHARE [000D02FC] Loading Vxd = VWIN32 [000D02FE] LoadSuccess = VWIN32 [000D02FE] Loading Vxd = VFBACKUP [000D02FF] LoadSuccess = VFBACKUP [000D0300] Loading Vxd = VCOMM [000D0301] LoadSuccess = VCOMM [000D0301] Loading Vxd = COMBUFF [000D0302] LoadSuccess = COMBUFF [000D0302] Loading Vxd = C:\WINDOWS\system\VMM32\IFSMGR.VXD [000D0308] LoadSuccess = C:\WINDOWS\system\VMM32\IFSMGR.VXD [000D0309] Loading Vxd = C:\WINDOWS\system\VMM32\IOS.VXD [000D030C] LoadSuccess = C:\WINDOWS\system\VMM32\IOS.VXD [000D030C] Loading Vxd = SPOOLER [000D030E] LoadSuccess = SPOOLER [000D030E] Loading Vxd = VFAT [000D0313] LoadSuccess = VFAT [000D0313] Loading Vxd = VCACHE [000D0315] LoadSuccess = VCACHE [000D0315] Loading Vxd = VCOND [000D0317] LoadSuccess = VCOND [000D0317] Loading Vxd = VCDFSD [000D0318] LoadSuccess = VCDFSD [000D0318] Loading Vxd = VXDLDR [000D031A] LoadSuccess = VXDLDR [000D031A] Loading Vxd = VDEF [000D031B] LoadSuccess = VDEF [000D031B] Loading Vxd = VPICD [000D0325] LoadSuccess = VPICD [000D0326] Loading Vxd = VTD [000D0327] LoadSuccess = VTD [000D0327] Loading Vxd = REBOOT [000D0328] LoadSuccess = REBOOT [000D0328] Loading Vxd = VDMAD [000D0329] LoadSuccess = VDMAD [000D032A] Loading Vxd = VSD [000D032A] LoadSuccess = VSD [000D032A] Loading Vxd = V86MMGR [000D032E] LoadSuccess = V86MMGR [000D032E] Loading Vxd = PAGESWAP [000D032F] LoadSuccess = PAGESWAP [000D032F] Loading Vxd = DOSMGR [000D0333] LoadSuccess = DOSMGR [000D0333] Loading Vxd = VMPOLL [000D0334] LoadSuccess = VMPOLL [000D0334] Loading Vxd = SHELL [000D0337] LoadSuccess = SHELL [000D0337] Loading Vxd = PARITY [000D0337] LoadSuccess = PARITY [000D0338] Loading Vxd = BIOSXLAT [000D0338] LoadSuccess = BIOSXLAT [000D0338] Loading Vxd = VMCPD [000D0339] LoadSuccess = VMCPD [000D033A] Loading Vxd = VTDAPI [000D033A] LoadSuccess = VTDAPI [000D033A] Loading Vxd = PERF [000D033C] LoadSuccess = PERF [000D033E] Loading Vxd = vserver.vxd [000D033F] LoadFailed = vserver.vxd [000D0340] Loading Vxd = vredir.vxd [000D0345] LoadSuccess = vredir.vxd [000D0346] Loading Vxd = ndis.vxd [000D034D] LoadSuccess = ndis.vxd [000D034E] Loading Vxd = ndis2sup.vxd [000D034F] LoadFailed = ndis2sup.vxd [000D0351] Loading Vxd = vnetbios.vxd [000D0352] LoadSuccess = vnetbios.vxd [000D0358] Loading Vxd = DYNAPAGE [000D0359] LoadSuccess = DYNAPAGE [000D035A] Loading Vxd = VDD [000D035E] LoadSuccess = VDD [000D035E] Loading Vxd = VKD [000D0360] LoadSuccess = VKD [000D0360] Loading Vxd = EBIOS [000D0360] LoadFailed = EBIOS [000D0361] Loading Vxd = INT13 [000D0362] LoadSuccess = INT13 [000D0362] Loading Vxd = VCD [000D0363] LoadSuccess = VCD [000D0363] Loading Vxd = VPD [000D0364] LoadSuccess = VPD Not that the last line finished with a load success. Now the vxd listed in the registry (regedit /l:c:\windows\system.dat /e lvxd.txt hkey_local_machine\system\currentcontrolset\control\vmm32files) "vdd.vxd"=hex:00 "vflatd.vxd"=hex:00 "vmouse.vxd"=hex:00 "vshare.vxd"=hex:00 "vwin32.vxd"=hex:00 "vfbackup.vxd"=hex:00 "vcomm.vxd"=hex:00 "combuff.vxd"=hex:00 "vcd.vxd"=hex:00 "vpd.vxd"=hex:00 "spooler.vxd"=hex:00 "vfat.vxd"=hex:00 "vcache.vxd"=hex:00 "vcond.vxd"=hex:00 "vcdfsd.vxd"=hex:00 "int13.vxd"=hex:00 "vxdldr.vxd"=hex:00 "vdef.vxd"=hex:00 "dynapage.vxd"=hex:00 "configmg.vxd"=hex:00 "ebios.vxd"=hex:00 "vmd.vxd"=hex:00 "dosnet.vxd"=hex:00 "vpicd.vxd"=hex:00 "vtd.vxd"=hex:00 "reboot.vxd"=hex:00 "vdmad.vxd"=hex:00 "vsd.vxd"=hex:00 "v86mmgr.vxd"=hex:00 "pageswap.vxd"=hex:00 "dosmgr.vxd"=hex:00 "vmpoll.vxd"=hex:00 "shell.vxd"=hex:00 "parity.vxd"=hex:00 "biosxlat.vxd"=hex:00 "vmcpd.vxd"=hex:00 "vtdapi.vxd"=hex:00 "perf.vxd"=hex:00 "vkd.vxd"=hex:00 Only these vxd were not loaded : vflatd.vxd, vmouse.vxd and vmd.vxd Is windows\system\vmm32.vxd missing? NO Is vmm32.vxd corrupted ? I checked with a 386 SX 20 5MB RAM laptop with a functional win95C. There, I read Bootlog.txt and vmm32files lists and I saw that vflatd.vxd and vmd.vxd were not loaded or even tried to load even if they are present in the vmm32files list. Now I copied the vmm32.vxd file from my 386SX25 with Cyrix 50 to my laptop replacing its original vmm32.vxd. I restarted the laptop and its Win95C loads fine !! I know vmm32.vxd file is not really exchangeable but here the computer hardware are quite older than the win95 OS and they are primitive and quite same. So, the vmm32.vxd file is not corrupted. Now the hypothesis about the circumstances around the win95 first start hang. Is wmm32.vxd finished to process then win95 load frost ? The next step is normally the SYS CRIT INIT process ... and I can't see its track in Bootlog.txt. Is vmm32.vxd broke before the end ? The last Bootlog.txt line finished by a load success and at least vmouse.vxd is not loaded but no error is displayed anywhere ... what to think here ? What else could stop the vmm32.vxd loading without warning ? I have no solid clue to try to solve this problem. I did not find any similar problem in the web. Any help will be greatly appreciated.

Hi, I had a problem with my DVD multiboot when it exceeds 4.xx Go (I don't remember exactly the xx) : WinPE and Windows XP Pro SP2 fail to start : ntoskrnl.exe or setupdd.sys could not be loaded ... Now, this disk becomes large in size : Geexbox Amiga Forever WinPE 2005 VistaPE beta 009 MSDOS 6.22 installation Windows 3.11 installation Windows 95 installation Windows 98 SE installation Windows ME installation Windows 2000 Pro installation Windows XP Pro installation Windows 2003 installation Acronis suite Paragon NTFS Linux Rescue and some other small tools ... All of them work fine. The last added tool was Knoppix DVD version. WinPE did not boot correctly. If I delete Knoppix DVD from the DVD multiboot, WinPE works. I have read somewhere that if you enclose a file in a deep directory (large number of subdirectories), this file is written far in the ISO file (then it is burned towards the end of the CD/DVD disk). I decided to place the file system KNOPPIX in the directory path \KNOPPIX\FS\K\K, deeper than \Windows\system32\drivers. Therefore, I assume that the ntoskrnl.exe and setupdd.sys files are burned under the 4Go limit on the disk. Result : WinPE loads normally without error. The same for the other tools. Hope this help someone.

Thank for the clarification. To illustrate your lesson on an example, suppose your DVD driver labeled D:. On your multiboot DVD, WinXPProSP2 files are in \setup\winxppro. During all the setup process, Windows Setup finds the Windows files in D:\setup\winxppro\i386 (setup path) unless it can't find one so the default path is D:\i386 (but we know your own DVD is ok and you haven't this trouble). Here my situation. In the best of my knowledge, all necessary Windows setup files are on my multiboot DVD (entire original Windows xp pro + integrated SP2 in \setup\winxppro\, Win51, Win51ip, Win51ip.sp2 in the DVD root and in \setup\winxppro\, SetupSourcePath = "\setup\winxppro\" in \pro1\txtsetup.sif and no unattend.txt or winnt.sif file) : From the first boot to the first restart of the Windows setup process, all is ok : files are found in D:\pro1\ and D:\setup\winxppro\. So I suppose the default path is D:\setup\winxppro. When the first Setup restart is done (multiboot DVD keeped in the optical drive), Setup continues a brief moment and stops asking to insert the Service Pack 2 CD. When I press OK, a window box propose to enter a new path which is by default : D:\i386. Learning from your last post, I deduce that there are missing files in my multiboot DVD. The first file claimed by Windows setup in ASMS directory. After checking, ASMS is in D:\setup\winxppro\i386 and it is not empty. If I enter D:\setup\winxppro\i386 in the window box 'Insert the SP2 CD ...', Windows setup continues. If ASMS is effectively missing, corrupt or in the case of a DVD filesystem error, Windows setup can't continue until I enter the good path of a non corrupt media. Therefore, it is a contradiction : Windows setup reacts as if D:\setup\winxppro\i386\ASMS is missing, it asks this directory in the default path D:\i386 and it continues the installation when I enter D:\setup\winxppro\i386 in the windows box !! (I recall you that Win51*.* files are in D:\ and D:\setup\winxppro\) This situation is repeated for a lot of other files until the end of the process, but all these files are on the multiboot disk. The produced Windows OS is functional. I have tested this with two computers: two different hardware configurations. I have rebuilt the multiboot DVD several times on a DVD-RW disk reading again and again the page http://flyakite.msfnhosting.com/xpprosp1.htm. I don't know what to do now.

Thank for the reply. 'ASMS' directory is not a problem, I just mention it to illustrate that Windows Setup asks files from a Service Pack CD (because default path in Setup Windows is \i386 although SetupSourcePath = "\setup\winxppro\" when I keep the multiboot DVD in the drive). When I eject multiboot DVD during the first reboot of installation setup, default path in Windows setup is \setup\winxpro\ but drive letter is wrong so I have to introduce the multiboot DVD in another drive to continue the installation. Sorry for my heavy explanations. I'm not very good at English. I notice that you have multiple optical drives. I would to ask you another things : 1) Do you keep the multiboot DVD during all the time of the Windows installation process ? 2) Do you use CDSHELL to manage the multiboot ? If not, what soft do you have ? Thank.

Yes, I enter the true path and Setup finds 'asms' ... Since I have posted the first message, here I describe what I have found. For example, Setup CD is in drive I:. Setup launches installation ... all is right. Setup achieve the first reboot and Setup CD is in the drive. After rebooting, CDSHELL starts. I do nothing and CDSHELL boots the first HD. XP Setup continues. A window appears : Insert Service Pack 2 CD ... When I press OK, default path is I:\i386. As I said before, files are in I:\setup\winxppro\i386 although SetupSourcePath = "\setup\winxppro\" in I:\PRO1\txtsetup.sif and Win51, Win51ip, Win51ip.sp2 are in I:\ and I:\setup\winxppro\. So it is an undocumented problem. Other test I made. Before the first restart of Windows XP pro Setup, I eject the CD. Then the system reboots and setup continues. But this time, Setup asks SP2 files (first is 'asms' directory) in J:\setup\winxppro\i386. Surprise ! Path is good but drive letter is bad. If I insert the Setup CD in J: (not in I:), Setup continues to the end of the installation. Conclusion : the presence of the CD during the first reboot generates the default path as I:\i386 but without it this path is J:\setup\winxppro\i386. Why ? I don't know. How can I eliminate the variation of the default path ? I don't know. My computer have a SCSI DVD drive and a IDE DVD burner. Any idea ? Can someone having two optical drives (or more) tell me if his multiboot CD/DVD hasn't this issue installing Windows XP Pro + SP2 (or Windows 2000 + SP4 or Windows 2003) ? Thank.

I don't think it applies in my situation. Win51*.* are right on the disk. How many optical drives have you got on your computer ? When you install an OS, do you keep the multiboot DVD in the drive during the first restart or not ? Do you use CDShell software for the menu boot ? Thank for your help.