cdob

sp39700.exe HDA64.inf HardwareID does match. Try the driver.

cdimage -? -h include hidden files and directories -n allow long filenames (longer than DOS 8.3 names) -o optimize storage by encoding duplicate files only once -m ignore maximum image size of 681,984,000 bytes mkisofs -iso-lelvel 4 -r Try mkisofs -iso-lelvel 4 -r -D -b BOOT/loader.bin -hide loader.bin -hide boot.catalog -no-emul-boot -boot-load-size 4 -force-uppercase -duplicates-once -o C:\AIO-DVD.iso \MAIN http://smithii.com/files/cdrtools-2.01-bootcd.ru-w32.zip

A observation at given example: pci\cc_01018a is a Parallel ATA Controller pci\cc_010185 is a Serial ATA Controller Is this general at nforce? Does it make sense using pci\ven_10de&cc_01018a, pci\ven_10de&cc_010185 or pci\ven_10de&dev_nnnn&cc_010185 ? There are both *_nvraidbus and scsi\nvidia__raid_disk_20_____. What's the conclusion? I'm confused.Is this a mix because of driver mix? Well a gendisk is a disk. Is to be expected.

@Vertigo RT Which OS do you use? Which SP do you use? Does OS contains HD Audio Bus driver? Which HardwareId goes to your HD Audio device?

Sapphire used nVRAID BIOS v4.24, v4.60 and v4.81. http://www.msfn.org/board/index.php?s=&amp...st&p=813201 Does nVRAID BIOS set HardwareID *NVRAIDBUS and *NVRAID20? %NVRAID_BUS_DESC%=nvraidbus,*NVRAIDBUS %NVRAID_BUS_DESC%=nvraidbus,*NVRAID20 Does nVRAID BIOS v4.24 match *NVRAIDBUS ? Does nVRAID BIOS v4.81 match *NVRAID20 ? Story remids to Intel iastor. Hardware support more modes than the official driver. http://www.intel.com/Assets/PDF/specupdate/316973.pdf refers a AHCI 8023. iaAHCI.inf dosn't match 8023. I used PCI\VEN_8086&CC_0106 in the past. And I had to change this concept in the past. Thanks for examples: this show NVidia behave similar. Driver nvgts.sys support more modes than *.inf files. Yes, edited *.inf files are fine.

I understand: old nforce controllers don't use AHCI. They are either PCI\VEN_10DE&CC_0101 or PCI\VEN_10DE&CC_0104. PCI\VEN_10DE&CC_0106 match all nforce AHCI controllers. This includes a PCI\VEN_10DE&DEV_044D&CC_0106. PCI\VEN_10DE&DEV_044D is not part of iSmart nvgts.inf. Currently: a new driver may match all nforce AHCI controllers. However this may fail in future. A old driver may fail at new hardware. PCI\VEN_10DE&CC_0106 is a good idea today, but may fail in future. Nvidia may release conflicting drivers. PCI\VEN_10DE&DEV_0ABC match PCI\VEN_10DE&DEV_0ABC&CC_0101 PCI\VEN_10DE&DEV_0ABC&CC_0104 PCI\VEN_10DE&DEV_0ABC&CC_0106 PCI\VEN_10DE&DEV_0ABC&CC_0180 PCI\VEN_10DE&DEV_0ABC&CC_1234 The last two examples dosn't exist. All new nforce controllers are connected to nvgts.sys. This maybe a good or bad idea. PCI\VEN_10DE&DEV_*&CC_* may get more stable results now and in future. iSmart Nvrd32.inf: there are only Raid*20 HardwareIDs. Does this refer to old nforce controllers only? %NVRAID_DESC%=nvraid,GenNvRaidDisk %NVRAID_DESC%=nvraid,SCSI\NVIDIA__Raid_Disk________ %NVRAID_DESC%=nvraid,SCSI\__NVIDIA_______Raid_Disk %NVRAID_BUS_DESC%=nvraidbus,*_NVRAIDBUS %NVRAID_BUS_DESC%=nvraidbus,*NVRAIDBUS Another question: Does BIOS or driver set Raid HardwareID?

@David McMahon HP offers sp26740.exe AMD offers catalyst driver package. http://game.amd.com/us-en/drivers_catalyst...integratedip-xp

Txtsetup.sif dosn't support high capacity USB floppy drives. http://support.microsoft.com/kb/916196/ http://www.msfn.org/board/F6-Driver-USB-Floppy-t82711.html http://www.msfn.org/board/index.php?s=&amp...st&p=681916 Does nLite add high capacity USB floppy drives HardwareID to txtsetup.sif? [HardwareIdsDatabase] USB\Class_08&SubClass_04&Prot_00 = "usbstor"

SP39700.exe contains a \WDM\Vista\ and a \WDM\WinXP\ directory. http://h10025.www1.hp.com/ewfrf/wc/softwar...product=3795407 There are 32 and 64 bit drivers: \SP39700\WDM\WinXP\sthda.sys \SP39700\WDM\WinXP\sthda64.sys

http://www-307.ibm.com/pc/support/site.wss...ocid=MIGR-70477 There is a \prepare\install.cmd. Follow instructions.

Keep WinSxS *Windows.Common-Controls* files.

Vista boot sector is case sensitive at ISO9660: use name \BOOT\BOOTMGR, not \boot\bootmgr. And use \SOURCES\BOOT.WIM Syslinux chain.c32 does chainload NTLDR at media with Master Boot Record. I've no idea how to use this at DVD.

ISO96660:1999 and RockRigge support long file names and my requirements. E.g. DOS, XP, PE and Knoppix at one DVD.Joliet dosn't support long names: official 64 chars, does work up to 110 chars. Actually RockRidge is not a addinal file system, that's a extension ot ISO9660. Extension is included within ISO9660 possibilities. http://www.msfn.org/board/Super-Disc-Multi...-Pr-t94398.htmlhttp://syslinux.zytor.com/wiki/index.php/SYSLINUX Documentation within syslinux http://www.kernel.org/pub/linux/utils/boot/syslinux/ Of course: the tool is a proper CD writer. Use gigarec=1.2 and write 840Mb at 700Mb media.

Thanks, I didn't recogniced this new feature so far.However I'm used to use CAIN to chainload another hard disk in the past. Does this refer to the same DVD too nowadays? Yes, of course. But I can't change boot sector myself. I need a solution supporting my needs.As for myself I like to use file system ISO9660:1999 and rock ridge at DVD. My choosen boot environment has to support this. Sorry I used a wrong word: general. Let's say for some special features.Overall I can't recomend a single boot loader: There is no best boot loader arround. All have benefits and weak points. I'm using BCDW, syslinux and grub4dos at different projects.

@jetman There are OEMScan additons http://siginetsoftware.com/forum/forumdisplay.php?f=14

There is no best boot loader arround. All have restrictions. There dosn't exist a boot loader using best features of all. Some examples, not complete: BCDW: +does chainload setupldr.bin +does hexedit setupldr.bin in RAM +does chainload isolinux and grub4dos -not developed since 2004, work arround for 2003 SP1 checksum not integrated -fails at some newer strange BIOS -works from CD/DVD only Isoliux, part of sylinux project: +activley developed +a lot CD use this, therefore tested at a lot of hardware -dosn't chainload setupldr.bin -XP boot sector is requried, boot sector fails at rock ridge file system -dosn't hexedit setupldr.bin in RAM grub4dos: +activley developed +does chainload setupldr.bin -dosn't hexedit setupldr.bin in RAM +swap drive order virtually +works from CD, internal HDD, USB As for a XP multi boot CD: BCDW As for a windows and linux multi boot DVD: isolinux As for a general multi boot DVD: grub4dos

@jetman OEMScan does work fine at Flyakite's multi boot scheme. $OEM$\cmdlines.txt [COMMANDS] OEMSCAN.cmd OEMSCAN.cmd OEMScan\OEMScan.exe >> %SystemRoot%\Temp\OEMScan.logUse directory $OEM$\OEMSCAN\ that's $OEM$\OEMSCAN\OEMSCAN.EXE and $OEM$\OEMSCAN\OEMSCAN.INI

@jodan PEBuilder process layout.inf to select files. Iastor is missing in layout.inf. Hence file is not copied and missing at final BartPE. Avoid nlited source files for PEBuilder so far. Or copy missing files yourself.

Attached files contain Version First 8.5 link match However 82801GR/GH is not mentioned anymore.Dosn't 82801GR/GH match a ICH7? Try old Version 7.8 or 7.0.

Not tested, try [Disks] disk1 = "PowerVault DAT Driver", pvdatw2k.sys, \ [Defaults] scsi = pvdatw2k [scsi] pvdatw2k = "PowerVault DAT Driver" [Files.scsi.pvdatw2k] driver = disk1, pvdatw2k.sys, pvdatw2k inf = disk1, pvdatw2k.inf catalog = disk1, pvdatw2k.cat [Config.pvdatw2k] ;HKR,,TypesSupported,%REG_DWORD%,7 [HardwareIds.scsi.pvdatw2k] id = "SCSI\SequentialARCHIVE_Python_06408-XXX","pvdatw2k" id = "SCSI\SequentialSEAGATE_DAT____06408-XXX","pvdatw2k" id = "SCSI\SequentialSEAGATE_DAT____9SP40-052","pvdatw2k" id = "SCSI\SequentialSEAGATE_DAT____DAT72-052","pvdatw2k" id = "SCSI\SequentialARCHIVE_Python_06409-XXX","pvdatw2k" id = "SCSI\SequentialSEAGATE_DAT____DAT72-452","pvdatw2k"Copy all driver files to floppy root directory.

First example: boot.bin is seeked at .\Source Second example: "Microsoft Corporation.img" is seeked at .\test Be aware: -b is case sensitive. Case does matter. And / goes to a directory. That's not \.

I've no idea.Anyway I would neither use XP nor Vista for a BIOS update. Don't you have a DVD or CD drive? What about the CD-ROM solution?

Toshiba Model Selector offers a BIOS update for floppy, CD-ROM and windows installation. http://www.csd.toshiba.com/cgi-bin/tais/su/su_sc_modSel.jsp

http://www.msfn.org/board/Modify-your-drivers-t16222.html PNP use HardwareID and ranking to select drivers. Driver signing and date set ranking. edit new *.inf. Driver is not signed anymore. Different approaches: comment CatalogFile [Version] ;CatalogFile = signed.cat comment old HardwareID's [Nvidia] ; DisplayName Section DeviceID ;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_01C3 ;%NVENETFD.DeviceDesc% = NVENETFD1.NDI, PCI\VEN_10DE&DEV_0066 ;%NVENETFD.DeviceDesc% = NVENETFD3.NDI, PCI\VEN_10DE&DEV_0086 comment DriverVer [version] ;DriverVer = 07/11/2007, 67.5.3

What about root directory? Tag files \WIN51* are at root directory. Did you add tag files at all?