Vista - CD Eject causes Explorer to close

Hello,

I have a weekly task where I copy about 2 dozen CDs onto a network volume.
Every since I got Vista, I've been confronted with a frustrating "FEATURE".
When I eject a CD to insert the next one, the Explorer that has the content
of the current CD closes, instead of the previous windows action of moving
"up" the tree to the next ready device.

My work around is to click back to my C: drive between each copy, but that's
a lot of extra clicks over a month or a years time, which I never had to do
until Vista.

I've searched the web extensively since beta looking to kill this and never
found a good solution. I've seen lots of comments to the effect of "That's
not a normal Vista behavior".... If it's not a normal behavior, how come all
5 of my systems do it? One is a Dell Laptop, factory loaded Vista Ultimate.
One is an HP purchased new with Vista home. The other 3 are clone boxes that
have been loaded by me with retail copies of Vista. One is 64 bit and the
other 2 are 32 bit versions. Every single one of these machines exhibits
this behavior, which they didn't do when they had XP on them..

As well, I've tested on a few friends systems and same result there.
Obviously this is a default behavior. I finally resigned myself to live with
it, and have done so for nearly a year, but today, I got the renewed bug to
get rid of this annoyance, so here I am.

Can anybody tell me if there is a way to disable this, and if so, how?

Thanks a million times over if you can!

Sorry, that's normal Vista behaviour all right. I think it's normal XP
behaviour also when in single-pane Explorer mode. I don't know of any way
to stop it either, sorry.

--
Richard G. Harper [MVP Shell/User]
* NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
* PLEASE post all messages and replies in the newsgroups
* The Website - http://rgharper.mvps.org/


"David B" <> wrote in message
news:...
> Hello,
>
> I have a weekly task where I copy about 2 dozen CDs onto a network volume.
> Every since I got Vista, I've been confronted with a frustrating
> "FEATURE". When I eject a CD to insert the next one, the Explorer that has
> the content of the current CD closes, instead of the previous windows
> action of moving "up" the tree to the next ready device.
>
> My work around is to click back to my C: drive between each copy, but
> that's a lot of extra clicks over a month or a years time, which I never
> had to do until Vista.
>
> I've searched the web extensively since beta looking to kill this and
> never found a good solution. I've seen lots of comments to the effect of
> "That's not a normal Vista behavior".... If it's not a normal behavior,
> how come all 5 of my systems do it? One is a Dell Laptop, factory loaded
> Vista Ultimate. One is an HP purchased new with Vista home. The other 3
> are clone boxes that have been loaded by me with retail copies of Vista.
> One is 64 bit and the other 2 are 32 bit versions. Every single one of
> these machines exhibits this behavior, which they didn't do when they had
> XP on them..
>
> As well, I've tested on a few friends systems and same result there.
> Obviously this is a default behavior. I finally resigned myself to live
> with it, and have done so for nearly a year, but today, I got the renewed
> bug to get rid of this annoyance, so here I am.
>
> Can anybody tell me if there is a way to disable this, and if so, how?
>
> Thanks a million times over if you can!
>

Thanks for the response. Another lame thing about Vista... and no, XP didn't
behave that way. I copy in the order of 100 CDs per month onto the network,
so I became very aware of this Vista annoyance.

Maybe it's time for some coder out there to write a better explorer.exe for
Vista


"Richard G. Harper" <> wrote in message
news:...
> Sorry, that's normal Vista behaviour all right. I think it's normal XP
> behaviour also when in single-pane Explorer mode. I don't know of any way
> to stop it either, sorry.
>
> --
> Richard G. Harper [MVP Shell/User]
> * NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
> * PLEASE post all messages and replies in the newsgroups
> * The Website - http://rgharper.mvps.org/
>
>
> "David B" <> wrote in message
> news:...
>> Hello,
>>
>> I have a weekly task where I copy about 2 dozen CDs onto a network
>> volume. Every since I got Vista, I've been confronted with a frustrating
>> "FEATURE". When I eject a CD to insert the next one, the Explorer that
>> has the content of the current CD closes, instead of the previous windows
>> action of moving "up" the tree to the next ready device.
>>
>> My work around is to click back to my C: drive between each copy, but
>> that's a lot of extra clicks over a month or a years time, which I never
>> had to do until Vista.
>>
>> I've searched the web extensively since beta looking to kill this and
>> never found a good solution. I've seen lots of comments to the effect of
>> "That's not a normal Vista behavior".... If it's not a normal behavior,
>> how come all 5 of my systems do it? One is a Dell Laptop, factory loaded
>> Vista Ultimate. One is an HP purchased new with Vista home. The other 3
>> are clone boxes that have been loaded by me with retail copies of Vista.
>> One is 64 bit and the other 2 are 32 bit versions. Every single one of
>> these machines exhibits this behavior, which they didn't do when they had
>> XP on them..
>>
>> As well, I've tested on a few friends systems and same result there.
>> Obviously this is a default behavior. I finally resigned myself to live
>> with it, and have done so for nearly a year, but today, I got the renewed
>> bug to get rid of this annoyance, so here I am.
>>
>> Can anybody tell me if there is a way to disable this, and if so, how?
>>
>> Thanks a million times over if you can!
>>
>

Cant you set the "auto play" to open the file explorer when a disk of your
selected type is inserted ?
Open one explorer window to your network share, then let windows open a
second window automatically when your disk type is inserted. then just drag
and drop.


"David B" <> wrote in message
news:...
> Thanks for the response. Another lame thing about Vista... and no, XP
> didn't behave that way. I copy in the order of 100 CDs per month onto the
> network, so I became very aware of this Vista annoyance.
>
> Maybe it's time for some coder out there to write a better explorer.exe
> for Vista
>
>
> "Richard G. Harper" <> wrote in message
> news:...
>> Sorry, that's normal Vista behaviour all right. I think it's normal XP
>> behaviour also when in single-pane Explorer mode. I don't know of any
>> way to stop it either, sorry.
>>
>> --
>> Richard G. Harper [MVP Shell/User]
>> * NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
>> * PLEASE post all messages and replies in the newsgroups
>> * The Website - http://rgharper.mvps.org/
>>
>>
>> "David B" <> wrote in message
>> news:...
>>> Hello,
>>>
>>> I have a weekly task where I copy about 2 dozen CDs onto a network
>>> volume. Every since I got Vista, I've been confronted with a frustrating
>>> "FEATURE". When I eject a CD to insert the next one, the Explorer that
>>> has the content of the current CD closes, instead of the previous
>>> windows action of moving "up" the tree to the next ready device.
>>>
>>> My work around is to click back to my C: drive between each copy, but
>>> that's a lot of extra clicks over a month or a years time, which I
>>> never had to do until Vista.
>>>
>>> I've searched the web extensively since beta looking to kill this and
>>> never found a good solution. I've seen lots of comments to the effect of
>>> "That's not a normal Vista behavior".... If it's not a normal behavior,
>>> how come all 5 of my systems do it? One is a Dell Laptop, factory loaded
>>> Vista Ultimate. One is an HP purchased new with Vista home. The other 3
>>> are clone boxes that have been loaded by me with retail copies of Vista.
>>> One is 64 bit and the other 2 are 32 bit versions. Every single one of
>>> these machines exhibits this behavior, which they didn't do when they
>>> had XP on them..
>>>
>>> As well, I've tested on a few friends systems and same result there.
>>> Obviously this is a default behavior. I finally resigned myself to live
>>> with it, and have done so for nearly a year, but today, I got the
>>> renewed bug to get rid of this annoyance, so here I am.
>>>
>>> Can anybody tell me if there is a way to disable this, and if so, how?
>>>
>>> Thanks a million times over if you can!
>>>
>>
>