64bit Windows 7 Ultimate won't share folders

[dmillerav]

I have Windows 7 Ultimate build 7100 installed in VB 3.0.4 on my Mac OS 10.5.8. I cannot make the audio work, nor do the Shared Folders appear. I have installed the additions and all else seems to be working. I have tried using the run command line to enter net use D: \\vboxsvr\milledan . Nothing works. I've tried both audio driver options as well. Can anyone help me?

[Perryg]

net use D: \\vboxsvr\milledan

I am going under the assumption that the main drive is C: and that the CD is D:
If the above is true you can not mount the share to D: because it is already in use.
Try a different drive letter like S.

For audio you should select the default that VBox used and then in Windows 7 you need to download the drivers from realtek.com. Install them and then tell Windows to do an update. The proper drivers will then be installed.

[enghemin]

Hi there, may I ask if you have solved the folder sharing problem on Windows 7 or not? I have the same problem so I thought I ask if you have come to a solution? Many Thanks

[Perryg]

Hi there, may I ask if you have solved the folder sharing problem on Windows 7 or not? I have the same problem so I thought I ask if you have come to a solution? Many Thanks

Tell us what you have tried, steps that you have taken to create the share, so we can figure out what you need to do.

[Mr Incredible]

I too have had problems with Shared Folders under 64bit Windows 7 Ultimate.

I created the "permanent" Shared Folder(s) within the settings screen and pointed them to both a root directory on one drive and a folder on another drive.

On booting the VM I was expecting to see the folders already shared in "My Computer" (just the same as the Guest Additions functionality in Virtual PC 2007). But they were not.

However, if I manually created a mapped drive and browsed for the drive I then saw the shared names I had defined in the settings. Selecting one of these shares for the mapped drive letter resulted in them appearing in "My Computer" with a drive letter. But without manually creating a mapped drive, the Shared Folders definitions were nowhere to be seen as being available.

[Sasquatch]

I too have had problems with Shared Folders under 64bit Windows 7 Ultimate.

I created the "permanent" Shared Folder(s) within the settings screen and pointed them to both a root directory on one drive and a folder on another drive.

On booting the VM I was expecting to see the folders already shared in "My Computer" (just the same as the Guest Additions functionality in Virtual PC 2007). But they were not.

However, if I manually created a mapped drive and browsed for the drive I then saw the shared names I had defined in the settings. Selecting one of these shares for the mapped drive letter resulted in them appearing in "My Computer" with a drive letter. But without manually creating a mapped drive, the Shared Folders definitions were nowhere to be seen as being available.

That is the correct behaviour. VB does not know what kind of OS you're running as Guest, so they aren't mounted in any way. It's quite possible VB mounts it on drive E:, while you want to have it on drive G: instead. Hence the choice. MS VPC only accepts Windows as Guest, so it's a lot easier to implement the auto assignment to a drive letter. VMWare doesn't auto-mount them either IIRC.

[Mr Incredible]

Well, if that's the case then there is a permission problem on shared folders and mapped drives using Pinnacle Media Manager.......

The Shared Folders" functionality in a VB machine creates shares with the name \\Vboxsvr\XXXXXXX where XXXXX is the name assigned in the definition for the share.

If I map a drive letter to that share within the VB, MediaManager reports access is denied on rading the files within the mapped drive. However if I point Mediamanager directly at the share name and not the mapped drive, it reads the files fine.

It may be MediaManager, but its odd it should be able to read files using the share and not the mapped drive.

[Sasquatch]

I'm guessing that it's a bug in the program, not VB. E.g. Office has a similar problem with writing to existing files in Shared Folders. As test, can you create a normal share and try it with that? If you use NAT, you can access the Host through 10.0.2.2.