USB Booting issues Original title "BOOTMGR Missing"
Posted 03 July 2008 - 02:20 AM
Something that has proved to be working is to "wipe" the first, say 100 sectors by writing 00's to them, see here:
before re-running the HP utility.
Alternatively or additionally try using the batch by fuwi referenced before.
Alternatively or additionally, you can try my "indirect" way through batch:
Alternatively or additionally, do try once again formatting it with the HP utility as FAT (yes it is FAT16), then use hdhacker:
make a copy of BOTH MBR (physicaldrive) AND bootsector (logicaldrive) of your USB stick, compress them in a .zip archive and post the .zip file as attachment, and I'll have a look at them.
Posted 03 July 2008 - 04:04 AM
This post has been edited by toja92: 03 July 2008 - 12:28 PM
Posted 03 July 2008 - 05:12 AM
WHY did you save them as .txt?
They are filled with 2E's
What did you use to 00 fill the drive?
You didn't open them in NOTEPAD (or other non-binary-enabled application) and saved them, didn't you?
Since you are working with Vista , try using it's DISKPART utility as follows:
(to make sure that the USB stick is disk 1 below, if not change accordingly)
create partition primary
select partition 1
Remove the USB stick.
Reinsert USB stick.
Right click on it in Explorer and choose to format it.
Run bootsect.exe /nt52
Remove the USB stick.
Reinsert USB stick.
Use HDhacker to save MBR and bootsector, give to the files the extension .dat, do not open them with any program, just zip or rar them and attach them.
Posted 03 July 2008 - 12:26 PM
Quite hard to run since I don't have the DVD, I bought a cheap laptop with preinstalled Vista and I did not get a DVD with it, so I can't run it.
Anyways I skipped that step and posting the .dat files here.
Number of downloads: 9
This post has been edited by toja92: 03 July 2008 - 12:30 PM
Posted 03 July 2008 - 01:07 PM
I thought bootsect.exe wass installed by default, have you tried opening a command prompt and running it?
However the MBR you posted is simply "crazy", cannot say what may cause this behaviour.
Get beeblebrox here:
and use it to access your stick, you'll see values:
"Right" values should be:
Try correcting them, save changes, extract and reinsert USB stick, re-format it.
Still we need to find a way to correct the bootsector to invoke NTLDR if you do not have bootsect.exe, Vistabootpro should have a feature for it:
See if it works...
Posted 03 July 2008 - 02:01 PM
EDIT: Placed ntdetect.com, ntldr and boot.ini files, and it worked(I see the two fake entries I wrote in boot.ini) So, to see if it worked, I started the installation, copied the files (no change partitioning, so it's FAT16), and guess what? Same old blinking "_" and it don't work. I tried running a bootsect /nt52 again, changing boot.ini (the two old entries still not there and changed timeout to 30, but still, no dice. I appreciate your big help so far, do you know how I should continue? Can you make it boot some way? Remember, windows is "half-installed" (files only copied), or should I remove the files and try something else?
This post has been edited by toja92: 03 July 2008 - 02:49 PM
Posted 04 July 2008 - 01:05 AM
I need to know EXACTLY which steps you took for "starting" the installation, or if you prefer, a link to the tutorial you are using/trying to follow.
Since this "peculiar" machine (or couple stick/motherboard) appear to behave weirdly, ANY step that involves re-formatting or re-partitioning the stick should be avoided, if the stick is booting and after the whatever-you-do it is not booting anymore, it means that the procedure changes something.
For the record, a blinking cursor is usually connected to a problem with the bootsector, whilst the "Non system disk, replace and press any key" is usually connected to a MBR problem.
You should repeat the steps that made the stick bootable, I would try also - before formatting - to experiment in beeblebrox changing the 06 (FAT16 CHS mapped) to 0E (FAT16 LBA mapped).
Once you have a booting stick, simply use hdhacker to save both MBR and bootsector, then, once the stick fails to boot, simply restore those two sectors with hdhacker.
Please save your current (NOT BOOTING) MBR + bootsector, then repeat the procedure for making the stick bootable and save the (GOOD, BOOTING) MBR + bootsector, post the four of them, maybe I can find by looking at them what is wrong.
This post has been edited by jaclaz: 04 July 2008 - 01:10 AM
Posted 04 July 2008 - 05:53 AM
Number of downloads: 5
Posted 04 July 2008 - 07:14 AM
The three bootsectors are IDENTICAL (exception made for volume serial that is irrelevant).
The three MBR's are ALMOST identical:
Bad_MBR_HardDisk1.dat and MBR_HardDisk1.dat are identical.
Win_XP_MBR_HardDisk1.dat, instead has partition type set as 0E instead of 06.
The non-booting of the couple Win_XP_MBR_HardDisk1.dat+Win_XP_BootSector_DriveH.dat can be attributed to the partition type change (it should mean that your motherboard BIOS does not like LBA addressing on USB stick).
But there is NO reason why the couple Bad_MBR_HardDisk1.dat+Bad_BootSector_DriveH.dat does not boot while the couple
MBR_HardDisk1.dat+BootSector_DriveH.dat works, as they are IDENTICAL.
Maybe in the haste of testing you "mixed" versions? Or a "cold" or "warm" reboot was needed?
Just in case I am attaching a "fixed" MBR that implements the same "hack" the HP USB formatting utility uses, see here for reference:
It should be "more" compatible and hopefully let you boot with both 06 and 0E as partition type.
Number of downloads: 6
Posted 05 July 2008 - 03:15 AM
If it is 0x0000007b "Inaccessible boot device", first thing to try is the modified NTDETECT.COM:
However, besides tutorial 5, you may want to look here:
And here, a "less known" page that may clear some points:
And even try the "fully automated" way:
Just in case I am attaching an archive containing the (supposedly working, UNTESTED by me) .sif and .in_/.inf files.
Number of downloads: 48
This post has been edited by jaclaz: 05 July 2008 - 03:59 AM
Posted 05 July 2008 - 02:24 PM
Posted 06 July 2008 - 04:37 AM
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
Check the the file %SystemRoot%\Ntbtlog.txt
POOL_BAD_DRIVER says nothing to me, post the CODE of the BSOD, and any other reference.
Check the Event Viewer files on a working machine:
i.e. *.evt under %SystemRoot%\System32\Config\
This app has a FREE personal license:
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?
Use the files I posted, after having re-chacked them.
Posted 06 July 2008 - 09:27 AM
"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")
Number of downloads: 2
This post has been edited by toja92: 06 July 2008 - 09:30 AM
Posted 06 July 2008 - 10:02 AM
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? )
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:
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:
autoreboot to 0
(Offline you will need to access ControlSet001 instead of CurrentControlSet)
No, it does not change system files, only cannot say if it would run under Vista.
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.
Posted 06 July 2008 - 10:49 AM
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 0xE15D0004I 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
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?
This post has been edited by toja92: 06 July 2008 - 04:08 PM
Posted 07 July 2008 - 01:45 AM
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.
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.
This post has been edited by jaclaz: 07 July 2008 - 01:46 AM
Posted 07 July 2008 - 03:19 AM
- ← Intel Motherboad Driver intergration
- Nlite does not remove chosen languages under "Western Europe and →