a "repair installation" simply
replaces system files that are
missing or corrupted.
this method leaves the
third party programs in tact
and preserves your personal
files, like pics, docs,
"my documents", etc.
the cd also provides the
option to install a new
windows completely.
when you reinstall windows
you will have the option
to overwrite the o.s. on the disk
or install it into a new folder or
partition or drive.
i saw a posting with the links
that can walk you through the
above. a repair installation
should be used before a complete
reinstall of the o.s.
"however", if a repair installation
doesn't prove helpful, it is doubtful
that a new installation will be any
better and you may have a hardware
problem. if you ultimately choose
to do a new installation
of windows, do it into
"another partition".
that way it won't overwrite your
old and corrupted o.s. that may
also have your "personal" files that
you didn't backup.
at least with a secondary o.s.
functioning from a different
partition it can be of help in
fixing the old o.s. or accessing
your personal files.
incidentally, you mentioned
the registry.
the registry can be repaired
via the recovery console
however, because you cannot
access safemode and because
there were no error messages
indicating a faulty config folder
during your attempt to boot up,
the registry can be fundamentally
excluded as a cause.
[keep in mind, that if a repair
installation doesn't work, then
you may have a physical/mechanical
problem with your hardware. but
the ultimate test is a new installation
into a separate partition/drive].
--
db·´¯`·...¸><)))º>
john loone said:
I had an issue like this on a server and MS walked me through on booting into
recovery mode and repairing the registry by compacting it and doing some other
things that i dont remember. Do you know how i can do that. I did a chkdsk and
fixboot and Fixmbr but same thing. I know i can do an install of windows ontop
of the old install but i dont remember the correct way to do that.
thanks
db ´¯`·.. > said:
the windows cd offers
three options:
1) new installation of the o.s.
2) repair the current installation
on the disk
3) the "recovery console"
the recovery console method
will log you into the disk system
you can run the following
commands at the command
prompt>:
chkdsk
fixboot
fixmbr
then you type/run exit,
remove the cd and hope the
pc reboots normally.
if not then option 2
from the above would
be the next option.
the repair installation
will repair/replace system
files on the disk, leaving
your program files intact.
[the chkdsk generally fixes
file errors on the disk. but
if there is an issue with the
boot menu's and accessing the
safemode bootmenu options,
then the fixmbr and fixboot
can help.
what you can do, if you want,
is to run one command then
exit to see if you can reboot
into safemode. if not then repeat
the process with the next command]
--
db·´¯`·...¸><)))º>
john loone said:
Thats right my only option is to boot into repair mode. what commands should
i run to resolve this.
thanks
" db ´¯`·.. ><)))º>` .. ." <databaseben.public.newsgroup.microsoft.com>
wrote in message the registry can be corrupted
however, if safemode is failing
as well, then there is something
else involved.
unfortunately, if safemode isn't
working then a system restore
back to a date when the pc
was functional is not an
available option.
you might try the option
to boot to last good configuration.
if this works, then it is also
a clue to the infliction.
if it does not work, then
you might try the method
called "repair installation"
provided via your windows
cd.
however, you can also use
the "recovery console" with
"any" windows cd and then
running a couple of commands
from the disk prompt can repair
some file system errors, if any.
--
db·´¯`·...¸><)))º>
Windows hangs at Loading Personal settings...
any suggestions on how to fix this. I tried to boot in safemode and i cant
get in safemode it reboots.
Everything was working fine until this morning my laptop screen was blank
and i couldnt get to come on so i cold booted. I think the registry is
corrupt.
