cdob

Do you use uppercased tagfiles \WIN51 and \WIN51* ?

@icnocop ImDisk does mount a UDF image at command line. http://www.ltr-data.se/opencode.html#ImDisk There is a 64bit port available too.

Isoinfo list boot information from U3 CD-ROM. 'cdrecord -scanbus' list device numbers. Recogince the 'Removable CD-ROM' and the 'Removable Disk'. http://cdrecord.berlios.de/ Win32 binaries: http://www.student.tugraz.at/thomas.plank/ Thanks for confirmation. Unfortunaletly I use old hardware: no U3 boot.

http://openvpn.net/archive/openvpn-users/2...1/msg00341.htmlhttp://www.boot-land.net/forums/index.php?...ost&p=24923 Which RAMDisk driver do you use?

That's a well known troublemaker.Use a edited ntdetect.com http://www.msfn.org/board/-t112630.html&am...st&p=738009

Yes, it's about boot from USB drive. However BIOS has to support fake U3 CD-ROM drive. Some BIOS boot from real USB CD-ROM drive, but not from a fake U3 CD-ROM drive. @mg.eggink Which machine and mother board do you use? @jaclaz I edited Memorex LaunchPad in the past. But BIOS dosn't support U3 CD-ROM drive. Grub4dos booted from U3 data partition: 'cdrom --init' dosn't detect U3 CD-ROM drive too, well no BIOS support.

Slipstream SP3 first. Goto BIOS, disable multicore support.Install XP. Enable multicore support.

http://en.wikipedia.org/wiki/USB_mass_storage_device_classhttp://www.usb.org/developers/devclass_doc...msc_cbi_1.1.pdf USB drive firmware set device class. A BIOS asssumes partition system and file system according to this device class. E.g. CDFS at USB CD-ROM. And a MBR at a USB hard disk. Actually a USB flash drive or a USB hard disk sould work in most cases. This maybe a U3 data partition, that's not the U3 CDFS partititon. I've to corrent myself, there is a 'Universal Serial Bus Mass Storage Specification For Bootability' released in 2004. http://www.usb.org/developers/devclass_doc...sc_boot_1.0.pdf Older hardware dosn't support this specification, newer may support this specification. A hint: Or the other way arround: El Torito CD-ROM boot specification is not used for non optical devices (a average USB flash disk).Almost no sense to format a average USB stick to UDF or CDFS. Approach is out of scope, booting may work or fail. Anyway it's nice to test at different hardware. Try other approaches first.

No, the BIOS contain a basic CD driver. A CD drive dosn't know a file system.There is a Bootable CD Specification http://en.wikipedia.org/wiki/El_Torito_(CD-ROM_standard) http://www.phoenix.com/NR/rdonlyres/98D321.../specscdrom.pdf Different hardware and software manufacturer follow this specification. A CD boot is reliable nowadays. BIOS and boot CD follow this specification. A current BIOS should boot a USB CD-ROM too. However that's not part of Bootable CD Specification, hence it's not supported officially. The BIOS may boot a fake CD-ROM (U3 CD part). Or the BIOS may fail. Remember, there is no USB boot specification. Different manufacturer created different solutions. One USB stick may boot at one machine, but fail at another machine. Some BIOS may even boot a UDF or CDFS file system from USB massstorage. However that's most unlikely. Often a floppy or hard disk is expected at USB massstorage. Remember again, there is no USB boot specification. It is not possible to create a always working USB boot solution. I doubt, formating UDF or CDFS at USB massstorage gives reliable results. I suggest: use a hard disk approach at USB massstorage Or try: UDF or CDFS at fake USB CD-ROM (U3 part)

Hence the BIOS has to handle this USB drive. Site mentiones a SmartDriver device driver. Most likely this driver is required for writing and reading. BIOS won't read this device. CDFS partition is an emulated CD-ROM drive. http://en.wikipedia.org/wiki/U3 U3 firmware emulates the CD-ROM drive. Should be a USB Hub, one USB CD-ROM drive and one USB massstorage device. A average USB stick dosn't support this, a special firmware is required. And BIOS has to support this emulated device. Well, create a image file and copy file sector per sector. Use e.g. dd.However most likely BIOS won't boot from this device. BIOS may fail at UDF or CDFS at USB massstorage device. A idea: prepare a multi-boot ISO image. Write this Image to U3 fake CD-ROM. http://www.911cd.net/forums//index.php?showtopic=19066 http://www.911cd.net/forums//index.php?showtopic=20565

Do you use a stick without U3 feature now? BIOS, USB boot and U3 fake USB CD drive may get strange results.

Actually there are different approaches and different solutions.How do you like to install windows? Local installation from CD or RIS installation are different cases. No, you don't have to include a cab file to I386\. No, don't edit txtsetup.sif. Editing txtsetup.sif is another approach. That's a fine solution too. Well mentioned example use a strange solution.[MassStorageDrivers] [OEMBootFiles] sould copy file already. No need to use OemPnPDriversPath. However example should work too. Some other examples: http://support.microsoft.com/kb/288344/ http://support.microsoft.com/kb/816299/ http://support.microsoft.com/kb/289707/ This copy files twice: \I386\$OEM$ \I386\$OEM$\TEXTMODE This dosn't match CD installation. Find a solution matching your windows installation method.

Setting is missing at txtsetup.oem [sCSI] section. File symmpi.inf is not used that early. Try one single line at [MassStorageDrivers] section [MassStorageDrivers] ; Used when custom disk drivers must be specified ; Enter the description name =Retail or OEM "LSI PCI Fusion-MPT Driver (XP 32-bit)" = OEM No need to add txtsetup.oem to [OEMBootFiles]. Try [OEMBootFiles] ; This section is used to specify custom HALs, and also maps to the Mass Storage Device section lsipseud.inf symmpi.sys symmpi.inf mpixp32.cat

Yes, FBWF driver is missing. That's bad news. Actually idea was to replace winnt32.exe. Basically: copy files yourself and prepare boot environment. So far a rough idea only. Not tested. Contrary your idea should work too. Run winnt32.exe once and create a Image of the HD. Winnt32 dosn't care about HAL. Installation works at uniprocessor and multiprocessor machines.

Well, overall I guess: Setupldr.bin behave different at windows installation and at minint mode. PE read migrate.inf at a device fixed media (internal hd, CD, USB hard disk), but not at removable media (most USB stick). Setupreg.hiv is to be prefered. Works always. @fusan Did you tried tempdrive? @jaclaz I understand gray's statement different: WriteProtect requires FBWF. Rough idea: don't use winnt32.exe. File acess is slow at USB stick. Reading one big file is faster. Copy ISO image to USB stick. (The same ISO image maybe written to CD for installation.) Boot PE. Extract ISO image to hd (run 7-zip or mount with imdisk). Use a primary active partition. Use a ntfs partition. Files goes to \$winnt.~ls$. Hardlink \$winnt.~ls$\I386 files to \$winnt.~bt$. Use boot.ini to boot renamed setupldr.bin. Or use grub4dos and boot \$winnt.~bt$\setupldr.bin.

The classic approach: @echo off set directory=variable\I386\Extras for %%a in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%a:\%directory% start "%%a:\%directory%" Added: I don't understand clearly: How do you create a short cut? A environment variable approach: cmdlines.txt [COMMANDS] CDROM.cmd CDROM.cmd reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment" /v "CDROM" /t REG_SZ /d "%~d0" /fEnvironment variable valid after boot. Or use setx.exe http://support.microsoft.com/kb/927229 Environment variable is active imediately.

@marco70 Read flyakite's again. Follow this guide. But replace SP1 by SP3.

Sorry, bad memory: FBWF plugin is expected too.http://www.911cd.net/forums//index.php?s=&...st&p=133433 Overalll find the error source. Try set tempdrive: X:\xpsetup\i386\winnt32.exe /makelocalsource /syspart:c: /tempdrive:c: /unattend:X:\xpsetup\i386\Winnt.sif

Check flag files cdrom_* and WIN51*. Use e.g. WIN51IP.SP2 for SP2. Flag files has to be twice at DVD: http://flyakite.msfn.org/2000.htm http://flyakite.msfn.org/xpprosp1.htm

fusan@ I don't use a 16GB USB stick. Migrate.inf may fail. Try editing registry: run regedit, load file \minint\setupreg.hiv Add writeprotect setting. Which winnt32 command do you use? Do you set syspart and tempdrive?

This is not a valid line: dword: dosn't work.Try the previous named example. Don't change this for first testings. Sysinerals filemon work at BartPE, if you use a proper plugin. No idea about injecting files after. May work or fail. A log should show cause of 2-5 min delay. BartPE boot from a NTFS USB stick. However BIOS has to support USB NTFS boot first.

You may add a file \minint\system32\migrate.inf to BartPE. Set StorageDevicePolicies at migrate.inf, compare http://www.msfn.org/board/-t61384.html&amp...st&p=638830 How long does delay durate?Are there another write/read acess to USB stick? Did you integrated sysinternals filemon? Do you use FAT32? This may delay file acess at USB stick. Do you use fast USB hardware? Fast access time is more importand, fast transfer speed is next.

Setup search file <cdroot>:\I386\$OEM$\TXTSETUP.OEMDon't use <cdroot>:\I386\$OEM$\Textmode\. Congratulations. How do you install windows? Do you boot from CD?Do you use winnt32.exe?

Try to add AutoLogon [GuiUnattended] AutoLogon=YesI don't get mentioned screen at XP SP3, no edited files added. http://technet2.microsoft.com/windowsserve...d799eb1033.mspx By the way: Do you provide acess for Moondance? http://www.pbase.com/bmcmorrow/image/90681729

Well a hint is http://support.microsoft.com/kb/816299/en-us However Generally follow KB816299, but use different directory names. Textmode winnt.sif [MassStorageDrivers] require files twice at CD: \I386\$OEM$ \$OEM$\Textmode Then winnt.sif [unattended] OEMPnPDriversPath is not required for MassStorageDrivers. Be aware: The name \I386\$OEM$ has to be at ISO9660 file system. ISO9660 Level 1 dosn't allow a $ sign. Adjust your ISO creation tool to break ISO9660. IsoBuster list ISO file system. In addition: do you boot from IDE CD-ROM? Add [MassStorageDrivers] "IDE CD-ROM (ATAPI 1.2)/PCI IDE-Controller" = "RETAIL"Setting is language specific and should match your case. Another approach is txtsetup.sif [sCSI.LOAD] and [*.LOAD] sections. Nlite and driverlacks use this approach.