cdob

Did you edited setupldr.bin? Change setupldr.bin, apply renamed names. And edit setupdd.sys.

Feature is called GigaRec. This was introduced at Plextor Premium, a CD writer. Later true Plextor drives support GigaRec too. Remember Plextor dosn't manufactur drives anymore. Today that's OEM drives with a Plextor label. Have a look for GigaRec at product manual. Most drives should read GigaRec factor 1.2 (read 840mb data at 700mb media). Of course reading is not guaranteed. I'm using 'cdrecord driveropts=gigarec=1.2' A average drive dosn't read GigaRec factor 1.4 (980mb data at 700mb media). The same drive or on another identical one is required.

First congratulations to new section at MSFN. If I recall correctly from 2006 http://www.msfn.org/board/-t81788.html&amp...st&p=584906 Txtsetup.sif [setupData] SetupSourcePath is ignored at USB. Using a different directory set: change setupldr.bin and setupdd.sys.

Of course this is not safe. If you like a safe solution: use graphic card drivers from Laptop manufacturer. If Laptop manufacturer dosn't provide appropiate drivers, try a non safe solution. Of course that's at your own risk. Which nvidia driver version do you use currently? Try a newer one, but don't use the newest.

Driver for Laptop Nvidia Graphic cards: http://www.laptopvideo2go.com/ There are default desktop drivers and modded *.inf files.

Yes, there are 8.5GB dual layer DVD media. http://en.wikipedia.org/wiki/Dual_layer#Dual_layer_recording

Which DVD media do you use? There are dual layer DVD media. ISO-9660 and UDF file system handle files greater 4GB. To include a 5GB file to bootable media http://www.msfn.org/board/OSCDIMG-error-t111776.html

Hard disk is connected to a ICH8M. Use drivers for this massstorage controller. Get Storage Manager Intel Windows XP 7.5.0.1017 http://uk.computers.toshiba-europe.com/cgi...selShortMod=675

There is a new WAIK http://www.msfn.org/board/-t84446.html&amp...st&p=734826 This contain a new OSCDIMG 2.54. -u2 includes a file greater 4 GB.

I get Does a newer oscdimg version exist? Another approach is mkisofs. Big files greater 4 GB can be included to a bootable media. Maybe that's a solution. Ask if you like to try this and need help.

Integrate KB883667 http://www.msfn.org/board/Unattend-Install...ver-t39479.html Can you try XP SP3 RC too?

@Masters If you like to create one DVD then follow Siginet's aproach. Add different renamed winnt.sif to the DVD.

Setupreg.hiv is a registry file. Use regedt32.exe or regedit.exe and load file. What do you like to do finally? Do you need different winnt.sif? Do you like loading PNP drivers from different locations?

bootsect.dat is a copy of partition boot code. You get different bootsect.dat at different partitions. Don't copy bootsect.dat across different hard disks. Partition and format a hard disk. Extract boot code next. http://www.msfn.org/board/index.php?showtopic=53366 dd, dsok, bootpart and mkbt are usable applications. A default boot code load file ntldr. You may change extracted boot code. nt2peldr is mentioned. This changed boot code load file name peldr.

No, you can't set another location for winnt.sif. CD and A:\ are fixed. However you may use a virtual floppy in RAM. http://www.911cd.net/forums//index.php?showtopic=20543

@gugutz Try real hardware. Which VirtualBox version do you use? Try current version. Cdimage dosn't support a "boot-info-table" option. Remember isolinux bootfile is greater 2048 bytes. This works at a lot of different BIOS. But fail at some BIOS. In doubt follow isolinux documentation http://syslinux.zytor.com/iso.php mkisofs -boot-info-table This patch isolinux.bin, a El Torito Boot Info Table is set.

Did you install chipset drivers?

BCDW, UBCD and isolinux use no-emulation boot mode. Does BCDW fail at very old or new machines (this year) ? There are different BIOS and different BIOS boot cd implementations. A bootloader has to include work arrounds for a strange BIOS. BCDW isn't developed since 2004. BCDW may fail at new hardware nowadays. UBCD v3 used CD shell bootloader. BCDW can be chainloaded. UBCD v4 uses ISOlinux bootloader. I don't know a bootloader supporting all your needs. Isolinux is developed still. Do you use UBCD v4 ? Does this boot at all your machines?

@ilko_t and wimb to prepare3, haven't tried usb_prep.cmd yet. Congratulations, does work as builded. Windows installation files are perpared in vitual disk and copied to USB drive. Installation does work. Windows does boot. No files are delete at USB drive. But allow me to play the bad guy (a sophisticated end user, the worst customer): Next I installed windows at folder c:\windows51. First reboot failed. Obviously boot.ini at USB stick dosn't match: multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="GUI Mode Setup" /FASTDETECT This failed: \$WIN_NT$.~LS\$OEM$\CMDLINES.TXT [COMMANDS] "binifix4.cmd C:"Do I use false files? How to run binifix?.cmd at end of textmode setup? First reboot should work at c:\windows51 too. Another example: c:\boot.ini d:\windows How to support this? Do we restrict to c:\windows only? Three suggestions to _prepare.cmd: Ask temporary image size in megabytes I prefer OS internal solutions. Third party tools if internals fail. Use fsutil instead of fsz. Fsutil.exe is a default XP application. format /Q: Quickformat In addition there is a undocumented 'format /Y' as YES. A end user dosn't have to confirm format.Contrary a end user might select a false drive by accident. Don't use 'format /Y'. A end user has to confirm format always. USB stick get C: too, if you use a brand new hard disk (no partitions). If need be you don't have to use U:, another letters are possible too. A third parameter goes to migrateinf.cmd

I don't understand clearly. Do you like to insert new data? A old sector does exist and you like to overwrite this sector? Use a hex editor or dd. I'm using dd. $ dd count=1 bs=2048 skip=625 if=C:/temp/image.iso of=bootimage.img $ dd count=1 bs=2048 seek=625 conv=notrunc if=bootimage.img of=C:/temp/image.iso

There are Compatible ID's too. A Iomega USB floppy XP txtsetup.sif contain some USB floppy Hardware ID's VID_*&PID_* . Some USB floppy drives are missing. In addtition there are some usbstor Compatible ID's already. USB\Class_08&SubClass_04&Prot_00 is missing. Hence the txtsetup.oem addon. What about: add Compatible ID to txtsetup.oem? #--The following lines give additional USB floppy support id = "USB\Class_08&SubClass_04&Prot_00", "usbstor" #Compatible ID

@ilko_t I like adding lines to TXTSETUP.SIF at a batch files. This goes to a end user solution. Free time: unfortunately I havn't tried hole solution yet. I dislike possible changed boot sector still. Winnt32.exe goes back to NT4 times, there was no USB at all. Except some third party drivers. Used at a not supported environment may get unexpected results. Don't rely on a unsupported feature. You never know results. By design Winnt32.exe /syspart makes a internal hard disk bootable. MBR and boot sector are updated, if it is necessary. Necessary according to Winnt32.exe rules. This rules may fail at USB. A boot sector maybe valid by change according to Winnt32.exe rules. The question: Use a solution requiring a Winnt32.exe friendly boot sector? Does all BIOS boot from a PEtoUSB boot sector? Isn't PEtoUSB limited to FAT16? My opinion: A end user friendly solution dosn't require a winnt32.exe friendly boot sector. You mentioned ImDisk already. There are other Virtual Disk Drivers too. What about? create a virtual disk winnt32.exe writes to this virtual disk copy files to USB next Granted, this may take longer. But final USB stick may work at more machines.

That's syspart design: prepare install for another machine. http://support.microsoft.com/kb/241803/en-us This goes for XP too.Obviously winnt32.exe wasn't created for USB devices. BIOS hard disk sort order maybe involved too. Syspart work fine at internal drives. C:\$WIN_NT$.~BT\BOOTSECT.DAT contain a boot sectors, string ntldr is edited.

Xcopy.exe copy files, folders and subfolders. Run xcopy /? Or read files from different folders: add fodler c:\boot and folder c:\add mkisofs ... c:\boot c:\add

Your root-of-iso-tree is c:\boot Actually it's about relative path. How do you launch the script? At current working path c:\boot, there dosn't exist another folder boot. Try @echo off cd /d c:\boot mkisofs -b loader.bin -hide loader.bin -no-emul-boot -boot-load-size 4 -l -o main.iso . pause Another solution. Try mkisofs -b loader.bin -hide loader.bin -no-emul-boot -boot-load-size 4 -l -o main.iso c:\boot