Sculla |
Tuesday 5 April 2016 at 20:38
|
Sculla
|
Hello PoM members,
with the newest version 4.2.10 I experience a printer problem. Upon printing, my applications tell me that Windows has a problem printing, "no printers are connected".
Exactly the same software runs fine in a wine environment created by Wineskin Winery, printing is as it should be. So I strongly assume that PoM is the problem, fucking things up with the printer or network connection.
The log only shows
"err:dc:CreateDCW no device found for L"Screen"
fixme:win:WINNLSEnableIME hwnd 0x201be enable 0: stub!"
Are there any solutions?
Kind regards,
Sculla
Edited by Sculla
|
observe |
Wednesday 8 June 2016 at 20:36
|
observe
|
Have experience the same issue with 4.2.10 on multiple Macs running different versions of OSX & have just filed bug report #5289. As a workaround for now you can install 4.2.9 or earlier from http://repository.playonlinux.com/PlayOnMac/
Kind regards
Ian.
|
Quentin PÂRIS |
Saturday 11 June 2016 at 17:46
|
Quentin PÂRIS
|
I really don't believe that 4.2.10 has anything to do with this problem.
I'd rather check the wine version your app is using. You may want to try an older one
|
Erdeslau |
Saturday 27 May 2017 at 11:33
|
Erdeslau
|
Don't know about Linux, but this is a definite Bug in PlayOnMac Version 4.2.10 irrespective of what version of Wine is used, which makes the use of PlayOnMac virtually impossible for anything other than gaming.
The 'Bug' must either be in the PlayOnMac app or the method used to prepare the Wine installations for PlayOnMac. Evidence: Printer recognition in very same Windows software apps works perfectly on the same Mac computer when apps are created ith Wineskin Winery or using a trial version of Crossover for Mac and exactly the same Wine Engine. Using PlayOnMac 4.2.10, installed Printers are simply not recognised by any Wine App.
Is there any possibility that this is going to be looked at; or is it a wait and see if Version 5 works.
|
Erdeslau |
Saturday 27 May 2017 at 17:41
|
Erdeslau
|
I believe I have found the problem. It lies within whatever process is being used to prepare the Wine Engine Builds for use within PlayOnMac, including the built-in default.
I substituted a Wineskin Wine Engine build for the same version of an existing PlayOnMac version; and all apps which used that Engine immediately recognised the installed printers.
|
Valkrider |
Saturday 27 May 2017 at 22:24
|
Valkrider
|
@Erdeslau i am a bit of a novice at this whole PlayOnMac setup. Can you give a few more details of exactly how you did what you did to get the printer working?
|
Erdeslau |
Wednesday 31 May 2017 at 17:33
|
Erdeslau
|
@Valkrider
I downloaded a couple of the WINE Engine available from https://mega.nz/#F!I98VVIiY!uSZgcyFdEFtmpXpLoYAGpA!to8hzAyB After unpacking them and copying the content to the PlayOnMac Folder: User Library/PlayOnMac/Wine/darwin-x86/, they were then usable for updating existing application prefixes and the Wine apps I tested immediately recognised all installed printers. See you soon on FHUG (under a different idenity!)
Edited by Erdeslau
|
Quentin PÂRIS |
Monday 5 June 2017 at 11:50
|
Quentin PÂRIS
|
This is interesting. We need to investigate why printers are not currently supported
|
Erdeslau |
Tuesday 6 June 2017 at 12:01
|
Erdeslau
|
Thanks for picking this up. It would be interesting to know whether it is something fixable within the PlayOnMac app, or if there is something in the build process for the WINE engines. I don't use Linux, but presume the issue isn't appearing in Linux, or would have expected there to have been a lot more issue reports.
Perhaps a slight difference between Linux variants and operating systems such as MacOS (derived from BSD )?
|
observe |
Wednesday 23 September 2020 at 18:27
|
observe
|
|