Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.help_and_support,microsoft.public.windowsxp.perform_maintain,microsoft.public.windowsxp.configuration_manage (
More info?)
Sorry if I intimated you were a *tinkerer* Ian...
Have you ever made a
BartPE disk to boot from? It has an integrated file manager that will let
you browse the files of the corrupt installation, as well as moving and
copying files to different locations, that is, if you haven't already been
in there with Linux 9.0. BartPE has saved me a tremendous amount of time on
several occasions. I wish I had more insight into your trouble though.
--
Cheers,
Tinkerer
"Ian St. John" <istjohn@noemail.usa> wrote in message
news:esaoJISoFHA.3936@TK2MSFTNGP10.phx.gbl...
The reason I say "safe mode is of little utility" is that I have not yet got
a command console to open in 'safe mode', even when I select 'safe mode with
command console'. So far it has been of 'little utility for me'. WinXP may
not like what I am doing. Even Linux 9.0 install will only allow me to
install certain multiboot options. The file systems are my property, in my
possession, but perhaps the security features of the OS's do not allow easy
access. Out of necessity at one point, I was forced to install a second
WinXP OS on a new partition, when my first failed to boot. I had used the
first since ~2001. I had 4 years of work on that partition. I found the only
way I could access my work from the second installation of WinXP was to use
'Backup' and then 'Restore in a new location', with the security features
disabled. I'm not a tinkerer. I'm a mature user who wishes to circumvent
what may be built in security features that make an OS like WinXP 'lockup'.
But at this point I am only hypothesizing, since I have not yet opened up my
WinXP file system. I'll keep trying until I do.
"Tinkerer" <me@myhouse.com> wrote in message
news:eazo90RoFHA.2472@TK2MSFTNGP15.phx.gbl...
> What part of the repair install isn't *working*? Even with Grub, I doubt
> you'll be able to get XP to log on properly. Also, sfc /scannow *will*
> run
> in safe mode, as will installing the recovery console to disc. You can
> also use the XP disc in safe mode to do an in place upgrade of the
> installation, so I don't really know why you're calling it "of little
> utility".
>
> --
>
> Cheers,
> Tinkerer
>
>
> "Ian St. John" <istjohn@noemail.usa> wrote in message
> news:uQx%23ehRoFHA.2484@TK2MSFTNGP15.phx.gbl...
> "Fixmbr", "fixboot": been there, done that. Thanks anyway.
> "Safe mode" in WinXP is of little utility, I find. Not like 'safe mode' in
> WinME.
> "In place repair" ought to work but in my hands I have not got it to work
> as
> well as for WinME. The problem with WinXP installation in a multivolume,
> multiOS setup is that WinXP likes to screw up stuff that already works.
> Mind
> you, there are many packages like that. I had a problem with Seagate's
> "DiscWizard". It installed a disk detector that screwed up my Castlewood
> Orb
> work. The reply I got back from Seagate was "reformat your removable
> disks".
> Thanks, but no thanks.
>
> Presently, I'm installing Linux 9.0 on the unused space of my Seagate
> drive.
> Maybe Grub can open up WinXP.
>
> "Tinkerer" <me@myhouse.com> wrote in message
> news:%23c76ffQoFHA.4012@TK2MSFTNGP09.phx.gbl...
> IIRC, there is also a "fixmbr" and "fixboot" option, and another one that
> I
> can't remember the name of that searches for windows installations and
> adds
> them to the registry. These may, or may not help.
>
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcons_fixmbr.mspx
>
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/bootcons_fixboot.mspx
>
>
> If that fails, I would try to do an inplace repair.
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;315341
>
> Also, can you boot into safe mode? If so, you may want to try installing
> the recovery console as a start up option to make things go a bit quicker.
>
>
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/recovery_install_console.mspx
>
>
> --
>
> Cheers,
> Tinkerer
>
>
> "Ian St. John" <istjohn@noemail.usa> wrote in message
> news:e0rS%23xPoFHA.1088@TK2MSFTNGP14.phx.gbl...
> The "sfc /scannow" command is not recognized by the recovery console
> started
> up by the WinXP install CD I have here at home, which is rather old. I
> noticed that number of useful commands documented online do not work
> either.
> Maybe the problem is the limitations of my rather old WinXP install CD.
> I'll
> check for a more up-to-date release at work. Thanks.
>
> "Tinkerer" <me@myhouse.com> wrote in message
> news:OGyZHOPoFHA.1204@TK2MSFTNGP12.phx.gbl...
>> Have you tried "sfc /scannow", without the quotes from the command
>> prompt?
>>
>> --
>>
>> Cheers,
>> Tinkerer
>>
>>
>> "Ian St. John" <istjohn@noemail.usa> wrote in message
>> news:OCEQqGPoFHA.2472@tk2msftngp13.phx.gbl...
>> Hi,
>>
>> I've added a new drive and changed the partition configuration on a
>> multiboot system. As a result, WinXP became unbootable. After study of
>> the
>> problem, I've used recovery console to fix various problems including
>> boot.ini using bootcfg options. It is a learning process. I've come to
>> the
>> point where I think I've done everything correctly. At this point, I have
>> only one partition, and one OS, WinXP on its original drive. I have the
>> administrator's password. Everything looks OK. Since there is only one
>> OS,
>> the boot process boots directly and fast. There is a screen with a
>> scrolling
>> bit display, then the screen flashes and displays a light blue screen
>> with
>> dark blue bands top and bottom. In the middle of the light blue screen is
>> the MS logo and "Microsoft Windows XP". It looks good but it seems to
>> have
>> locked my out. It does not give me an logon screen. I can't logon as
>> administrator or user. What do I need to do? Thanks.
>>
>> Ian St. John
>>
>>
>>
>
>
Facebook
Twitter
Instagram