laddanator

Can this be used in the everyday menu.lst to map the HD for more than one HD or is this for test purposes?

Text setup mode runs really slow on a older computer with this method as would if loaded from the actually CD. Wonder if the small ISO trick could be map to mem to say (0xFF) and after reboot to start GUI , cdob's, new setup command would run and mount the big ISO and finish install? Just to speed up text setup mode? If the path to the big ISO has been written to the ISOimage.ini...don't see why not

This part can be removed from the menu.lst floppy,vmem=find:/Inst/XP_INST.IMA ;\n\0 and just use this part write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO;\n\0 The Find Floppy is not needed due to memory or direct map of IMA

That will work. I do my multiboot ISO a little different (don't use BOOTFIX.BIN). I hex edit my setupldr.bin to change the path of the boot folder(can only use 4 letters or number). I use the same mod setupldr.bin over and over..only has to be hexed once...I could do a whole write up on this but I will try not to go off-topic Didn't mean to say your was simple as in lame but for someone who is new to this, meant its easier to understand. I use a mod BOOTWS folder with the firadisk ISO loads. Been testing all day and I am going to put this registry thing on the back burner (given me a headache) since the 1 boot to USB method is working with your IMA stuff, all is good...besides I still have winsetupfromusb which I hear may be getting a newer release. Tried this before but didn't have any luck but that was before your IMA file with setup.cmd. Will try now. Been testing the new XP_INST.IMA today on my Asus M4A88TD-M/USB3 with three internal HD. The BOOTWS mod has come in nicely. All three XP (Home-Pro-MCE) have installed fine. Will test on Dells tomorrow at work. Also I use variables so that I can use one XP_INST.IMA and much easier to write ISO name on the fly. Under each menu title I have this set XPISO=HOME.ISO set Image=XP.IMA set XPISO=PRO.ISO set Image=XP.IMA set XPISO=MCE.ISO set Image=XP.IMA So end result looks like this write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n; write --offset=0 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n; write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/%XPISO%;floppy,vmem=find:/XP/Floppy/%Image%;\n\0 UPDATE @cdob, just finished an install with PRO and only used this line write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/%XPISO%;\n\0 so now this line is not needed floppy,vmem=find:/images/firadisk.img;\n\0 Also I guess it would be a good idea to remove the firadisk driver and imdisk. I saw in the setup.cmd you have a line to remove Imdisk but not firadisk. Did I miss something? If not might not be a bad idea to add it to the cleanup section. Something like this devcon remove *\firadisk del %WinDir%\system32\drivers\firadi*.sys

Cant answer for sure but I don't think Server2003 is supported by cdob can answer that better Seems it is not set to run at default so thought maybe some kinda switch -cleanup if /I %1.==-cleanup. (call :cleanup &goto :eof) if /I %1.==-usb_boot. ( call :set_usb_boot_setting SYSTEM CurrentControlSet bootcfg.exe /TIMEOUT 8 goto :eof makes me think this is a switch. Ok, is a switch. Just ran setup -cleanup from a test.cmd and the cleanup process ran only. Cool Will do. What does this do exactly?

maanu, post 250 sums it up. Just have to expand your setup.exe and add it to the new IMA as described on the first page and use, cdob menu.lst from post 250

is the -cleanup like a switch to the cmd file?

You been around here along time so your opinion is always welcome. I been doing this awhile but never really had to explain how I came to a point or my methods to others. I need to remember that instead of posted advance menu.lst and so on, that the simple basic will work also so people who are new to this can start with the basic and change things to fit their needs as they get more comfortable.

Just notice my slashes are the wrong way reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,vmem=find:%CDDRIVE%/XP/ISO/HOME.ISO" g4d uses the slashes that way. Should be reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,vmem=find:%CDDRIVE%\XP\ISO\HOME.ISO"

I would like to make a video tutorial (would be my first) for winsetupfromusb and this method. Just need to get permission from ilko_t and cdob It's easy for me to say but this method is really simple. Sometimes I can't find the words to make since of the details but maybe in video would clear things up.

Sorry, didn't mean to say what you suggested was wrong...just figured it would be a bigger add Yes but the reboot pro link you gave (will have to find exact post) some examples do not have the drive letter. Since DP sets drive letter as %CDDRIVE%, I also tried this in the presetup.cmd reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,vmem=find:%CDDRIVE%/XP/ISO/HOME.ISO" but didn't accomplish my goal.

cdob, should I be posting here about added firadisk to registry and skipping imdisk mount during install or would it be better to post in the XP from RAM post?

I added the above as you suggested (this is just a test inside a running machine) Just doesn't look right to me. Should there be more in the registry for firadisk to find the ISO after reboot on an install?

Wasn't entirely random. We are also talking about it here and I knew cdob would know what I was talking about but I guess that doesn't help anyone else much. so that's why it seems random here. Will give this a whirl. Thanks, jaclaz

I was saying since you can actually load XP with nothing but firadisk (but has to be done in two boots to USB and using grub4dos) and Imdisk is never used. I like Imdisk but if it all can be done with one driver (firadisk) would be great also. I have successfully installed XP with nothing but two firadisk commands but I don't like having to boot to USB to run a second g4d command This being in the first command write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/HOME.ISO;floppy,vmem=find:/XP/Floppy/firadisk.img;\n\0 and this in the second boot to USB and g4d command write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/ISO/HOME.ISO;\n\0 I was reading you can add this command to registry (can't remember the link..will find and post) reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "StartOptions"="cdrom,vmem=find:/?" and this would eliminate a second boot to USB for a second g4d command and the need for Imdisk mount for GUI My problem is I added the registry command to my presetup.cmd and added a reboot command shutdown /r and when computer reboots, the command is not run and I get that global can't find CD error thing. So not exactly sure if the command is wrong. At this point I am not using, cdob XP_INST_v05 for this test but just the plain firadisk.ima. @cdob, I just finished a XP Home install on my Asus M4A88TD-M/USB3 with you new XP_INST_v05.7z and all went well.

When does the addition reboot take place if needed? If I could get this registry entry to work, could be wrote on the fly to the setup.cmd and imdisk mount would not be needed reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "StartOptions"="cdrom,vmem=find:/images/winsetup.iso" What is the? Does this new setup.cmd run cleanup automatically?

Will test today. Did you have to update the setup.cmd in anyway I would add the chainloader line as below title Setup Windows from ISO : \nBoot once from USB; with virtual CD+Floppy XP_INST.IMA map /images/winsetup.iso (222) map --mem /images/XP_INST.IMA (fd0) map --mem /images/XP_INST.IMA (fd1) map --mem (md)0x800+4 (99) checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd0) (hd1) checkrange 0x80 read 0x8280 && geometry (hd1) && map (hd1) (hd0) map --hook write --offset=0 (fd0)/setup/ISOimage.ini \\images\\winsetup.iso\n;\n;\n; write --offset=0 (fd1)/setup/ISOimage.ini \\images\\winsetup.iso\n;\n;\n; write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/images/winsetup.iso;floppy,vmem=find:/images/firadisk.img;\n\0 chainloader (222)/I386/SETUPLDR.BIN In my case if I don't add the line on bold, my ISO will prompt me to hit any key to boot but with the line...boots right into setup Glad you posted this. Much simple menu.lst than mine. I actually was going to post a very simple version of my method later today but you beat me to it Thanks, cdob

Actually working on something or a different type of mapping that doesn't require mapping to virtual type floppy (fd0) or (fd1) Is the cleanup, the line below? (Already in the newer setup.cmd) :cleanup ====================================================== set SYSTEM=HKLM\SYSTEM set CriticalDeviceDatabase=%SYSTEM%\CurrentControlSet\Control\CriticalDeviceDatabase set Services=%SYSTEM%\CurrentControlSet\Services REM +=======================================================+ REM | restore default USB settings | REM |-------------------------------------------------------| reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0300" /f reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0310" /f reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0320" /f reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_08" /f reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_09" /f reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB" /f reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB20" /f reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Start" /d 3 rem net.exe stop imdisk rem sc.exe delete ImDisk rem delete drivers\imdisk.sys REM +=======================================================+ goto :eof === cleanup ====================================== If so I run a ProgramInstaller.cmd in runonce at first login, I could just add the line to that cmd? No, that's why I was wondering if writing the reg entries to the setup.cmd along with the other entries on the fly would work? Are you referring to this? and why would this cause another reboot And can the reg command be added like this write --offset=251 (fd0)/setup/setup.cmd reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\XP\ISO\HOME.ISO write --offset=251 (fd1)/setup/setup.cmd reg.exe add "HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk","StartOptions",0x0,"cdrom,vmem=find:\XP\ISO\HOME.ISO This was added to registry from setup.cmd and after DP finishes...Global cant find CD Rom error popped up reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "cdrom,file=%CDDRIVE%\XP\ISO\HOME.ISO" And this failed also. reg add HKLM\SYSTEM\CurrentControlSet\Control\FiraDisk /v StartOptions /t REG_SZ /d "StartOptions"="cdrom,vmem=find:/XP/ISO/HOME.ISO" I know this was added because after load is finished (had to use part two of the firadisk method for this test to finish install)...the command is in the registry Also added this to my ProgramInstaller.cmd that runs on first log in after install finishes (runonce) :cleanup ====================================================== set SYSTEM=HKLM\SYSTEM set CriticalDeviceDatabase=%SYSTEM%\CurrentControlSet\Control\CriticalDeviceDatabase set Services=%SYSTEM%\CurrentControlSet\Services REM +=======================================================+ REM | restore default USB settings | REM |-------------------------------------------------------| reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0300" /f reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0310" /f reg.exe delete "%CriticalDeviceDatabase%\PCI#CC_0C0320" /f reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_08" /f reg.exe delete "%CriticalDeviceDatabase%\USB#CLASS_09" /f reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB" /f reg.exe delete "%CriticalDeviceDatabase%\USB#ROOT_HUB20" /f reg.exe add "%Services%\usbohci" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbuhci" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbehci" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbhub" /f /t REG_DWORD /v "Start" /d 3 reg.exe add "%Services%\usbstor" /f /t REG_DWORD /v "Start" /d 3 rem net.exe stop imdisk rem sc.exe delete ImDisk rem delete drivers\imdisk.sys REM +=======================================================+ goto :eof === cleanup ====================================== The first 7 delete commands give can't find registry entry command The 5 add complete successfully By the way, the rebooting I don't mind,,,its the rebooting to grub4dos to run a second menu.lst command is what I try to avoid

Couldn't firadisk driver be added to the XP source and then add the registry stuff? Also since firadisk is copied to the system from txtseup.oem maybe the could be written to the setup.cmd on the fly?

Actually got this to work. Had an invisible space before the first backslash (invisible script killer..as I like to call it) write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n; write --offset=0 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n; Will work with variable but should both offset=0 for fd0 and fd1? Both should be offset=0 I will give this a try. I agree. Did a new method last night that I just added your newer setup.cmd to the IMA and didn't change anything else and just wrote the ISO name and path on the fly in the ISOimage.ini and XP installed fine (if you don't map the IMA file to memory, the write change will be permanent) . So pretty much everything was done from the menu.lst. If folks are confused about editing the IMA, then I will not post a "write up" on the registry method but will post if it worked for me or not Again agree...will post my new findings later with no setup.cmd editing and all done on the fly I do but not testing on customer computer. We have crap tons of computer from HP to Dell and so on laying around I test on. Do you think it's a good idea too? No, that I have found so far. I tested all USB ports with different USB HD and USB JumpDrive Like I said, not tested on customers computer as of yet. Wanted to make sure all is good before I do. What would you suggest to do this? No problem. I installed an XP Home on my Asus M4A88TD-M/USB3 last night with the newer setup.cmd from your later post and on the fly write of the ISOimage.ini and all went well. Look forward to any new stuff and thanks, cdob

Not sure haven't tested this Again, not sure I will work on this but would like for, cdob, to give me the ok

To be clear I should replace the setup.cmd in the IMA file from page one with the one in the link above and is this the only line dll = setup, fixBoot.USB to deleted from txtsetup.oem? I do work on Dells. Reloaded 7 this week and two were Optiplex 845 (actually not sure if they were 845, will check Monday.) I will start making a better note of the make and models so I can report working and not working.

I do but you don't have to. I don't do anything major with the ISO but slipstream updates and add driver packs. Do you not like the method I listed above? Been getting allot of personal mail as to the how to of my method. I am thinking about making a YouTube video Let me sum it up a little. My menus.lst and method seems confusing because context is lost sometimes online. Just follows this You can leave the paths default and name your ISO default and use this timeout 15 color white/blue write 0x8274 0x2001 title Boot From Hard Drive (Windows Vista/7 or Xp)\nBoot Into Main OS Drive checkrange 0x80 read 0x8280 && map () (hd1) checkrange 0x80 read 0x8280 && map (hd1) () checkrange 0x80 read 0x8280 && map --hook rootnoverify (hd0,0) chainloader +1 || chainloader /ntldr title root title XP Home Install From ISO With 1 USB Boot\nWorks With Low Ram also find --set-root /Inst/XP_RAM.ISO map --mem (md)0x800+4 (99) checkrange 0x80 read 0x8280 && map (hd1) (hd0) checkrange 0x80 read 0x8280 && map (hd0) (hd1) map /Inst/XP_RAM.ISO (222) #map --mem /Inst/XP_INST.IMA (fd0) #map--mem /Inst/XP_INST.IMA (fd1) map /Inst/XP_INST.IMA (fd0) map /Inst/XP_INST.IMA (fd1) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/Inst/XP_RAM.ISO;floppy,vmem=find:/Inst/XP_INST.IMA ;\n\0 rootnoverify (222) chainloader (222)/I386/SETUPLDR.BIN If you don't use Imdisk to mount ISO at GUI, you will have to boot a second time to USB and use the second firadisk command is which I was trying to get away from checkrange 0x80 read 0x8280 && map (hd0) (hd1) checkrange 0x80 read 0x8280 && map (hd1) (hd0) map --hook write (99) [FiraDisk]\nStartOptions=cdrom,vmem=find:/XP/HOME.ISO;\n\0 root (hd0,0) chainloader /ntldr chainloader (hd0)+1 How do you write the ISO name to ISOimage.ini on the fly? Like this? This is almost working for me. The error I am getting is can't find ISO \\XP\ISO\HOME.ISO backslash in front of the XP part. If I remove the double backslash I get XXP\ write --offset=0 (fd0)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n; write --offset=1 (fd1)/setup/ISOimage.ini \\XP\\ISO\\%XPISO%\n;\n;\n; Fixed

Does they setup.cmd mention here replace the setup.cmd in the XP_INST_v04.7z from the first post?

Been lucky enough that the error using IF EXIST only happens on a live machine...get that can't find drive error, hit enter to continue. I have found a solution in the code below and has been error free so far on installs and live machines. I need to change that IF EXIST line in the winnt.sif to this For %%I 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 A B) do (dir %%I:\ 1>nul 2>nul && if /i exist "%%I:\whaterever" set USBDrive=%%I:) Thanks for the links. Got some reading to do today.