Install fails if no c: drive

[mstaggerlee]

I'm a licensed subsonic user, and I've just brought up a new Windows XP system that for reasons I won't go into (cuz I'm not entirely sure I understand them) has no drive named C:. My system drive (where Windows is installed) is H:. The Subsonic installer crashes when attempting to write certain files to the C: drive. Can anyone suggest a work-around for this, or must I wait for a new version to be able to use what I've purchased once again?

[BKKKPewsey]

Can you open a command prompt and just type set (then return)
This will list all the environment variables.
Then check the paths for HOMEDRIVE and SystemDrive.
In your case they should be both set to H:

[mstaggerlee]

Yes, they are ... and always have been, to the best of my knowledge.
Nevertheless, the Subsonic installer still fails while attempting to access folders on C:.

[BKKKPewsey]

Hmm! There is something odd with the windows installer
You could try entering

Code: Select all

SUBST C: H:\

in a command line and install again.
No guarantees though

[sindre_mehus]

Hi,

Will look into this.

Thanks,
Sindre

[Exrace]

I would question a windows setup which has a first drive as H:
It sounds like the installer assumes there is a C: drive like 99.999% of most home users XP setups.

[BKKKPewsey]

Yes you are correct in that it appears to be assuming C: drive as system drive
but the installer should be checking the environment variables and making the correct choice.
If the OP or whoever installed the os had something like a usb card reader
(which grabs the first available drive letters) in the machine and then installed windows that sort of problem can arise.

[mstaggerlee]

[quote="Exrace"]I would question a windows setup which has a first drive as H:
It sounds like the installer assumes there is a C: drive like 99.999% of most home users XP setups. [/quote]

I said in the OP it was a strange situation ... the drives were originally configured as RAID1 - I was more interested in storage capacity than in absolute data integrity, so I wanted to UN-RAID the system, and this is how things turned out.

And yes, sometimes when I put in a removable drive, it claims C:. STILL can't reliably install that way, unless I want to make the "removable" drive a permanent fixture.

I'm fairly sure that this is an issue for the developer to deal with, and Sindre has stated that he's gonna look into it. I'll put my faith in him.

To all the rest of you - thanx just the same.

[mstaggerlee]

Since I started this topic, I thought I'd stop back in and say that there is no further urgency as far as I'm concerned that this issue be solved. I've found another app that "misbehaves"
similarly, and I've had my arm twisted to re-assign one of my data drives as c:.

[BKKKPewsey]

It is on Sindre's TODO list to fix - hopefully on the next release