... I don't think I can install it without the Perl API... but the MUI isn't always needed.
The reason I ask is that I've just succeeded - after many days of hard work, in getting a portable VM guest onto a USB hard drive with an auto-installing copy of vmware server, so my guest/s can be truly portable.
One of my main troubles was windows' tendancy to dynamically assign removable drive letters each time one unplugs a drive. I use lots of removable drives, and Windows kept changing the drive letter so paths would screw up each time I reconnected a drive. This resulted in continuous modification of guest settings on each host.
But not now... I scripted (a quiet) installer which works on any win32 host, and it is true freedom!
The Guests on the portable drives now work on any computer I connect to, though I've not yet scripted a Fusion or Linux installer also. But then again, they don't suffer from Parkinson's disease when mounting drives, so it doesn't exactly matter to me.
However wherever I need to use a win32 host I can now just plug in and do a quick install with a known result, so long as I can get admin rights. It takes less than a minute on each new host I use. Yippeee!
After that, each time I plug it in I can set it to automatically starts my choice of VMs (am still working on that part, but there are a few space issues at present...
My installer even puts shortcuts to vmware-cmd statements in the Host's menu so I can start and stop it without the MUI. Which is why I am wondering if I can knock leave the MUI out of my scripted windows installer (msiexec -i "vmwareserver1.03.msi" ADDLOCAL=ALL... etc.)
I have yet to find anything that explains clearly what can be removed to minimize the installation footprint, so I was windering if anyone here would know?
Many thanks in advance for any thoughts...