Mac emulation and insights

I’m scaring myself. I’ve been playing around with Mac emulation on my PC at home (I can get an old Quadra or something from work for nothing or virtually nothing, but finding space to set it up properly in these cramped quarters would be an issue, especially since I’d have to give it its own keyboard and mouse and possibly its own monitor). My Celeron-400 certainly feels faster than the last 68040 I used, and I greatly prefer my clackety IBM keyboard and my Logitech mouse over anything Apple ever made, so this emulation setup isn’t bad. I’ve got MacOS 8.0 running on my Celeron 400, though on an 040 (especially an emulated 040), 7.6.1 would be much better if I can track down an installation CD for it by some chance.
Of course, there’s the issue of software. A lot of the ancient 68K Mac software is freely available (legally) these days, and it raises the old “Are we better off now than we were 10 years ago?” question. I don’t know. I still think the software of yesterday was much leaner and meaner and less buggy. By the same token, programs didn’t necessarily work together like they do today, and the bundles of today were virtually unheard of. Software ran anywhere from $99 to $999, and it typically did one thing. More, an outliner from Symantec (not to be confused with the Unix paging utility), made charts and outlines. That was it. And it cost around $100. The functionality that’s in MS Office today would have cost many thousands of dollars in 1990. Of course, the very same argument could be made for hardware. You couldn’t get the functionality available in a $399 eMachine for any price in 1990–there were very high-end machines in 1990 with that kind of CPU power, of course, but the applications weren’t there because you don’t buy a supercomputer to run word processing.

Messing around with this old Mac software gave me some insights into the machine. One of the freely available packages is Think Pascal. In high school, we did computer applications on Macs and programming (at least the advanced programming classes I was taking) on IBM PCs. So I know Pascal, but this was my first exposure to it on the Mac. Reading some of the preliminary documentation on programming a Mac in Think Pascal gave me some insight into why the Mac has (and always had) such a rabid following. I don’t really find the Mac any easier to use than Windows (and there are some things I have to do that are far easier in Windows) but I won’t deny the Mac is a whole lot easier to program. Implementing “Hello, World!” in Think Pascal on a Mac is much easier than implementing it in C on Windows, and the Think Pascal version of “Hello, World!” makes more sense to me than even the Visual Basic version of “Hello, World!” on Windows. It’s more complicated than the main() { printf(“Hello, World!\n”); } you would use in DOS or Unix, but if you use all available tools and put the dialog boxes and buttons in resources it’s not much more complex, and programmers can rough in GUI elements and get on with the code while they shove the GUI elements off to artsy people, then it’s easy to use ResEdit or another resource editor to put the final GUI elements in.

And, bite my tongue, it would appear that programming the Mac was easier than programming the Amiga as well. I wrote plenty of command-line tools for the Amiga but I never mastered the GUI on that platform either.

I’m not saying anyone can program a Mac, but having attempted unsuccessfully to learn how to program effectively in Windows, I can say people who wouldn’t program in Windows can (and probably do, or at least did back in the day) program the Mac. My friends Tom Gatermann, Tim Coleman and I stand no chance whatsoever of being able to develop a decent Windows app, but we would have made a decent Mac development team with Tom and Tim handling the GUI and me writing code and all of us contributing ideas.

The next time I need a computer to do something for me that I can’t find a readily made program to do, I’m apt to load up Think Pascal on a Mac emulator and take a crack at it myself. My simple mind can handle programming that platform, and I suspect some of the innovative programs that appeared on the Mac first may have originally been written by people like me who have ideas but don’t think like a traditional programmer.

———-

From: Robert Bruce Thompson

“I can count on one hand the number of people I know who’ve ever built anything from discrete components, myself included…”

You’re hanging out with way too young a crowd. I’m only 47, and I used to build stuff from discrete components, including ham transmitters, receivers, amplifiers, and so on using *tubes*. You probably wouldn’t recognize a tube if it bit you, so I’ll explain that they were glass things kind of like light-bulbs. They were available in hundreds of types, which one used for various purposes–diodes, triodes, and so on. When they were running, they lit up with an orange light. Very pretty. And they did burn out frequently, just like light bulbs.

And I’ll be that if I were pressed hard enough, I could even remember the resistor color codes.

Geez.

———-

Too young and too lazy. But I do know what tubes are–they’re still used in audio equipment, for one, because they give a richer tone than transistors. And I remember when I was really young, there was a drugstore we used to go to that still had a tube tester in back.

But I remember the eyebrows I raised in high school when I was building something that needed a particular logical gate, and I couldn’t quickly locate the appropriate chip. I had a book that told how to build the gate using discrete components, so I did it. Actually I raised eyebrows twice–once for building the thing that required the chip in the first place, and once for making the chip stand-in.

“Apple lost,” Steve Jobs says

Apple obsession continues. See if you can guess who said the following:

The desktop computer industry is dead. Innovation has virtually ceased. Microsoft dominates with very little innovation. That’s over. Apple lost.

ArsTechnica readers may already know the answer. The answer (drum roll) is, none other than Steve Jobs, in an interview that appeared in the Feb. 1996 issue of Wired. Jobs was, at the time, CEO of NeXT, maker of overstyled and overpriced Unix boxes (though by then they were out of the hardware business and just selling NeXTStep, their Unix variant). Apple, of course, bought NeXT a few months after Jobs said this, and in a strange turn of events, Jobs ended up becoming Apple’s CEO.

It was an interesting interview. In it, Jobs said he didn’t think there was any way Microsoft could seize control of the Web (they’ve tried, and they’ve succeeded far more than Jobs probably anticipated–exhibit the large number of sites that only look right in Internet Explorer), but I found I agreed with a surprisingly large percentage of the things he said–particularly when he talked about things other than computers.

Here’s the link if you’re interested.

——-

From: Scott Vogt

Subject: Win2k On A Maxtor..

Dave,

I am running Windows 2000 with SP1 on a Maxtor 40gig 7200rpm drive with no troubles at all.

Great site, Glad to see you back!

Scott

———-

Thanks, both for the answer and the compliment.

Macintosh buying advice

What’s up with someone asking me for Mac advice? Yeah, Dan Bowman is in the process of selling his soul to (or at least buying a computer from) some egotist in Cupertino.

From: “Bowman, Dan”
Subject: Macs
To: Dave Farquhar
Dead serious request:

We keep getting hammered by graphic artists and printers; the Mac is ubiquitous in this arena locally. I’ve proposed we purchase a Mac for the GM to use (he’s a passable artist and knows what he wants and is not afraid to do it his way).

What configuration (for that matter, what machine) should I look to price this. We’re bidding another contract and the cost of the machine would likely be saved twice over by the artist fees and the GM’s time (time he could spend just doing it).

Any bets on programs?

Networking issues?

Thanks. Not my idea of fun; but in this case the right tool for the job if he can make it work.

Dan

I can’t recommend packages, they’ve gotta be what he’s comfortable working with. Rent some time at Kinko’s if need be to determine that. I definitely suggest avoiding Adobe PageMaker, because they’re abandoning the thing. Let me take back what I just said. If you can avoid using Adobe products, do it, because the company’s policies… Umm, just take every bad thing I’ve ever said about Microsoft, multiply it by about 10, and you’ve got Adobe. You may not be able to avoid Photoshop, but avoid the rest of it if you can. Macromedia and Quark, between the two of them, make just about everything you need.

If he wants to use a jillion fonts, you need a font management program, because the self-styled King of Desktop Publishing can’t juggle more than 254 fonts, I believe. I’m not certain on the number. Extensis Suitcase will do the job.

Get AlSoft Disk Warrior, Micromat Tech Tool Pro, and Symantec Norton Utilities. Once a month (or whenever you have problems), run Apple’s Disk First Aid (comes with the system), then Disk Warrior, Tech Tool Pro, and Norton Disk Doctor, in that order. Fix all problems. They’ll find a bunch. Also get Font Agent, from Insider Software, and run it once a month. It’ll want to delete any bitmapped fonts over 12 point. Don’t do that, but let it do everything else it wants. That helps a ton.

You’ll spend $500 on utilities software, but if you want your bases covered, you need them. Get them, use them, and you won’t have problems. Neglect to get them, and there’ll be no end to your problems, unless he never uses it.

Hardware: Get a 400-MHz G4, 256 MB RAM, IDE disk (poorly threaded, cooperative multitasking OSs don’t know what to do with SCSI). Frequently you can get a better price by getting the smallest disk possible, then buying a Maxtor drive at your local reseller. I know they were charging $150 a month ago to upgrade a 10-gig disk to a 20-gig disk, and you can buy a 20-gig disk for $150. Video, sound, etc aren’t options. If 450 is the slowest you can get, get that. MacOS doesn’t do a good enough job of keeping the CPU busy to warrant the extra bucks for a higher-end CPU. You’ll want the memory because you have to assign each app’s memory usage (it’s not dynamic like Windows), and it’s not a bad idea to assign 64 MB to a killer app. I also hear that G4s are totally unstable with less than 256 megs. I can’t confirm that. We’ve got G4s with more and we’ve got G4s with less, but I haven’t seen both in the hands of a power user yet.

Networking: NT’s Services for Macintosh are worthless. Don’t use NT for a print server for a Mac (it’ll ruin the prints), and don’t use it as a file server if you can help it (it’ll crash all the time). Linux isn’t much better, but it’s better. (It’ll just crash some of the time, but at least you can restart the daemons without rebooting.) I don’t know if MacOS 9 can talk to printers through TCP/IP or if they still have to use AppleTalk. AppleTalk is an ugly, nasty, very chatty protocol–it makes ugly, nasty NetBEUI look beautiful–but it’s what you get. Turn on AppleTalk on one of your network printers and print to it that way. One Mac and one printer won’t kill a small network, though a big enough network of Macs can keep a 10-megabit network totally overwhelmed with worthless chatter. Killer DTP apps don’t like their PostScript to be reinterpreted, and that’s one of the things NT Server does to mung up the jobs. So that’s the only workaround.

Multitasking: Don’t do it. When I use a Mac like an NT box, keeping several apps and several documents open at once, it’ll crash once a day, almost guaranteed. Don’t push your luck. It’s an Amiga wannabe, not a real Amiga. (Boy, I hope I’ve got my asbestos underwear handy.)

So, who makes the best Mac utility?

When it comes to Macintoshes, I feel like a catcher playing shortstop. Yes, a good athelete can play both positions, but very few can play both exceptionally well. The mindset’s all different. The ideal physique for each is all different.
I fix Macs for the good of my team. Period. Right now my job is to nurse along a dozen Macs for four months until the new fiscal year starts, then they can replace them. I think those machines have four months left in ’em. The bigger question is, do I have four months’ tolerance left in me? Hard to say.

But thanks to my pile of Macs on their last legs (these are 120 MHz machines with no L2 cache and a pathetic 10 MB/sec SCSI-II bus, and they’ve never had regular maintenance) I’ve gotten a lot of first-hand experience with Mac utilities suites.

I said in my book that Norton Utilities for Windows is, in most regards, the second-best utilities suite out there. Problem is, the other two big ones split first place, and the third-placer is usually so bad in that regard that you’d prefer not to use it. So Norton Utilities compromises its way to the top like a politician. The Mac Norton Utilities is the same way. There are two reasons to buy Norton Utilities for the Mac: Speed Disk and Norton Disk Doctor. Period. The rest of the stuff on the CD is completely, totally worthless. Eats up memory, slows the system down, causes crashes. Copy SD and NDD to a CD-R, then run over the original with your car. They’re that bad. But of course your end-users will install them since all software is good, right? You should install everything just in case you need it someday. Famous last words, I say…

But you need Speed Disk and Norton Disk Doctor desperately. Macs are as bad as Microsoft OSs about fragmentation, and they’re far worse about trashing their directory structures. Use a Mac for a week normally, and use a PC for a week, turning it off improperly on a whim (with automatic ScanDisk runs disabled), then at the end of a week, run a disk utility on each. The Mac will have more disk errors. Apple’s Disk First Aid is nice and non-invasive, but it catches a small percentage of the problems. NDD scoops up all of the routine stuff that Disk First Aid misses.

As for Speed Disk, it works. It’s not the least bit configurable, but it has enough sense to put frequently used stuff at the front of the disk and stuff you never touch at the end.

But if you need to do what Norton Utilities says it does, you really need Tech Tool Pro. Its defragmenter is at least the equal of Speed Disk, and its disk repair tools will fix problems that cause NDD to crash. Plus it has hardware diagnostics, and it’ll cleanly and safely zap the Mac’s PRAM (its equivalent to CMOS) and cleanly rebuild the Mac’s desktop (something that should be done once a month).

But the best disk repair tool of them all is Disk Warrior. Unlike the other suites, Disk Warrior just assumes there are problems with your disk. That’s a pretty safe assumption. It goes in, scavenges the disk, rebuilds the directory structure, and asks very, very few questions. Then it rewrites the directory in optimal fashion, increasing your Mac’s disk access by about the same factor as normal defragmentation would.

Oh yes, Disk Warrior comes with a system extension that checks all data before it gets written to the drive, to reduce errors. I really don’t like that idea. Worse speed, plus there’s always something that every extension conflicts with. That idea just makes me really nervous. Then again, since I regard the Mac’s directory structure as a time bomb, maybe I should use it. But I’m torn.

Which would I buy? If I could only have one of the three, I’d take Tech Tool Pro, because it’s the most complete of the three. I’d rather have both Tech Tool and Disk Warrior at my disposal. When a Mac goes bad, you can automatically run Disk Warrior, then rebuild the desktop with Tech Tool Pro before doing anything else, and about half the time one or the other of those (or the combination of them) will fix the problem. Or they’ll fix little problems before they become big ones.

Disk Warrior is positively outstanding for what it does, but it’s a one-dimensional player. For now, it does ship with a disk optimizer, but it’s limited to optimizing one of the Mac’s two common disk formats. At $79 vs. $99 for Tech Tool Pro, if you’ve only got a hundred bucks to spend, you’re better off with Tech Tool Pro.

As for Norton Utilities, I’ve got it, and it’s nice to have a third-string disk utility just in case the other two can’t fix it. Sometimes a Mac disk problem gets so hairy that you have to run multiple disk utilities in round-robin fashion to fix it. So run Disk Warrior, then Tech Tool Pro, then Norton Disk Doctor, then Apple Disk First Aid. Lather, rinse, and repeat until all four agree there are no disk errors.