Help - Search - Members - Calendar
Full Version: XP Recovery Console
The CD Forum > The CD Forum > Bootable CDs
Ed_P
I downloaded the Windows XP Recovery Console CD from here and set up GRUB4DOS to boot it directly rather than burn a CD. My menu has
CODE
title 06. Boot XP Recovery Console ISO on E:
map (hd0,2)/rc.iso (hd32))
map --hook
chainloader (hd32)

The ISO is on my E: drive, and contiguous, it starts and prompts to press a key to boot the CD, which I do, it then runs for about 10 or so seconds then I get a BSOD with an x07B error. What am I doing wrong here??
Ed_P
I tried this config also with the same results.
CODE
title 06. Boot XP Recovery Console ISO on E:
map (hd0,2)/rc.iso (0xff))
map --hook
chainloader (0xFF)/I386/SETUPLDR.BIN


I also ran CHKDSK on the E: drive which showed no problems.

What I see each time is attached. 1st the top screen after the drivers are loaded then the bottom screen.
cdob
I assume you did build the ISO file locally...

XP install booting and BartPE booting are equal. Add a windows driver to support ISO files.
Compare http://www.911cd.net/forums//index.php?showtopic=24023
jaclaz
QUOTE (cdob @ Mar 13 2011, 07:59 AM) *
I assume you did build the ISO file locally...

Wrong assumption.... whistling.gif
QUOTE (Ed_P @ Mar 12 2011, 08:31 AM) *
I downloaded the Windows XP Recovery Console CD from here ..... What am I doing wrong here??


QUOTE (Ed_P @ Mar 12 2011, 08:31 AM) *
What am I doing wrong here??

Most.

Build your own rc.
Add to it a ramdisk/filedisk driver.
Procedure, and links to methods with different approaches, can be found here:
http://reboot.pro/11393/

BTW you also have "wrong" grub4dos settings, you have an unneeded closing bracket at the end of mapping line.
As a general rule unless really wanted hardcoding entries to a device is not the "best" choice, and also taking the habit of establishing root is a good idea:
QUOTE
title 06. Boot XP Recovery Console ISO
find --set-root /rc.iso
map /rc.iso (0xFF)
map --hook
root (0xFF)
chainloader /I386/SETUPLDR.BIN


jaclaz
Ed_P
QUOTE (cdob @ Mar 13 2011, 01:59 AM) *
I assume you did build the ISO file locally...

Actually I downloaded it from a link in a story in Windows Secrets related to a recent personal experience.

QUOTE
XP install booting and BartPE booting are equal. Add a windows driver to support ISO files.

That's the clue that I needed. thumbsup.gif
CODE
title 06. Boot XP Recovery Console ISO on E:
root (hd0,2)
find --set-root /rc.iso
map --mem /firadisk.gz (fd0)
map --mem /rc.iso (0xff)
map --hook
chainloader (0xFF)/I386/SETUPLDR.BIN

This works. It's the same GRUB4DOS commands that I use for PEBuilder.iso. And I suspect that's what your link pointed to. wink.gif

With my limited GRUB4DOS knowledge I thought the problem was my GRUB4DOS commands.

Thank you worthy.gif cdob.

QUOTE (jaclaz @ Mar 13 2011, 04:32 AM) *
BTW you also have "wrong" grub4dos settings, you have an unneeded closing bracket at the end of mapping line.
As a general rule unless really wanted hardcoding entries to a device is not the "best" choice, and also taking the habit of establishing root is a good idea:

Thank you jaclaz. Nice to see you back. Hopefully you were on holiday and not ill.

Would your nonspecify device entries find the rc.iso on my E: drive without the device entries being added or the root (hd0,2) command?
jaclaz
QUOTE (Ed_P @ Mar 13 2011, 07:27 PM) *
Would your nonspecify device entries find the rc.iso on my E: drive without the device entries being added or the root (hd0,2) command?


Sure, that's EXACTLy the idea of find --set-root.
Obviously it is NOT "universal", meaning that grub4dos will scan available devices in a "common sense order" to find "rc.iso", and will set root to the FIRST instance of "rc.iso" file it finds.
As said, establishing ROOT is always a good idea.
Jist TRY the suggested now with the added firadisk line) in the hypothesis that rc.iso and firadisk.gz are on root of the same drive:
CODE
title 06. Boot XP Recovery Console ISO
find --set-root /rc.iso
map --mem /firadisk.gz (fd0)
map /rc.iso (0xFF)
map --hook
root (0xFF)
chainloader /I386/SETUPLDR.BIN


jaclaz
Tux-Box1
Hello, I'm trying to do the same thing boot a iso image on a thumb drive. This way I can change the iso image at will drooling.gif . Well I followed as much of this post as I was able. Now I'm stuck. sweatingbullets.gif
I get the same x07b BSOD. I've changed the grub menu.lst to mach up with well I have 2 entrys in their to try different things so I don't have to back track as much
thumbsup.gif
CODE
title Boot XP Recovery Console ISO
find --set-root /rc.iso
map /rc.iso (0xFF)
map --hook
root (0xFF)
chainloader /I386/SETUPLDR.BIN

title Boot XP Recovery Console ISO other try
find --set-root /rc.iso
map --mem /firadisk.gz (fd0)
map /rc.iso (0xFF)
map --hook
root (0xFF)
chainloader /I386/SETUPLDR.BIN


Both give me the same BSOD.
To also note I haven't gotten BartPE to successfully build once.
What I want to do is load the recovery console and be able to access the local hard drive.
I keep seeing references to problems with SATA. The systems this will be used on have SATA, could this be the problem?
Thank you for your patience.
Ed_P
QUOTE (jaclaz @ Mar 15 2011, 12:46 PM) *
Sure, that's EXACTLy the idea of find --set-root.

Thanks jaclaz. I was not aware that the find was so far reaching. I thought it only searched the current partition. I will try your suggestions later today. Thanks. thumbsup.gif

And the Recovery Console iso is not exactly what I was expecting. I thought it would go directly to Recovery Console when booted not a XP install setup screen. angry2.gif
Ed_P
QUOTE (Tux-Box1 @ Mar 16 2011, 12:35 PM) *
I keep seeing references to problems with SATA. The systems this will be used on have SATA, could this be the problem?

Firadisk will allow you to boot the rc.iso file however the booted iso won't have access to your SATA drives. Firadisk is required to boot the ISO so your "other try" option should work.
jaclaz
QUOTE (Tux-Box1 @ Mar 16 2011, 05:35 PM) *
Both give me the same BSOD.
To also note I haven't gotten BartPE to successfully build once.
What I want to do is load the recovery console and be able to access the local hard drive.
I keep seeing references to problems with SATA. The systems this will be used on have SATA, could this be the problem?
Thank you for your patience.

It must be the (re-vamped) problem of the week. hmm.gif

Read these:
http://reboot.pro/14037/
http://reboot.pro/14095/
AND given links in them.
Basically the Recovery Console is a "very limited PE" or, if you prefer a Bart PE is a "much better RC with a GUI", the base way to have it working (when mapped as .iso with grub4dos) is the SAME, BOTH being "one side" of the Windows "Install" disk.

ALSO please take into account this (about the *any* .iso idea, which is basically flawed ph34r.gif):
http://reboot.pro/8944/

Generally speaking if a driver for the SATA device is missing in the build, you won't have a 0x0000007b STOP error (since you are booting from the USB stick, BUT you won't be able to see the internal (SATA) devices.

Also remember that on some hardware a modified NTDETECT.COM might be needed (independently from having the "right" drivers or not) :
http://www.911cd.net/forums//index.php?showtopic=24097

You can choose to actually integrate the drivers to your source or use what is suggested here (in the second part):
http://sites.google.com/site/rmprepusb/tut...-xp-from-an-iso
(this way you can have a "F6 floppy" with the needed drivers "integrated" with the firadisk or Winvblock floppy image)


QUOTE (Ed_P @ Mar 16 2011, 07:18 PM) *
And the Recovery Console iso is not exactly what I was expecting. I thought it would go directly to Recovery Console when booted not a XP install setup screen. angry2.gif

There are ways wink.gif, do read the given thread:
http://reboot.pro/14037/
AND given links in it.

jaclaz
Ed_P
QUOTE (jaclaz @ Mar 16 2011, 02:25 PM) *
There are ways wink.gif, do read the given thread:
http://reboot.pro/14037/
AND given links in it.

Thanks jaclaz. I'll try the GRUB4DOS writes to memory and see what happens. I really wasn't looking to make a project out of this.
Ed_P
@jaclaz

The GRUB4DOS find does indeed search the whole hdd and not just the base partition. Thanks for explaining that.

As for the rc.iso, I tried the GRUB4DOS writes to memory commands for cmdcons but it ended up with an error msg:
CODE
INF file txtsetup.sif is corrupt or missing, status 18.

As noted previously, I'm not looking for a project. It is what it is. Thanks for your help. smile.gif
jaclaz
QUOTE (Ed_P @ Mar 17 2011, 03:59 AM) *
As for the rc.iso, I tried the GRUB4DOS writes to memory commands for cmdcons but it ended up with an error msg:
CODE
INF file txtsetup.sif is corrupt or missing, status 18.

As noted previously, I'm not looking for a project. It is what it is. Thanks for your help. smile.gif


Still communication problems w00t.gif. The given link clearly says that the CMDCONS edit of the partition/volume bootsector WILL NOT work on a .iso.

jaclaz
Ed_P
QUOTE (jaclaz @ Mar 17 2011, 06:08 AM) *
Still communication problems w00t.gif. The given link clearly says that the CMDCONS edit of the partition/volume bootsector WILL NOT work on a .iso.

QUOTE (http://reboot.pro/14037/page__view__findpost__p__124838)
or using the grub4dos "modify bootsector on the fly" trick:
http://reboot.pro/5316/page__st__61

QUOTE (http://reboot.pro/5316/page__view__findpost__p__69862)
@wimb
Try reading the above two snippets together and with the fact that the WHOLE point of writing cmdcons to bootsector is EXCLUSIVELY that of getting to RC directly, without the "press R".

QUOTE (http://reboot.pro/2254/page__view__findpost__p__28719)
Particularly, the finding of a workaround for the RC CATCH 22 (by yours truly ):
http://www.911cd.net/forums//index.php?sho...20983&st=25
as far as I know this is the first time this has been somewhat documented (self-connecting to \CMDCONS\).

So No I do not see that the edit will not work on an .iso. What I see is posts ponting to other posts pointing to other posts pointing to other posts. Obviously you must be a lawyer. icon8.gif
jaclaz
QUOTE (Ed_P @ Mar 17 2011, 05:36 PM) *
So No I do not see that the edit will not work on an .iso. What I see is posts ponting to other posts pointing to other posts pointing to other posts. Obviously you must be a lawyer. icon8.gif


Hmm. hmm.gif

The given link:
http://reboot.pro/14037/

Post #5 (not something like #2138 whistling.gif)

http://reboot.pro/14037/page__st__4
QUOTE (Wonko the Sane' timestamp='1300275039) *
If you use the "vlaurie" .iso you will have anyway to press the "R", AFAIK/AFAICR, to use the "cmdcons" bootsector trick you need to have a "super-floppy" or "hd-like" image:
http://reboot.pro/2362/page__st__4
Permanently modified or using the grub4dos "modify bootsector on the fly" trick:
http://reboot.pro/5316/page__st__61

it does look like plain English to me unsure.gif

In even plainer words:
Is the filesystem where the actual RC files are? (please choose one):
  1. FAT12
  2. FAT16
  3. FAT32
  4. NTFS
  5. CDFS


If you answered *any* in the range #1#4, assign yourself +1 point (one positive point) thumbsup.gif and go on.
If you answered #5 assign yourself -132.17 points (onehundredthirtytwoandseventeenhundredths negative points) w00t.gif, go back to the mentioned thread , and start re-reading it ....


Just for the record:
QUOTE
I am not a lawyer and I did not ever stay in a Holiday Inn. I am simply a person pretending to be an actor who once played the role of a space lawyer lost in space. wink.gif


cheers.gif
jaclaz
Ed_P
QUOTE (jaclaz @ Mar 17 2011, 05:10 PM) *
it does look like plain English to me unsure.gif

Plain and understood are not the same thing. I interpretted the red text as referring to GRUB4DOS parameters like (0xFF) and (hd32) and alike not the actual file itself. My bad.

QUOTE (jaclaz @ Mar 17 2011, 05:10 PM) *
2. CDFS

dubbio.gif Must be a bug in the forum's sw. happy62.gif
jaclaz
QUOTE (Ed_P @ Mar 18 2011, 01:39 AM) *
dubbio.gif Must be a bug in the forum's sw. happy62.gif

No prob whatever smile.gif.

Point assignment changed to avoid possible misunderstandings:
QUOTE
If you answered *any* in the range #1#4 BUT "CDFS", assign yourself +1 point (one positive point) thumbsup.gif and go on.
If you answered #5 "CDFS" assign yourself -132.17 points (onehundredthirtytwoandseventeenhundredths negative points) w00t.gif, go back to the mentioned thread , and start re-reading it ....


wink.gif

cheers.gif

jaclaz
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2014 Invision Power Services, Inc.