cdob

I created two approaches finally: mkISO_RAMload_sort.cmd creates a grub4dos menu RAMboot.lst. Example: Recognice the first line, this contain the sector numbers.The RAMboot.lst is called from main menu.lst. First approach: configfile, use preconfigured RAMboot.lst. title Loading XP RAM install - swap hd0 hd1 \n loading N sectors configfile RAMBOOT.LST 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 (hd0) (hd1) map (hd1) (hd0) map --hook map --unmap=0xFE configfile (0xFE)/I386/RAMBOOT.LST title Loading XP RAM install - no map hdN \n loading N sectors configfile RAMBOOT.LST 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 --unmap=0xFE configfile (0xFE)/I386/RAMBOOT.LST Second approach: universal solution, read sectors from RAMboot.lst title Loading XP RAM install - no map hdN \n loading N sectors from RAMBOOT.LST ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #optional, (fd1) required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map /Inst/XP_RAM.ISO (0xFE) map (hd0) (hd1) map (hd1) (hd0) map --hook #kDn [url="http://www.msfn.org/board/index.php?s=&showtopic=137714&view=findpost&p=886626"]http://www.msfn.org/board/index.php?s=&amp...st&p=886626[/url] # EMPTY512.LST content 512 spaces write --offset=0x00 (fd0)/setup/EMPTY512.LST default 0\n write --offset=0x10 (fd0)/setup/EMPTY512.LST \ntimeout 0\n\n write --offset=0x20 (fd0)/setup/EMPTY512.LST \ntitle RAM load\n write --offset=0x30 (fd0)/setup/EMPTY512.LST \nmap --mem (0xFE)+ (0xFF)\n write --offset=0x52 (fd0)/setup/EMPTY512.LST \nmap --hook\n write --offset=0x60 (fd0)/setup/EMPTY512.LST \nmap --unmap=0xFE\n write --offset=0x72 (fd0)/setup/EMPTY512.LST \nchainloader (0xFF)/I386/SETUPLDR.BIN\n # RAMBOOT.* content like "#123456" without quotes dd if=(0xfe)/I386/RAMBOOT.LST of=(fd0)/setup/EMPTY512.LST skip=1 seek=0x42 bs=1 count=0x07 #cat (fd0)/setup/EMPTY512.LST configfile (fd0)/setup/EMPTY512.LSTEMPTY512.LST is included in XP_INST_v04.7z, attached to first post.

What happens if you boot XP from the hardrive? Which messages do you get? Do you get a black screen and a blank cursor? Adjust MBR, bootrecord or boot.ini.

Windows XP dosn't support your mass storage controller. Use a USB floppy drive. Load drivers. Or add drivers to XP. http://www.msfn.org/board/88-t51140.html Or use a virtual floppy http://www.msfn.org/board/3-t137461.html Or goto BIOS, set IDE emulation mode.

@kDn Thanks, I like the idea. The (fd0)/EMPTY512.LST offers a universal solution. EMPTY512.LST settings can be adjusted to special needs. Have to do some tests. There are different approaches to create RAMBOOT.TXT. Maybe I add a ramload.lst to ISO image too. ramload.lst offer a basic setting with swap hd0 hd1 and without map. Haven't made a final decision so far. @Siginet I don't know a reliable solution with two single ISO files. Remember grub4dos dd is more a hex editor. You can copy sectors, but file system is not adjusted. You may mount a second ISO file, and dd oembios.cat to RAM ISO. Given different oembios.cat file sizes results are interesting. Try and report. A multi session CD (or fake multi session as growisofs) may get a approach too. dd file system parts to RAM. However this is rather difficult at two single ISO images. A multi boot ISO file gives reliable results. To 3: It should be possible to load a small iso into RAM (textmode boot files, about 10mb), mount the big ISO file to a virtual CD drive and continue installation. Setup search all CD drives for source files, does work at U3 fake CD drive. No need to add a special search. I don't know a setupldr.bin textmode driver to mount the big ISO file.

I'm using the same ISO file at CD and at RAM ISO method. However I'm used to SetupSourcePath and BootPath nowadays: XP01\I386\WINNT.SIF http://www.msfn.org/board/index.php?s=&amp...st&p=814566 http://www.msfn.org/board/index.php?s=&amp...st&p=832507 No idea about classic flyakite's tutorial. Given renamed winnt.sif files, this seems another solution too. Yes, BTS installer support all drives, this includes USB drive.

Windows setup expect target drive at (hd0). Most BIOS map boot USB drive to (hd0). And give one internal hard disk, internal hard disk is mapped to (hd1). Compare first post, use grub4dos map to change mapping: map (hd0) (hd1) map (hd1) (hd0) Unattended installation does work too. I understand, there is a setupldr.bin containing winnt.sif. And there is a XPPC.bin containing wXPPC.sif There is a file wXPPC.sif, but no winnt.sif. Did you call setupldr.bin or XPPC.bin? Remember wimb's suggestion And remember a a:\winnt.sif (a:\wXPPC.sif) goes first. This is the floppy image in this case. Did you add a w*.sif to floppy image. No, this is not necessary. @kDn Another idea: Imagine there exist a file \I386\RAMBOOT.TXT 123456\nsome text123456 refers to RAM load sectors count. Grub4dos menu.lst dosn't contain sector numbers by default. Do you have a idea to boot grub4dos, read RAMBOOT.TXT at grub4dos and call map --mem (0xFE)+123456 (0xFF)

Thanks for the reminder. Sorry, haven't used bootfont.bin in years myself. I'm using codepage 850 and won't detect a big difference. It's a real pleasure do find another 'mkisofs -sort' user. Attached is a updated version: status is changed from experimental to very experimental There is a new function call :patch_sort_iso despide unresolved unresolved grub4dos questions http://www.boot-land.net/forums/index.php?showtopic=9306 A fake file RAMBOOT.ISO should be patched to a RAM load ISO image. Third party applications gsar.exe and dd.exe are used. @Siginet BCDW is a fine bootloader, because setupldr.bin is loaded to RAM, patched in RAM and executed. Grub4dos dosn't support this. Patch setupldr.bin before. I'm using: gsar.exe -o -si386 -r%boot_4_char% multi_bootpath\%boot_4_char%\SETUPLDR.BIN Attachment removed, use version from XP_INST_v05.7z at first post.

This indicates: setupdlr.bin dosn't find ntdetect.com. Which bootloader do you use by default? Can you try grub4dos? Do you hexedit setupldr.bin? i386 --> XPPC I wonder, does some configurations require root (0xFF) ? Try root (0xFF) chainloader (0xFF)/XPPC/SETUPLDR.BIN Try the CD image bootloader too chainloader (0xFF) @kDn Thanks for ISOimage.ini corrections. Yes, change this settings. Correct or false sorting is confusing. The sort file is one part only. The builded ISO image is importand. Mentioned function :mk_sort_list_static is not used anymore. This is a reference from last year. I'll check .//BOOTFONT.BIN again, as far as I remember // is replaced by / internally.

Boot different XP ISO images from one USB stick or hard disk. Edit txtsetup.oem, uncomment the line dll = setup, ISOimage.txt There are two approaches: One add different XP ISO files but one floppy image Example: /Inst/XP_PRO.ISO and /Inst/XP_HOME.ISO title Loading XP PRO install - write /Inst/XP_PRO.ISO ls /Inst/XP_PRO.ISO || find --set-root /Inst/XP_PRO.ISO map --mem /Inst/XP_INST.IMA (fd0) #optional, (fd1) required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_PRO.ISO (0xFF) map --hook write --offset=0 (fd0)/setup/ISOimage.ini \\Inst\\XP_PRO.ISO\n;\n;\n; chainloader (0xFF)/I386/SETUPLDR.BIN title Loading XP HOME install - write /Inst/XP_HOME.ISO ls /Inst/XP_HOME.ISO || find --set-root /Inst/XP_HOME.ISO map --mem /Inst/XP_INST.IMA (fd0) #optional, (fd1) required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_HOME.ISO (0xFF) map --hook write --offset=0 (fd0)/setup/ISOimage.ini \\Inst\\XP_HOME.ISO\n;\n;\n; chainloader (0xFF)/I386/SETUPLDR.BIN Or use a multi boot ISO Image, that's one ISO file, one floppy image To create a ISO Image compare Multi-Boot CD/DVDs http://www.msfn.org/board/index.php?showforum=82 title Loading XP PRO install - write /Inst/XP_RAM.ISO ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #optional, (fd1) required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) map --hook write --offset=0 (fd0)/setup/ISOimage.ini \\Inst\\XP_RAM.ISO\n;\n;\n; chainloader (0xFF)/XPPR/SETUPLDR.BIN title Loading XP HOME install - write /Inst/XP_RAM.ISO ls /Inst/XP_RAM.ISO || find --set-root /Inst/XP_RAM.ISO map --mem /Inst/XP_INST.IMA (fd0) #optional, (fd1) required at some BIOS #map --mem /Inst/XP_INST.IMA (fd1) map --mem /Inst/XP_RAM.ISO (0xFF) map --hook write --offset=0 (fd0)/setup/ISOimage.ini \\Inst\\XP_RAM.ISO\n;\n;\n; chainloader (0xFF)/XPHM/SETUPLDR.BIN Yes, grub4dos support ISO files, ancient grub dosn't do this. Setup require stable hardware, this includes the ports.A i848 support SATA ports too. Can you disable broken port at BIOS?

Which menu.lst sections does work at existing menu.lst? Do you use find already? Which boot configuration do you use? Do you boot from USB? Do you boot from internal hard disk? How do you start grub4dos? Which directory and files did you add? Which hardware: motherboard and BIOS do you use? Which grub4dos do you use? Try a current version http://nufans.net/grub4dos/How do you build the ISO image? In addition: /I386/SETUPLDR.BIN is case sensitive. Does exist a file \I386\SETUPLDR.BIN ?

The user has to use AHCI mode at setup to implement built in support. Which settings did you import?Does settings contain relating HardwareID? Enable AHCI. Boot windows 7 DVD, open command line and run regedit. Try generic Intel AHCI HardwareID pci#ven_8086&cc_0106 too. http://www.msfn.org/board/index.php?s=&amp...st&p=845633 Built in support was not enabled at setup, because there was no relating hardware.Import at Win7 Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msahci] "Start"=dword:00000000

Can you partition and format the hard disk within setup? Did you integrate mass storage drivers? How did you integrate the mass storage drivers? Do you use a unattended setup CD? Remove winnt.sif and create a new CD. Do you possess a USB floppy drive? Use a empty file a:\winnt.sif. Boot a Vista or Waik DVD. Run diskpart clean. Or use Parted Magic. http://partedmagic.com/ Read too: Setup cannot copy the file cmnicfg.xml http://www.lancelhoff.com/setup-cannot-cop...ile-cmnicfgxml/

Does your source files contain HD Audio drivers? Or slipstream SP2. Try the WDM directory. This contain XP 32bit and XP 64 bit drivers. Add this directory. PNP should load the drivers.

XP dosn't support your mass storage controller by default. Integrate relating drivers http://www.msfn.org/board/37-t107504.html

No warez support.

Thanks for the reminder. That way menu.lst dosn't have to contain sector numbers. Not integrated yet. Need some time to settle current features, maybe next year. @demontager Don't use addional mapping. Try title Load PLoP boot manager - USB find --set-root /boot/plpbt.bin kernel /boot/plpbt.bin In addition you may configure PLoP plpbt.bin http://www.plop.at/en/bootmanager.html#plpcfgbt plpcfgbt stm=hidden cnt=on cntval=1 dbt=usb plpbt.bin @kDn Thanks for VMSCSI report, fixed. @TigerWhite Sorry no further idea, don't use I VirtualBox. fd0 and fd1 seems a good work arround.

There are IDE and RAID drivers for a PC2500E http://www.idot.com.tw/en/downloads/ What's poor OS performance? Why do you search SATA drivers at all? What do you expect? What's current condition? Can you access the hard disk? Which BIOS mode do you use? Do you use IDE emulation, AHCI or RAID? Be aware: the PC2500E use a VT8237, that's a old controller with a limitation: Adjust a SATA II hard disk to SATA I speed. As for Intel mass storage drivers read the sticky message http://www.msfn.org/board/37-t107504.html VIA drivers http://www.viaarena.com/ A gateway m-1631u use a AMD RS690T Chipset http://www.gateway.com/systems/product/529668270.php AMD drivers are at http://game.amd.com/us-en/drivers_catalyst.aspx Finally there dosn't exist Windows 2000 for all SATA controllers.

Does the type match REG_EXPAND_SZ? Did you selected directory %SystemRoot%\Inf manually?

What about your DevicePath? Does 2000 machine use default still: http://support.microsoft.com/kb/314479/ HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\DevicePath: REG_EXPAND_SZ:%SystemRoot%\Inf Try navigate to %SystemRoot%\Inf manually.

Thanks. That's awesome grub4dos usage too. Can you clarify some details? Txtsetup.oem does contain a empty [Defaults] section. Do I have to set a [Defaults] entry? Or does windows load all [scsi] drivers by default? Yes, firadisk v0.0.1.12 does solve this. I'm using this too in the mean time.

I'm using mkisofs -sort and investigate some ocassions currently.Sorry no further hint so far. 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. No need for deaming, should work already. The ISO image is loaded at BIOS speed. This maybe solw despite USB2.0 hardware. A 700 mb imgae is loaded in about a minute at USB2.0 speed. Setup does work. Try the PLOP Boot Manager. This allows USB2.0 speed at some 1.1 speed BIOS. @TigerWhite Thanks for report. Which BIOS settings do you use? Does your VirtualBox use a floppy drive? Does exist a floppy controller? I've no Idea. Should work without errors.

This maybe hardware too. Try a shorter cable too. Which mobo do you use? Which mobo update do you use? nLite dosn't support PEBuilder requirements.

Massstorage package is reconstructed currently. User reports are highly welcome. Ask at Driverpacks for a Massstorage testing version. http://forum.driverpacks.net/

Use good quality CD/DVD media, use a good burner. Write at decent speed.

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.