cdob

txtsetup.sif is used from inside /WINSETUP/XPpSP3.ISO

It's possible to add nForce mass storage at running system, hence at Precision Workstation 470. http://forums.nvidia.com/index.php?showtopic=109384 Integrating at offline system (XPS630i) with BartPE is possible too. http://www.911cd.net/forums//index.php?showtopic=20464 http://www.911cd.net/forums//index.php?showtopic=22523 Ask at 911cd if you need further help. Nvgts.sys may need a adjustment.

Can you name examples? Are there unicode names used inside ISO image? Are there unicode names at src directory name? I've no idea to handle unicode names at vbs or cmd.exe. Even a 8 bit char at src directory name may get unexpected results. Yes, this is a example. Most likely this user added a security fix. Security fixes add lowercase file names. At boot setupldr.bin dosn't find NTKRNMP.exe, despide the ntkrnlmp.exe message. Yes and no. No, boot sector has to be relative to source folder. However you may collect different source folders. Create a dummy sub folder and add boot sector Collect files from Windows source folder and dummy sub folder. If bootable And Not fso.FileExists(locpath & "bootsect\" & bootsect) Then MsgBox "Boot sector missing (" & bootsect & ")", 16, "Error" WScript.Quit(1) End If If bootable Then wsh.Run chr(34) & locpath & "\exec.cmd" & chr(34) & _ "mkisofs.exe -iso-level 4 -joliet-long -duplicates-once -force-uppercase" & _ " -no-emul-boot -b " & bootsect & _ " -hide boot.catalog -hide " & bootsect & _ " -hide-joliet boot.catalog -hide-joliet " & bootsect & _ " -sysid ""Win32"" -V ""Windows"" -m thumbs.db" & _ " -o """ & src & ".iso""" & " """ & src & """ """ & locpath & "bootsect""" Else exec.cmd @setlocal EnableExtensions %* @IF %ERRORLEVEL% GTR 0 pauseThat's a work around to display actual used command line. And to pause at a error. I need used command line and mkisofs output to debug error conditions. How to do this within vbs? By the way: remember name bootsect.bin is case sensitive. bootsect.bin is not BOOTSECT.BIN, nor BootSect.bin. Another question: Which ISO file size does create end customers? Setupldr.bin and ntldr access first 4GB of a ISO9660 media only. Textmode files and ASMS folder has to be within first 4GB of media. Mkisofs does sort by name by default. Simple approach: ask end user to use a name after I386. E.g. add third party setup files at \setup\ This way I386 goes first to media.

How do they do this? Massstorage driver are loaded early, case is importand. Does exist lower case names at hard disk after adding massstorage drivers? Actual question was: may a end user use \I386\$OEM$\TXTSETUP.OEM ? $OEM$ has to exist at ISO9660 name. A "$" char is invalid at ISO9660 Level 1. Which chars does use the "dozens of installers and hundreds of files" ? Are there any unicode chars? Are there plain ASCII (7 bit) chars?

Create a test version: Use a XP gold or SP1 CD as source. Slipstream SP3. Installation fails because of a mixed case name win51ip.SP3. Should be supported a slipstreamed version? -force-uppercase goes to ISO9660 file system names only. That's the same case as ISO9660 Level 1 to 3. Joliet or Rock Ridge names are mixed case still. Windows display Joliet names, if Joliet is available. Windows display mixed case names, despide uppercased ISO9660 names. Which names should be supported? Can you name some examples? Is winnt.sif [MassStorageDrivers] used? May a end user use this option?

Current args are broken. A file SETUPLDR.bin is added as SETUPLDR.bin. Bootector search file SETUPLDR.BIN only, booting fails.

There is no final answer. Do you expect plain OS files (OS, SP and security fixes)? Do you expect custom files with non ASCII chars? About file system and NT to 2003, to summarize : core boot setup does read ISO9660 names, only upper case names are found -iso-level 4 allow lower case names, core boot may fail; -force-uppercase set upppercase names a NT based bootsector does fail at ISO9660 Level 1, lower restrictions -iso-level 4 includes -relaxed-filenames, -l and -allow-multidot 2003 SP2 use a long directory name -boot-load-seg 0x7C0 is a internal default -boot-load-size defaults to whole file (remember Windows 7 use 2048 byte bootsector) Rock Ridge is not required at a single NT based boot cd. Joliet file system is not required at NT based boot cd, ms dosn't use Joliet at NT based boot cd. Joliet could be useful at custom addons with unicode chars, or at 2003 SP2 with -iso-level 3. A suggestion: -iso-level 4 If bootable Then wsh.Run chr(34) & locpath & "\mkisofs.exe" & chr(34) & " -b " & chr(34) & bootsect & chr(34) & _ " -no-emul-boot -hide " & chr(34) & bootsect & chr(34) & " -iso-level 4 -duplicates-once -force-uppercase " & _ "-sysid ""Win32"" -V ""Windows"" -o " & chr(34) & src & ".iso" & chr(34) & " " & chr(34) & src & chr(34)-duplicates-once -force-uppercase require a special forged version. Not supported since 2004, does work fine for boot cd. Or -iso-level 3 with Joliet If bootable Then wsh.Run chr(34) & locpath & "\mkisofs.exe" & chr(34) & " -b " & chr(34) & bootsect & chr(34) & _ " -no-emul-boot -hide " & chr(34) & bootsect & chr(34) & " -hide-joliet " & chr(34) & bootsect & chr(34) & _ " -hide boot.catalog -hide-joliet boot.catalog -relaxed-filenames -iso-level 3 -D -d -l -N -joliet-long -allow-multidot " & _ "-sysid ""Win32"" -V ""Windows"" -o " & chr(34) & src & ".iso" & chr(34) & " " & chr(34) & src & chr(34)Use any version.

There is no need to redistribute the bootsector. It's stored inside spcmdcon.sys. Search for 0xfa 0x33 0xc0 0x8e second match and extract 2048 bytes.

This is not about bootable USB. This converts a external USB disk to a internal IDE disk, hence the rdisk(9). This dosn't match install from USB. Don't use this approach.

How do you burn this one? Which *.ibb project file do you use? Create a ISO image and burn ISO iamge at ImgBurn.

Installer is not required. Basically there are three boot files: setupldr.bin, ntdetect.com and txtsetup.sif. Set SetupSourcePath and BootPath at txtsetup.sif.

Open device manager, select details of network card. Which HardwareId do you get?

WinSetupFromUSB_1-0-beta6: XP 32 bit files at second primary partition at USB stick and removable bit set. txtsetup.sif [SourceDisksFiles] ... dmmydisk.sys = 1,,,,,,,4,0,0 [BootBusExtenders.Load] ... dmmydisk = dmmydisk.sys [BootBusExtenders] ... dmmydisk = "USB Fixed Disk filter driver",files.none,dmmydiskAnd copy dummydisk.sys I386\dmmydisk.sys Windows setup complete from second partition at removable USB stick. Dummydisk is active at installed windows.

Half broken hardware. Use another media, burner or software. Try ImgBurn.

Just to clarify: you used the syslinux MBR boot code from mbr.bin and intalled syslinux to the partition? Which bootable device do you have at all? Do you have the old 1.8" disk still? Which OS, size and partitions goes to old 1.8" disk? Can you dd first part of 1.8" disk to CF card?

Can you use a USB floppy drive?. There is PLop boot mangager to continue USB flash. PeToUSB did enable USB flash boot (2GB) at a T40. http://www.gocoding.com/page.php?al=petousb I've no idea.A work arround: grub4dos or syslinux at MBR / partition boot code

Add drivers relating to your mass storage controller.

That's 255 heads.Booting fails at a 240 heads BIOS: blinking cursor... Do not use a third party tool. Zero first sector. Insert CF card internally. Boot windows install media, partition and format the CF card. You may need a fixed disk. http://www.thinkwiki.org/wiki/Compact_Flash_boot_drive http://kb.sandisk.com/app/answers/detail/a_id/51 http://communities.sandisk.com/sandisk/board/message?board.id=extreme3&thread.id=796

http://www.sevenforums.com/sound-audio/51455-boston-735-usb-speakers-realtek-ac97.html

Well, setup.cmd does support driverpack method 2 already. There is no need to include driverpack fake setup.exe to floppy image. Quite contrary you may get strange results: read it's not supported. In addition Driverpack masstorage add textmode files to txtsetup.sif too. Anyway if you need to incldue a second setupORG.exe to floppy image. Adjust txtsetup.oem inside floppy image [Disks] setup32 = "setup files x86", \txtsetup.oem, \setup\I386\ se03_32 = "2003 setup files x86", \txtsetup.oem, \setup\I386_03\Copy 2003 setup.exe to \setup\I386_03\setupORG.exe. Use a hexeditor, open txtsetup.oem, remember offset to Example: 0x596Use the previous offset at menu.lst write --offset=0x596 (fd0)/txtsetup.oem se03_32

Cfadisk.inf has to contain the HardwareID. Edit cfadisk.inf first: [cfadisk_device] %Microdrive_devdesc% = cfadisk_install,USBSTOR\DiskIntenso_ %Microdrive_devdesc% = cfadisk_install,USBSTOR\GenDisk run devcon install cfadisk.inf USBSTOR\DiskIntenso_ or devcon install cfadisk.inf USBSTOR\GenDiskThis is a generic approach: cfadisk is connected to current attached USB storage devices

Create a drive letter on the fly: pushd /? Try pushd "%~dp0" dir pause popd or pushd "%~dp0.." dir pause popd

Different size is a different condition at USB booting. A BIOS may use different mapping. Congratulations. Basically the HP tool does support a HP BIOS.The formated USB stick may fail at other BIOS. This was the reason to develop different USB format tools. RMPREPUSB is one example. USB_MultiBoot.cmd author wimb offers a enhanced format version too. U-XP-SET can format a USB stick nowadays.

Which data space does this stick provide?How did you partition and format this stick? How did you partition and format the 4GB Corsair Flash Voyager stick? The 4GB stick may need other settings.

Which result do you get? "Windows will dump" is not a clear error report. Firadisk 0.0.1.18 does work fine at 2003 SP2 32 bit files. If I recall correctly v0.0.1.12 did work too. Which 2003 files do you use? Integrate a 2003 setup.exe to floppy image. Do not use a XP setup.exe for 2003.