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.
A new version of FileIndexer is available, fixing a rather nasty bug, and adding support for SHA-256 hashes. Grab it in the Tools section, as usual.
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.
Today, I am happy to announce the start of CyanogenMod 13 nightlies for Xperia Tablet Z (pollux) and Xperia Tablet Z Wifi (pollux_windy). This means CM13 is considered stable enough for daily use on these devices, so the terrors should be rather limited. Anyone interested can find the official downloads at the usual location. Active development on the fusion3 platform is ongoing, I will attempt to shift focus to the phones now.
You all know the drill – go download it from the WinUAE section!
As of today, all Sony Xperia devices based on the Fusion3 board (Xperia Z, ZL, ZR, Tablet Z, Tablet Z WiFi) are getting official CyanogenMod 12.1! When I first started looking at these devices in December 2014, the CM12 source code would not even compile, let alone boot, and even the recovery was broken.
Well, here we are, hundreds of commits and quite a lot of annoyances later: F2FS is now supported, a plethora of kernel changes and the new BFQ scheduler made the user experience better than ever, the latest proprietary blobs are integrated, SELinux is properly set up, and a ton of reorganization and cleanup has been done – for all of Sony’s MSM8960 devices and beyond.
Still many things to do, but for today, I’m lighting a cigar! If you have one of these devices, check out GET.CM and give it a whirl. There is a truly fantastic team of developers at Cyanogen and CyanogenMod, and without them, none of us could enjoy mobile computing quite like we do.
After a long, arduous development road, I’ve enabled CyanogenMod nightly builds for the Sony Xperia Z. This brings nightlies directly from CM11 to CM12.1, which hopefully all users will enjoy. Thanks to everyone at my XDA thread, especially Andy van der Steen, who lent me his phone for development. Without that, I would never have come this far.
Starting with early March 2015, CyanogenMod for the whole original line of Sony’s Xperia Z devices support F2FS, a filesystem optimized for flash memory. Tests have shown it to outperform the default ext2/3/4 that we used previously, so definitely a nice thing to have.
However, if you want to benefit from F2FS, you need to manually convert your phone. Be aware that this needs some understanding of how to use ADB and the conversion process will DELETE all you user data/settings!
First, you need to have CyanogenMod 12 or higher installed on your phone, and be using the official recovery. Also, you need ADB installed and ready to use on your computer.
This is how you convert to F2FS:
– Connect your phone via USB and boot into recovery mode
– Open a command line and type “adb shell”
– Type “mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/cache”
– Type “mkfs.f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata”
– Reboot the device