PC Sync Install Error 1327 Invalid Drive C:\

When trying to install PC Sync I get this error message and the installation
cancels itself. I presume its because my main Windows drive is actually G:
rather than C:, which is itself a quirk of installing windows on what was at
the time a secondary drive in another machine then transplanting it into
another PC as the primary boot drive. Does anyone know a workaround to this
installation problem? Are there perhaps any command line parameters that
can be used?

---

› See More: PC Sync Install Error 1327 Invalid Drive C:\

"ITMA" <[email protected]> wrote in message
news:[email protected]...
> When trying to install PC Sync I get this error message and the
installation
> cancels itself. I presume its because my main Windows drive is actually
G:
> rather than C:, which is itself a quirk of installing windows on what was
at
> the time a secondary drive in another machine then transplanting it into
> another PC as the primary boot drive. Does anyone know a workaround to
this
> installation problem? Are there perhaps any command line parameters that
> can be used?

Not sure if there's a specific way to do it, but with other software I've
had this problem on (actually when running WINE under Linux to run Windows
programs) I've managed to install the software by creating the windows
specific folders on the C drive. Try creating c:\windows, c:\windows\system,
c:\windows\system32, c:\program files, etc.

After installation, if there are any files in these folders copy them to
your actual windows drives. Be careful about writing over any files that may
already be there on your G drive.

This may not work at all of course.

Adam

Good thinking. I stuck a USB portable memory / solid state disk thingy in
to my PC, which it configured as C:\, and then install didn't throw up the
initial error message. Unfortunately, it still choked on another problem -
something about a dll call, whatever that is.

Next question then, ought to be, what alternative is there to Nokia's own
software? I've tried Oxygen, but you've got to pay for it, and also I found
it required a degree of user intervention to coax it along. Nokia's PC sync
can be a bit temperamental as to whether its going to detect the phone or
not, but if / when it does, its all automated.

> Not sure if there's a specific way to do it, but with other software I've
> had this problem on (actually when running WINE under Linux to run Windows
> programs) I've managed to install the software by creating the windows
> specific folders on the C drive. Try creating c:\windows,
c:\windows\system,
> c:\windows\system32, c:\program files, etc.

"ITMA" <[email protected]> wrote in message
news:[email protected]...
> Good thinking. I stuck a USB portable memory / solid state disk thingy in
> to my PC, which it configured as C:\, and then install didn't throw up the
> initial error message. Unfortunately, it still choked on another
problem -
> something about a dll call, whatever that is.

I've had an even better idea... a long time ago I used to use the subst
command to fool software into thinking a CD was in the drive for software
that required it, but instead it was really looking at a folder. The subst
command basically maps one location to a new virtual drive letter. For
example you could map "c:\my documents" to your g: drive and if you go into
g: you'll really be in my documents...

You'll need nothing allocated to your c: drive, so in the properties for
your drive that's currently taking up the c: space move it to another letter
(like d.

Then drop into a command prompt (start, run, cmd) and type "subst c: g:\"
(assuming g: is your windows drive). This will make a new drive (until you
remover the drive with "subst c: /d" or reboot) called c: which will really
be your g: drive. Your g: drive will still be there of course.

Let us know if it works.

Adam

All looks very clever but I think I have solved the problem by simply using
an earlier version of PC Suite that was not so picky - it installed without
hiccup. I might have been tempted to use your method but having spent all
of two weekends trying to get Windows XP installed on a machine that would
not boot and without a CD drive to run the software from I'm inlcined to
adopt the if it aint broke dont fix it approach! When I did get XP
installed (which is how it comes to be on G not C) I then had to waste
another half day correcting the big mess created by using Partition Magic to
try to change the drive from G back to C. As I say, I'll make a note to try
what you suggest at some stage in the future