Forty years ago, Newsweek sent me and another photographer, Marty Umans, out to Brooklyn to take photos of the blackout. There were fires everywhere and by the time I got there, most of the looting was over. This building, at the corner of Stone (now Mother Gaston Blvd) and Somers St in Brownsville was in flames. The Google Street View photo from 2014 shows the same intersection.
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.
Fishing season is starting. I got a good deal on this old Abel Big Game Standard Arbor Pt.5 Fly Fishing Reel at the Oakland Museum of California’s White Elephant Sale.
I’ll probably use it on larger rivers with my 5 and 6 weight rods – it has a more substantial cork drag system and a little more room for backing than my 17 grams lighter Abel TR1. Now all I need to do is find a new reel seat for my Angler’s Roost 5 weight.
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.
I found a nice script for “Rebooting the Raspberry Pi when it loses wireless connection“. It’s a script that runs in crontab and checks for a network connection by pinging a local address. If the ping fails, it restarts wlan0.
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.
I decided to update to the current Raspbian Jessie with Pixel and some other webcam software. The Motion-Project seemed not to difficult – I could use it as a streaming webcam. I decided to use Motion 4.0 and Kenneth Lavrsen’s Motion 4.0 Guide to help set it up. I don’t know if the image oscillation is an issue caused by using the Creative Live! Cam Chat HD (auto exposure?) but this current setup seems to have resolved the issue.