Windows Shares

[darrenfinch]

Hi,

I have setup multiple VM sessions which all look like they are working fine on my laptop.

However, since I have added some shared drives Windows Vista 64 takes an age to shutdown and I was wondering if this is because one of the shares is on an external HD (actually, I store the VB images on this same drive also).

I setup a new image last night and added two shares:
The first - to my local D: (mapped as Y: on the VB session)
The Second to the general share on the external HD on z: (and mapped as z: on the VB session).

I wanted to make the startup / shutdown of the VBox sessions as trouble free as I could, but was wondering if anyone else had this issue (I think this more as a Windows Share issue than anything else).

I guess the easiest thing to do would be to make the shares not permanent and just write a few batch scripts for mapping the drives in.

Any ideas?

[Perryg]

Are these network shares or VBox shared folders?
I have seen this kind of behavior with sharing of a USB external hard drive, and I found that if I disconnect it via devices it shuts down faster.
I suspect that Windows is trying to find the drive and shut it down before it completes the shutdown process, but not totally sure.

[darrenfinch]

Hi,

I think your right - the shares are local.

And whether I disconnect the external device before I shutdown the machine or unplug before it still seems to hang (I am guessing Vista is waiting on device timeout).
I have two shares on my local D: (going to a VBox Webserver session and the other to a C# VBox session) and then the usb disc is on Z: (shared - like a sandpit test / doc area), I thought this would make sense to try and do some easy load balancing.

i think I will have to modify my vistaLogout script. The drive mappings are common across the VBox sessions so it should not require a huge effort (it is just annoying!).

Cheers