[clearscreen]

Hello I'm new to the forums, but have been booting to USB for quite a while now.

My issue is that when I use my UBUSB in the Dell Optiplex Series (gx260,270,280,520,620) and try using Recovery Console (for the sole purposes of chkdsk /r) It loads through the initial load screen but then Blue Screens with:

0x0000007b (0xF99D9524, 0xC0000035, 0x00000000, 0x00000000)

I use the same key in my HP series PCs and it will load flawlessly and allow a checkdisk to happen.

I am using the current version of UBUSB that came in the newest version of UBCD4WIN and even tried using the plugin in UBCD4WIN to create the usb without drivers, with the sata/raid drivers, but to no avail.

The other thing, is that when I load into UBCD4WIN it does not bluescreen and that is what my search on the forums returned the most. I can use the UBCD utility but can not load into Windows Recovery Console

Any ideas/suggestions?

Thanks,
CLS

This post has been edited by clearscreen: 29 April 2009 - 01:19 PM

[BvF7734]

0x7b is a very common error when booting most desktops from dell with USB. 0x7b is a stop code referring back to a lack of contactable boot device. As it was explained to me a long time ago that you should have found numerous times had you searched to begin with, is that XP resets the USB buss during boot thusly losing reference to the boot partition it is on. I am sure it is the same as if from the recovery console as well... From CD it works fine. If you have been having the project work frin from USB on those desktops, then you have had better luck than I as I have never een able to get the project to bot on any Dell desktops and only the laptops where I needed it more anyways.

The stop code has been mentioned many times. Granted niot in relation to recovery console to my knowledge but it has been discussed ad naseum.

This post has been edited by BvF7734: 29 April 2009 - 01:37 PM

[clearscreen]

BvF7734, on Apr 29 2009, 11:35 AM, said:

0x7b is a very common error when booting most desktops from dell with USB. 0x7b is a stop code referring back to a lack of contactable boot device. As it was explained to me a long time ago that you should have found numerous times had you searched to begin with, is that XP resets the USB buss during boot thusly losing reference to the boot partition it is on. I am sure it is the same as if from the recovery console as well... From CD it works fine. If you have been having the project work frin from USB on those desktops, then you have had better luck than I as I have never een able to get the project to bot on any Dell desktops and only the laptops where I needed it more anyways.

The stop code has been mentioned many times. Granted niot in relation to recovery console to my knowledge but it has been discussed ad naseum.

I understand that this has been discussed for the actual UBCD load but that still leaves me with the confusion as to why I am able to load into UBCD where the bulk of the BSOD issues arise, but not into Recovery Console.

If XP resets the USB Bus during boot, would using Windows 2000 load instead work for using Recovery Console?

The funny thing about this is that I am trying to use the UBUSB to fix blue screen issues by running chkdsk but get BSOD while using it

I tried using the UBCD to run checkdisk through but once I reboot the PC it doesn't seem to work as well as running from the recovery console.

[cdob]

clearscreen, on Apr 29 2009, 01:18 PM, said:

My issue is that when I use my UBUSB in the Dell Optiplex Series (gx260,270,280,520,620)

Yes, this machines are famous for strange USB.
Use 'Dietmar's ntdetect.com'.

[adamsojc]

Don't know if this will help or not but I had a lot of BSODs with RecCons as well. If you are using Grub4dos as your bootloader be sure you are writing the name CMDCONS to Setupldr.bin as it loads. My "menu.lst" looks like this:

title Launch Windows Recovery Console
map (hd0,0)+1 (hd0)
map --hook
find --set-root /cmdcons/setupldr.bin
chainloader /cmdcons/setupldr.bin
#####################################################################
# write string "cmdcons" to memory 0000:7C03 in 2 steps:
#####################################################################
# step 1. Write 4 chars "cmdc" at 0000:7C03
write 0x7C03 0x63646D63
# step 2. Write 3 chars "ons" and an ending null at 0000:7C07
write 0x7C07 0x00736E6F

[clearscreen]

adamsojc, on Apr 29 2009, 01:19 PM, said:

Don't know if this will help or not but I had a lot of BSODs with RecCons as well. If you are using Grub4dos as your bootloader be sure you are writing the name CMDCONS to Setupldr.bin as it loads. My "menu.lst" looks like this:

title Launch Windows Recovery Console
map (hd0,0)+1 (hd0)
map --hook
find --set-root /cmdcons/setupldr.bin
chainloader /cmdcons/setupldr.bin
#####################################################################
# write string "cmdcons" to memory 0000:7C03 in 2 steps:
#####################################################################
# step 1. Write 4 chars "cmdc" at 0000:7C03
write 0x7C03 0x63646D63
# step 2. Write 3 chars "ons" and an ending null at 0000:7C07
write 0x7C07 0x00736E6F

Set my menu.lst to yours and it worked flawlessly.

-This was the missing link-
map (hd0,0)+1 (hd0)
map --hook
------------------------------

Thank you!

[pcuser]

Thanks adamsojc and clearscreen

Quote

-This was the missing link-
map (hd0,0)+1 (hd0)
map --hook

This is noted for the next UBUSB release.

[cdob]

@adamsojc
Thanks for report.
Can you name some examples?
Which hardware does require "map (hd0,0)+1 (hd0)" ?

@ all
Can you try current grub4dos too?
http://nufans.net/grub4dos/
http://nufans.net/gr...-2009-04-30.zip

There is another Recovery Console setting

menu.lst said:

map () (hd0)
map (hd0) ()
map --rehook

[RChadwick]

I added the "map (hd0,0)+1 (hd0) map --hook" line as well. Before I couldn't boot UBCD4Win from most of my machines. After adding the lines (Where it boots the UBCD4Win), I can boot from my Optiplex GX260. However, it still BSOD's on an Asus M2NPV-VM, amd an Iomega 200d NAS. A Compaq Presario 6000 series boots fine with or without the line.

Any ideas on what I can try?

[pcuser]

Did you read my reply in the other thread you asked this question in?

[RChadwick]

pcuser, on May 8 2009, 05:03 PM, said:

Did you read my reply in the other thread you asked this question in?

I just noticed it now, thanks. Will give it a try.

[Icecube]

chain.c32 of Syslinux 3.85-pre1 and higher can chainload the recovery console.

How to use:

LABEL recoveryconsole
MENU LABEL Recovery Console
COM32 chain.c32
APPEND cmldr=/cmldr

or:

LABEL recoveryconsole
MENU LABEL Recovery Console
COM32 chain.c32
APPEND cmldr=/SETUPLDR.BIN

This will do the same as this Grub4Dos entry:

title find and load CMLDR, the Recovery Console of Windows NT/2K/XP
chainloader /cmldr
# write string "cmdcons" to memory 0000:7C03 in 2 steps:
# step 1. Write 4 chars "cmdc" at 0000:7C03
write 0x7C03 0x63646D63
# step 2. Write 3 chars "ons" and an ending null at 0000:7C07
write 0x7C07 0x00736E6F

http://www.boot-land...t=0&#entry88342

WinVBlock driver can also be used to create a Recovery Console disk image that can be booted with MEMDISK or Grub4dos memory mapping:
http://www.boot-land...showtopic=10073