cdob

setupORG.exe from XP Source slipstreamed with DriverPacks is a renamed ORIGINAL setup.exe: new name setupORG.exe This approach and naming goes back to Pyron http://www.msfn.org/board/solved-drivers-cd-t12566.html Acutally I assumed, you copied setupORG.exe from XP Source slipstreamed with DriverPacks to the floppy image. And wondered about the error report. Added: Idea for full BTS support: Given a sorted ISO image, OEM at end of ISO image. Use grub4dos map to load first part to RAM only. Does grub4dos support loading half a file? Added 2: Example: load the first 234567 sectors to RAM. Remember one CD sector holds 2048 byte data title Loading XP RAM install - /Inst/XP_RAM.ISO (0xFE)+234567 ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) map /Inst/XP_RAM.ISO (0xFE) map --hook map --mem (0xFE)+234567 (0xFF) map --hook chainloader (0xFF)/I386/SETUPLDR.BIN Added 3: Just to confirm. Yes, the idea does work. You may add several hundred megabyte data with BTS driverpacks method 2 to end of ISO image. And you may RAM load first part of ISO image only. Driverpacks addon won't require more RAM usage. Windows installation does work.

Watch for a flag file \WIN51*.SP2. Case is importand.

The work arround work for a single driver at a single setting. Default iastor.sys expect to use F6 and select a appropiate line. Default match one setting only, a lot of HardwareID are not supported that way. [Defaults] scsi = iaStor_8ME9MEPCHM ;############################################################################# [scsi] ; iaAHCI.inf iaAHCI_ESB2 = "Intel® ESB2 SATA AHCI Controller" iaAHCI_7RDH = "Intel® ICH7R/DH SATA AHCI Controller" iaAHCI_7MMDH = "Intel® ICH7M/MDH SATA AHCI Controller" iaAHCI_8RDHDO = "Intel® ICH8R/DH/DO SATA AHCI Controller" iaAHCI_8MEM = "Intel® ICH8M-E/M SATA AHCI Controller" iaAHCI_9RDODH = "Intel® ICH9R/DO/DH SATA AHCI Controller" iaAHCI_9MEM = "Intel® ICH9M-E/M SATA AHCI Controller" iaAHCI_10DDO = "Intel® ICH10D/DO SATA AHCI Controller" iaAHCI_10R = "Intel® ICH10R SATA AHCI Controller" iaAHCI_PCHM = "Intel® PCHM SATA AHCI Controller 4 Port" iaAHCI_PCHM_1 = "Intel® PCHM SATA AHCI Controller 6 Port" iaAHCI_PCH = "Intel® PCH SATA AHCI Controller" ; iaStor.inf iaStor_ESB2 = "Intel® ESB2 SATA RAID Controller" iaStor_7RDH = "Intel® ICH7R/DH SATA RAID Controller" iaStor_7MDH = "Intel® ICH7MDH SATA RAID Controller" iaStor_8R9R10RDOPCH = "Intel® ICH8R/ICH9R/ICH10R/DO/PCH SATA RAID Controller" iaStor_8ME9MEPCHM = "Intel® ICH8M-E/ICH9M-E/PCHM SATA RAID Controller" Actually this was my intention back then: http://www.boot-land.net/forums/index.php?...ost&p=76974 Old Firadisk version didn't support this back then, but does it now.Yes, firadisk is the missing driver. Add firadisk to the floppy image. There is no need to edit boot.ini. At F6 load three drivers, firadisk and the two hardware drivers. Add firadisk.sys to root directory TxtSetup.oem File Format http://msdn.microsoft.com/en-us/library/ms794587.aspx ;to section [scsi] firadisk = "FiraDisk Virtual Disk" [Files.scsi.firadisk] driver = d1, firadisk.sys,firadisk [Config.firadisk] d1 is a example, has to be set at Disks section. Example menu.lst title nvgts.ima firadisk map --mem /Inst/nvgts.ima (fd0) map --hook chainloader /SETUPLDR.BIN To summary: A addional driver is requiered for full F6 virtual image Contrary the double floppy (fd0) (fd1) approach is nice for most drivers. Remember F6 wont work, edit [Defaults] section to your needs.

Files are read from RAM, hence the fast file copy.The extra reboot is by intention, USB support is added. Maybe selectable in future. DriverPacks are not supported yet. This is not a default XP ISO image.Yes, there are parts for testing included. This part is not documented. Technically it's insane to load this 7z files to RAM. Including mass storage and chipset packs may make sense. Contrary it's insane to include all driverpacks to ISO image. A huge data is loaded to RAM, without usage. Haven't made a decision so far.

A addional hint: firadisk F6 floppy image does work at a PE too. Twice was the work arround without full floppy firadisk support. Compare http://www.msfn.org/board/index.php?s=&amp...st&p=881138 This is not necessary anymore at firadisk 0.0.1.12. Once is sufficient now map --mem /Inst/XP_INST.IMA (fd0)

Well, maybe I should have mentioned, first release is 32 bit only.There are 32 bit drivers and a 32 bit fake setup.exe included so far. The included fake setup source code does compile at 64 bit mingw environment. Use a 64 bit fake setup.exe to edit a 64 bit $winnt$.inf. I like to solve F6 loading first, then create a 64 bit version. Some patience please. Been there already and failed so far. ImDisk is arround since some years, works pretty stable. Yes, firadisk is set to start=0. It seems to be possible, to use boot.ini in future. Or firadisk support registry in future.Anyway you have to set ISO image location XP_RAM.ISO. This maybe difficult to set a unique location within txtsetup.oem (current approach should work at multi DVD too). Added: F6 does work with new firadisk 0.0.1.12.

Install XP from a RAM loaded ISO image. Use a default XP ISO image. Addional files are at a F6 virtual floppy. After years of search a new driver is developed: FiraDisk: File/RAM Disk driver for Windows. http://www.boot-land.net/forums/index.php?showtopic=8804 The driver is at early development. The driver does mount a grub4dos RAM drive. That's awsome and can be used at a lot of conditions. Use grub4dos to load a virtual floppy and XP installation image to RAM first. The virtual floppy is used at F6 stage. 32 bit FiraDisk drivers are loaded by default.You don't have to press F6. You may press F6 to get selection choice. There is a fake setup.exe used after first reboot. The idea is used from drivers from CD The integrated version is changed: this fake setup.exe launch a batch setup.cmd. There are includeded the source code, a hidden window processed setup.exe. And a visible window debug version setup_dbg.exe. To use this version rename this to setup.exe. The fake setup calls the original, renamed setup: setupORG.exe The original version is not includede. Therefore edit the floppy image and add the file: Expand setup.ex_ from your windows version expand.exe SETUP.EX_ setupORG.exe copy the file to \setup\I386\setupORG.exe or \setup\AMD64\setupORG.exe BTS DriverPacks method 2 are supported. http://driverpacks.net/ This use a fake setup and setupORG.exe too. If you use a DriverPacks version, copy this setupORG.exe to floppy image. You may add a file \WINNT.SIF too. Used files at USB: \Inst\XP_INST.IMA \Inst\XP_RAM.ISO A basic XP_INST.IMA is attached. Add setuporg.exe as described. XP_RAM.ISO is a default XP ISO image. This file is loaded to RAM. grub4dos menu.lst title Loading XP RAM install - /Inst/XP_RAM.ISO ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #(fd1) optional, required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) map (hd0) (hd1) map (hd1) (hd0) map --hook chainloader (0xFF)/I386/SETUPLDR.BINAssumptions: hd0 : booted USB device hd1 : windows target device Tested at virtual machine. Has to be tested at real hardware: several hard disks, several USB drives, internal multi card reader As wimb indicated, comment this if you read and install to the same hard disk. #map (hd0) (hd1) #map (hd1) (hd0) XP installation from CD and remapped drive order: Files are not deleted from installation media. Setup creates a valid boot.ini. No need to fix boot.ini. Boot once from USB. Setup may assign letter c: to another device. C: is not available for new installed windows. Setup.cmd deletes MountedDevices. At reboot windows assign letters again: c:\windows txtsetup.oem copy a flag file fixDrive.USB to activate this behaviour If you don't need this behaviour, comment the lines ;dll = setup, fixDrive.USB Setup.cmd uses ImDisk to mount the ISO file. http://www.ltr-data.se/opencode.html#ImDisk The name \Inst\XP_RAM.ISO is the internal default. The name can be configured: The floppy image contains a file \setup\ISOimage.ini. Edit this file. Next the file $winnt$.inf is adjusted. Windows setup continues and use the mounted ISO file. Install from USB to USB is possible too. This part based on Dietmar's tutorials. http://www.winusb.de Read \USB32\to_usb.txt for details. At windows setup press F6 and load firadisk and all usb drivers. In addition there is optional approach to lower RAM usage, e.g. use a 600mb image at 512mb RAM. Integrated mkISO_RAMload_sort.cmd creates a sorted ISO image: boot and textmode files are in front of media. Mkisofs.exe, dd.exe and gsar.exe are used to the create the ISO image. http://cdrecord.berlios.de/private/cdrecord.html http://www.student.tugraz.at/thomas.plank/ dd.exe http://www.chrysocome.net/dd gsar.exe http://home.online.no/~tjaberg Given a sorted ISO image, OEM at end of ISO image. Use grub4dos map to load first part to RAM only. Integrate all \I386 and \AMD64 files. IsoBuster Free does list LBA (Logical Block Address) of files. http://www.isobuster.com/license-models.php The LBA show the file location. Calculate N: LBA of file and add file length Use this number to load image to RAM. Example: load the first 234567 sectors to RAM. Remember one CD sector holds 2048 byte data title Loading XP RAM install - /Inst/XP_RAM.ISO (0xFE)+234567 ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) map /Inst/XP_RAM.ISO (0xFE) map --hook map --mem (0xFE)+234567 (0xFF) map --hook chainloader (0xFF)/I386/SETUPLDR.BINXP_RAM.ISO has to be continuous, defrag a splitted file. v02: firadisk updated: map to (fd0) only. F6 does work 64 bit prepared, unfortunately BSOD 0x7b at 64 bit firadisk added flag file fixDrive.USB added config file ISOimage.ini under construction: install from USB to USB v03: added: install from USB to USB added: added sorted files added: multiboot ISO image, sub directory v04: ISOimage.ini is enabled by default enhanced: sorted files, experimental RAMboot.lst created v05: update: firadisk and imdisk driver - flat file possible in addition if required, USB drivers loaded at a addional reboot v06: major redesign: One driver only - firadisk no need to include setup.exe in floppy image XP_INST_v04.7z XP_INST_v05.7z XP_INST_v06.7z

At second glance, setup dosn't support this kind of virtual floppy fully. Read: the virtual floppy is processed automatic, you can't use F6. Setup dosn't find the virtual floppy. You have to adjust txtsetup.oem [Defaults] SCSI entry. http://msdn.microsoft.com/en-us/library/ms794593.aspx And there are drivers pair http://http.download.nvidia.com/Windows/nF...Shield_UGv5.pdf This requires to load two drivers "NVIDIA RAID CLASS DRIVER (required)" "NVIDIA NForce Storage Controller (required)" The question is open still: how to use a full supported F6 virtual floppy?

It's more than 5 days, more several years, actually since d4vr0s's message http://www.911cd.net/forums//index.php?showtopic=20543And real worse http://www.911cd.net/forums//index.php?s=&...st&p=152244I prefer to learn to correct false knowledge. I just installed XP from a RAM loaded image. A default XP ISO image was used. Addional files are at a F6 virtual floppy.

The winner is grub4dos, no addional driver required. fujianabc described virtual floppy usage http://www.boot-land.net/forums/index.php?...ost&p=77011 A VMware SCSI example: title Install XP, load VMWARE disk drivers map --mem /VMSCSI.IMG (fd1) map --mem (md)0x6000+800 (fd0) map --hook dd if=(fd1) of=(fd0) count=1 chainloader /SETUPLDR.BIN VMSCSI.IMG contain files txtsetup.oem and relating files, that's at given example disk.tag, vmscsi.cat,vmscsi.inf and vmscsi.sys. At windwos boot do NOT select F6, setup load the files by default.

Actually I dislike the current work around, that's not a nice solution. I seek and prefer a ParentIDPrefix explanation still. I addition searching the net I found further hints: a digital camera and MP3 player use ParentIDPrefix&6. Even some memory sticks seems to use ParentIDPrefix&6. Do we support install XP from a digital camera? This would require ParentIDPrefix 6 7 8 and all possible combinations. Seems redicilous. I realy, realy like to get a ParentIDPrefix explanation. I prefer to get some further custom reposts. Sorry, therefore I won't add W: currently. Any clean solution is highly welcome, has to support running Winwos 2000, XP, Vista and 7.

http://downloadcenter.intel.com/Detail_Des...l*〈=eng There is a addional file: STOR_AllOS_MRUSetup_1.2.0.7100_PV_Marvell.exe does contain the Marvel xtsetup.oem.

Thanks, U: was expected at your machine. Remember ParentIdPrefix 8&35debb9c&0 is used at current running windows and new installed windows. S: should work at cases, if a change is required. Compare http://www.msfn.org/board/http-msfn-org-bo...p;view=findpost

Poor Poor Macster, sorry couldn't resist too. A new tester volunteered. I haven't found a full ParentIdPrefix explanation. Windows store drive letter at HKLM\SYSTEM\MountedDevices. Migrate.inf contains these drive letter settings. Assumption: current running windows and new installed use the same MountedDevices string. This assumption is false today. E.g. Windwos 7 use a different MountedDevices. http://www.msfn.org/board/index.php?s=&amp...st&p=863404 A string RemovableMedia#7&*&0 is used very often. There is a example machine with ControlSet007 http://www.msfn.org/board/index.php?s=&amp...st&p=852520 A new installed windwos use Old and new windows crates different ParentIdPrefix.RemovableMedia#8&*&0 hat to be changed to RemovableMedia#7&*&0. Another example shows a different behaviour http://www.msfn.org/board/index.php?s=&amp...st&p=880180 ParentIdPrefix 8&35debb9c&0 is used at current running and new installed windows. This is different to the previous example. A clear solution is missing so far. @ilko_t I've only RemovableMedia#7&*&0. U: and W: is a good idea as a work arround. Added: I've found a machine with NextParentID 1168ba30.7 reminds to ParentIdPrefix 7&1168ba30. And the dword seems to be a counter to RemovableMedia#?&*&N New assumption: this counter is set to zero at new installation. If a error occour (bad connections) and windows redetect the hardware, this counter is increase by one. Added 2: Overall there is a new approach, set up to three letters. Thanks to ilko_t. U: MountedDevices as read from current running windows, XP style assumed T: RemovableMedia adjusted: counter set to zero: RemovableMedia#?&*&0 S: RemovableMedia adjusted: counter set to zero and 7 set: RemovableMedia#7&*&0 MkMigratgeInf_c.cmd

That's fine. Continue.

@Macster Which ParentIdPrefix does USB Thumbdrive use at regular windows?

That's broken hardware. First suspect capacitors at PSU or motherboard.

You may use grub4dos to load virtual floppy to RAM. Textmode part does find the file and use them. However windows setup copy part won't find the files using windows drivers. I don't known a virtual floppy available at windwos setup. There are two drivers under cunstruction currently. Currently integrate the drivers to your windows files.

All mentioned tools can handle the partition boot record, hence the *VOLUME* Boot Record. I did NOT recommend the MBR so far. E.g. dd if=//./x: read data from partition x:. Partition x: start with the volume boot record. If you like first 16 sectors from partition d:, you have to set count=16. dd if=//./d: of=c:/bootsector count=16 http://www.nu2.nu/mkbt/ What about using expert mode? BOOTSECT.DAT is edited in addition, the string ntldr is changed to cmldr. Yes, it's often LBA 64, given often a 63 sectors mapping is used.However, most likely it's another LBA for second partition at first hard disk.

Why don't you use mkbt.exe? http://www.nu2.nu/mkbt/ Besides there is dd. E.g. http://www.chrysocome.net/dd dd if=//./x: of=c:/bootsector count=1 dsfok http://members.ozemail.com.au/~nulifetv/freezip/freeware/ and bootpart http://www.winimage.com/bootpart.htm http://www.msfn.org/board/index.php?s=&amp...st&p=400021 In addition: D: has to be a primary partition.

Format partition d: using windows default tools. Extract the boot code from partiton d: to a file. Copy this file to c:\. This has to be the same hard disk. Add this file to c:\boot.ini. http://www.msfn.org/board/boot-pe-hard-drive-t53366.html WinPE 1.x use directory \minint at hard disk. Copy \I386 to \minint. Boot sector file launch file d:\ntldr: copy d:\minint\setupldr.bin to d:\ntldr And copy d:\minint\ntdetect.com to d:\ntdetect.com.

This goes if you build from scratch. You don't need this parts.Boot existing WinPE2.0 and run USB_XP_Setup.exe.

There is no final answer. Use a file system supported by your hardware, by the BIOS. Some BIOS dosn't boot from NTFS. Try NTFS, FAT32, or even FAT16.

As USB booting is involved, different machines may result different results.Given a BIOS without USB boot support. And USB booted with PLoP Boot Manager: XP setup does read files from a CD drive and write to a internal hard disk: no USB drives involved Setup dosn't add USB drivers. USB drivers are not loaded at first reboot, there is no USB drive available at first hard disk boot. :set_usb_boot_setting does add USB boot settings at first hard disk boot. The USB drive is available at hard disk second boot. Contrary there is UsbBootWatcher.exe prepared too. This maybe useful at USB boot friendly BIOS, target USB device. Assumption setup adds USB drivers for first hard disk boot. Not tested, under construction.

No, it's not a boot sector propblem. Different OS may get diffrent results the same way. XP setup dosn't boot from USB that way. Use another approach: http://www.msfn.org/board/index.php?showforum=157