Re: More thoughts on drive letters
From: Al Christoph (ac2_at_too.net)
Date: 03/27/04
- Next message: Sniffer: "Cannot access recovery console"
- Previous message: neon_starfish: "*.exe file extension"
- In reply to: Jeff: "RE: More thoughts on drive letters"
- Next in thread: D.Currie: "Re: More thoughts on drive letters"
- Reply: D.Currie: "Re: More thoughts on drive letters"
- Reply: joust in jest: "Re: More thoughts on drive letters"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 27 Mar 2004 07:49:29 -0500
Sorry Jeff, to have communicated so poorly on my part. Virtual PC was the
excuse for a major overhaul of my hardware. It had nothing to do with the
problem.
The problem was that a change in BIOS manufacturer did the following:
1) Completely rearranged my drives.
2) Gave the drive with the WinXP system the wrong letter.
3) When WinXP booted in ANY mode it quickly rebooted itself with a blue
screen of death passing by quickly.
So the question remains, is there a tool that outside of the BIOS and WinXP
would have allowed me to relabel the drives?
Regards,
Al
"Jeff" <anonymous@discussions.microsoft.com> wrote in message
news:6A03D005-2B0F-4A08-AA55-26CACAB180A7@microsoft.com...
> If none of the suggestions you've seen here will help, why ask your
question here?
> You need help with Virtual PC 2004 and this is a Windows XP Group.
> Jeff
>
> ----- Al Christoph wrote: -----
>
> Here is what I started with:
> C: - Win ME
> D: - CD-ROM
> E-G: Various
> H: - Win XP
>
> Then I fell in love with Virtual PC 2004 and decided to upgrade.
Switched
> mother board vendors and processors.
>
> On boot what I got was
> C: - Win ME
> D-F: - Various
> G: - Win XP
> H: - CD-ROM
>
> UGH! None of the suggestions i've seen here could work because they
involve
> making windows work. And as soon as Win XP got started under these
> circumstanes it blue screened and rebooted itself.
>
> The BIOS dispite lots of looking had no way I could see to handle
this.
> (Intel's Motherboard.)
>
> So, I did a variety of things (not of particular interest here) and
ended up
> having to let H: get reinstalled - no loss of software soooo far. Of
course
> the drivers for the ethernet connection weren't there so I ended up
having
> to do a phone Good House Keeping Seal of Approval (I can't think of
that
> silly thing that keeps us sort of honest at this late hour.) UGH!
>
> Besides putting the original pieces back in the box, is there
anything i
> could have done to get around this?
>
> Regards,
> Al
>
>
>
- Next message: Sniffer: "Cannot access recovery console"
- Previous message: neon_starfish: "*.exe file extension"
- In reply to: Jeff: "RE: More thoughts on drive letters"
- Next in thread: D.Currie: "Re: More thoughts on drive letters"
- Reply: D.Currie: "Re: More thoughts on drive letters"
- Reply: joust in jest: "Re: More thoughts on drive letters"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
