[laddanator]

Quote

[Boot Loader]
Timeout=30
Default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS
[Operating Systems]
C:\$WIN_NT$.~BT\BOOTSECT.DAT = "1st, text mode setup (Boot from flash again after finished)"
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="2nd, GUI mode setup, continue setup + 1st start of Windows" /fastdetect
C:\ = "---> DEBUG, in case of HAL.DLL or NTOSKRNL.EXE not found errors <---"
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="Debug boot rDisk 1 partition 2" /fastdetect
multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="Debug boot rDisk 1 partition 3" /fastdetect
multi(0)disk(0)rdisk(1)partition(4)\WINDOWS="Debug boot rDisk 1 partition 4" /fastdetect
multi(0)disk(0)rdisk(2)partition(1)\WINDOWS="Debug boot rDisk 2 partition 1" /fastdetect
multi(0)disk(0)rdisk(2)partition(2)\WINDOWS="Debug boot rDisk 2 partition 2" /fastdetect
multi(0)disk(0)rdisk(2)partition(3)\WINDOWS="Debug boot rDisk 2 partition 3" /fastdetect
multi(0)disk(0)rdisk(2)partition(4)\WINDOWS="Debug boot rDisk 2 partition 4" /fastdetect

Is this created in txtsetup.sif?

[jaclaz]

laddanator, on 06 January 2012 - 08:55 AM, said:

Is this created in txtsetup.sif?

OWWW, comeon , that's a BOOT.INI.
JFYI:
http://www.msfn.org/...ent-hard-drive/

jaclaz

[laddanator]

Quote

OWWW, comeon , that's a BOOT.INI

Yup...saw this [Boot Loader] and meant to edit post as to never mind just saw this kinda thing but got side tracked

This post has been edited by laddanator: 06 January 2012 - 11:30 AM

[jaclaz]

Bymnadvanna, on 16 January 2012 - 02:05 AM, said:

Desidero parlare con voi, ho qualcosa da dire.

Who is the "voi" (you)?

If you have something to say, we are all ears, but you may want to post in English on the board.

jaclaz

[puntoMX]

Bymnadvanna, on 16 January 2012 - 02:05 AM, said:

Desidero parlare con voi, ho qualcosa da dire.

Right, you want to "have a conversation about anything"? Not here... Keep it on-topic and in English.

[ilko_t]

For everyone using 1.0 beta7 version of the program and already put Windows 2000, XP, or 2003 source(s) on USB disk- a quick bug fix before the next version is ready.

There are a few lines in winsetup.lst to be edited to avoid possible "I/O error...." errors at the very beginning of Text mode.
The error would come up only if you previously started one of your Windows 2000/XP/2003 setup sources on computer with 2 or more internal hard disks and use the same setup source on a computer with different number of internal disks.
This happens because BootDevice and SetupSourceDevice values in TXTSETUP.SIF in the small ISO file got permanently changed to new rdisk(X) values, thus consequent search for rdisk(1) & replace with rdisk(Y) will fail as rdisk(1) has been set to other value, according to the number of the hard drives connected in the previous boot of this menu entry. In other words- Setup will be searching for its files in the wrong disk and will throw an error that the disk is not accessible.

Edit in root of the USB disk winsetup.lst in Notepad and change the line:

map /WINSETUP/_ISO_FILENAME (0xff) || map --mem /WINSETUP/_ISO_FILENAME (0xff)

where _ISO_FILENAME will vary according to your source, to:

map --mem /WINSETUP/_ISO_FILENAME (0xff)
map --e820cycles=3

Also replace GRLDR file in root with the one in this archive:
http://grub4dos-chen...b-2011-12-30.7z

You need only the GRLDR file from the archive.

If you already are experiencing the "I/O error", you may recreate the USB disk, or edit TXTSETUP.SIF in all present small ISO files in WINSETUP folder using UltraISO or a similar program and change all occurrences in SetupData section from rdisk(X) to rdisk(1) where X will vary. Next change the above mentioned lines in winsetup.lst to avoid further issues of this sort.

[laddanator]

Quote

Edit in root of the USB disk winsetup.lst in Notepad and change the line:

map /WINSETUP/_ISO_FILENAME (0xff) || map --mem /WINSETUP/_ISO_FILENAME (0xff)

where _ISO_FILENAME will vary according to your source, to:

map --mem /WINSETUP/_ISO_FILENAME (0xff)
map --e820cycles=3

Works like a charm. Thanks, ilko_t

[Bojann]

What is the procedure putting two type windows XP installation on one USB? Is it possible to have two Windows XP versions?

This post has been edited by Bojann: 02 February 2012 - 05:10 AM

[Bojann]

OK, so I managed to find the tutorial to install both windows, but I have problem installing grub4dos. Every time i get error tha it cant copy the GRDL file to USB.

"Error: Grldr failed to copy to USB drive G:! File not found"

I have followed the steps shown here: http://www.rmprepusb...to-internal-hdd

[wimb]

You can also try to use the procedure described here
http://www.911cd.net...showtopic=24424
http://www.911cd.net...showtopic=23931
http://www.911cd.net...showtopic=23553

In that case:
- First use BOOT_USB.exe to prepare USB drive for booting with Grub4dos Menu and using Boot Image file
- After booting with PE or Portable XP from USB, you can use R-mouse to Mount Windows Setup ISO in ImDisk virtual drive
- Then use WinNTSetup2_x86.exe to prepare your Target drive for Install of XP or Windows 7
- Reboot from Target drive and Install XP or Windows 7

This post has been edited by wimb: 02 February 2012 - 05:50 AM

[Bojann]

Wimb , thanks for your help. Here is what I need. I need to use USB to instal two different versions of Windows XP pro, and All In One Windows 7.
I managed to solve problem with copyng GLRDL file by downloading the latest RMPrepUSB program
Now, If I format the drive using NTFS file system, I get error while booting from usb "Cannot find GRLDR" (or something). If I format the flash driver using FAT, everything is OK. I need NTFS because it is faster and one of my ISO's is 4 GB large. Can I use BOOT_USB that you suggested to install multiple version of Windows?

After all of this, I would like to add portable versions of Windows XP and Win7, BootCD and UBCD. Is all this possible on one USB flash disk?

Thanks for your anwser in advance

This post has been edited by Bojann: 02 February 2012 - 06:46 AM

[wimb]

You can use BOOT_USB.exe to format USB-stick with NTFS filesystem.

Instead of USB-stick, it is much better to use Portable 2.5 inch USB harddisk e.g. Samsung S2

In that case the speed is much higher and the larger capacity (e.g. 500 GB) is useful for your purpose.
Besides, then you can use normal windows OS to partition and format such USB disk,
and you can use BOOT_USB.exe to prepare USB drive for booting with Grub4dos Menu and using Boot Image file.

You have enough space for all your Windows Setup ISO files and can make it bootable with all other IMG or VHD files.

This post has been edited by wimb: 02 February 2012 - 06:58 AM

[moataz]

Hello guys,

I'm in the process of setting up xp from Samsung G2 320 GB (USB Hard Disk)

my USB Hard is formated as follows:
1st primary partition NTFS - 8 GB Active (destination drive)
2nd extended ~290 GB

After text setup finished, just after boot screen passes, it's BSOD 0x000000C2

Any info?

[ilko_t]

Is this a customised source?
Do you boot for the second part from USB again or directly from the internal disk?

[moataz]

ilko_t, on 10 February 2012 - 12:43 PM, said:

Is this a customised source?

I have tried both (customized and untouched) with sata.

ilko_t, on 10 February 2012 - 12:43 PM, said:

Do you boot for the second part from USB again or directly from the internal disk?

it doesn't matter also, i thought it might be problem with this rdummy.sys, cause WinSetupFromUSB doesn't made such error from USB Flash.

i also found that there is no need for boot.ini to be in the root of the USB at all. i'm booting from internal hard disk like this:

map (hd1) (hd0)
map --hook
rootnoverify (hd0,0)
chainloader +1

[ilko_t]

Which version of the program have you used? I guess 0.2.3, right?

Quote

WinSetupFromUSB doesn't made such error from USB Flash

Let's stand correct, it's windows throwing an error, for a reason yet to be determined.
Windows handles USB flash and hard disks in a different way. In addition, USB hard disks have a spin-up time as well as power saving functions which may cause a critical delay when accessing the disk.

Quote

i also found that there is no need for boot.ini to be in the root of the USB at all. i'm booting from internal hard disk like this:

map (hd1) (hd0)
map --hook
rootnoverify (hd0,0)
chainloader +1

Well, don't, that seems quite wrong with unpredictable results, despite the fact it might have worked for you.
Stick to tested and supported method of booting, to start with.

[moataz]

ilko_t said:

Which version of the program have you used? I guess 0.2.3, right?

Yes

ilko_t said:

Let's stand correct, it's windows throwing an error, for a reason yet to be determined.
Windows handles USB flash and hard disks in a different way. In addition, USB hard disks have a spin-up time as well as power saving functions which may cause a critical delay when accessing the disk.

ok, it seems that i just have to stay with the USB Flash.

ilko_t said:

Well, don't, that seems quite wrong with unpredictable results, despite the fact it might have worked for you.
Stick to tested and supported method of booting, to start with.

Please try it ilko_t, don't say "quite wrong" only cause i'm newbie, i just wanted to point to easier method.

[ilko_t]

moataz, on 10 February 2012 - 03:03 PM, said:

Please try it ilko_t, don't say "quite wrong" only cause i'm newbie, i just wanted to point to easier method.

Not saying because you are newbie, I don't even have a slight idea how newbie you possible could be reading only a few lines of yours, nor can I judge.
Even the idea is very good.

Lets put it this way- you have an issue, and you have a good idea how to boot the second part of setup, eliminating the need of boot.ini/ntldr/ntdetect.com on the USB disk.

Let's focus on the issue first- the start with, go back to the default behavior, leave boot.ini/ntldr/ntdetect.com alone on the USB disk and boot ntldr as the default and take it from there, eliminating any possible user interventions.

Once resolved, move to the good idea, test it with various ntldr/ntdetect.com versions and computers, confirm if that doesn't mess up disk enumeration later on and we are good to say "hey, that's a brilliant and working idea!". For now, for me, it's just a good idea, which in my slowly precessing and conservative mind needs time to bloom

Quote

ok, it seems that i just have to stay with the USB Flash.

Not necessarily. If you have the willingness to troubleshoot the problem you have, here we are, all yours.
But you will have to forget what you have in mind, and just follow the advices given. Sounds reasonable?
Or are you giving up only because there was no quick answer do A and all is good?

Quote

Yes

There is also a much newer beta versions with lots of improvements over the previous versions, the first one having no requirement to boot from USB twice, and being beta only because the method of installing is relatively new and not that long tested.

[IceBoy]

ilko_t, on 18 January 2012 - 12:31 PM, said:

For everyone using 1.0 beta7 version of the program and already put Windows 2000, XP, or 2003 source(s) on USB disk- a quick bug fix before the next version is ready.

There are a few lines in winsetup.lst to be edited to avoid possible "I/O error...." errors at the very beginning of Text mode.
The error would come up only if you previously started one of your Windows 2000/XP/2003 setup sources on computer with 2 or more internal hard disks and use the same setup source on a computer with different number of internal disks.
This happens because BootDevice and SetupSourceDevice values in TXTSETUP.SIF in the small ISO file got permanently changed to new rdisk(X) values, thus consequent search for rdisk(1) & replace with rdisk(Y) will fail as rdisk(1) has been set to other value, according to the number of the hard drives connected in the previous boot of this menu entry. In other words- Setup will be searching for its files in the wrong disk and will throw an error that the disk is not accessible.

Edit in root of the USB disk winsetup.lst in Notepad and change the line:

map /WINSETUP/_ISO_FILENAME (0xff) || map --mem /WINSETUP/_ISO_FILENAME (0xff)

where _ISO_FILENAME will vary according to your source, to:

map --mem /WINSETUP/_ISO_FILENAME (0xff)
map --e820cycles=3

Also replace GRLDR file in root with the one in this archive:
http://grub4dos-chen...b-2011-12-30.7z

You need only the GRLDR file from the archive.

If you already are experiencing the "I/O error", you may recreate the USB disk, or edit TXTSETUP.SIF in all present small ISO files in WINSETUP folder using UltraISO or a similar program and change all occurrences in SetupData section from rdisk(X) to rdisk(1) where X will vary. Next change the above mentioned lines in winsetup.lst to avoid further issues of this sort.

None of this works for me.

I've tried 5 programs to get xp on usb. They all don't work including this one. Why is there such a large volume of problems with xp on usb. MS made one that works for win7 that works 100%, unetbootin works 100% with linux distros. What is the deal with XP on USB that is so dam troublesome? Can I get an amen?

Anyways, how can I get this program to work?

I get I/o errors, I did the edit thing, then I get couple other errors with numbers like Error 11, (I just got error 15 right after I replaced GRLDR with recommended GRLDR in the zip.)

I am so frustrated, I've been on this mission for 15 hours. I'd use a cd rom drive but I dont have one and cannot get one.

This post has been edited by IceBoy: 11 February 2012 - 09:22 PM

[ilko_t]

Quote

None of this works for me.

Then you have some other problem.

Quote

Why is there such a large volume of problems with xp on usb

Because installer used in up to 2003 incl. is poorly documented and ancient, since times when not only USB boot was not possible, but USB was not even out. Thus USB has never been kept in mind.

Quote

unetbootin works 100% with linux distros

Open source? If Microsoft have published Windows code it probably would have been much different. But that's another story.

Quote

Anyways, how can I get this program to work?

Mostly by giving proper information what exactly the errors are and when they appear.

Quote

I get I/o errors

When exactly and what error code?

The easiest thing would be to start from a scratch. Reformat the USB disk and prepare it again. Replace the files and lines mentioned. Report what errors do you see and when exactly.
I am thinking that BIOS sees the USB disk as a superfloppy/zip disk, hence the problems. But let's first rule out any interventions.

What hardware are you installing to? Motherboard or laptop model? Using what USB disk?