This past weekend I finally removed Flash. Adobe has declared that Flash will die this year or next, so I decided to get it done now. It's somewhat sad, as I liked the Flash panoramas, and I had some hope of playing with a Flash to do what could be done with QuickTime in LiveStage Pro. However, it died a long time ago, too,
Yesterday I updated my copy of BBEdit, a Mac-only text editor from Bare Bones Software that I have been using for over a decade. I never got far with the program during my English-teaching career, but this semester the program was particularly useful to me in writing Python code for the final project in ECE 463.
After installing the update, I opened the About… window and scrolled down to find a familiar name. I cannot recall what I might have done to get on the list, or whether that is coincidentally someone with the same name, but there I am:
For my networking course, we are assigned some labs that require using a Wireshark, a free packet sniffer. These labs have forced me to start learning some basic commands in Terminal. I am currently running Mac OS X 10.11.
To get one's IP address, assuming en1 to be what you want:
ipconfig getifaddr en1
To find your DNS address:
To flush the DNS cache:
sudo killall -HUP mDNSResponder
For my internship, I have been learning Python, particularly v2.7.11, with Learning Python the Hard Way, various online resources, and a couple of books. Usually I do my work in my office on a Windows machine, on which I typically use Spyder and Windows PowerShell—how had nobody ever heard of it?—for Python.
At home, in the past, I have used the text editor BBEdit to write the Python code and IDLE. Now I am trying to copy what I do in the office, which led me to discovering that Mac OS X' Terminal does not have tab-autocompletion enabled by default. A travesty!
Thankfully, MacDaddy.com has very helpful page that explains how to add tab-autocompletion functionality and make Terminal far more useful.
I have begun dabbling some with C++, since a good part of my senior project is to be written in the language. Earlier today, I messed a bit with Microsoft Visual Studio 2008, which was fine. This evening, I wanted to mess a bit with Apple's Xcode, its free IDE. The following video was helpful in getting me started.
My MacBook Pro returned on the 20th after going off for repairs following the failure of one Nvidia chip. The flat fee of $310 resulted in replacement of the logic board, replacement of the hard drive, and upgrade to OS X 10.9 Mavericks, which has been working quite well. With service like this, Apple keeps me a happy customer.
Not long before I left Japan, I bought a MacBook Pro. It has been a good machine. Last year I began running Windows 7 in Boot Camp on it after partitioning the hard drive.
Problems began to appear when booted in Windows. Certain sites would crash Windows fairly reliably. Video would sometimes crash it. There were warnings about a need to update the Nvidia graphics drivers, but doing so was difficult; the one time I did, the crash was so bad I had to reinstall Windows 7. When booted into Mac, however, problems were fewer.
Then I upgraded to OS X 10.9. That was a disaster! The Mac crashed constantly, always with the same warning about a graphics CPU or something. Eventually I took the machine to the local Apple Store once an attempt to restore it from a backup failed. It turned out there had been a recall due to faulty graphics chips. However, I was told the program had ended because most of the problems were ultimately attributable to software conflicts; regardless, the recall had ended only a few weeks before I came in. I was also told people running Windows in Boot Camp seemed to be having more of these kernel panics, so I quit running Boot Camp. They were able to get my machine running, so I ran with it.
Until a few days ago when the crashing began occurring multiple times per day. I booted off backups on both USB and FireWire drives to restore from the respective backups, but the MacBook Pro crashed a few times during restoration. Eventually it would not even boot from OS DVDs.
On Friday the 12th, I lugged the MacBook Pro back to the Apple Store. This time the diagnostic tests showed one of two graphics chips were not responding. Since the chip itself cannot be replaced, I need a new logic board, which alone costs around $900, an Apple quote. However, because my problem seems tied to the recall problem, I should be able to have everything done for $310. I left the machine with them and returned home. They will contact me in another day or two if some other problem is found. Otherwise, the MacBook Pro should be back and working inside a week.
Too bad it did not crash over the summer instead. In the third week of classes has been inopportune, to say the least.
The week before finals, my OS file hierarchy collapses irreparably. I take the chance to do a clean install of OS 10.9 Mavericks, which has kernel panics a few times per hour. I update to 10.9.2, which results in a few kernel panics per day. So it is sayonara, Mavericks, you worthless OS.
My 2010 MacBook Pro runs well under 10.8, but I fear 10.9 is going to be the future of Mac OS X. If so, I'll need a different OS.
Yesterday I returned home from class to find my MacBook Pro unresponsive. I did manage to coerce it into booting, but it would abruptly restart about 3 minutes after the booting process was complete. The charging indicator stayed green, never the orange of charging; the battery indicator turned into a X.
Today I took the 2010 MacBook Pro to the Apple Store here in Indianapolis, where they ran tests to find the file hierarchy was destroyed. That might be why the Mac would not even countenance Alsoft's Disk Warrior, on which I once relied. Problem identified, I brought the Mac back, wiped the hard disk, partitioned it again, and installed the free Mac OS X 10.9, Mavericks. It still sucks: three kernel panics alone tonight with only the basic system installed and Microsoft Office 2011. It seems Macericks itself is the problem.