You're done, you can access your share with the Z drive letter. Z is the letter you want to give, and ReactOS is the name of your share (you gave it in VMware configuration) Execute hackssign assign z ReactOS (for instance).But accessing via NetworkPlaces worked fine. Go to C:\ReactOS\bin (or whatever, depending on your setup).If you want to assign a driver letter to ease their usage. (0.4.11), only the option worked - at least for me.Īt that point, you can already access your shared folders from cmd or explorer with UNC path (for instance: \\vmware-host\Shared Folders\ReactOS) Configure your shared folders (in VMware VM configuration GUI).After that, it seemed to hang, but only paused for about one minute before continuing and complete successfully. While Installing, the Installer first showed an error related to tpvmon.dll.
I had to do a custom Install with the following Configuration Options activated: (WMI Performance Logging) and (Shared Folders). They don't replace the required tools from VMware or VirtualBox! They come as an add-in! Just download the ISO and grab the needed tools from their. You can find an ISO with them on Jira: CORE-10033. Note: because both application hackssign & rosvboxmgmt are hacks to workaround missing features in ReactOS, there aren't included in default builds you can download on our website. In all cases, you'll find your shares in 'Network Places'. With VirtualBox, a drive letter can be assigned to your shares, just look at 'My computer' place. Reboot, you're done! There's nothing more to do.Installing using the msi directly circumvents the problem. Use setup.exe /x which extract vmwaretools.msi to a temporary folder.
If ReactOS doesn't shutdown because of a stale Setup.exe:
0 kommentar(er)
