The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Bill on Tuesday October 21st 2008, 18:29
PSIService.exe is a program that is supposed to run (separately) as a "service" in Windows. This is the Protexis licensing service that Painter uses to verify the license of the program, by contacting a Protexis server via the internet. Whether this will work under Wine I cannot say, but even if it did run, the question is whether Painter running under Wine would pass the test.
by Bill on Sunday October 19th 2008, 12:08
In the interest of moving this forward here are a few things I have discovered:
I am testing with Wine git version 1.1.6-255 at this time.
The behavior of the demo is different from the full version in that the demo complains that it's files are corrupted and/or compromised, and then refuses to run. The full version does not complain, running up to a certain point and manages to draw some graphical elements like the menu titles and a little bit of the toolbar(s). My testing will be strictly for the full version.
Installing Painter inside a Win2K environment (via winecfg) is different than that of a WinXP environment, in that the installer assumes that it needs to install it's own gdiplus.dll (and others?) in the case of Win2K. Although this may (eventually) provide a workaround, I would like to see Wine gdiplus advanced as much as possible, so I am focusing my testing on a WinXP install (assume I am testing WinXP env unless noted otherwise). I have not yet tried a Vista env.
The Painter installer writes over the following system32 dlls:
The Painter installer adds the following system32 dlls/exe:
Probably the installer is checking dll versions and "upgrading" them. I think it would be best to restore the original Wine msvcrt.dll, oleaut32.dll, olepro32.dll files, however doing so does not alter Painter behavior thus far.
I have not been able to run/install the Painter X.1 (SP1) update.
Running Painter with winedbg produces (many) gdiplus crashes initially.
Running Painter with wine produces two (consistent repeatable) errors:
fixme:win:WINNLSEnableIME hUnknown1 0x1002a bUnknown2 1: stub!
The WINNLSEnableIME problem may be benign (not sure). I started a Wine bug #15651 to address the CreateHBITMAPFromBitmap issue.
Running inside a virtual desktop does not change anything (although it makes the Painter lockup more managable). Unchecking the "Allow the window manager to decorate..." and "... to control the windows" in winecfg does not alter the behavior.