I try to keep up with the latest Windows and macOSs by participating in the Windows Insider Preview program and the Apple Developer Program. I run both of these OSs on a Macbook Pro Retina (mid-2012). As of today, that is Windows 10 Build 16232.1000 and macOS 10.13 beta 2 (17A291m).
A lot of the time, things don’t work because I am running beta OSs with released apps.
One of the recent problems I encountered with macOS High Sierra (17A291j) was a kernel panic when I was using Paragon NTFS for Mac 15 with Dropbox (v30.3.14). I don’t know if it’s a good idea, but my Dropbox directory for both Windows and Mac is the same directory on an NTFS volume. Every time I started Dropbox, I would get a kernel panic. I opened a support ticket with Paragon Software and a few days later they sent me a new version that had the same problem.
For interoperability between the two OSs, read/write capability really helps. In the macOS (High Sierra), NTFS read/write capability is not native. I was very happy with Paragon NTFS for Mac 15 until I started getting kernel panics. On the Windows side, I haven’t found something that will read the Apple File System (APFS) in macOS 10.13.
With earlier versions of MacOS, I had used the open source NTFS-3g. When Paragon NTFS for Mac 15 stopped working in my situation with Dropbox, I decided to try the commercial version of Tuxera’s NTFS for Mac. This seemed to work ok until I installed the macOS High Sierra Developer Beta 2 Update 1 (17A291m).
On booting macOS, I would get the error message:
Aligned I/O enabled.
/System/Library/Filesystems/fusefs_txantfs.fs//Support/10.9/tufs/tufsfs.kext failed to load -… check the system/kernel logs for errors or try kextutil(8).
the MacFUSE file system is not available (71)
I traced this error to Gatekeeper in macOS 10.13. After I allowed the software, Tuxera NTFS for Mac started working again.
I built a streaming webcam showing the view from my downtown Oakland apartment in November 2012. I used a Raspberry Pi (Model B Revision 1.0) and the Raspian Wheezy (2012-10-28) image. For the webcam/web server software, I used MJPG-streamer. The problem with MJPG-streamer is that if the images/stream is available on the internet, then anyone can access the software.
Recently my Raspberry Pi began to lose the WiFi connection. In researching various solutions, I disabled WiFi power management on the Edimax EW-7811Un nano-size USB WiFi adapter. That didn’t solve the problem. I switched to Ethernet but the connection still dropped.
The checkwifi.sh script worked great, but then I had an issue with the video stream image oscillating. The image would continually go between light and dark and the only way to stop it was to restart MJPG-streamer.
After the failure of an old computer running Windows Server 2003, I setup Windows Server 2012 on a Macbook.
Years ago, I set up a Sony Vaio PCG-Z505HS running Windows Server 2003 at home so I could keep up with Macs and Active Directory. When I recently experienced problems with DHCP and DNS, I discovered that the Vaio had died. There was no LED power indication. My troubleshooting consisted of jiggling the power connector and checking the power supply voltage. When I measured voltage from the AC adaptor, I gave up, using the rationale that it had lived its useful life. The Vaio, with a Pentium 3, 500 MHz CPU, was introduced in January 2000.
The Windows Server 2012 installation was simple using the Server with a GUI mode installation. The Server Manager and configuration tools greatly simplify the setup. With Windows Server 2012 on a Macbook running silicon introduced in 2006 – an Intel® Core™2 Duo Processor T7200 that has Intel® Virtualization Technology (VT-x), the next step is to try virtualization. As a Macbook running OS X, I successfully ran VMware Fusion VMs running Ubuntu and Windows 2000, though I forsee the 3 GB of RAM in the current system will be a limiting factor.
The best part about running an Active Directory domain at home is joining computeres to the domain. The welcome message says, “Welcome to the lower_slobbovia domain.
ifixit’s MacBook Core 2 Duo Logic Board Replacement guide was helpful with the disassembly. After removing the logic board, I stripped the bottom case of the remaining parts (SSD, hard disk, speakers, display, etc). The MacBook logic board was short enough to fit in the case with the ports and connectors lining up with the opening for the Mini-ITX backplane.
I thought using the Macbook bottom case would be the best way to mount the system board because the case helps to align the MagSafe connector and the fan/heatsink assembly. I also wouldn’t have to mount other stand-offs in the Mini-ITX case. I used Dremel cut-off wheels to cut down the case bottom. To mount the logic board in the Mini-ITX case, I used double-sided foam tape.
The wiring for the ancillary devices – Wi-Fi, Bluetooth and speakers – were routed around the inside of the new case. The Mini-ITX case came with a bracket to mount 3.5″ hard drives internally but with non-standard headers on the logic board, I abandoned that idea. There was also a power supply, which I removed. I wired the power switch on the front of the case to the trackpad/keyboard connector on the logic board.
I had already removed the DVD drive when it stopped working in the summer of 2011 and replaced it with an SSD. I used double-sided tape to mount the SSD and the second hard drive to a bracket mounted above the logic board. Eventually, the short cable for the second hard disk failed and when I replaced it, the connector on the logic board failed from too many insertions.
When I first powered it on, it actually worked. The Mini-ITX case is slightly larger than a Mac mini (200 x 225 x 56mm vs 197 x 197 x 36mm) and slightly less attractive but it works. My only regret was breaking the circuit board for the system LED when I was disassembling the case.