cdob

El Torito specs http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf Idea: The BIOS use fixed heads and sectors at floppy emulation. Tracks are not limited to floppy 0x50, hard disk numbers are possible. This mentiones menuetos http://www.menuetos.net/cdboot.htmSector 19 from file isohdr contain a 1.44 floppy emulation boot entry. To set 2.88 floppy emulation goto address 0x9820 and change 0x88 0x02 to 0x88 0x03 Create a 36mb floppy image floppy36.IMA (36 sectors, 2 heads, 1024 tracks). Connect files Or build a ISO header file using debug < debug288.txt To connect files: copy /b ISOHDR288.iso+floppy36.IMA floppy36.isoIf you like to add addional files to CD: Run ImgBurn, build a hard disk emulation ISO image, add 36mb floppy image. Adjust boot catalog to floppy emulation: 0x88 0x04 to 0x88 0x03 Or adjust a appplication to 36mb floppy image El Torito specs http://download.intel.com/support/motherboards/desktop/sb/specscdrom.pdf Doesn't use a HD-like ZIP fourth partition table entry? Contrary fourth entry may be first entry, partition count may be reversed. BIOS behaviour is unclear.

Which size do you get? greater 4GiB?At textmode boot there maybe a 4GiB limit. E.g. setupldr.bin read up to 4GiB and won't find files at end of media. Be careful about file layout. File sorting is important greater 4GiB. ImgBurn support command line, multiple folders and optimising ISO. There is a unofificial branch too. DFL author reanimatolog integrated DFL to mkisofs. Source files are preserved.mkisofs -duplicates-once http://www.nu2.nu/pebuilder/ http://www.paraglidernc.com/links/links.htm

My condolence. There are strange BIOS approaches. Random ideas: boot a PE, run winnt32 /unattend http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/winnt32.mspx try burg, a grub2 with grub4dos use a physical floppy still Adjust original OEM restore disc. It's insane, if you are allowed to use USB key boot, but not to change original OEM restore disc.

Sorry, could not resist: What's a SATA cdrom? Did anybody build a CD-ROM drive with SATA connectors? Do you use AHCI mode? Do you use IDE emulation mode? Do you use a friendly BIOS? Try SATA optical drive at IDE emulation.

Remember: The manufacturer dosn't support XP USB install. And different BIOS gives different results. Did you tried WinSetupFromUSB vers. 0.2.3? Did you tried all sticky solutions?

Try a current grub4dos. Boot grub4dos, open a command prompt, enter line by line.

Which "XP Setup Source Path" do you use? Does selected path contain spaces? Try path "c:\xp_source"

Then most BIOS map USB key to hd0. Remap this to CDROM boot order: hd0 internal hard disk Uncomment the lines

Idea, not tested:RAM load the whole OEM CD. Use grub4dos write and edit \i386\winnt.sif Help us to help you: answer the question. Boot device is importand. Example, may work or fail at unknown boot device title load floppy image - launch setupldr.bin ls /FLOPPY.IMA || find --set-root /FLOPPY.IMA map --mem /FLOPPY.IMA (fd0) #(fd1) optional, required at some BIOS map --mem /FLOPPY.IMA (fd1) #map (hd0) (hd1) #map (hd1) (hd0) map --hook ls /I386/SETUPLDR.BIN || find --set-root /I386/SETUPLDR.BIN chainloader /I386/SETUPLDR.BIN In addition: grub4dos may write to virutal floppy \winnt.sif Imagine one floppy image and different winnt.sif configurations. Compare the mentioned thread.

Which boot device do you use? Do you have a second DVD drive? Do you boot from USB? Grub4dos can emulate a floppy drive. And can chainload setupldr.bin from DVD drive. Setupldr.bin does access virtual floppy drive.

Try FAQ Q3:

Yes, it works. This is another approach. That's two times RAM loading.You may load part of file the first time. You have to load whole file the second time. This may be impossible at low RAM machines. Fake setup does this. Setup.cmd search Inst/XP_RAM.ISO. At most machines a USB drive is available at first reboot, ISO file is available within windows. At some machines a USB drive is missing at first reboot, ISO file is not available within windows. There is a fix fixboot.usb at txtsetup.oem available. This is disabled by default, enable this. If the file is found, imdisk is used to mount the image. Setup continue.

Why two more entries?Add one entry to boot from internal hard disk. Set this as grub4dos default entry. Why do you do this? Did anybody suggest this at previous messages? Boot from hard disk at first restart. There is no need to load image to RAM at first restart. If you use a broken BIOS, adjust txtsetup.oem and enable fixBoot.usb. Yes, that it. Windows install run %systemroot%\system32\setup.exe at first reboot. That's a installation default feature.

Can you name a hardware example? With support for current CD media. A 10 years old hardware may be half broken today. Certainly firmware is not updated to current CD-R media. Current example: http://www.lg.com/us/products/documents/LG_HE_IT_SS_GH22NP21.pdf Slowest CR-R write speed is 16x. @peppino Which hardware do you use? Anyway: What's a CD? Listen music from a SSD nowadays.

Use a original XP CD. Setupldr.bin process file txtetup.oem at (virtual) floppy drive. That's a installation default feature.

That's a urban legend. That's nonsense at current hardware. Neither burner nor media are build for 1x speed. No current burner support 1x speed. No software can change this.

I don't understand clearly.Yes, after initial text mode setup windows installation continues. No, don't add virtual floppy to ISO image. Windows read fake setup.exe from virtual floppy disk.

Add windows 7 files to DVD. Use uppercased ISO9660 names. At isolinux.cfg launch default boot sector file label W7 BOOT /boot/etfsboot.com

Yes, that's true often. However, does current official driver support your Samsung R519? Suggestion was for testing purposes. Read opinion from a DriverPacks MassStorage developer: Post #26 http://forum.driverpacks.net/viewtopic.php?id=4631&p=2

As for testing purposes there are non official 10.0.0.1046 WHQL drivers. http://www.station-drivers.com/page/intel%20raid.htm

Ask at LiveXP forum http://www.boot-land.net/forums/index.php?showforum=52

Does this refers to SM Bus controller or flash drive devices? This reminds to a Realtek network card. Does flash drive devices work at your machine? Does device mangager list a strange device? Goto device mangager, details. Which HardwareID goes to this device?

@LittleRed Usually windows dosn't load a driver for SM Bus. Example from machine.inf Which hardware do you use?

Why? Which part list a third partition? Does HP SmartStart 8.50 fake isohybrid approach work at real hardware? Most likely HP SmartStart 8.50 won't find MBR in memory. MBR at disk is used to mount partition. This use a partiton type, not used by current OS.You may change the 0x06, try 0x82 or another one.

map --in-situ changes mbr in memory Mapping is active at real mode. Mapping is lost at protected mode. http://grub4dos.sourceforge.net/wiki/index.php/Mr What's your idea?