cdob

This refers a outdated version and dosn't mention development source. Solution was developed here at msfn. Current version http://www.msfn.org/board/index.php?showforum=157

File read speed maybe fast. However: File and Directory Descriptors are at begin of a session. If you add a big file: User data are at end of media. File access time is pretty slow. Acessing a lot of files require a lot of full stroke. This result to a slow drive. I doubt this. Which Iso does force the file sort order?http://www.ecma-international.org/publicat...ds/Ecma-119.htm Section '9.3 Order of Directory Records' set sort rules.This is similar to the table of contents of a book. This are not the files. File sort order itself is not ruled. You may change file order. A general PE example http://www.911cd.net/forums//index.php?showtopic=6869At least textmode part should be similar. I don't know a full example for a windows installation. Dosn't setup parse dosnet.inf ? Parse dosnet.inf too, add to the sort file. Parse txtsetup.sif, adjust the sort file.

@imalone Compare: How to install an x64-based version of Windows Server 2003 by using an x86-based Windows Preinstallation Environment http://support.microsoft.com/kb/925279/

I don't use Nero Burning Rom. I don't dare to burn italian capital city Sounds reliable, should work.Break, let me try myself again: Previous mentioned iastor v8.6 floppy files. Your settings to winnt.sif [Unattended] OemPreinstall=Yes DriverSigningPolicy=Ignore NonDriverSigningPolicy=Ignore DriverSigningPolicy=Ignore OemSkipEula=Yes [Data] MsDosInitiated="0" [MassStorageDrivers] "Intel(R) ESB2 SATA AHCI Controller" = OEM "Intel(R) ICH7R/DH SATA AHCI Controller" = OEM "Intel(R) ICH7M/MDH SATA AHCI Controller" = OEM "Intel(R) ICH8R/DH/DO SATA AHCI Controller" = OEM "Intel(R) ICH8M-E/M SATA AHCI Controller" = OEM "Intel(R) ICH9R/DO/DH SATA AHCI Controller" = OEM "Intel(R) ICH9M-E/M SATA AHCI Controller" = OEM "Intel(R) ICH10D/DO SATA AHCI Controller" = OEM "Intel(R) ICH10R SATA AHCI Controller" = OEM "Intel(R) ESB2 SATA RAID Controller" = OEM "Intel(R) ICH7R/DH SATA RAID Controller" = OEM "Intel(R) ICH7MDH SATA RAID Controller" = OEM "Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller" = OEM "Intel(R) ICH8M-E/ICH9M-E SATA RAID Controller" = OEM "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL" [OEMBootFiles] TXTSETUP.OEM iaahci.cat iaAHCI.inf iastor.cat iaStor.inf IaStor.sys XP files are at directory Thinkpad. Iastor floppy files copied to I386\$OEM$. Read: there is a I386\$OEM$\TXTSETUP.OEM Boot sector file (Microsoft Corporation.img) copy and renamed to Thinkpad\bootsect.bin. That's file bootsect.bin, not BOOTSECT.BIN. ISO image created: mkIsoThinkpad.cmd mkisofs -iso-level 3 -U -D -force-uppercase -volid "XP_SLP_LENOVO" ^ -b bootsect.bin -hide bootsect.bin -hide boot.catalog ^ -no-emul-boot -boot-load-size 4 ^ -graft-points ^ -o Lenovo_OEM.iso ^ Thinkpad /$OEM$/Textmode/=Thinkpad\I386\$OEM$Read directory Thinkpad goes to CD root. And directory Thinkpad\I386\$OEM$ goes to CD \$OEM$\TEXTMODE. http://smithii.com/files/cdrtools-2.01-bootcd.ru-w32.zip Virtual machine does boot. Iastor files are copied to hard disk. Real machine does boot. There is a hard disk connected to iastor. Installation F3 aborted at partition menu.

Method does work. However there are addional requirements. Setupldr.bin read CD at textmode setup. Setupldr.bin read file system ISO9660 only. A Joliet file system is ignored that early. $ is a invalid char according to ISO9660 Level 1. You have to break ISO9660 anyway, to create a NT based boot CD. cdimage -j: This creates two file systems: ISO9660 and Joliet. A $ flips to a _ at ISO9660. \I386\_OEM_\TXTSETUP.OEM : ISO9660 \I386\$OEM$\TXTSETUP.OEM : Joliet Setupldr.bin read ISO9660 file system and dosn't find \I386\$OEM$\TXTSETUP.OEM. Create \I386\$OEM$\TXTSETUP.OEM at ISO9660 file system. Don't use cdimage -j. Edited: Quote changed @SyntaxError Sorry for the quote confusion. It's a kind of syntax error.

Can't you select AHCI at BIOS? As for ICH9R use HardwareId PCI\VEN_8086&DEV_2822&CC_0104 or compatible ID PCI\VEN_8086&CC_0104 Try add settings too [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_8086&DEV_2822&CC_0104] "Service"="iaStor" "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_8086&CC_0104] "Service"="iaStor" "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

Yes, that's nice.CriticalDeviceDatabase, service and base registry eintries from txtsetup.oem should work too. What about compatible HardwareId PCI\VEN_10DE&CC_0106 ?

Try, not tested: add_nvgts_online.reg REGEDIT4 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_10DE&CC_0101] "Service"="nvgts" "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\PCI#VEN_10DE&CC_0106] "Service"="nvgts" "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvgts] "Type"=dword:00000001 "Start"=dword:00000000 "Group"="SCSI miniport" "ErrorControl"=dword:00000001 "ImagePath"="system32\\drivers\\nvgts.sys" "DisplayName"="NVIDIA nForce Serial ATA Driver" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvgts\Parameters\PnpInterface] "5"=dword:0x00000001Use a nvgts.sys version relating to your hardware. Copy file nvgts.sys to %SystemRoot%\system32\drivers. Another question may arise: RAID. However: how to change RAID online? Does this make sense at all? Maybe if you like to change hardware and keep RAID. Again, not tested. Anyway REGEDIT4 ;nvrd32.sys [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#NVIDIA__Raid_Disk________] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#__NVIDIA_______Raid_Disk] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#NVIDIA__Raid_Disk_20_____] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\SCSI#__NVIDIA____Raid_Disk_20] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*_NVRAIDBUS] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*NVRAIDBUS] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*NVRAID20] "Service"="nvrd32" "ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\nvrd32] "Type"=dword:00000001 "Start"=dword:00000000 "Group"="System Bus Extender" "ErrorControl"=dword:00000001 "ImagePath"="system32\\drivers\\nvrd32.sys" "DisplayName"="NVIDIA nForce RAID Driver"

Run IsoBuster, open the ISO image. Choose files system ISO9660 : the red ISO label. Does exist file \I386\$OEM$\TXTSETUP.OEM ? Case is importand and watch for $ sign.

Integration of Intel's SATA AHCI and RAID drivers http://www.msfn.org/board/index.php?showtopic=107504

There is a \I386\winnt32.exe at a XP CD. Use this application. Prepare external drive e: winnt32.exe /makelocalsource /noreboot /sysdrive:e /tempdrive:e Edit file migrate.inf at drive e: You may change e: to c: Or delete file migrate.inf.

That's a fixed drive. XP differs USB fixed drive and USB removable drive. Removable or what? http://www.uwe-sieber.de/usbstick_e.html Question was about a USB flash drive, most likely a USB removable drive. There is a major speed difference with write cache at a USB removable drive.

Be aware, there is no full ATA AHCI support currently. Read you may get BSOD at AHCI or RAID mode currently. Copy uniata.sys and uata_xp.inf to \I386 For testing purposes replace all IDE drivers. Edit txtsetup.sif: edit lines, comment lines and add lines: [SourceDisksFiles] uniata.sys = 1,,,,,,3_,4,0,0,,1,4 ;;;uata_xp.inf = 1,,,,,,,20,0,0 ;mshdc.inf = 100,,,,,,,20,0,0 [HardwareIdsDatabase] ;PCI\VEN_8086&DEV_1230 = "intelide" ;PCI\VEN_8086&DEV_7010 = "intelide" ;PCI\VEN_8086&DEV_7111 = "intelide" ;PCI\VEN_8086&DEV_2411 = "intelide" ;PCI\VEN_8086&DEV_2421 = "intelide" ;PCI\VEN_8086&DEV_7199 = "intelide" ;PCI\VEN_8086&DEV_244A = "intelide" ;PCI\VEN_8086&DEV_244B = "intelide" ;PCI\VEN_8086&DEV_248A = "intelide" ;PCI\VEN_8086&DEV_7601 = "intelide" ;PCI\VEN_1106&DEV_0571 = "viaide" ;PCI\VEN_1179&DEV_0105 = "toside" ;PCI\VEN_1095&DEV_0648 = "cmdide" ;PCI\VEN_1095&DEV_0649 = "cmdide" ;PCI\VEN_10B9&DEV_5229 = "aliide" ;PCI\VEN_105A&DEV_4D33 = "pciide" ;PCI\VEN_105A&DEV_4D33 = "pciide" PCI\CC_0101 = "uniata" PCI\CC_0104 = "uniata" PCI\CC_0105 = "uniata" PCI\CC_0106 = "uniata" *PNP0600 = "uniata" ;PCMCIA\KME-KXLC005-A99E = "atapi" ;PCMCIA\_-NinjaATA--3768 = "atapi" ;USB high capacity floppy drive USB\Class_08&SubClass_04&Prot_00 = "usbstor" [SCSI.Load] ;atapi = atapi.sys,4 uniata = uniata.sys,4 [BusExtenders.Load] ;pciide = pciide.sys ;intelide = intelide.sys ;viaide = viaide.sys ;cmdide = cmdide.sys ;aliide = aliide.sys [SCSI] uniata = "Universal ATA Driver (Win XP)" VMWare Player at IDE hard disk. XP installation does work. XP does boot. Driver updated with uata_xp.inf. XP dosn't boot anymore.

Yes, NT4 dosn't support USB.Contrary there are third party drivers, e.g. Inside Out Networks USB drivers. http://www.msfn.org/board/index.php?s=&amp...st&p=603313 Install NT4 from USB maybe possible. But what's the benefit? Any volunteer arround? I second this approach too.

Nvidia dosn't test new drivers at old hardware thoroughly. Try older drivers: e.g. 71.84, 66.93, 56.72 http://www.nvidia.com/object/winxp-2k_archive.html

Check PIO/DMA transfer mode. Set ResetErrorCountersOnSuccess in addition. http://support.microsoft.com/kb/817472/

No, I didn't "attached" cfadisk to gendisk. Gendisk is not changed: GenDisk is attached to disk_install still. That's the windows default setting. USBSTOR\GenDisk is attached to cfadisk_install. That way cfadisk is loaded at USB disks only, not at internal hard disk. Unfortunately "CompactFlash Filter Driver" is not loaded at CompactFlash card at IDE or pcmcia connector. Solution should work at all USB removable hardware, turning to a "fixed drive". Yes, that's a generic solution.BTW: textmode part if from http://www.911cd.net/forums//index.php?sho...mp;#entry142544

I integrated "fixed drive" USB driver. Cfadisk is active at textmode setup, first boot to gui setup and following bootings. Cfadisk is added to drives with HardwareID "USBSTOR\GenDisk". Change windows source files. Prepare Text mode setup: Copy file CFADISK.SYS to directory \I386 edit file \I386\txtsetup.sif: [SourceDisksFiles] cfadisk.sys = 1,,,,,,3_,4,0,0,,1,4 [BusExtenders.Load] cfadisk = cfadisk.sys [HardwareIdsDatabase] USBSTOR\GenDisk="Disk",{4D36E967-E325-11CE-BFC1-08002BE10319} [BusExtenders] cfadisk = "CompactFlash Filter Driver",files.none,cfadisk edit file \I386\setupreg.hiv, import file cfadisk_textmode.reg: REGEDIT4 [HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10319}] "Class"="DiskDrive" @="cfadisk filter 'fixed drive'" "Installer32"="StorProp.Dll,DiskClassInstaller" "SilentInstall"="1" "NoInstallClass"="1" "Icon"="-53" "LowerFilters"=hex(7):63,66,61,64,69,73,6b,00,00 "UpperFilters"=hex(7):50,61,72,74,4d,67,72,00,00 [HKEY_LOCAL_MACHINE\loaded_SYSTEM\ControlSet001\Services\cfadisk] "group"="System Bus Extender" "tag"=dword:0000000f Import settings copy setupreg.hiv setupreg.hiv.bak copy setupreg.hiv setupreg.hiv.bak.%date% reg load HKLM\loaded_SYSTEM setupreg.hiv regedit /s cfadisk_textmode.reg reg unload HKLM\loaded_SYSTEM prepare GUI mode setup: Edit hivesys.inf, add three lines to section [AddReg] [AddReg] HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\usbstor#gendisk",Service,0x00000000,disk HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\usbstor#gendisk",ClassGUID,0x00000000,{4D36E967-E325-11CE-BFC1-08002BE10318} HKLM,"SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\usbstor#gendisk","LowerFilters",0x00010002,"cfadisk" Expand disk.inf, edit disk.inf. Edit [disk_device] section and add sections: [disk_device] %disk_devdesc% = disk_install, GenDisk "'Fixed Disk' Filter Driver" = cfadisk_install, USBSTOR\GenDisk [cfadisk_install.NT] ;Section is importand for ranking [cfadisk_install.NT.HW] AddReg=cfadisk_addreg DelReg=cfadisk_delreg [cfadisk_addreg] HKR,,"LowerFilters",0x00010008,"cfadisk" [cfadisk_DelReg] HKLM,"SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10319}" [cfadisk_install.NT.Services] AddService=disk,2,disk_ServiceInstallSection AddService=cfadisk,,cfadisk_ServiceInstallSection [cfadisk_ServiceInstallSection] DisplayName = "CompactFlash Filter Driver" ServiceType = 1 StartType = 0 ErrorControl = 1 ServiceBinary = %12%\cfadisk.sys LoadOrderGroup = SCSI miniportCompress file: makecab disk.inf At VMware USB drive is not possible as target. Remember there is no BIOS USB boot support. No idea about system with USB BIOS support.

@infiniti25 At testing cfadisk.sys I got a BSOD DRIVER_IRQL_NOT_LESS_OR_EQUAL at usbuhci.sys. That's at VMware USB1.1. Cfadisk.sys does work fine at usbehci.sys USB2.0. Do you get similar results?

Try devcon.exe hwids * devcon.exe driverfiles * http://support.microsoft.com/kb/311272/

Boot machine and open task manager. What's RAM usage? If RAM usage is nearby 256 MB, try the RAM upgrade. Given 256 MB RAM: I would upgrade the RAM. Local testing is a fine solution. Especial if you can take it back.

Get devcon.exe. http://support.microsoft.com/kb/311272 Run devcon hwids * or devcon hwids *usb*Select a appropiate HardwareID. A generic USB storage HardwareID: Cfadisk does work with this HardwareID.

http://support.microsoft.com/kb/314082/ Import mergeide.reg and extract files Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys.

As for Boot Sector: follow flyakite's tutorial replace I386 with used 4 char name, remember .\XP64\ directory. that's replace I386 with XP64

New tutorial here: Follow flyakite's tutorial and ignore flyakite's tutorial. Don't use winnt32.exe. Create a directory .\XP64. Copy directories \I386 and \AMD64 to .\XP64\. Create win51* flag files at root and at .\XP64\. Copy files setupldr.bin, txtsetup.sif and ntdetect.com to \XP64\. DVD Layout: .\WIN51 .\WIN51AP .\WIN51AP.SP2 .\XP64\AMD64\ .\XP64\I386\ .\XP64\WIN51 .\XP64\WIN51AP .\XP64\WIN51AP.SP2 .\XP64\NTDETECT.COM .\XP64\SETUPLDR.BIN .\XP64\TXTSETUP.SIF Edit setupldr.bin at directory .\XP64\ @echo off rem multiboot_XP64.cmd - edit XP64 setupldr.bin rem created by cdob rem use gsar.exe: Tormod http://home.online.no/~tjaberg/ set setupldr=SETUPLDR.BIN set char4=XP64 rem checksum: geitonaki http://www.msfn.org/board/index.php?showtopic=58410 gsar.exe -o "-s:x46:xda:x74:x03" "-r:x46:xda:xEB:x1A" %setupldr% rem adjust \i386\ntdetect.com and AMD64 gsar.exe -o "-s\i386\ntdetect.com" "-r\%char4%\ntdetect.com" %setupldr% gsar.exe -i -o "-sAMD64:x5C" "-r%char4%:x5C:x00" %setupldr% gsar.exe -o "-sAMD64:x00" "-r%char4%:x00:x00" %setupldr% Edit txtsetup.sif, adjust SetupSourcePath and create BootPath: [SetupData] SetupSourcePath = "\XP64\" BootPath = \XP64\AMD64\ BTW: txtsetup.sif, SetupSourcePath, BootPath does work at XP32 too.