http://bugs.winehq.org/show_bug.cgi?id=11811
Fred Wright fw@fwright.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |fw@fwright.net
--- Comment #58 from Fred Wright fw@fwright.net --- One thing I haven't seen mentioned in this thread is that the DEVICEMAP keys are *volatile*, which means that adding them manually only lasts as long as the current incarnation of wineserver. Obviously the best solution is for wineserver to create the keys when it starts up, but in the meantime, the options are:
1) Launch wineserver with -p, then edit the registry.
2) Leave regedit running (after making the edit(s)) until the serial application is launched.
3) Create a wrapper that keeps wineserver up while making the necessary registry fixes and running the application.
I've implemented #3 as a Python script, which I'll upload.
The application I'm using only seems to care about the values, not the value names, so I elected to derive the value names from the actual device names, but with a bit of "Windowsification". E.g., "/dev/cu.XXX" -> "\Device\cu.XXX". Actual Windows systems have names of the form "\Device\Serial0", "\Device\BthModem0", etc., which are somewhat less informative.
I've tested this with SXBlue Config running under Wine 1.62 on OSX 10.9.1. It also has code to perform the equivalent setup for parallel ports, but that's untested.