A little gift before we end the 2010s – go grab the latest help file from the download section and have a happy and successful next decade!
After the massive update last time around, only minor changes this time. Caught up with WinUAE 4.2 thanks to Peter, and made some minor corrections. Go download it!
Also, this is some anniversary: 20 years ago, I started pulling together the first content of the help file together with Brian King. How time passes…
There is a new version of the WinUAE Help file available as of now, which is 2.2.15. You may grab the updated version in our downloads section, as usual.
Also, in a rare case of promised and actually completed some work: the online version of the WinUAE Help is now up-to-date with the latest development! There have been a lot of changes going on in an attempt to vastly improve the content quality. This will ultimately result in a version 3.0 for the file. In the meantime, keep track of progress at winuaehelp.vware.at!
After some jackass tried attacking our old website host, vware.at and it’s content went offline for some time. That was not due to a successful attack but rather dissatisfaction with the hosting company. We have since moved to a new host with modern software and HTTPS support. Do enjoy.
Business as usual: Peter has been toiling away on our latest revision of the official WinUAE Help file. Meanwhile, I am working on a way to deliver it’s content easier and in more ways than in the last decade or so. Stay tuned, and grab the file at the usual place.
Microsoft has graced us with a new security update that patches a flaw in the printer spooler service. So far, so ordinary. This had some unforseen consequences: deploying printers in a Active Directory domain might not work as expected anymore for certain printers, logging “0x80070bcb Specified printer driver was not found and needs to be downloaded”.
Long story short: printer drivers which are not package aware will not be installed automatically by your client OS, no matter what you do, even in a GPO. The easiest fix is getting new drivers, but that’s not even possible for all devices out there. So here is a way to get the spooler service to think the driver is package aware: open the Registry, navigate to “HKLM\System\CurrentControlSet\Control\Print\Enviroments\Windowsx64\Drivers\version-x\Driver name“, and edit the PrinterDriverAttributes value. Specifically, increment whatever is there by 1. After that, restart the printer spooler service.
Run gpupdate on the affected devices, the printer should be mapped fine.