cdob

Boot order was IDE first. At IDE emualtion the first hd was the WD SATA hard disk. At AHCI mode, the first IDE hard disk is the Maxtor. Hence the ntldr not found. I guess you reconnected the maxtor and changed boot order in the meantime. Yes, there is a time out at ahcix86.sys. The driver wait for late drives.

There are two hard disks. Does the BIOS change load order and try to boot from IDE hard disk? As for testing purposes disconnect the IDE hard disk.

That's at early boot stage, there is MBR, partition boot sector involved so far. There is no windows driver involved so far. Did you changed anything else? May be a strange BIOS. Which hardware do you use?

Which drivers are at hard disk after first reboot? Can you do a favour and upload file system.sav too, again the version after first reboot? I'm rather curious about USB settings.

I used in the meantime [Unattended] UnattendSwitch=Yes OemPreInstall = Yes OemFilesPath = \!OEM!\ There is both a \$OEM$\cmdlines.txt and \!OEM!\cmdlines.txt. \!OEM!\cmdlines.txt is not processed. Instead \$OEM$\cmdlines.txt is processed. Still no solution for OEMFilesPath for CD installs. Using one $OEM$ at hard disk and create several $OEM$ at ISO image application:use mkisofs -graft-points: connect one $OEM$ directory from HD to different directories at CD. Several directories are added at CD, but files themself are added once to CD. A basic -graft-points example mkisofs -o image.iso -graft-points /XP01/$OEM$=$OEM$ /XP02/$OEM$=$OEM$ /XP03/$OEM$=$OEM$ . If you need further examples, name your added windows versions and used directories.

Well, I missed a setting last time. http://technet.microsoft.com/en-us/library...944(WS.10).aspx Did you set OemPreInstall so far?

Use dd or dsfok. http://unxutils.sourceforge.net/ http://www.chrysocome.net/dd http://members.ozemail.com.au/~nulifetv/freezip/freeware/

Nice, a volunteer with nice testing machines. Most machines does find USB at first reboot, however some fails. True reason is unkown so far. Can you try two more applications at first reboot? Mount Storage PE http://www.kare-net.de/plugins.html ShowDrive http://bbs.wuyou.com/viewthread.php?tid=116177 Run the applicaion and use "mnt" to view mapping.

Does USB-CD contain 4.1 GB - 4 GB data? Try a image below 4 GB. No, the fake USB-CD is not writable from a OS. dd can't write to the fake USB-CD.

The CD contains a boot sector too. The option refers to the used boot sector at CD. Typically you use another boot sector at a multi boot CD. As you hard disk is partitioned already, you may ignore the setting. This setting dosn't change hard disk alignment.

I've different experience:NT4 SP1 boot sector and setupldr.bin does work at -iso-level 4. The installation does complete. 2000 SP1 boot sector and setupldr.bin does work at -iso-level 4. The installation does complete. No, you do NOT need UFD bridge for Windows 7. ISO9660 is sufficient.Yes, the -j1 -u1 is another solution. However this require addional space.

Sorry for the confusion. Yes, directories are not sorted themselves. There are Path Table Records at ISO9660. ECMA 119 is also approved as ISO9660. http://www.ecma-international.org/publicat...ds/Ecma-119.htm 6.9.1 Order of Path Table Records request the sort order. Some hardware rely at this sort order. As far as I know all applications create the Path Table Records to the specification. I'm used to set a weight at directory level, mkisofs set this level to all files within this directory and all sub directories. E.g. a weight to I386 includes all files from I386, I386\ASMS\1, I386\ASMS\10 and I386\ASMS\1000 Textmode boot files are sorted in addition. Example: part of sort.txt by mkISO_RAMload_sort.cmd ./boot.catalog 10000 ./bootsect.bin 9990 ./WIN* 9978 ./AMD64/* 1100 ./AMD64/SYSTEM32 9000 ./AMD64/COMPDATA 20 ./AMD64/LANG 1000 ./AMD64/WINNTUPG 1000 ./I386/* 1100 ./I386/SYSTEM32 9000 ./I386/COMPDATA 20 ./I386/LANG 1000 ./I386/WIN9XMIG 1000 ./I386/WIN9XUPG 1000 ./I386/WINNTUPG 1000 ./DOCS -1000 ./DOTNETFX -1000 ./WIN51IP 9899 ./WIN51IP.SP3 9898 ./BOOTFONT.BIN 9897 ./I386/*.SY? 9010 add_copy_sort_files -1 ./I386/_DEFAULT.PI_ 7999 ./I386/1394.IN_ 7998 ./I386/1394BUS.SY_ 7997 ./I386/1394VDBG.IN_ 7996 ./I386/1394VDBG.SY_ 7995 ./I386/8514FIX.FO_ 7994 ./I386/8514OEM.FO_ 7993 ./I386/8514SYS.FO_ 7992 ./I386/61883.IN_ 7991 ./I386/12520437.CP_ 7990 ./I386/12520850.CP_ 7989 add_boot_sort_files -1 ./I386/SPCMDCON.SYS 9896 ./I386/TXTSETUP.SIF 9895 ./I386/BIOSINFO.INF 9894 ./I386/NTKRNLMP.EX_ 9893 ./I386/NTOSKRNL.EX_ 9892 ./I386/BOOTVID.DL_ 9891 ./I386/SETUPDD.SY_ 9890 ./I386/SPDDLANG.SY_ 9889 ./I386/SETUPP.INI 9888 ./I386/KDCOM.DL_ 9887 ./I386/SETUPREG.HIV 9886 ./I386/CTYPE.NL_ 9885 ./I386/LOCALE.NL_ 9884 ./I386/L_INTL.NL_ 9883 ./I386/SORTKEY.NL_ 9882 ./I386/SORTTBLS.NL_ 9881 ./I386/UNICODE.NL_ 9880 ./I386/SETUPLDR.BIN 9600 ./I386/WINNT.SIF 9599 ./I386/BOOTFIX.BIN 9598 ./I386/BOOTFONT.BIN 9597 ./I386/NTDETECT.COM 9596 ./I386/SYSTEM32/$OEM$/* 9596 ./OEM/* 200 ./$OEM$/* 100 ./$OEM$/TEXTMODE/* 9950 Given a ISO9660:1999 disk:MS DOS mscdex.exe find 8.0 upper case directory names and 8.3 upper case file names, longer names are not acessible. Basically all DOS files are accessible. FreeDOS shsucdx does find long ISO9660:1999 names, lower case is possible. No idea about Win9x. Well, I hope this too.Contrary as you indicated already oscdimage with ISO9660, Joliet and UDF is another working approach. Maybe I'm forced to use this file system mix in future.

Old habits: basic sort at directory level. Special sort at file level in addition. I prefer to change as less as possible: set SetupSourcePath and BootPath http://www.msfn.org/board/windows-xp-profe...vd-t126480.html ISO9660:1999 allows a path up to 207 chars. Windows 7 default names are within this limit. If you add custom names longer 207 chars, use UDF. NT4 and up does read ISO9660:1999. ISO9660:1999 dosn't bite you and won't harm.

Do you have lower case names? i386 is not I386 Filecase.exe can uppercase directories and files at hard disk. Create the ISO image next. -iso-level 4 use this names then. http://www.stevemiller.net/apps/ Simple approach: uppercase whole \I386\, \BOOT\ and \SOURCES\ and sub directories. Sorry, only open questions. http://technet.microsoft.com/en-us/library...243(WS.10).aspx http://www.msfn.org/board/index.php?s=&amp...st&p=856888 Does oscdimg support full path only? What about directories and wild cards?

Well I'm using draft ISO9660:1999 since several years. There hasn't been a issue so far. I feel free to name draft ISO9660:1999 as plain. Granted MS uses UDF as default. Maybe most people use this setting too.Well, I prefer own testings. There is no need for UDF so far. NT4, 2000, XP (32bit and 64bit), 2003 and Windows 7 does boot and install from a -iso-level 4 media. Yes, there is ISO-filesystem only. Setupldr.bin and bootmgr find uppercased file names at ISO9660 only. Uppercase required directory and file names. Bootmgr find lowercase file names at UDF. I don't have a explanation. Are both files fully within the 4GB range? Which ERD do you use at all?Most likely there is no UDF driver loaded at boot. This may cause a error too, if you use UDF filesystem. A serupldr.bin ERD does work with -iso-level 4. The RAM laod approach may get different results. A 2003 SP1 setupldr.bin based ERD support RAM loading. Add a proper winnt.sif. Or don't use UDF, but sort required files.

Previously file system ISO9660 and Joliet did work: Windows 7 setup did complete. Tried again: file system plain ISO9660: added one big 5GB dummy file, sorted between boot.wim and install.wim. Install.wim is at end of a 8GB ISO image. Setup does load boot.wim and finish loading files for the gui-based setup. Next there is a error message, no DVD drive found, load drivers. Shift-F10 shows the mounted DVD drive d: big 5GB dummy file added, sorted at end of media. Install.wim is after boot.wim, within first 4GB of media. Windows 7 setup does fully install Windows 7. Windows 7 setup does not require Joliet or UDF. Plain ISO9660 is sufficient. Sort order is importand! Try create a ISO file below 4GB. Be aware: Cdimage sort by directory deep, Win32 ASMS files goes to end of media. Do you have a link?http://en.wikipedia.org/wiki/Universal_Dis...tive_OS_support Windows 98 can read UDF 1.02. Windows 2000 file system driver udfs.sys can read UDF up to 1.50. This includes UDF 1.02. Windows 2000 udfs.sys can't read UDF 2.0 and up. A DVD-Video uses UDF 1.02. Windows 2000 can read a UDF at a DVD-Video. The firadisk floppy image should work at ERD.

Yes, setupldr.bin/ntdetect.com dosn't like -udf. Just croschecked Windows 7 does intall fine.Maybe there is another reason. There is a72 ftp://ftp.berlios.de/pub/cdrecord/alpha/ Did you compile the version? Do you use cygwin or mingw32 environment? -follow-links and -cache-inodes is default enabled since several years at cygwin environemnt. Isn't winload.exe part of boot.wim? When do you get the missing winload.exe? Do you sort boot.wim too? Setupldr.bin access first 4 GB of media. No idea about bootmgr. What's your final ISO file size? http://www.msfn.org/board/multiboot-erd-co...pid-902469.html Another approach to XP32 / XP64 layout http://www.msfn.org/board/windows-xp-profe...vd-t126480.html A approach to create a sort list file, single boot so far. mkISO_RAMload_sort.cmd http://www.msfn.org/board/7-t137714.html BTW: -iso-level 3 and up support files greater 4GB.

Integrate a registry setting to setupreg.hiv http://www.msfn.org/board/index.php?s=&showtopic=75713

That's nice. Can you try again? map (hd0) (hd1) map (hd1) (hd2) map (hd2) (hd0) There is after map: hd0: target drive hd1: USB source drive That way resembles the default USB boot with a single hard disk.

I understand so far: There is without mapping hd0: Windows 7 drive hd1: target XP drive with BIOS mapping, active at hard disk boot. The second hard disk goes to hd0 hd0: target XP drive hd1: Windows 7 drive However the BIOS igores hard disk swap at USB boot. At USB boot there is: hd0: USB drive hd1: Windows 7 drive hd2: target XP drive XP setup writes boot data to hd0. Map the target XP drive to hd0. Try at first USB boot. map (hd0) (hd2) map (hd2) (hd0) Don't insert a cat line, or delete the added line.

Then watch for relating onboard drivers. There is a NVRAID controller. Continue at http://www.msfn.org/board/integration-nvid...ers-t51140.html You may “slipstreamed” cd on another pc.

I understand you boot from cd or dvd on ide. There is a NVRAID controller onboard. http://www.tyan.com/archive/products/html/thunderk8we.html Which target drive do you like to use? Is the on card: "siig" a addional PCI card? Like http://www.siig.com/ViewProduct.aspx?pn=SC-SA4R12-S2 Then add relating siig drivers as textmode drivers. Can you run and port the result? devcon.exe hwids *cc_01* *raid* *scsi*http://support.microsoft.com/kb/311272

Tried at XP SP3 again: Directories [Data] MsDosInitiated=No [Unattended] UnattendSwitch=Yes OemFilesPath = .. ;OemFilesPath = ..\ ;OemFilesPath = ..\$OEM$ ;OemFilesPath = $OEM$ ;OemFilesPath = D:\ ;OemFilesPath =\\.\D:\ \$OEM$\cmdlines.txt is ignored, contrary XP01\$OEM$\cmdlines.txt is processed. Does OemFilesPath work at "MsDosInitiated=Yes" only? At multboot: add the $OEM$ files once to CD but add several links to the same file.Optimize the layout at CD: duplicate files are once at CD. Or create a junction to $OEM$ at hard disk first. Create the ISO image next. Or create one $OEM$ at hard disk. And create several $OEM$ at ISO image application.

What is *not* there: - any mention of relative or absolute paths - any mention of a difference between CD or RIS installs, setup.exe and winnt32.exe Yes, deploy.chm dosn't refer to a multi boot cd. Setup dosn't search at root, hence the files are not copied.Nonetheless, the relative path OemFilesPath="..\$oem$" may work. File copy and OemFilesPath are two different cases. If you like a non default copy path, you have to copy the files yourself. Add a command at unattended mode. Flyakite suggest $oem$ beside I386, not in root.Why do you use $OEM$ at root? Is there any special reason? What's the general request?

At XP 32 bit a dir does behave different. Open a command prompt and run "dir I:". There is a command line message displayed only, but no "No Disk" window. In addition there is errorlevel set internally: therefore the following && find is not executed. Finally: "No Disk" window is not displayed. Try too: remove find FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y) DO ( FOR %%j in (%ISO_file_search%) DO ( echo search ISO file "%%i:%%j">>presetup.log DIR "%%i:%%j" && ( SET ISOfile=%%i:%%j goto :ISO_file_found) ) )