Page 2 of 2
Re: Don't see the shared path
Posted: 20. Dec 2012, 11:10
by HuaMin
Thanks. I will further provide you with the log file.
But what is the reason for that I cannot see shared path of the host, within this VM? I do not have the same problem on one other VM, that is running Win 08 server inside, and is also given 4 GB ram like the current one.
Re: Don't see the shared path
Posted: 20. Dec 2012, 11:12
by noteirak
The reason would be that the guest additions didn't install properly.
I do see your shared folder in the log, I see that it should be working, but you just can't see it, which makes me believe something is wrong with it.
Re: Don't see the shared path
Posted: 20. Dec 2012, 11:43
by HuaMin
Thanks a lot. Please see the log of the current VM in which I am suffering from the same issue. I did remove the previous VM thoroughly as it is always a black screen after having set up the additions.
Re: Don't see the shared path
Posted: 20. Dec 2012, 12:26
by noteirak
I'm out of ideas, might be missing something obvious tho.
Perryg, mpack, any idea?
Re: Don't see the shared path
Posted: 20. Dec 2012, 13:39
by mpack
Well, I would start with the suggestion that you should never share a complete drive, though I can't see that being the problem here. Second suggestion is that I've had problems in the past when share names were not as simple as possible - use letters only, capitalizing the first letter only, or at least use the same case throughout. Hence "D_Drive" is asking for trouble. I would suggest "Dshare".
Also it would be helpful if the OP clarified where he has been looking for the shared folder. It should be found along the guest's "My Network Places | Entire network | VirtualBox Shared Folders" path.
Re: Don't see the shared path
Posted: 20. Dec 2012, 16:16
by Perryg
If I may,
I see the guest is called WIN 12, if this is Windows 12 then you probably need to upgrade to VirtualBox 4.2.4 or 4.2.6 since the support for Windows 12 was not added until then. I also don't see the guest additions being loaded. This is a requirement for shared folders.
Re: Don't see the shared path
Posted: 21. Dec 2012, 08:11
by HuaMin
Thanks all.
Perry,
I have already upgraded it to Ver 4.2.6. But now inside VM, I don't see any additions available there to set up the shared drive.
Re: Don't see the shared path
Posted: 22. Dec 2012, 09:10
by HuaMin
Any help?
Re: Don't see the shared path
Posted: 22. Dec 2012, 15:14
by Perryg
Have you looked a your VirtualBox users manual? Here is the online version.
http://www.virtualbox.org/manual/ch04.html
All you need to do click on the devices tab at the top and select install guest additions. You can also read about the shared folders and how to install and use them.
Re: Don't see the shared path
Posted: 25. Dec 2012, 15:26
by HuaMin
Good day Perry,
I have selected
Devices > Install Guest Additions
but then nothing happened. Why?
Re: Don't see the shared path
Posted: 25. Dec 2012, 15:57
by Perryg
Then the additions are already mounted in the guest. Either unmount them and click install guest additions again or use the file manager and start them manually.
Re: Don't see the shared path
Posted: 25. Dec 2012, 16:44
by mpack
Or else autoplay has been disabled - in which case run the .exe manually from the CD.
Re: Don't see the shared path
Posted: 25. Dec 2012, 17:40
by HuaMin
Thanks all.
I can now see
CD Drive (D:) VirtualBox Guest Additions
within the VM.
Can I run this file
VBoxWindowsAdditions-amd64
that is one Application, inside that (D:) drive? Can I run the highlighted file in the attached screenshot?
Re: Don't see the shared path
Posted: 28. Dec 2012, 09:37
by HuaMin
Any help?
Re: Don't see the shared path
Posted: 28. Dec 2012, 11:44
by mpack
ISTM this conversation is already too long. You mentioned seeing some .exe files in the CD folder. It surely does not take you three days to work out what needs to be done next? If that is really the case then we are into the realms of basic Windows OS tuition - that I really don't want to get into. In a tiny fraction of that time you could have backed up the VM and simply tried it. I really think that occasionally you need to apply some of your own common sense, and not wait for instructions down to the level of the trivial.
But no, the file to execute would be VBoxWindowsAdditions.exe.