cdob

Install XP from a ISO file. Use a original ISO file. Or use a custom version, e.g. integrate mass storage drivers. No RAM disk used. Usefull at low RAM machines and slow USB BIOS speed. http://reboot.pro/8168/New winvblock 2011-01-23 version maps a ISO file from a USB drive. Thanks Sha0. Windows setup recognice ISO file as a CD: Installation is possible. This is experimental so far: use a current development version http://github.com/Sha0/winvblock/commits/master/ Create a floppy image winvblock.ima Create a bootable USB drive. Grub4dos menu.lst title 1 Start Windows XP setup map /winvblock.ima (fd0) map /winvblock.ima (fd1) map /Inst/XP_RAM.ISO (0xff) checkrange 0x80 read 0x8280 && map (hd0) (hd1) checkrange 0x80 read 0x8280 && map (hd1) (hd0) map --hook chainloader (0xff) title 2 Continue Windows XP setup map /winvblock.IMA (fd0) map /winvblock.ima (fd1) map /Inst/XP_RAM.ISO (0xff) checkrange 0x80 read 0x8280 && map (hd0) (hd1) checkrange 0x80 read 0x8280 && map (hd1) (hd0) map --hook chainloader (hd0)+1Boot twice from USB drive. Use continuous files. Wincontig does defragment files: http://wincontig.mdtzone.it/ A default XP SP3 ntdetect.com did work at a old AMI BIOS, 256MB RAM. Flat file PE1 booting results to a 0x7b at this BIOS. Other machines has to be tested. Happy testing.

Yes, this works. I'm used to grub4dos, read original setupldr.bin and edit setupldr.bin in RAM. No need to hex edit a file at build time. Compare post And to use three boot files only Edit txtsetup.sif, adjust SetupSourcePath and create BootPath: [SetupData] SetupSourcePath = "\XHO1\" BootPath = \XHO1\I386\ XP 64 example

http://web.archive.org/web/20071007000721/www.cdshell.org/ CDshell is not supported since 2005. In addition web page is down. Time to use another boot loader?

Just do it. If booting fails, goto BIOS and set IDE mode again. There is no harm. Of course a backup is recommended, as always. You don't have to use ID=2922, use a generic Intel AHCI HardwareID: CriticalDeviceDatabase\pci#ven_8086&cc_0106 Approach did work at countless machines in the past.

This require a appropiate chipset and BIOS, e.g. mentioned Gigabyte EP43-UD3L However, not all BIOS support this. This assumes, your windows disk is connected to SATA Port 0-3. SATA Port 0-3 are at IDE emulation still. Addional SATA ports use AHCI mode. Windows booting works, because it's booting a IDE disk still. describes a work around at selected hardware. In addition: 6) If you like Windows using AHCI mode at system disk: reboot, goto BIOS SATA Port 0-3 Native Mode [Disabled], reboot BIOS dosn't support mixed mode IDE - AHCI. Import registrry settings to running XP first and copy iastor.sys first.

Thanks for explanation. Yes, this explains it: running at Intel CPU adds intelppm.sys. Sorry to ask again, can you clarify this once more. I haven't run a VMWare machine at AMD CPU so far, hence I'm curious. Didn't you used a VMWare machine? Does a VMWare machine emulate a CPU? Did you run this VMWare machine at a host AMD CPU machine or a host Intel CPU machine? Back from 2005 http://communities.vmware.com/message/165289 Did this changed in the last years?Some more image settings, e.g. agp, PS/2 and USB mouse and keyboard http://www.911cd.net/forums//index.php?showtopic=22092

Can you clarify: which part did include intelppm.sys? Did you boot standard image at AMD processors only? Did you boot standard image at a Intel processor? Did you include intelppm.sys manually?

Does this image load intelppm.sys at default? http://support.microsoft.com/kb/953356/ Set driver intelppm to demand start=3.

Simple words require understanding. Understanding require basic knowldege. First post explains used solution. May be you call this a summary. From first post, second line This implies you have to know F6 floppy disks. This exist since about 15 years. I consider a F6 floppy basic knowledge as for a windows installation. Back then some manufacturer delivered a real driver floppy. If you don't know a F6 floppy, you won't understand internal details. Learn TxtSetup.oem File Format New: setupldr.bin read a virtual floppy too. Did you learn this so far? FiraDisk is loaded at txtsetup.oem. Read txtsetup.oem to learn the details. And more files are copied from txtsetup.oem. If you like the details, read txtsetup.oem. A fake setup.exe is injected. Windows install launch this at first reboot. Setup.cmd is launched. Setup.cmd installs ImDisk.

Learn basic windows installation from CD first. Learn driver integration. Learn fake setup. Learn real floppy usage. Learn F6 requirements. Learn batch files next. All is available here at msfn.org since several years. Read the whole thread. Print it out, read all lout, use a pencil and write the text. Open floppy image, read txtsetup.oem and read setup.cmd. No, after first reboot there is no RAM disk anymore.RAM is cleared at reboot. ISO file is read from USB drive. SATA drivers are loaded at textmode and PNP added at GUI mode. TEXTmode is very first boot: black back ground and blue back ground with TEXT messages. It's about RAM usage and more.If you use FiraDisk only, you have to RAM load twice. Feel free to use this or not. Remember: OS manufacturer dosn't support this. Different BIOS gives different results.There are other approaches too. There is no one size all solution. Try all sticky threads.

Yes, that's setupldr.bin default behaviour. A floppy txtsetup.oem is processed by default, no need to press F6. at first reboot. At text mode. At very first boot only. Windows support native ISO: read CD like drives. A CD drive is not a ISO file. That's a major difference. No default windows driver can open a ISO file. Installation fails, because installation files are missing. Third party drivers are required to read ISO files.

Strange: why was a new drive letter created? Can you try another one Addional cmd.exe is run within first hidden console.And another one more, remark above start line and set

Long shot: don't use iastor.sys version 9.x.

Read the sticky thread How to boot/install from USB key ? - the historical thread - how it all began

Which hardware, BIOS do you ue? Compre first message, try set fd1 #(fd1) optional, required at some BIOS map --mem /Inst/XP_INST.IMA (fd1)

Which Run window do you use? Which OS do you use?Run XP to slipstream a XP SP. Unclear still: slipstream error or USB boot error. Verify slipstreamed XP first. Create a ISO file. Burn a CD. Make a test installation. Anyway: which hardware do you use? Motherboard, BIOS, USB device, USB storage size

How do you slipstream? As for testing purposes: did you create a ISO image? can you install XP SP3 using this ISO image? (CD or vitutal machine) MSVCIRT.DL_ contains msvcirt.dll too. This may lead to confusion.Do not use MSVCIRT.DL_ and msvcirt.dll. Delete older file. This goes to all file pairs.

In addition I'm convinced out of experience, no full proof so far: (often I've access to testing hardware short time only, fixing a special problem is more important) certain BIOS access first part of USB drive only. There is no fixed size, can be 512MB, 2GB, 8GB or another Imagine a BIOS access first 512MB only. Basic windows boot files are withing first 512MB. Basic booting and installation does work. Imagine a winnt.sif at end of 2GB drive. Setup won't read the file winnt.sif. File layout is important at media.

It's known: some BIOS dosn't like grub4dos MBR. Other BIOS will fail at partition size, file LBA. And there are more reasosns. Most likely there are different BIOS and different causes. So far any reason is possible. Test very thoroughly, make notes: which version works at which machine, which BIOS and version.

As for testing purposes: can you use another USB media? can you empty and create a single 120GB partition at 500GB hard disk? Was grub4dos integrated to MBR? Use a windows default MBR at hard disk and add grub4dos to partition boot code. Or replace MBR boot code with mbr.bin from syslinux project.

Nonetheless describe boot behaviour.Make / let make pictures. Which messages are displayed? Even a blinking cursor is a hint. That's greater 128GB. Some BIOS does support 48 bit LBA internally, but dosn't support 48 bit LBA at USB boot. Did you create one 500GB partiiton? Did you create several partiitons? Are all installation files within first 128GB of hard disk? How does this BIOS handle a USB hard disk?Added: A WD Elements Portable SE firmware set idle mode within seconds by default: platter stands still. This could be another issue at some BIOS. Try another USB boot hardware too.

@Cosmin3 Increasing success from 95% to 100% is a simple as a Perpetuum Mobile. Increasing success from 95% below 100% require detailed information. Name computer model (read the labels outside), motherboard and BIOS. Which USB HDD do you use? Different size may get different results.

How do you intend to do this?Do you like to use one partition still? Do you like to use several partitions? Did you created several partitions already? Windows 7 find first partition at a "Removable" drive. A driver can set this to a "Fixed" drive: all partitions available Source code http://www.codeproject.com/KB/system/soviet_direct_hooking.aspx 32 bit driver does work at Windows 7 32 bit PE. Can you or another member compile a 64 bit version?

Read MSFN Forum Rules 1.a http://www.msfn.org/board/index.php?showtopic=18408

How much RAM does support hardware? Which motherboard do you use? Which chipset do you use? Which processor do you use?