"V7Goose" <V7Goose@discussions.microsoft.com> wrote in message
news:380106BB-745A-4FF3-9B1D-7322AD424439@microsoft.com...
> "Pegasus (MVP)" wrote:
>
>>
>> "V7Goose" <V7Goose@discussions.microsoft.com> wrote in message
>> news:5BF08C27-180E-4B24-89CD-DA5719FC45A6@microsoft.com...
>> >I have a new installation of XP Pro on a new computer based on the
>> >Gigabyte
>> > GA-P35-DS3R motherboard running mirrored SATA HDD drives in RAID1 from
>> > the
>> > native Intel RAID controller. Two IDE optical drives, configured as
>> > Master
>> > and Slave on the single IDE controller available. I have successfully
>> > changed the drive letter of the master drive, but the slave drive
>> > reverts
>> > back to G: (the first available letter after HDD assignments) on
>> > reboot.
>> > I
>> > have replaced the drive but still happens.
>> >
>> > I am pulling my hair out trying to figure out why this one device will
>> > not
>> > hold a new drive letter after reboot! Any ideas? Thanx
>>
>> This could happen if you have insufficient access rights
>> to this registry key:
>> HKLM\SYSTEM\MountedDevices
>>
>> You could try and change your access rights or else you could
>> manually rename the value \DosDevices\G: to \DosDevices\W:
>> (for example), followed by a reboot.
>>
> Thanx for your reply, Pegasus. Unfortunately, this has not helped yet. I
> have full administrator rights on the machine, and drive letter changes to
> any other device work fine and stay changed. I have tried to manually
> change
> the reg key, but it also does not stick. I have tried to remove the
> devices
> from device manager and let them be re-discovered, but the results are the
> same.
>
> One oddity I DID find, however, is that my registry has both a
> MountedDevices AND a MountedDevice1 entry. The drive letter is reverting
> in
> the MountedDevices entry, but not in the MountedDevice1. Don't know if
> this
> might give you or anyone else a clue . . . I'm still playing with it.
> May
> try to delete MountedDevice1 all together.
I suspect that there is some agent on your machine that mucks
around with your drive letter assignments. Since you say that
it is not ZA, it must be something else. I would do this to isolate it:
1. Reboot in Safe Mode.
2. Change the drive letter assignment.
3. Reboot into Safe Mode. Does the assignment stick?
4. If yes, run msconfig.exe and disable all tasks under the
Startup tab.
5. Reboot into Normal Mode. Does the assignment stick?
6. If yes, enable the various tasks selectively until you find
the culprit.
You should disconnect your machine from the Internet while
your virus & firewall protection is disabled.