Re: Local Disc (F:)
- From: "Anna" <myname@xxxxxxxxx>
- Date: Sat, 2 Feb 2008 11:57:42 -0500
Ken:
Without belaboring the issue I can only repeat what I've stated in my last
post.
The problems we've run into re this issue along the lines I've described
involving many, many users over the years in an XP environment have
impressed us to strongly suggest that, wherever practical, the user should
establish his/her system (boot) disk as the C: drive even if it means a
fresh install of the OS.
As I've indicated, I fully realize that this is not always the most sensible
approach based on the reasons I've previously stated, i.e., it is simply not
practical for the user to reinstall his/her programs/applications currently
existing on the non-C: drive because they are either so numerous and/or the
user simply does not have the requisite reinstall media available or for any
other reason that may make a new fresh install of the OS a tortuous process.
In those cases he or she will need to live with a system (boot) drive that
bears a non-C: drive letter designation.
But...
As apparently in the OP's case (recall that he or she has already attempted
a fresh install of the OS thus deleting all the data on the disk), if the
chore of undertaking another fresh install of the XP OS and doing it
correctly so that the HDD on which the OS will be installed will then be
designated the C: drive and the task of undertaking this process is not
terribly onerous, then my advice still holds, i.e., it is *most* desirable
that the system (boot) drive be designated with the C: drive letter
assignment.
Anna
"Ken Blake, MVP" <kblake@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3c39q39hfetdun0pb8vss37kb7viq3a6k3@xxxxxxxxxx
On Sat, 2 Feb 2008 09:51:16 -0500, "Anna" <myname@xxxxxxxxx> wrote:
Over the years in a Windows environment we've encountered many problems
and
annoyances with users' machines where their system (boot) drive had not
been
designated with the ubiquitous C: drive assignment letter because of one
reason or another, chiefly because another (potentially) bootable storage
device had been connected in the system while the user was attempting to
fresh-install the XP OS. (I believe this is the root of the OP's
problem.)
Yes, that's almost certainly the reason.
Also, problems arising from faulty processes involving a disk cloning
operation.
In any event, the problems we subsequently encountered because of this
situation involved the inability (present & future) for the user to
install
a particular program on his/her system (boot) drive because the program
simply balked at any attempt to install such program other than on a C:
designated drive. True, virtually any major program in existence today
will
allow this capability but there are still a host of programs out there
(including "custom-made" programs) that simply don't have this
capability.
As I said in my earlier message in this thread, yes, there are some
older programs that insist on installing on C: and simply won't work
otherwise. But my experience is that such programs are *extremely*
rare these days. In several years of running with both Windows XP and
Windows Vista installed on drive F:, with a wide variety of different
programs, I haven't run into a single one.
My recommendation to the OP is that, unless he knows that he is in a
situation where he has to install a program that won't install on F:,
he ignore this possibility. If he doesn't already have such a program,
it is *extremely* unlikely that any new program he buys will have such
a restriction.
We also encountered problems where future user configuration
modifications
simply wouldn't work because the program had originally been installed on
a
non-C: designated drive.
Can you be more specific? What modifications? I've never run into such
a problem.
Also, we've run into many problems with subsequent upgrades, patches,
fixes
of one sort or another affecting an installed program that either would
not
modify the targeted program because the program resided on an
other-than-C:
drive (even though the user had not originally experienced any difficulty
in
installing that program on a non-C: drive), or even if the upgrade,
patch,
etc. appeared to be installed properly we ran into subsequent problems of
one kind or another which we attributed to the fact that the program
resided
on a non-C: designated drive.
Again, please be more specific. I have never run into such a problem
in several years on my own computer (again running both XP and Vista),
nor on any other computers, nor have I ever heard of such a problem
from anyone else.
So all-in-all as I've suggested to the OP, if it's not too terribly
onerous
to "start over" as it were and perform a correct fresh install of the XP
OS
so as to install that OS on a C: designated drive, our advice is do so.
Unless it's a very recent installation, with very little on the drive,
reinstalling cleanly *is* usually onerous, and often gets the person
into even more difficulties. My advice to him is contrary to yours. Do
not do this unless you need to because you are trying to install some
program that refuses to install on F:. I doubt very much that he is in
that situation and simply needs to change the drive letter from the
default that is presented to him.
--
Ken Blake, Microsoft MVP - Windows Desktop Experience
Please Reply to the Newsgroup
.
- Follow-Ups:
- Re: Local Disc (F:)
- From: Ken Blake, MVP
- Re: Local Disc (F:)
- References:
- Re: Local Disc (F:)
- From: Anna
- Re: Local Disc (F:)
- From: James Silverton
- Re: Local Disc (F:)
- From: Anna
- Re: Local Disc (F:)
- From: Ken Blake, MVP
- Re: Local Disc (F:)
- Prev by Date: Re: WINXP,HP Comp.,No Winxp disks, how do Setup?
- Next by Date: Re: Xp install problem
- Previous by thread: Re: Local Disc (F:)
- Next by thread: Re: Local Disc (F:)
- Index(es):
Relevant Pages
|
Loading
