ilko_t

original 2.lst: map (hd0) (hd1) map (hd1) (hd0) map --hook ls (0xff)/ && root (0xff) ls (0xff)/ && chainloader (0xff)/I386/SETUPLDR.BIN ls (0xff)/ || rootnoverify (hd0) ls (0xff)/ || chainloader (hd0)+1 boot becomes: ls (hd0,0)/laddsbootdvd.tag && map (hd0) (hd1) ls (hd0,0)/laddsbootdvd.tag && map (hd1) (hd0) map --hook ls (0xff)/ && root (0xff) ls (0xff)/ && chainloader (0xff)/I386/SETUPLDR.BIN ls (0xff)/ || rootnoverify (hd0) ls (0xff)/ || chainloader (hd0)+1 boot original 3.lst: map (hd0) (hd2) map (hd1) (hd0) map (hd2) (hd1) map --hook ls (0xff)/ && root (0xff) ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/I386/TXTSETUP.SIF ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/AMD64/TXTSETUP.SIF ls (0xff)/ && chainloader (0xff)/I386/SETUPLDR.BIN ls (0xff)/ || rootnoverify (hd0) ls (0xff)/ || chainloader (hd0)+1 boot becomes: ls (hd0,0)/laddsbootdvd.tag && map (hd0) (hd2) ls (hd0,0)/laddsbootdvd.tag && map (hd1) (hd0) ls (hd0,0)/laddsbootdvd.tag && map (hd2) (hd1) map --hook ls (0xff)/ && root (0xff) ls (0xff)/I386/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/I386/TXTSETUP.SIF ls (0xff)/AMD64/ && cat --locate=rdisk(1) --replace=rdisk(2) (0xff)/AMD64/TXTSETUP.SIF ls (0xff)/ && chainloader (0xff)/I386/SETUPLDR.BIN ls (0xff)/ || rootnoverify (hd0) ls (0xff)/ || chainloader (hd0)+1 boot and so on. Got it? Again- wherever in those files, except fd.lst and 1.lst, you see map (hdX) (hdY) change to ls (hd0,0)/laddsbootdvd.tag && map (hdX) (hdY)X and Y varies, ls (hd0,0)/laddsbootdvd.tag && stays the same.

Ummmm... ls (hd0,0) on all lines in question. Not (hd0), or (hd1) or anything else.

First two lines, just add "ls (hd0,0)/laddsbootdvd.tag && " in front of them, note the space after &&. Same way edit every other X.lst file except fd.lst. Add that at from of each "map (X) (Y)" line. Grub4dos does not loop through active partitions. Hard disk numbering is according to BIOS order.You had 3 internal hard disk. That's hd0, hd1 and hd2. USB disk logically became hd3, but on some systems, according to BIOS hard disk boot order, it may get in the middle, say hd1 or hd2, or even hd0.

Quite useful report, thanks. Can you do again, after you load PLoP read 0x8280 calc *0x475 & 0xFF as well as root (then pressing TAB key on the keyboard? As for the weird behavior- try changing the line in winsetup.lst map /WINSETUP/XPpSP3.ISO (0xff) || map --mem /WINSETUP/XPpSP3.ISO (0xff) to only map --mem /WINSETUP/XPpSP3.ISO (0xff) This may lead to hangs on some buggy machines, use the solution as in here, maybe as another, backup entry of title First part of Windows ... part of the menu and newer grub4dos version which supports "map --e820cycles" option: http://reboot.pro/15956/ There are plenty of important changes to be done, new version of the program should be out soon. It appears if an ISO is mapped not in memory and do a cat --locate=foo --replace=bar /FILE/IN/THE/ISO the file is changed permanently on the disk. map --read-only and map --fake-writes do not help to change the string we need to in txtsetup.sif, Setup sees it as it was before. Could you also check if latest PLoP boot manager works the same way on this machine- Setup works and grub4dos commands I asked you to type return the same results as the previous PLoP version? Get just plpbt.bin from here, place it in root of the USB drive and rename it to plp513.bin. Then add these lines at the end of menu.lst: title Start PLoP boot manager 5.0.13 ls /usbdrive.tag || find --set-root --ignore-cd /usbdrive.tag kernel /plp513.bin When you are saying with PLoP it works how far did you get? Did you install Windows from start to end, until first desktop? The program installs grub4dos MBR, did you select the advanced option "do not check and install grub4dos MBR"?

That's very nice machine...What's motherboard model and make? What's the name of the ISO file in WINSETUP folder, or just attach winsetup.lst with your next post. I'll prepare another file to test several options. What is the result of these two commands in grub4dos CLI? read 0x8280 calc *0x475 & 0xFF Do you have an option in BIOS for the USB disk emulation- USB-FD, HDD-ZIP, USB-HD? If yes, what is it set to? How did you partition and format the USB disk, using which program and which options?

@laddanator Try editing each of the files in BOOTWS folder starting from 2.lst. Add " ls (hd0,0)/laddsbootdvd.tag && " in front of each line which swaps the hard disk order e.g.: 2.lst: ls (hd0,0)/laddsbootdvd.tag && map (hd0) (hd1) ls (hd0,0)/laddsbootdvd.tag && map (hd1) (hd0) .... ....In other words, do hard disk swapping only if USB disk is first. If not- no swapping at all, assume it's last and since we already read from BIOS how many disks are present (checkrange N calc *0x475 & 0xFF && configfile %Offset%/N.lst) we should know the USB disk number, if it's really last. This should work if USB disk is first or last. Please test on computers which do support USB boot. On the others, I doubt it would work, even with the help of PLoP, but of course a test wouldn't hurt.

When you do that, where is the usbdrive.tag file found without any HD mapping? Is it (hd0,0), or (hd1,0), or...?Can you test that on a few machines? BIOS boot order may interfere too, say CD first, HD second and USB disk third may give different results than CD first, USB disk second and HD third. Can you try on a few machines? I don't have any test machines around to play with. I didn't think Hiren's was warez anymore since 10.5. All the illegal stuff was removed and replaced with all free stuff. You don't consider the included mini Windows XP free and legally redistributed, do you? AFAIK MS DOS has the same limitations.

Just run the program the same way if you want to add another XP/2000/2003. You can add up to 99 versions of XP/2000/2003 in the same partition. If need to add another Vista, 7, or Server 2008, refer to the links in the first post how to do it. The program is designed to add only one of those.

1) Download the latest 1.0 beta7 from the first post in the topic and extract it to simple path, say D:\winsetup 2) Partition and format the USB disk using Windows disk management. Make the first partition primary, NTFS and active and use it for the purpose. 3) Run the tool, put checkmark on XP/2000/2003 and press the "..." button to point the program to your XP source. This must me extracted ISO, ISO mounted in a virtual CD or similar, NOT an ISO file itself. You must select the parent directory of I386, for example if XP source is in c:\winxp\ select that directory. 4) Put checkmark on Windows 7 field, browse for it's source. Again, ISO is not accepted, extract it using 7-zip for example or mount it as a virtual DVD. 5) Press GO button and wait until program completes its job.

Sets another file where default entry of the sub-menu in winsetup.lst is written to. E.g. if user once starts Text mode, GUI mode will be set as default, thus next reboot if left unattended GUI mode will start automatically.http://diddy.boot-land.net/grub4dos/files/menu.htm#default Good to know, thanks.

What if the biosinfo file was added to the small ISO to load to memory and hook it that way? Wouldn't help. Setup will complain about the next file, whichever it is, if the path in Txtsetup.sif to boot and source files is not valid.

In this case, boot from a CD or other source than the USB disk, there is no ARC path to the USB disk or it's not valid after the grub4dos mappings, Setup error is a bit misleading. There is nothing wrong with biosinfo.inf, it's the wrong path to it and Setup cannot read it. Need to think a bit in this direction, it's possible the fix is easy.

Try RMPrepUSB, plenty of options to play with, there are other USB formatting utilities mentioned too in the thread above. Avoid PEtoUSB and HP USB format tool for now.

Give it a read: In short- try other formatting tools and experiment with the various formatting options each has until you find the right combination for your motherboard/BIOS. Test if it boots as showed in that thread, then use usb_multiboot.

And that error exactly is...?Come on, is it really so hard to provide proper details if you are looking for help, so no mind reading is involved?

You'd need to be more detailed what are you trying to achieve, how, and what exactly the problem and the errors are.

I tried them both along few others in the past, Beyond Compare is for me by far more intuitive, easy and with more options, comes like free as well. Please read again: In short, edit these, if I am not missing something: 1) winsetup.lst 2) txtsetup.sif in the small ISO file 3) setup.cmd in \WINSETUP\XP.....\I386

The boot group of the USB drivers is also changed. There are also a few lines added to SourceDisksFiles section. Folder name is tied up to the lines you quoted, winsetup.lst and setup.cmd in \I386 folder. If you want to go that route- get Beyond Compare: http://www.scootersoftware.com/ Trial version works for looong time. Compare original txtsetup.sif in the small ISO file and the original in \I386 folder. Compare I386 folder structure on USB disk and in your source. I could be forgetting something.

That message is from grub4dos. Type the commands manually and report the output after each one: find --set-root /mycorpxppro.iso map (hd0) (hd1) map (hd1) (hd0) map --mem /firadisk.img (fd1) map --mem (md)0x6000+800 (fd0) map --mem /mycorpxppro.iso (0xff) map --hook dd if=(fd1) of=(fd0) count=1 chainloader (0xff) boot You get grub4dos command prompt by pressing "c" key. Pay attention to the last command "boot", it's not needed when using menu file but is needed when typing those manually.

Could you shed some light on that? How far does it go? Do you get a BSOD or what? What error code if yes?Are there differences in winnt.sif between the working and non working ones?

You may have second, third or fourth primary partition. Or 3 primary and one extended. There is room for four partitions, some could be extended as a holders of many logical ones. Which one are you installing onto? You may also see that when booting the first part of Setup, the partition screen, read this post for details: Have a look at FAQs too- Q4/A4 in particular: Reading your first post it seems you have to be playing with rdisk value too, you most likely have another disk or storage device on the way. Just experiment a bit with the rdisk values. partition values you should be able to get from where the first link explains. The tool is NOT limited in that matter, but one has to know how to use it. FYI- there are number of tools and methods in the pinned topics which do not have these drawbacks, no files are deleted and no messing with boot.ini.

You may also try in advanced options in WinSetupFromUSB to select "Display disk drives on all interfaces, not only USB" and press refresh button.

Have you tried another flash drive? Which version of HP USB format tool did you use? Later than 2.0.6 if I recall correctly do NOT do the job, 2.0.6 is included in WinSetupFromUSB 0.2.3. Another possibility is that the WMI query if the device has a primary partition does not work that way in Windows 2000 or does not work at all. They should be using Windows APIs part of kernel.dll, ntdll.dll etc. etc, not executing single files such as format.com and the likes so I wouldn't be taking this path at all.Reminder:

I'd prefer to run it in Windows 2000 if possible. I tried WinSetupFromUSB but I get this when trying to format the drive: Did you try if the stick is bootable, ignoring the error message? From what I can see RMPrepUSB did its job. There are also FBinst/FBinstTool (you need to google a bit or search in reboot.pro for its usage) and PEtoUSB (limited to 2(4) GB disks) in \files\tools folder. You may also use HP USB format utility which is included in 0.2.3 version.Under 2000 you also might be good simply to use the built in disk management.

Can you zip and attach your txtsetup.sif file? In beta7 I think that issue was fixed, wonder what's in your file that it didn't recognize 2000 source. Do you get the black screen in Text mode once drivers are loaded, or after reboot and star t of GUI mode? Yep, it is. There are lots of things happening in background, I have no idea how to add a simple, but descriptive enough window saying what's going to happen. Basically, it's going to add to USB flash/hard disk whatever was chosen in the options One may watch the status bar and/or select SHOW LOG which window shows a lot of detailed information what's exactly going on. GO button becomes STOP once pressed. PAUSE button on the keyboard pauses the program.