cdob

@TheCrowX [MassStorageDrivers] has to match the description in txtsetup.oem. That's not the hole line. Remove iaAHCI_ICH7R. [code][MassStorageDrivers] "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)" = "OEM"[/code] Or try[code][MassStorageDrivers] "Intel SATA RAID Controller" = "OEM" "Intel SATA AHCI Controller" = "OEM"[/code] [code]; **************************************************************************** ; **************************************************************************** ; ** Filename: TxtSetup.OEM ; **************************************************************************** ; **************************************************************************** [Disks] disk1 = "Intel Matrix Storage Manager driver", iaStor.sys, \ [Defaults] scsi = iaStor ;----------- Component Section ----------- [scsi] iaStor = "Intel SATA RAID Controller" iaAHCI = "Intel SATA AHCI Controller" ;------------------------------------------- [Files.scsi.iaStor] driver = disk1, iaStor.sys, iaStor inf = disk1, iaStor.inf catalog = disk1, iaStor.cat [Files.scsi.iaAHCI] driver = disk1, iaStor.sys, iaStor inf = disk1, iaAHCI.inf catalog = disk1, iaAHCI.cat ;------------------------------------------- [Config.iaStor] value = "", tag, REG_DWORD, 1b value = "", ErrorControl, REG_DWORD, 1 value = "", Group, REG_SZ, "SCSI miniport" value = "", Start, REG_DWORD, 0 value = "", Type, REG_DWORD, 1 ;------------------------------------------------------- [HardwareIds.scsi.iaStor] id = "PCI\VEN_8086&DEV_27C3&CC_0104","iaStor" id = "PCI\VEN_8086&DEV_2652&CC_0104","iaStor" id = "PCI\VEN_8086&DEV_24DF&CC_0104","iaStor" id = "PCI\VEN_8086&DEV_25B0&CC_0104","iaStor" ;id = "PCI\VEN_8086&CC_0104","iaStor" [HardwareIds.scsi.iaAHCI] id = "PCI\VEN_8086&DEV_27C1&CC_0106","iaStor" id = "PCI\VEN_8086&DEV_2652&CC_0106","iaStor" id = "PCI\VEN_8086&DEV_2653&CC_0106","iaStor" ;id = "PCI\VEN_8086&CC_0106","iaStor"[/code]

@trainee I've few hardware only. [quote name='txtsetup.oem'][Disks] d1 = "Mass Storage Drivers", \TXTSETUP.OEM, "" [Defaults] ;48 bit LBA scsi = Ultra [scsi] Ultra = "Promise ULTRA Controller" iaStor = "Intel SATA Controller" viaraid_multiple = "VIA RAID Controller"[/quote]

Thanks for correcting. Yes, my conclusion is wrong. Available hardware got me a false idea. I don't have access to VEN_1039&DEV_7012&SUBSYS_810D1043. You convinced me, current realtek AC97 drivers are broken.

I don't understand clearly. Do you get access to CD-ROM drive at all? Don't incldue SBI.CAB in image. Do you get a file below 500 mb? Add \SBI.CAB to cd. Boot PE into RAM, use a startup batch and detect cd drive. set PEDrive= rem ignore drive X for %%a in (C D E F G H I J K L M N O P Q R S T U V W Y Z) do if exist %%a:\SBI.CAB set PEDrive=%%a

[quote name='Hipster Doofus']"Please insert the disk labeled windows XP Home Edition CD-ROM into dirve A"[/quote]Does files \WIN51IC and \WIN51IC.SP2 exist at cd? Case is importand. Remember, a a:\WINNT.SIF goes first. Edit a a:\WINNT.SIF, remove [MassStorageDrivers] section and boot existing cd. Do you get error message still? @trainee Thanks for winnt.sif [MassStorageDrivers] solution. I'm using that at PE. Setupldr.bin in minint mode use files: \I386\SYSTEM32\WINNT.SIF \I386\SYSTEM32\$OEM$\TXTSETUP.OEM

AC'97 sound use part of south bridge and a audio codec - a pice of hardware. There are different kind of HardwareIDs. Alcxau.inf use HardwareID's VEN_*&DEV_*. This describe AC'97 southbridge, not audio codec. Alcxau0.inf use HardwareID's PCI\VEN_*&DEV_*&SUBSYS_*. Recognice SUBSYS. This describe AC'97 audio codec. Alcxwdm.sys does support SUBSYS_* devices. Example: There is a audio codec supported by soundmax drivers: PCI\VEN_8086&DEV_2445&SUBSYS_0056110A PNP use ranking to select a driver. A PCI\VEN_*&DEV_*&SUBSYS_* get a higher priority than a PCI\VEN_*&DEV_*. This works inside one *.inf file. At different *.inf files, DriverVer goes first. A newer *.inf is prefered. This may lead to false results. Realtek driver dosn't contain a SUBSYS_0056110A. But Alcxau.inf load driver alcxwdm.sys. Alcxwdm.sys dosn't support this device and gives a BSOD. Conclusion: Avoid VEN_*&DEV_* in AC'97 driver packs. Remove Alcxau.inf, keep other Alcxau*.inf files. Or edit Alcxau.inf, remove DriverVer line. PNP prefers other *.inf files now. A proper driver may be loaded. But remember, if PNP dosn't detect another PCI\VEN_*&DEV_*&SUBSYS_*, realtek Alcxau.inf is used. This may result in a BSOD.

What's your ISO filesize now? I guess filesize is below 4 gb now, ignore previous message.

@iainstott What do you include to your Multi-Boot DVD? Sort windows textmode boot files below 4 GB. XP SP2 setupldr.bin access first 4 GB only.

@gratz Does one machine contain one graphic or two graphic cards? Try (one graphic card assumed) @echo off for /f "tokens=1-3* delims=\& " %%a in ('"devcon hwids *CC_0300"') do ( if [%%b]==[VEN_1002] (echo ATI graphic card %%b %%c found &goto :install_ati_graphic_card) if [%%b]==[VEN_8086] (echo Intel graphic card %%b %%c found &goto :install_graphic_card) if [%%b]==[VEN_102B] (echo Matrox graphic card %%b %%c found &goto :install_graphic_card) if [%%b]==[VEN_10DE] (echo Nvidia graphic card %%b %%c found &goto :install_nvidia_graphic_card) ) echo Graphic card not found. goto :eof :install_ati_graphic_card echo Install graphic card. goto :eof :install_nvidia_graphic_card echo Install graphic card. goto :eof :install_graphic_card echo Install graphic card. goto :eof

Cdimage.exe dosn't support ISOLinux. Try ISO9660:1999 at one session. But remember that's case sensitive. BOOTMGR is not bootmgr. Uppercase windows files at hard disk first. Filecase.exe uppercase file names. "Win32 Console Toolbox": http://stevemiller.net/apps/

Alex Kopylov's 'mkisofs -duplicates-once' ignores file name and date stamp. Duplicate files are detected anymwy using md5 checksums. http://www.bcdwb.de/bcdw_e.html

There are limited possibilies with default 2003 SP1 setupldr.bin: -create four primary partitions -copy one image at each partition -run boot code from each partition or: -copy different images at one partition -use different a:\winnt.sif. Change floppy to boot different images.

Do you get a BSOD 0x7b? Idea: CD setupldr.bin require txtsetup.oem files at \I386\$OEM$\TEXTMODE \$oem$\TEXTMODE Try copy \I386\$oem$\TEXTMODE files to \$oem$\TEXTMODE

BCDW 2.01a support XP SP2 setupldr.bin. http://www.bcdwb.de/bcdw_e.html

@andyd What's 100% ? Do you like cdshell, PE and Knoppix? There are different file systems: ISO9660 Level 1: 8.3 file names ISO9660:1999 support files names up to 207 chars Rock Ridge: support files names up to 255 chars Joliet support files names up to 110 chars Non english PE use long files names, not supported by Joliet. PE works, if you use ISO9660:1999. Knoppix require either -ISO9660 and Joliet or -ISO9660 and Rock Ridge. CDshell 1.6 support ISO9660:1999. Use file system ISO9660:1999 and Rock Ridge.

@Bilou_Gateux Strange, version from posted link I get Do you use a NTFS partiton?Another possibility: cygwin dd

@Bilou_Gateux I'm glad, you got boot working. Are you ready for the next step? As jaclaz pointed above, ms use a bootcode "bootstrap code". Bootpart copy 512 byte bootsector only. Recocery Console use C:\CMDCONS\BOOTSECT.DAT, 8 kb. That's bootsector and "bootstrap code". How to use that way? Given a primary active partition c: and a partition e: Grap bootstrap from partition e: http://www.nu2.nu/mkbt/ c:\>mkbt -x -c e: c:\bootstrtap-e File bootstrtap-e is written, filesize 8 kb. Copy recocery console files to e:\cmdcons and edit c:\boot.ini c:\bootstrap-e="Boot e:" /cmdcons Booting recory console from e: is possible. By the way: of course [MassStorageDrivers] section is used, there are: e:\cmdcons\winnt.sif e:\cmdcons\$OEM$ geitonaki found a solution for multibooting WinXP/Win2003: http://www.msfn.org/board/index.php?s=&showtopic=58410 Thanks. Boot different SDI images from one partition: bootstrap-e loads file ntldr. bootstrap-e contains file name ntldr. Copy bootstrap-e to bootstrap-e01 Hexedit bootstrap-e01 offset 514, change ntldr to ldr01. Create file e:\ldr01 (editable w2003 sp1 setupldr.bin) Hexedit e:\ldr01: change winnt.sif win01.sif Edit e:\win01.sif, set another image. Edit c:\boot.ini: c:\boot-e01="Boot e: win01.sif" Repeat above steps and create c:\boot.ini: c:\bootstrap-e01="Bootstrap e: 01" c:\bootstrap-e02="Bootstrap e: 02" c:\bootstrap-e03="Bootstrap e: 03" c:\bootstrap-e04="Bootstrap e: 04" Files exit:

Thanks for detailed list. Blinking cursor indicates, partition 3 is not bootable. Backup data, boot recovery console and run 'fixboot "DriveLetter:"' You don't have to delete that partiton. I doubt, windows version does matter in that case. I used XP SP1 source in may 2004 and XP SP2 source today. There is no difference in minint booting, if I use XP SP2 setupldr.bin or 2003 SP1 setupldr.bin. OF course, SDI booting requires 2003 SP1 setupldr.bin.

@Bilou_Gateux Bootpart use a own partition numbers, starting at zero. Don't use another partition numbers, e.g. MS or MBRFixGUI. Either you selected a wrong partition or your partiton is not bootable. Remenber your pagefile partition size. Boot recovery console: map list your partitions, recognice your pagefile partition. fixboot (your pagefile partition) Bootpart list numbers. Post that numbers. Which command line did you used? Another idea: What's Boot-US boot manager? Boot Boot-US and select your pagefile partition. Next idea: Boot Windows, set pagefile partition actice and reboot. This may fail: keep a boot media by hand to set c: active. @jaclaz Yes, bootpart is not necessary. Thanks. Cygwin dd: $ dd if=//./x: of=c:/bootsector count=1 c:\boot.ini: C:\bootsector="Bootsector X:" PE boots.

@Bilou_Gateux File system dosn't matter. Yes, you can use NTFS. Bootpart.txt section 'Windows NT Multiboot menu' describe this feature. I wrote a bootpart example in May 2004: http://www.911cd.net/forums/index.php?show...indpost&p=38311 BOOTPART list your partitions. 'BOOTPART 1 C:\PEBOOT.BIN WinPE' maybe correct. Compare bootpart partion number. Use filesx:\winnnt.sif x:\RECOVERY\WINPE.SDI You don't have to use drive letter X:. You can assign another drive letter to that partition and use that drive letter, e.g. e: File ntldr is loaded. You can use in different ways: File can be ntldr or renamed setupldr.bin or renamed bootmgr.

Another possibility: boot a primary partition Given a existing primary active partition c: Create a additional primary partition, set drive letter x: Format x:, bootsector loads file \ntldr. Copy files to: x:\ntldr (renamed setupldr.bin) x:\ntdetect.com x:\minint\ (from PE \I386\) Edit C:\boot.ini, chain load bootsector x: Bootpart does create a appropiate boot file. http://www.winimage.com/bootpart.htm Scroll down and read BeOS exmaple. Changed usage: use x:\winnt.sif instead of x:\minint\. That way, you can boot a ISO image or SDI image.

Hardlink use one file, but create different directory entries. To get this at cd, one way is optimization: Read duplicate files twice, create MD5 chechsum for each file, find duplicate files, add file once and create different directory entries. cdimage and mkisofs-mingw32 bootcd-ru (PEBuilder use that version by default). Another solution: use NTFS hardlinks. Read hardlinks, read duplicate files once, add file once and create different directory entries. Cygwin support NTFS hardlinks: mkisofs-cygwin support NTFS hardlinks. Use: 'mkisofs -follow-links -cache-inode ...' The second solution require less CPU calculation.