159 replies to this topic

[was_jaclaz]

now HOW ll i logon to my D:\WINDOWS ? when i issue " logon " command , it again showed me with the choice of either logon to catch22 or windows .

i selected windows , and it again asked me for the password .

so what is the method of using catch22 ? (i have read the 911 topic bt could not find the way to use catch22) .

Well, it is not a way to bypass the Administrator password of the installed Windows.

You need to change a key in the installed Windows Registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Setup\RecoveryConsole\SecurityLevel
setting it to 1 in order to bypass the request for password.

Try re-reading the original post:
http://www.911cd.net...o...20983&st=25
And this page:
http://commandwindows.com/recovery.htm

Basically on a DEFAULT install of Windows XP, these settings for Recovery Console are set:

AllowWildCards = FALSE <-this means that you CANNOT use wildcards in commands like "dir" and "del".
AllowAllPaths = FALSE <-this denies access to some files and folders on the main system
AllowRemovableMedia = FALSE <-this means that you cannot copy to removable devices (read floppies)
NoCopyPrompt = FALSE<-this means that you cannot copy a file without being prompted to continue when you are overwriting an existing file.

In other words, try NOT running the batch setallon command, and play a bit in RC, navigating through the various filesystems, you should be denied access to most "system" directories.
Then try again after having run batch setallon.

About your map and map arc report, it is strange.

I'll try again:

And which drive letter has the RC you are booted in?

In Qemu, one single hard disk, the ramdisk image gets letter C:\ (and is NOT listed by the map or map arc commands) and the partition on the drive gets D:\
With two disks , the ramdisk image gets letter C:\ (and is NOT listed by the map or map arc commands) and the partitions on the drives get D:\ and E:\




jaclaz

[cdob]

6) and here comes the clever part:
you need an additional \I386 directory containing:
a copy of TXTSETUP.SI_

Thanks for the hint.
This is usefull at XP 64bit too: \cmdcons\txtsetup.sif is not found.

I used XP 64bit SP1 files, this is based on 2003 files.
A appropiate RAMdisk driver is included by default, let's try this version first.

There is a hard disk like image file wrapper.DSK at USB drive.

hard disk like image wrapper.DSK contain files

WINNT.SIF
NTDETECT.COM
SETUPLDR.BIN
RAMRC.DSK

;http://technet.microsoft.com/en-us/magazine/2006.10.windowspe.aspx

;adjusted for AMD64 recovery console



[SetupData]

BootDevice = "ramdisk(0)"

Architecture = "AMD64"

OsLoadOptions = "/noguiboot /fastdetect /rdimageoffset=32256 /rdpath=RAMRC.DSK"



[data]

msdosinitiated="1"

floppyless="1"

Remember, the rdimageoffset=32256 refers to 63 sectors hard disk image RAMRC.DSK.

menu.lst

title Ramdisk booting RC64

find --set-root /wrapper.DSK

map /wrapper.DSK (hd0)

map --hook

root (hd0,0)

chainloader /SETUPLDR.BIN

RAMRC.DSK contain directories

AMD64
cmdcons

There is a file \AMD64\txtsetup.si_.
There dosn't exist a file \cmdcons\winnt.sif.

As known: bootsector is changed MSDOS5.0->cmdcons of the ramdisk loaded image

[Wonko the Sane]

Thanks for the hint.

You are welcome , I knew it was clever , but didn't thought it could extend on x64.



Wonko

[was_JFX]

Quite some strange information this thread is given

Need compressed files (TXTSETUP.SI_)

wrong setupldr can handle both compressed and non compressed

Use 'real' disk images which MBR

Why setupldr doesn't even understand them

Patching the boosector is required

Why grub4DOS can directly put cmdcons to needed memory location

The 3 files (setupldr.bin, ramdisk.sys, ntdetect.com) from 2k3 sp1 are needed for ramboot

actually only setupldr.bin is required, thought the myth was busted?

[Wonko the Sane]

Quite some strange information this thread is given

wrong setupldr can handle both compressed and non compressed

Why setupldr doesn't even understand them

Why grub4DOS can directly put cmdcons to needed memory location

actually only setupldr.bin is required, thought the myth was busted?

Well, the myth was officially busted only when you (so gracefully) did so:
http://www.911cd.net...o...23040&st=12

Since most of this thread was written before you started sharing your wisdom I guess it is understandable that someone may have been unaware of that.

Thanks to joakim:
http://www.boot-land...?...ic=9474&hl=
we now have a clearer idea on how the thingy works.



Wonko

[was_JFX]

@Wonko

Okay, you got me with this point. I wasn't aware this thread was that old.

But my intention was more to clarify incorrect information rather than to judge anyone.

[Wonko the Sane]

Okay, you got me with this point. I wasn't aware this thread was that old.

Yep.

But my intention was more to clarify incorrect information rather than to judge anyone.

Well, then carry it on.

I mean, as often happens on a board thread, in here there some "mix" between "good" information, "assumptions", completely out of scope posts, etc. etc..

By quoting a number of "snippets" WITHOUT properly doing so (with a link to where they were taken from), you actually contribute to the confusion.

Example:
Your kind of quote:

Quite some strange information this thread is given

"right" quote:

Quite some strange information this thread is given

additionally, I seem not to find the original snippets you quoted , and you cannot get away with an out-of-context oneliner.
Just as an example these:
"right" quote:

Need compressed files (TXTSETUP.SI_)

wrong setupldr can handle both compressed and non compressed
...

Patching the boosector is required

Why grub4DOS can directly put cmdcons to needed memory location

May appear as being uneeded if you read these:

If everything works, you can then "refine" with:
1) using either a patched bootsector or the (default in grub4dos) bootsector memory patching to avoid to go through the "blue screens of Text setup
2) clean (reduce) TXTSETUP.SIF, remove useless drivers
3) re-compress TXTSETUP.SIF to TXTSETUP.SI_
4) add the (by yours truly ) trick about allowing access, file copying, etc. (No more CATCH 22)
5) if you use the Server 2003 SP1 or R2 SETUPLDR.BIN put the whole thing in a RAMDISK image and have it really portable
6) do whatever else is suggested/hinted/explained in the referenced threads

Now, if something is wrong, it is a good thing if it is corrected or at least the issue should be raised (see the "But then why" in my sig ), but it should be done in such a way as to make things more clear and making clear that there is nothing against the OP, JFYI, see my personal point of view about entering with a "wrong" (pardon me the pun ) incipit:
http://www.boot-land...?...=4064&st=18



Wonko

[was_JFX]

... you actually contribute to the confusion.

You know I prefer this way

If everything works, you can then "refine" with:
1) using either a patched bootsector or the (default in grub4dos) bootsector memory patching to avoid to go through the "blue screens of Text setup
2) clean (reduce) TXTSETUP.SIF, remove useless drivers
3) re-compress TXTSETUP.SIF to TXTSETUP.SI_
4) add the (by yours truly ) trick about allowing access, file copying, etc. (No more CATCH 22)
5) if you use the Server 2003 SP1 or R2 SETUPLDR.BIN put the whole thing in a RAMDISK image and have it really portable
6) do whatever else is suggested/hinted/explained in the referenced threads

Well than small correction:

3) optional re-compress TXTSETUP.SIF to TXTSETUP.SI_

5) if you use the Server 2003 SP1 or R2 SETUPLDR.BIN put the whole thing in a RAMDISK image and have it really portable

Note R2 can be seen as AddOn, to both Server 2003 SP1 & SP2.

And the SP2 version has the 'Please wait (forever)' Bug.

[Wonko the Sane]

3) optional re-compress TXTSETUP.SIF to TXTSETUP.SI_

Well since the WHOLE set of points is under a:

If everything works, you can then "refine" with:

the WHOLE set of point are to be seen as an option.

In other words the illustrated setup (with uncompressed TXTSETUP.SIF) is working BUT there are some optional steps/refinements that one may want to pursue ( including re-compressing TXTSETUP.SIF to TXTSETUP.SI_ in order to save some 400 Kb), as BOTH (compressed and uncompressed) do work.

Note R2 can be seen as AddOn, to both Server 2003 SP1 & SP2.

And the SP2 version has the 'Please wait (forever)' Bug.

Really? What do you mean exactly?

Maybe this needs corrections too :
http://www.boot-land...?...c=4952&st=2



Wonko

[was_JFX]

Really? What do you mean exactly?

Maybe this needs corrections too :
http://www.boot-land...?...c=4952&st=2

Original Server 2003 R2 was based on Server 2003 SP1, so it was usefull for our RAM boot project.

However this one is mostly vanished and people will prefer Server 2003 R2 with SP2

but it's setupldr.bin is not usable for RAM boot.