PROBLEM in USB MULTIBOOT 10

[(=EZEKIEL=)]

Sir.

Good day!

i already red all of the thread regarding

how to and guidelines in making MULTIBOOT USB

but unfortunately i can't get a successful MUltiboot usb.. =(

i think i did it on the right way like

on what you've post..

i used USB_MULTIBOOT10.cmd

i click it and i follow all the instructions .as is...

and i begin to boot the pc using usb drive.

yes,i can see all the menu and i select the

1. text menu...etccc..... => to install windowXP

it load up all the drivers but after the STARTING WINDOWS

the BSOD appears.. so i try to modified the NTDETECT.com using

Tiny Hexer as you said..

i booted it up again and it loads all the driver and after the STARTING WINDOWS text

the BSOD still up again. and it saying SESSION3_INITIALIZATION_FAILED

i did already configuring my CMOS and Bios and IDE config.

but i still get the same problem..

sir i've almost a week doing this USB_MULTIBOOT10.. =)

but i think im the unlucky ones..

can you please HELP me with this.!?!?!?!

P L E A S E ! ! ! !

if you can't reply

here's my ym gil_gela@yahoo.com

THANKS! and

Best Regards!

[wimb]

You might be missing SATA Drivers.

Look here http://www.boot-land.net/forums/index.php?showtopic=4900

2. XP-Source Preparation - *** BEFORE YOU START ***

http://driverpacks.net/DriverPacks/

For Install of XP on a modern system with SATA Drives it is needed to use DPsBase.exe

for Integrating in your XPSOURCE BTS DriverPack Massstorage with TXT Mode Enabled.

In that case a lot of Extra RAID SCSI and SATA Drivers (about 120 extra) are Integrated which appear in the

XP Setup BootFolder $WIN_NT$.~BT on USB-Drive and can prevent a lot of XP Install Boot Problems.

First use RyanVM Integrator and then use DPsBase to Improve your XP-Source.

As alternative I advise you to use the NEW technique, which in my view is the Preferred approach.

Install XP from USB AFTER Booting with PE from HDD or USB using USB_XP_Setup.cmd

http://www.boot-land.net/forums/index.php?showtopic=5306

The advantage of the NEW technique is that there are no changes needed in the BIOS Setting.

Booting for XP Setup occurs all the time as normal from the C-Install Drive if you Install on C-Drive.

Thus the USB-stick does not need to be bootable

and it is not needed that the motherboard supports booting from USB.

So this is Install XP from USB without booting from USB

[(=EZEKIEL=)]

thanks sir..!

but how can i make a Modified XP

to be boot in USB??

or is there any possibility to make

it in BOOTABLE in USB ?=)

Edited October 8, 2008 by (=EZEKIEL=)

[wimb]

• Copy your XP CD to XPSOURCE folder on harddisk.
  
• First use RyanVM Integrator and then use DPsBase to Improve your XPSOURCE Folder.
  
• Then Run USB_MultiBoot_10.cmd to make your USB-stick
  

[(=EZEKIEL=)]

yess i already made a Usb bootable windows installation.

i follow your instructions wimb. but what i did is this,,

after the procedure no.2. i copy all the output

files that build by the RyanVM to the XPSOURCE Folder

in c:.. am i did it right?? or it is not to be on that way..?!?!?

thanks! =)

[cgbp]

I also encountered the same problem (BSOD just b4 going into Windows setup)

The multiboot method is great. Simple to understand and execute. Far better than the the many wall of text ones out there.

But doesn't work on my 702 model (1Gb ram and 8Gb ssd)

Anyone can provide simpler instructions on how to solve the blue screen problem during installation of Winxp??

[wimb]

Read here

http://www.boot-land.net/forums/index.php?...5306&st=106

[ilko_t]

I also encountered the same problem (BSOD just b4 going into Windows setup)

The multiboot method is great. Simple to understand and execute. Far better than the the many wall of text ones out there.

But doesn't work on my 702 model (1Gb ram and 8Gb ssd)

Anyone can provide simpler instructions on how to solve the blue screen problem during installation of Winxp??

You also should be using SP2 or SP3 if error code is not 0x0000007B.

What is the error code on the blue screen?

[cgbp]

Thanks to ilko_t

I checked a couple of older threads and turned out SP2 (or 3) was the saviour.

Previously I was using an old WinXP only CD.

After I slipstreamed SP2 to it and re-did everything, the installation works fine now.

[stiffy420]

I also have some trouble using Multiboot 10.

first i tried a nlited win xp home sp1, i kept manual install, but it just halts when it is about to copy the installation files, just a black screen and nothing happens.

then i tried MicroXp, which also is a nlited winxp, but there i got BSOD when its gonna copy the files.

at last i got to work with a clean copy of win xp home.

but i want to run a nlited casue im using a asus eee 1000h.

please help!

[ilko_t]

Why don't you nLite the copy which worked, there are plenty of guides around?

AFAIK on Asus EeePC you should be using at least SP2. The post above yours confirms this, and at the same time you are asking why the SP1 copy did not work

[stiffy420]

I tried to use Nlite on the copy that worked, and its SP1. just got a black screen when its about to start windows, after loading drivers.

the untouched windows sp1 worked fine.

but i really want to use MicroXP or my nlited version. cant stand bloatware =)

edit: if i remember it right the error code was 0x0000006f

Edited November 20, 2008 by stiffy420

[jaclaz]

MicroXP is a known WAREZ release.

You won't find assistance or help with it on the Forum.

Heck, SP2 was released in 2004:

http://en.wikipedia.org/wiki/Windows_XP

and there were REASONS for it.

While "forcing" SP3 might be overkill, SP2 should be the minimum pre-requisite.

jaclaz

[stiffy420]

ok, i see. but i have a legit windows key, got it when i bought my eee 1000h.

i had no luck nliting myself anyways...

[jaclaz]

Well, this is strange as well.

I mean nlite has users that can be counted in the tens if not hundreds of thousands.

The USB_multiboot has as well a very large "base", and an expecially large one coming from eeePC owners.

The reports about problems with both, are actually comparatively very few, and usually (no offence whatsoever intended to anyone, just trying to sum up experience ) after some troubleshooting they are solved, and the reason found to have been:

1) in very few cases by an actual problem with the app, that nuhi (for nlite) or wimb/ilko_t (for the install Xp from USB) generally fix in a few days at the most

2) in a large number of cases by people wanting to use features that are simply not there/ or using untested or modified source, or, again, not following instructions and introducing variations

3) in another large number of cases by various PBCAK related problems:

http://acronyms.thefreedictionary.com/PBCAK

Your problem seem to belong to #2) above.

You need a pragmatic approach.

Re-create a SP2 nlited version, keeping the components needed for install (see FAQ's).

Follow EXACTLY the available documentation/howto's, BOTH for nlite and for the USB install, do not rmove "too much".

DO not introduce variations.

Try and see if it works.

Report exactly the BSOD error (if any).

If everything goes well (by any chance) try removing something else, and loop through the steps until you actually get back the BSOD.....

...then redo what you did in your previous attempt....

jaclaz