Mapped drive "...does not have a program associated with it..."

Hi guys,

I have a 64-bit Vista Ultimate SP1 workstation that has mapped drives setup
at login by a script coming from SBS 2003 R2. This method of mapping drives
has been running quite happily on 32-bit machines for several years until I
purchased and setup this new 64-bit machine. Only on this machine, if I
double-click one of three mapped drives (S), I get the following error:

"This file does not have a program associated with it for performing
this action. blah blah blah."

The context menu for drive S is as follows:
Install or run program
Explore
Open
...The rest are the same as for other folders.

The Open and Explore items do as they're supposed to, but the [Install or
run program] item results in the abovementioned error. All other mapped
drives function as expected. I'm not sure if it makes any difference, but
among a raft of other files and folders, this drive also contains a system
folder called 'System Volume Information'. It appears to be the only drive
to contain this folder.

I had a look in the Registry, but couldn't find any difference between drive
S and any other mapped drive.

Can anyone shed some light on what may have happened here, and more
importantly, how to fix it??

Regards,
Graham R Seach

Look for an 'autorun.inf' file in the root of the S drive. If so there's
your reason. Opening it up in notepad would show further what it does.

--
Jon


"Graham R Seach" <gseach@accessmvp.com> wrote in message
news:76EE9C82-5DB6-4024-B90B-248AA35D6520@microsoft.com...
> Hi guys,
>
> I have a 64-bit Vista Ultimate SP1 workstation that has mapped drives
> setup at login by a script coming from SBS 2003 R2. This method of mapping
> drives has been running quite happily on 32-bit machines for several years
> until I purchased and setup this new 64-bit machine. Only on this machine,
> if I double-click one of three mapped drives (S), I get the following
> error:
>
> "This file does not have a program associated with it for performing
> this action. blah blah blah."
>
> The context menu for drive S is as follows:
> Install or run program
> Explore
> Open
> ...The rest are the same as for other folders.
>
> The Open and Explore items do as they're supposed to, but the [Install or
> run program] item results in the abovementioned error. All other mapped
> drives function as expected. I'm not sure if it makes any difference, but
> among a raft of other files and folders, this drive also contains a system
> folder called 'System Volume Information'. It appears to be the only drive
> to contain this folder.
>
> I had a look in the Registry, but couldn't find any difference between
> drive S and any other mapped drive.
>
> Can anyone shed some light on what may have happened here, and more
> importantly, how to fix it??
>
> Regards,
> Graham R Seach
>

Hi Jon,

Already checked that. No autorun or ini files.

Regards,
Graham R Seach

"Jon" <Email_Address@SomewhereOrOther.com> wrote in message
news:uIBV1CspJHA.1168@TK2MSFTNGP05.phx.gbl...
> Look for an 'autorun.inf' file in the root of the S drive. If so there's
> your reason. Opening it up in notepad would show further what it does.
>
> --
> Jon
>
>
> "Graham R Seach" <gseach@accessmvp.com> wrote in message
> news:76EE9C82-5DB6-4024-B90B-248AA35D6520@microsoft.com...
>> Hi guys,
>>
>> I have a 64-bit Vista Ultimate SP1 workstation that has mapped drives
>> setup at login by a script coming from SBS 2003 R2. This method of
>> mapping drives has been running quite happily on 32-bit machines for
>> several years until I purchased and setup this new 64-bit machine. Only
>> on this machine, if I double-click one of three mapped drives (S), I get
>> the following error:
>>
>> "This file does not have a program associated with it for performing
>> this action. blah blah blah."
>>
>> The context menu for drive S is as follows:
>> Install or run program
>> Explore
>> Open
>> ...The rest are the same as for other folders.
>>
>> The Open and Explore items do as they're supposed to, but the [Install or
>> run program] item results in the abovementioned error. All other mapped
>> drives function as expected. I'm not sure if it makes any difference, but
>> among a raft of other files and folders, this drive also contains a
>> system folder called 'System Volume Information'. It appears to be the
>> only drive to contain this folder.
>>
>> I had a look in the Registry, but couldn't find any difference between
>> drive S and any other mapped drive.
>>
>> Can anyone shed some light on what may have happened here, and more
>> importantly, how to fix it??
>>
>> Regards,
>> Graham R Seach
>>
>

On Tue, 17 Mar 2009 13:51:22 +1100, "Graham R Seach"
<gseach@accessmvp.com> wrote:

>Hi guys,
>
>I have a 64-bit Vista Ultimate SP1 workstation that has mapped drives setup
>at login by a script coming from SBS 2003 R2. This method of mapping drives
>has been running quite happily on 32-bit machines for several years until I
>purchased and setup this new 64-bit machine. Only on this machine, if I
>double-click one of three mapped drives (S), I get the following error:

Are any of the other 32 bit machines Vista based ?

Hi Bob,

Yes, in fact all are now Vista. This is the only 64-bit machine though.

Regards,
Graham R Seach

"+Bob+" <nomailplease@example.com> wrote in message
news:lqpvr4tc9465bihhe8hj6siapbf9neirce@4ax.com...
> On Tue, 17 Mar 2009 13:51:22 +1100, "Graham R Seach"
> <gseach@accessmvp.com> wrote:
>
>>Hi guys,
>>
>>I have a 64-bit Vista Ultimate SP1 workstation that has mapped drives
>>setup
>>at login by a script coming from SBS 2003 R2. This method of mapping
>>drives
>>has been running quite happily on 32-bit machines for several years until
>>I
>>purchased and setup this new 64-bit machine. Only on this machine, if I
>>double-click one of three mapped drives (S), I get the following error:
>
> Are any of the other 32 bit machines Vista based ?
>
>

Never mind. I found the problem on Google.

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\##sol#devtools]
had a Shell key appended to it. I deleted it, and all's well with the world.

Regards,
Graham R Seach

"Graham R Seach" <gseach@accessmvp.com> wrote in message
news:76EE9C82-5DB6-4024-B90B-248AA35D6520@microsoft.com...
> Hi guys,
>
> I have a 64-bit Vista Ultimate SP1 workstation that has mapped drives
> setup at login by a script coming from SBS 2003 R2. This method of mapping
> drives has been running quite happily on 32-bit machines for several years
> until I purchased and setup this new 64-bit machine. Only on this machine,
> if I double-click one of three mapped drives (S), I get the following
> error:
>
> "This file does not have a program associated with it for performing
> this action. blah blah blah."
>
> The context menu for drive S is as follows:
> Install or run program
> Explore
> Open
> ...The rest are the same as for other folders.
>
> The Open and Explore items do as they're supposed to, but the [Install or
> run program] item results in the abovementioned error. All other mapped
> drives function as expected. I'm not sure if it makes any difference, but
> among a raft of other files and folders, this drive also contains a system
> folder called 'System Volume Information'. It appears to be the only drive
> to contain this folder.
>
> I had a look in the Registry, but couldn't find any difference between
> drive S and any other mapped drive.
>
> Can anyone shed some light on what may have happened here, and more
> importantly, how to fix it??
>
> Regards,
> Graham R Seach
>