Lotsa feedback here. Many thanks. Helps clear away
quite a bit of the haze and fog surrounding M$ expee.
Notes from James, Cassandra, & Ken about security ids,
and the fact that "Repair" fouls up shared files, gave me
the lead to check the M$ knowledge base. The articles
said that if I could just delete one particular text file in the
system32 directory (undo_gui...something?.txt) before
doing the repair process, it wouldn't foul up those files.
So I learned how to create a floppy that I could boot from
that would allow me to access the ntfs file system, then I
cleared away some of the cobwebs in my memory about
dos.
When I booted with it -- instead of getting a command line,
as I expected -- windoze booted normally! Upon completion
of the boot-up sequence, windoze proudly informed me that
it had just recovered from a crash and asked if it could send
M$ a report. I agreed.
I checked for that text file and didn't find it. [As I write this,
I'm wondering if it was hidden from view ... a system file,
maybe?]
I'm taking SOTL's and Cassandra's tip (had already decided,
but haven't gotten around to it) to dump Netscape 7 in favor
of Firefox, and to set a new system restore point. Hopefully
all is OK, for now, until I can get Sweetie to agree to try the
Penguin.
One more question ... After having booted with a live Linux
CD, how do I access the hard drive's ntfs partition? I tried
it, but while I could see the properties of the partition like
size, etc., I couldn't see any files. What app should I use?
[The live CD is a KDE Mandrake distro.]
Dave
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 18:40:05 EDT