"Auric__" <***@email.address> wrote
| There are a few ports of Wine for OSX. I'm unwilling to try any of them on
| *my* Mac, but they exist.
|
I tried it on Linux at one point, a few years
ago. A WINE honcho came into a Windows
programming group looking for volunteers to
work on porting their Windows software to
WINE. The project didn't really work out. He
didn't want to cooperate or share info to help
us adapt Win32 API calls to what WINE could
handle. He just wanted us to work as lackey
bug testers in what turned out to be a sort of
paramilitary organization. (Thus, "honcho".
There was clearly a hierarchical command
structure in the WINE group. Maybe that's
just how corporate "cooperation" works. I
don't know. As someone who's self-employed
I didn't have patience with it, and it quickly
became clear that the WINE-os were not going
to provide any help to, or cooperate with,
Windows developers.)
In general I find WINE disappointing. It's over
20 years old now, with a new release about
every 10 days, yet they've never got the kinks
out. Their implementation of the API is inexplicably
unreflective of the Windows DLLs. And as is typical
on Linux, docs are all but non-existent. (Even
those were supposed to be specially "compiled".)
But even if they got their act together about
docs, if a shell32 call or kernel32 call on Windows
is not in shell32 or kernel32 under WINE then it
becomes very challenging to even look up what
functions are supported and how.
Nevertheless, in the course of my explorations I
tried out installing WSH on WINE and it worked
pretty well.
Since WINE interprets Windows API calls and then
sends them through the Linux API, VBS on Linux
was fairly useful. For instance, enumerating files
in a folder had no restrictions. I wrote up some
of the details here, for anyone who wants to do
similar:
http://www.jsware.net/jsware/vblinux.php5
That was several years ago. If anything WINE
should now be more adaptable to WSH than
it was back then.