Include what ?
Technologov wrote:Two ideas:
1. Why do you use softlinks ?
This is problematic, because it is a dependency on M$ add-on stuff.
Windows OS - NTFS has hardlinks, that are built-in into the OS.
See Windows Help: "Fsutil: hardlink"
Maybe "junctions" are nice, but it should be kept optional.
Technologov wrote:2. Why use VRDP ?
This is problematic, because it is a dependency on Proprietary VirtualBox stuff, and cannot be used with VirtualBox Open-Source Edition (OSE).
Technologov wrote:I believe, that after the guest OS has been installed and configured, it can be accessed via virtual Serial COM/virtual Ethernet network. VRDP is nice but it should be kept optional.
Technologov wrote:In short: Please do not introduce unnecessary dependencies.
Technologov wrote:Very nice effort indeed !
But my solution is not professional, and it's hacky, unlike yours.
Anyway - I would like to see your solution integrated better with official VirtualBox package, rather being a third-party, separate install add-on.
Technologov wrote:VirtualBox OSE doesn't have any remote GUI capabilities.
It can only draw GUI locally via SDL library. And VMs can be controlled from command-line.
This means, that Guest VMs need to be pre-installed "normally", having network and/or Serial connection configured, so people can enter VMs using those measures, and if something goes wrong, people will need to use command-line to restart the VMs.
Users browsing this forum: Google [Bot] and 34 guests