Repair is to repair a damaged 2k install.
Interesting. What does "damaged install" mean? In as much as an install
is either successful, or it isn't, is "damaged" simply another way of
referring to an install that was not successful? Does the repair process
figure out how far the unsuccessful install managed to get, and then
continue it from there?
There is no option to go to a command prompt because those are
actually install disks, not boot disks.
Ok. It's just that it seems as though enough of a system has been
established, after all four disks have been processed, that at least the
HDD file system could be interacted with, and perhaps some rudimentary
functionality available as well.
If you want a command prompt interface, boot with the CD and
choose the recovery console.
I assume you mean a regular installation CD, as opposed to a recovery CD.
I only have a recovery CD, which, like the setup boot diskettes, won't
fallback to a command line. I also don't recall any "recovery console"
option, but then I didn't go very far into it, being afraid of
inadvertantly invoking the recovery process and wiping out my HD.
It's about as dos like as your going to get in an NT enviroment
without using a third part app like ntfs4dos.
Sounds like this (recovery console thing) may be what I'm looking for. Is
it available as a separate entity? In other words, I don't wish to buy a
Win2k install disk just to get it.
The big question is what do you want to do at a command prompt?
The real answer to your question depends on the answer to that.
As intimated above, I'd just like to have some rudimentary functionality -
access to the HDD file system and some basic commands (e.g. attrib, chdir,
chkdsk, copy, dir, del, format, mkdir, rename, tree, type, xcopy, etc.). I
realize that one can boot to safe mode w/ command prompt and have this
functionality, but I suspect that there is a lot of unnecessary -- and
perhaps undesirable -- extra system stuff loaded at this time.
Joe