Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

VBoxVmService / News: Recent posts

Version 4.1 - Ginger released

What is new in this release?

  • Updated COM API to make it work with VirtualBox 4.3. Note this is not compatible with old versions of VirtualBox. If you need to use VirtualBox 4.2.X, please stay with 4.0 "Bayberry".
Posted by FB2000 2013-10-16

Version 3.1 - Coconut released

What is new in this release?

  • Updated COM API to make it work with VirtualBox 4.2. Note this is not compatible with old versions of VirtualBox. If you need to use VirtualBox 4.1.X, please stay with 3.0 "Sweet Potato".
  • Service now runs (again) as LocalSystem account by default.
  • Allow additional parameters to be set for VBoxWebSrv.exe.
  • Service is no longer set to DelayedAutostart. It's now Autostart and depends on Workstation and COM+.
  • Fixed a bug in sending pipe commands: need to write an additional null byte at end of message;
  • Removed pipelcat to simplify pipe comminucation;
  • Fixed compile warnings.
Posted by FB2000 2012-09-16

New Release 2008-07-28

What is new in this release?

Changes since version rel20080422:

  • Added a BRUTEFORCE option to the startup-calls. This will kill any possibly remaining run-
    or lockfiles for a VM before startup.

  • The non-cli versions of startup and shutdown now save all their outputs to the logfile.

Posted by Mathias Herrmann 2008-07-28

Runnig VBoxVmService together with VirtualBox 1.6.0 ...

... will be a little tricky, if you have been using the VRDP-headless server to operate your vms. starting with this version, the according tool has been renamed from VBoxVRDP.exe to VBoxHeadless.exe. You will have to adjust the corresponding value in the VBoxVmService.ini-file to meet this new naming convention. Please note, that hotlinking (like creating a shortcut to the new file,and assigning it the old name) will NOT work here! Additionally, after upgrading two machines with the 3rd XP service pack (5512, final build), "runserv" suddenly moved from being controlled by my system's LocalService into the realm of NetworkService, so if you are experiencing similar problems, try to establish another hotlink in "c:\docs & settings\NetworkService.VirtualBox\VirtualBox.xml" pointing to the corresponding valid file within your vbox-users home directory...

Posted by Mathias Herrmann 2008-05-04