Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Photo

USB Booting issues

- - - - -

  • Please log in to reply
55 replies to this topic

#26
toja92

toja92

    Newbie

  • Member
  • 40 posts
please remove this post, thanks ;)

Edited by toja92, 06 July 2008 - 09:05 AM.



How to remove advertisement from MSFN

#27
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
Check, re-check, and triple check EVERYTHING.

Set the BIOS to use as less "advanced" options as possible, disable in it any device that is not vital, like audio, parallel ports, network card, etc.

Boot with /BASEVIDEO and /BOOTLOG
http://technet.micro...s/bb963892.aspx

Check the the file %SystemRoot%\Ntbtlog.txt

POOL_BAD_DRIVER says nothing to me, post the CODE of the BSOD, and any other reference.
http://www.geekstogo...des-t43519.html
http://northtechs.com/blscreen.htm
http://www.updatexp....p-messages.html

Check the Event Viewer files on a working machine:
http://support.micro...kb/165959/en-us

i.e. *.evt under %SystemRoot%\System32\Config\

This app has a FREE personal license:
http://www.eventlogxp.com/

A good idea could be that of starting again from scratch.

I assume you ALREADY tested the nliting by installing from the modified source on a "normal" HD, didn't you? :unsure:

Use the files I posted, after having re-chacked them.

jaclaz

#28
toja92

toja92

    Newbie

  • Member
  • 40 posts
"I assume you ALREADY tested the nliting by installing from the modified source on a "normal" HD, didn't you?" Actually, no. I don't have any spare / extra harddrive laying around here. I have a external drive, but I don't want to "challenge destiny". That's why I want to install to my usb drive, so I don't have to use a extra harddrive.

"POOL_BAD_DRIVER says nothing to me, post the CODE of the BSOD, and any other reference." Tricky part, the bsod flashses by one second and then my computer restarts. Should I disable "reboot on system errors" when I press F8 before windows tries to boot?

Actually, it works (partially) with your .sif and .in_/.inf files. And no, I can't use the automated way, I don't know which computer I should do these steps on (it changes some system files, right? plus I can't NLite the files also ;))

I attached ntbtlog.txt (Or, one "normal" and one in "safe mode")

Attached Files


Edited by toja92, 06 July 2008 - 09:30 AM.


#29
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag

"I assume you ALREADY tested the nliting by installing from the modified source on a "normal" HD, didn't you?"


Actually, no. I don't have any spare / extra harddrive laying around here. I have a external drive, but I don't want to "challenge destiny". That's why I want to install to my usb drive, so I don't have to use a extra harddrive.


Yes, but the result is that you cannot boot from it, and we have several "layers" of possible causes:
1) the "quality" of the source (meaning the number of integrated SP's and KB fixes/security updates)
2) the "entity" of your nliting (did you remove too much? :unsure:)
3) hardware drivers
4) "my" .sif and .inf's

You should AT LEAST try installing your source (WITHOUT and WITH) the USB mods, in a Virtual Machine, VirtualBox should be allright:
http://www.virtualbox.org/

"POOL_BAD_DRIVER says nothing to me, post the CODE of the BSOD, and any other reference."


Tricky part, the bsod flashses by one second and then my computer restarts. Should I disable "reboot on system errors" when I press F8 before windows tries to boot?

YES, it is VITAL to know which exact error is, it may help in finding what the problem is.
You can change the Registry Entry:
http://www.pctools.c...try/detail/229/
autoreboot to 0
(Offline you will need to access ControlSet001 instead of CurrentControlSet)


Actually, it works (partially) with your .sif and .in_/.inf files. And no, I can't use the automated way, I don't know which computer I should do these steps on (it changes some system files, right? plus I can't NLite the files also ;))

No, it does not change system files, only cannot say if it would run under Vista.

I attached ntbtlog.txt (Or, one "normal" and one in "safe mode")

As expected, (since you get to the logon screen) the initial loading appers to be OK, the error happens later, do check the Event Logs.

jaclaz

#30
toja92

toja92

    Newbie

  • Member
  • 40 posts
Just remembered, have Microsoft Virtual PC 2007 Lol,... Will try right away... :P

EDIT: Seems like it's removed, trying virtual box instead.

EDIT2/update: Virtual Box is better than Virtual PC 2007, I have to admit. Now I can do the "fully automated" way, because I can "insert" my usb drive to the virtual XP. Here's the error message I got by the way:
***stop: 0x000000c2 0x00000007 0x00000CD4 0x00000000 0xE15D0004
I will try the automated way & report back ;)

EDIT3: Oh noes, I managed to write the MBR of the stick to my external drive, so now windows thinks it needs to be formatted and acronis disk director suite only finds a 1.91 gB (exactly the size of my stick) of the drive. Do you know how to recover my data? I'm searching with acronis disk direcor suite now to see if I find a deleted partition, but how should I do if it can't find it?

Nevermind. Will backup necessary files to various mp3's, my stick and my internal drive, so I'll work it out. Besides I will probably buy another 500 gB tomorrow, or in two days :D

EDIT4: Installed a nlited xp sp 3 in a virtual machine. It runs good. Used USBoot, worked good. Copied the files to my stick. Worked good. Trying to boot. Total failure. I tried replacing the bootsector with bootsect /nt52 <driveletter>, before doing that, it said invalid system disk. Now I only see a black screen, no "_" or something. So I don't know how to continue. Any clues?

Edited by toja92, 06 July 2008 - 04:08 PM.


#31
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
You can use testdisk:
http://www.cgsecurit...g/wiki/TestDisk
to recover your partition table.

SP3 is YET ANOTHER variable that you added. WHY?

...and possibly slipstreamed with nlite under Vista, which adds YET ANOTHER variable. :w00t:

Try with XP SP1 or SP2, NOT SP3.

To make the stick bootable, since for unknown reasons the programs that work for everyone do not work on your hardware/software, you can as you already did, re-use the MBR manually made, then re-format the stick and apply bootsect /nt52, make sure it boots with NTLDR+NTDETECT.COM+BOOT.INI before copying the files to stick.

REMOVE ANY OTHER USB DEVICE (excluded Mouse and Keyboard if USB) when working with bootable USB sticks.

As expected, the error is IRQ/Driver related.

Search for "0x000000c2" with google.

jaclaz

Edited by jaclaz, 07 July 2008 - 01:46 AM.


#32
Ponch

Ponch

    MSFN Junkie

  • Patrons
  • 3,238 posts
  • OS:none specified
  • Country: Country Flag
Just to add to the confusion, I once had a bad_pool_driver BSOD, the cause was a bad memory stick. Now maybe this can have other causes too.

#33
toja92

toja92

    Newbie

  • Member
  • 40 posts
"REMOVE ANY OTHER USB DEVICE (excluded Mouse and Keyboard if USB) when working with bootable USB sticks." Actually the only other usb device connected to my computer while trying, is my usb adapter (usb -> PS/2). I will try without SP3 now, and see how it goes. If it works, I'll try installing SP3 in portable XP instead.

#34
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
Just for the record, and should anyone have the same type of problems, the "magic numbers" in partition table I gave before can be easily calculated with the spreadsheet you can find here:
http://www.boot-land...?showtopic=2959

Actually the only other usb device connected to my computer while trying, is my usb adapter (usb -> PS/2).

Yep, but besides testing booting from the stick, it is a good idea to have anything removed also when "fiddling" with it, as you appear to have learned the "hard" way ;):

EDIT3: Oh noes, I managed to write the MBR of the stick to my external drive, ....


jaclaz

#35
toja92

toja92

    Newbie

  • Member
  • 40 posts
Total success! Using USBoot with SP2 worked perfect, now its working exactly as it should :D :D Big thanks for your help, jaclaz :thumbup Now I need to find alot of drivers, but that is not a problem. Thanks!

Edited by toja92, 07 July 2008 - 05:21 AM.


#36
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
Happy to hear a story of success! :)

jaclaz

#37
toja92

toja92

    Newbie

  • Member
  • 40 posts
Hmm is it possible you can help one more time? I bought a new 8gb usb stick, and it won't boot, and I have no idea why. I did a bootsect /nt52 but it didn't work, so I think the problem is within the MBR. Thanks in advance :thumbup

Attached Files



#38
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag

Hmm is it possible you can help one more time? I bought a new 8gb usb stick, and it won't boot, and I have no idea why. I did a bootsect /nt52 but it didn't work, so I think the problem is within the MBR. Thanks in advance :thumbup


I will :), if you tell me what the heck did you use to fdisk/format the stick this time. ;)

The MBR code is NOT a standard NT/2K/XP/2003 nor Vista one. :w00t:

Open the stick in beeblebrox, and try setting the "Boot" to 80 (currently it is 00, i.e. you have currently NO partition active).

Then, your geometry is once again "gone beserk"!
You have:
0B-00-0-1-1-243-32-63-32-15974368

Should be one of the following:
0B-80-0-1-1-243-254-63-63-3919797
0B-80-0-1-1-243-254-63-63-3919797
0C-80-0-1-1-242-254-63-63-3903732
0C-80-0-1-1-242-254-63-63-3903732

SO:
1) Use beeblebrox to write one of the given set of values
2) Eject and reinsert stick
3) Format the stick
4) Run bootsect.exe /nt52 against the stick
5) Copy to the stick NTLDR/NTDETECT.COM/BOOT.INI
6) Try booting from the stick
7) if it does not boot, loop to 2) and try another set of values

If it still does not boot,
Use MBRFIX:
http://www.sysint.no...ting/mbrfix.htm
http://www.sysint.no...NO/Default.aspx
MbrFix /drive <num> fixmbr
to fix the MBR code
and loop back to 1)

Report.

jaclaz

#39
toja92

toja92

    Newbie

  • Member
  • 40 posts
Acutally, it was preformatted from factory (brand new). If possible, is it necessary to format the stick? Oh well...

EDIT: If you want to know, it took a half hour to move 606 MB via virtualbox. My other usb memory, older, took maybe 3-4 minutes...

Edited by toja92, 09 July 2008 - 05:21 AM.


#40
toja92

toja92

    Newbie

  • Member
  • 40 posts
Hmm... writing either of those MBR's makes Vista lag incredibly. If I remove the drive vista becomes normal but as soon as I insert it it becomes slow. I managed to make it "half-working", it doesent display "System error, press ctrl+alt+delete to reboot", but instead a "_".

#41
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag

Hmm... writing either of those MBR's makes Vista lag incredibly. If I remove the drive vista becomes normal but as soon as I insert it it becomes slow. I managed to make it "half-working", it doesent display "System error, press ctrl+alt+delete to reboot", but instead a "_".


WHICH MBR's? :unsure:

Did you run MBRFIX?

Start again, run the HP formatting utility and post the MBR and bootsector, extracted with hdhacker, after running it.

jaclaz

#42
toja92

toja92

    Newbie

  • Member
  • 40 posts
I need some help again, I bought a new usb stick which don't work to boot.. Anyways I attached both the MBR and the bootsector and hope you can help me a final time. Here is the value I get with Beeblebrox: 0B-80-0-1-1-979-254-63-63-15743637

Attached Files



#43
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
The MBR appears to be OK, it is a 16 Gb stick formatted as FAT32 0B, i.e. CHS mapped.

The bootsector appears to have both invalid data and to be non-standard.

WHAT did you use to try and format it? :w00t:

It appears like you used an Acronis product on the stick. :whistle:

I would zero out the first, say, 100 sectors (just to make sure) then try running fuwi's newish batch/app:
http://www.911cd.net...showtopic=21702

Please report.

jaclaz

#44
toja92

toja92

    Newbie

  • Member
  • 40 posts
The stick is 8 gB, not 16 :P But maybe the MBR was weird, I dont know. I tried fuwi's batch, and it didn't work.. Before nothing happened, now i see this non-system disk error. I tried bootsect /nt52 but nothing happened after that. I also get NTLDR is missing, but it isn't. Any idea?

#45
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
I will repeat myself, do zero out first 100 sectors of the device
Try running fuwi's batch. (running it WITHOUT zeroing out the first sectors is NOT what I want, I need it run on a zeroed out stick)
DO NOT RUN ANYTHING ELSE.
Post the MBR and bootsector resulting from the above procedure, NOT those coming from ANY OTHER procedure.

This is the ONLY way I can:
1) make sure that no leftovers cause problems
2) that the batch did it's work properly

jaclaz

#46
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
I will repeat myself, do zero out first 100 sectors of the device
Try running fuwi's batch. (running it WITHOUT zeroing out the first sectors is NOT what I want, I need it run on a zeroed out stick)
DO NOT RUN ANYTHING ELSE.
Post the MBR and bootsector resulting from the above procedure, NOT those coming from ANY OTHER procedure.

This is the ONLY way I can:
1) make sure that no leftovers cause problems
2) that the batch did it's work properly

jaclaz

#47
toja92

toja92

    Newbie

  • Member
  • 40 posts
I done that and posting MBR and BootSect here. Thanks for your help.

Attached Files



#48
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag
OK, now it's better.

As often does, the HP Utility created a 0C (FAT32 partition LBA mapped) with correct LBA values but wrong CHS ones.
In other words, changing the partition type to 0B (FAT32 CHS mapped) may give wrong results.

The FAT32 partition was formatted using the DOS bootsector (the one invoking WINBOOTSYS/IO.SYS). :blink:

First thing to try is to add to the stick the DOS files (from a Win9x/Me bootdisk):
IO.SYS
MSDOS.SYS
COMMAND.COM
and see if it boots.

A possible way to fix:
1) Open the MBR with Beeblebrox, and change current:
80-0C-0-1-1-979-254-63-63-15744960
to:
80-0C-0-1-1-979-254-63-63-15743637
to "balance" CHS and LBA
2) remove the stick
3) re-insert stick
4) Format it from the running OS
5) If running Vista, run bootsect.exe /nt52 <DriveLetter:> /force
to change the bootsector code to the Windows NT/2K/XP/2003 one
6) Add to the stick:
NTLDR
NTDETECT.COM
BOOT.INI
7) see if it boots.

Another possible way:
a. do ONLY steps 4) to 6)
b. open the MBR with BEEBLEBROX
and change from:
80-0B-etc. (if present) :unsure:
to
80-0C-etc.

A third way, if the stick proves to boot from DOS:
1) copy to the stick BOOTPART.EXE:
http://www.winimage.com/bootpart.htm
2) boot to the DOS on the stick
3) run:
BOOTPART.EXE WINXP BOOT:C:
4) Add to the stick:
NTLDR
NTDETECT.COM
BOOT.INI
7) see if it boots.

A fourth way, if you are running Vista, is using the native diskpart as follows:
diskpart
list disk
select disk <discnumber>
clean
create partition primary size=<size of usbstick>
select partition 1
active
format fs=fat32
assign
exit
then use bootsect.exe as previously detailed to create a bootsector invoking NTLDR.

A fifth way (never tried it, mind you) could be to rename NTLDR to BOOTMGR, leaving the VISTA bootsector as is. :unsure:


If none of the above works, at the moment the only way out is to use (as provided in fuwi's
batch) grub4dos as a workaround.

jaclaz

#49
toja92

toja92

    Newbie

  • Member
  • 40 posts
The only method I got working is fuwi's batch. But I have never used grub4dos before, and when I boot, I see the vista-like screen he put there, and then I see a flashing message:

booting Bart PE

error 0X<something>
there were some other text here but I don't know what it was.


After this the computer reboots. So now I need help with editing the config file, can you possibly help me with this? :thumbup:

#50
jaclaz

jaclaz

    The Finder

  • Developer
  • 14,026 posts
  • OS:none specified
  • Country: Country Flag

The only method I got working is fuwi's batch. But I have never used grub4dos before, and when I boot, I see the vista-like screen he put there, and then I see a flashing message:

booting Bart PE

error 0X<something>
there were some other text here but I don't know what it was.


After this the computer reboots. So now I need help with editing the config file, can you possibly help me with this? :thumbup:


Sure, if you tell me what you are trying to boot. ;)

Basically you should have in ROOT of your stick (some files may be hidden):
IO.SYS
MSDOS.SYS
COMMAND.COM
CONFIG.SYS
LOGO.SYS
\grub4dos\grub.exe
NTDETECT.COM
NTLDR (this should be a SETUPLDR.BIN renamed)
wimbom.ini
\minint (if you are booting a XP/2003 based PE this directory contains the files)

The booting procedure, "as is" is the following:
1) MBR chainloads bootsector
2) bootsector chainloads DOS system files (IO.SYS, MSDOS.SYS, COMMAND.COM)
3) since a LOGO.SYS file is present, INSTEAD of the "usual" Windows 98 bootscreen that bitmap is displayed
4) CONFIG.SYS is parsed and executed
5) the following grub4dos menu.lst (that is written in CONFIG.SYS) is executed:
timeout 0
default 0
title Booting BartPE
find --set-root /ntldr
chainloader /ntldr

The easiest would be to:
1) Move grub.exe to ROOT of the stick
2) change CONFIG.SYS from:
device=\grub4dos\grub.exe --config-file="timeout 0;default 0;title Booting BartPE;find --set-root /ntldr;chainloader /ntldr"
to:
device=grub.exe --config-file=menu.lst
3) Add to ROOT of the stick a "conventional" menu.lst:
timeout 30
default 0
title Booting BartPE
find --set-root /ntldr
chainloader /ntldr

title Another way to boot BartPE
find --set-root /minint/SETUPLDR.BIN
chanloader /minint/SETUPLDR.BIN
(of course adding the proper entry for whatever you want to boot or experimenting with command line)

Do take a bit of time reading diddy's grub4dos guide:
http://www.boot-land...?showtopic=5187
so that you get familiar with basic grub4dos commands and menu entries. :)

Once the above works, one can try installing to the stick the grldr.mbr, that has been reported by ktp as working allright on biggish FAT32 volumes, thus bypassing the loading of DOS.

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users



How to remove advertisement from MSFN