10/23/2000

Quittin’ time. That means a big bowl of chicken soup, reflection and mail. I usually make my own, but yesterday when I was getting sickness supplies I also picked up some of the instant powdered stuff. Faster that way.

A Mac tech at his limits. One of the organizations I support has asked permission to bring in an outside consultant because they’ve, in something close to their words, found a problem Dave can’t seem to solve. Never mind they didn’t ask me to fix it. And never mind they’re probably chasing the Bogeyman. In my estimation, 90% of Mac problems are either related to extensions conflicts or disk/filesystem errors. This machine loads maybe a dozen extensions, so that’s not an issue. But it’s a wannabe server, so of course it has filesystem errors constantly.

Not that that’s the issue. Find me a tech who isn’t almost always at his/her limits. If they aren’t, they’re not growing. This industry’s so constantly changing that it’s nearly impossible to stay away from the fringes of your knowledge.

And good night. My songwriting partner asked me to call him today if my voice was cooperating. It seems to be. I wrote no usable lyrics yesterday. But I can give him a leftover that I wrote back in 1997 or early 1998. It’s a total Seven Red Seven ripoff, but seeing as that band’s hardly a household name, I don’t think anyone will know, and the song I ripped off from was itself a ripoff of Depeche Mode’s Never Let Me Down Again. That’s all assuming we even use the thing, of course.

I’d best make that phone call… Mail’s all answered and sent, so it may make an appearance tonight. Otherwise, look for it tomorrow.

Strange Windows development. While working on one Win98 box, I decided to see if I could figure out once and for all the optimal disk cache settings for Win98 on another. The preliminary answer is very surprising. On this partcular machine at least, 3072 bytes (3 megs) seems optimal. With higher settings, you get slightly (and I mean slightly) higher benchmarks, insignificant enough to appear not worth investing even one more meg. The difference between 4 megs and anything higher is even less significant.

I’ll have to try this out with some other systems and other benchmarks, of course. I figured optimal wouldn’t be any higher than 8 megs, but I’m a bit surprised to see it at 3. Optimal may depend greatly on the drive involved, however. But I thought a good percentage of you would be interested in that.

Whatever the results, it appears the conventional wisdom of using 1/4 to 1/8 your system RAM for disk caching may be incorrect, at least on today’s high-memory PCs.

I see Naviscope mistakes my logo for an ad. I’ll have to rename the file to fix that. Naviscope is an ad/cookie blocking program that doubles as a DNS cache. A Linux box sitting on your network is more versatile and capable at both, but Naviscope is easier.

Want a real computer? Amiga has changed its mind yet again about the hardware aspect of its strategy. Will we be running on commodity hardware? At least not exclusively, if The Register has its story straight. Unfortunately, at this point I’m afraid anything they might do is likely to be too little, too late. It’s hard for any system, no matter how good it is, to survive seven years of stagnation. Sure, Amiga was 8-10 years ahead of its time. In 1985. By 1993, their lead was really dwindling. And of course, by 1995 the masses got preemptive multitasking and everything else they would have had if they’d bought an Amiga in the first place. And they didn’t seem to mind the wait. That last bit troubles me, but hey.

I’d still love to see them come back and mop up the floor using the rest of the industry (Microsoft and Apple need some humiliation), but I’m not going to hold my breath.

Outta here. I seem to have caught cold, so I’m going to cut myself short. Hopefully it’ll be a slow day at work so I don’t run myself into the ground.

Mac data recovery

Interesting day yesterday. I talked with my agent about where I’ll be writing next. There’s a UK magazine editor who is expressing interest in my work. We’ll see where that goes. My college degree is in journalism, and my field of emphasis was in magazine editing and publishing, so writing for computer magazines doesn’t seem foreign to me at all. I actually have been published before in computer magazines, but the last time was in 1997, and the time before that was in 1991. And I think the UK attitude towards technology is a bit more sensible than the US attitude–the UK seems more interested in making the most of what they have, as opposed to the US philosophy of replacing right away. (My English, Scottish and Irish ancestry must be showing through right about now.) So I like the idea of writing for magazines in the UK.
Due to my weak wrists, magazine writing is probably better suited for me at this point anyway.

Just don’t expect me to move to Manchester, England right away. (Of course I’d choose Manchester. That’s where the good music comes from. Joy Division, New Order, Joy Division, The Smiths, Joy Division, Crispy Ambulance, Joy Division…)

More emergency Mac procedures. It should be noted that what I stated about dual G4s not booting off the current utilities CDs also applies to other new models, such as the iMac DV and the G4 Cube (assuming you’re one of the 12 people who bought one).

Unfortunately, my tip for yesterday won’t help you if the machine is already in service and you can’t take it down for a reformat and reinstall. What to do then? Go ahead and copy (once again, DO NOT INSTALL) the contents of your utilities CDs to the hard drive. When you need to run them, boot off your MacOS 9 installation CD. Assuming your drive isn’t damaged to the point of being unreadable by the OS, you can then launch and run the full battery of utilities programs to get the machine back up and running.

If your filesystem is damaged to the point of being unreadable, your best resort is to take out the hard drive, put it in a Mac that is working, and run DiskWarrior, then if that doesn’t bring it back from the dead, run Tech Tool Pro’s volume recover. (Unfortunately, I’ve had to do this before–good thing for me that I’m not uncomfortable ripping into the innards of a computer and transplanting pieces into another.) Of course, this trick works better for G4 towers than it does for iMacs.

If it happens to a PowerBook, your best bet is to put the machine into SCSI dock mode (where the machine just emulates an external SCSI hard drive), connect it to a SCSI-equipped Mac, and run repair tools from there. This is also a great way to transport large numbers of files in a pinch. This is much nicer than taking out a PowerBook hard drive.

Ahem. I see Dan Bowman has introduced me as the Daynotes’ “Resident Expert on Macs.” I suppose I qualify as that. But I’m not a Mac zealot. There are things about every computer architecture that drive me up the wall. I’ve had fully multithreaded, pre-emptive multitasking systems since I bought an Amiga in 1991, and frankly ever since then I’ve found it very difficult to live without that. I’m always doing more than one thing at a time, so I don’t think it’s unreasonable at all to expect my computer to juggle a few things. (For a few blissful days in 1992 I had two Amigas, which let me really juggle a lot of things. These days I normally work with at least two networked PCs going, and sometimes as many as six.)

So while I’m no friend of Microsoft, I’ve probably said more critical things of Apple in these pages than I have of Microsoft.

The only computer that I was ever religious about was the Amiga, and to a certain degree I probably still am. That got me absolutely nowhere. Microsoft zealots drive me up the wall. Linux zealots drive me nuts. Anti-Linux zealots drive me even battier. I sympathize with OS/2 zealots, when I run across them, but I won’t join them. They’re machines. Tools. Do you expect me to sing the praises of Craftsman screwdrivers while I’m at it? They’re nice screwdrivers, but hey, I can get work done with a Stanley too…

So… Thanks for the kind introduction, Dan. I guess I just finished it. So if you’re here courtesy of Dan, welcome aboard. I hope you’re not too offended. (Don’t feel bad. I offend everyone at one point or another.)

Wednesday mailbag

Short stuff today. There’s mail on nostalgia and my infamous books today, so let’s get right to them.
———-

From: “Jeff Hurchalla”

Subject: optimizing windows – ramdisk

Hello Dave,

First I wanted to thank you for the great book on optimizing windows. I’ve read it all now and picked up quite a bit. I think the book nicely fills a niche for windows tweakers- I know I was looking for it for a while. One thing I noticed, if you do a second ed. you might include information on hard disk setups -how IDE and SCSI work, RAID, and what cable and role(master/slave) to use for that new second IDE hard drive.

One tip to add could be the format /z command when using fat32. This undocumented /z switch sets the cluster size in number of sectors.. so “format /z:64” would create 64 sectors/cluster or 32k clusters. I got this from prorec.com a while back. You might want to check out their site just for the music recording discussions, never mind that they do a great job describing how to optimize for digital audio(I think the advice is generally applicable for any computer).

I really want to ask you about a problem I’m having when I run windows95(osr2) from ramdisk. I have it working, mostly as described, but user.dat and system.dat are pesky. I had to put these both into the ramdisk hard drive directory(the one with himem.sys. setver.exe, etc) to get it to boot. Io.sys looks at the registry early in the boot process way before it gets to autoexec.bat(where the ramdisk is created). So it’s not trivial to find a way to create the ramdisk and get the registry in there, where I think it belongs, in time to satisfy io.sys. The solution to put the registry in the ramdisk directory isn’t very good because windows constantly updates the registry(and usually for no apparent reason). Do you have any ideas for how to get the registry in the ram early, or how to get windows to switch to using the registry in the ramdisk later on? It would also be ok, though maybe not as satisfying, to somehow set windows to stop automatically updating the registry just because it’s apparently noticed 15 seconds of time has passed. I also thought to use lilo (possibly modified) to do some work with a ramdisk and then load a bootsect.dos, but I don’t know enough to tell if it could work. I used to have linux set up, but everything’s standard right now.

I read in your views that the outlook for your linux/win2k book is not very good. That’s a shame. I’d really like to read it in the future. I hope something works out.

Take care, Jeff

———-

Well, first off, thanks for the compliments. It’s things like that that make the time and effort that go into writing a book worthwhile.

I had forgotten the FAT32 cluster trick; that is a good one but you might as well just use FAT16 if you’re going to make big clusters–unless the 2GB limit bites you. So, yes, I can see it being useful.

I believe I did talk about hard drive setups, but I may have neglected it. Rather than look it up, I’ll be lazy and just state it: Hard drives should always be masters. If you must put two drives on a channel, make the newer, more modern drive the master. RAID would certainly be a good topic, and one that’s sorely missed from the book. I think I did a decent job of predicting some of the up-and-coming stuff, but two things that I missed were IDE RAID and USB networking. They didn’t exist in the summer of 1999 when I wrote the bulk of the book, and I didn’t anticipate them.

The chances of a second edition appear to be pretty slim, unfortunately. I could write another book for another publisher, provided I’m very careful not to violate the copyright I sold to O’Reilly, but I would almost certainly burn some bridges by doing that and that’s not exactly something I want to do, whether I agree with how O’Reilly marketed the book or not. I’m almost hesitant to say anything about it or even mention that possibility.

As for the Linux/W2K book, it’s tough to say what to do with it. There are a lot of things I’d love to say about it, but again, I’d burn some bridges that I probably shouldn’t. A year ago when it looked like both W2K and Linux 2.4 would be released within six months, it looked like a blockbuster book. With 2.4 delayed and W2K failing to take over the world, it’s becoming a tough sell, and frankly I’m getting really sick of the topic. I also know I tend to take some unpopular stances on the issues involved, which probably doesn’t help. If I thought the book would cover the expenses I’d have to outlay to write it, I’d be much more inclined to do it. So far for me, writing for O’Reilly has proven to be a very expensive hobby. (And if anyone from O’Reilly reads my site and doesn’t like hearing me say that, tough.)

I’ll probably re-evaluate after the 2.4 kernel starts firming up some more, and once my wrists start looking like they’ll hold up or I get the hang of NaturallySpeaking. As for my next book, if there is another one, I don’t want it to involve Linux, and I want to write for a small indie publisher who only releases a half-dozen or so books a year.

As for the registry problem in your ramdisk, did you make the modifications to msdos.sys? Specifically, the line WinBootDir parameter must point to the ramdisk, while WinBootDir points to your directory containing the boot files.

The only other thing that I can think of that might cause those symptoms would be if when you installed Windows to the surrogate partition, Setup may have found your old registry and grabbed some data from it, forcing you to keep the registry on your HD rather than in ram.

I messed around with the ramdisk trick for an entire weekend (literally–I didn’t do anything else for two and a half days) getting it to work right, and for all I remember, I may have spent a few evenings preceeding that weekend working on it. I do know this: Microsoft never intended for anyone to do that, which of course just made me all the more determined to do it.

Let me know if that doesn’t fix the problem, because I’m really curious now what may have caused it. I’ll think on it some more.

———-

From: “Gary M. Berg”

Subject: Pascal on the Mac

You can always pick up Turbo Pascal 5.5 from Borland for free: http://community.borland.com/article/0,1410,20803,00.html

———-

Thanks. For that matter, Borland made older versions of Turbo C and Pascal available for DOS too, which isn’t bad for quick-and-dirty stuff. I found the older versions of Turbo Pascal for DOS produced smaller, tighter executables than the later versions (I mostly used version 7, back in 1992-93). And I believe at least one of their Windows C compilers is available for free now too.
———-

From: “Brent Dickerson”

Subject: voice recognition stuff

In case your interested in reading another’s short eval. The link may not work after today. brentfd

http://www.gazette.com/weekly/ibiz/biz9.html

———-

Thanks. That’s the first positive piece I’ve read on VoiceXPress, but their findings on ViaVoice are certainly consistent with my experience and with what I’ve read elsewhere–though ViaVoice improves considerably with a good mic. I still prefer NaturallySpeaking though, and I get better results than he did, but again, with a highly recommended mic and sound card combo.
———-

From: Robert Bruce Thompson

Subject: RE:

Hmm. When I was in high school, the first integrated circuits were still in R&D labs. That was 1971 or thereabouts.
———-

By the time I was in high school (1989-1993), “build your own computer” meant driving up to Gateway Electronics, buying a 386sx motherboard, I/O card and video card, some memory and a case, then assembling it all yourself. This was slightly more exotic than today when you can go down the street to get your parts.

I was an anomaly in that I owned an Amiga, whose system boards didn’t change much and were very well documented, so there were literally dozens of hacks available on BBSs to add features to them–most involved at least a little soldering and some involved discrete components. So that’s where most of my experience with discrete components comes from.

Most twentysomethings like me never had to build our own circuit boards and can’t imagine doing so. I was surprised to see modifications requiring soldering to start popping up on the hardware sites, because I know an awful lot of overclockers are my age and have never soldered delicate electronics before.

I dated a girl a few years ago who vaguely remembered her dad building a computer from a kit in the late 1970s. He’d tell her what component he needed, and she’d find it from the pile and give it to him. With me being a computer professional, she was pretty proud of that. She knew not many people in our generation had even that experience.

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.

Amiga influence on Linux

Amiga lives! (Well, sort of). When it comes to GUIs, I’m a minimalist. Call me spoiled; the first GUI I used was on a 7.16-MHz machine with a meg of RAM, and it was fast. Sure, it wasn’t long before software bloat set in and I had to add another meg, and then another, but at a time when Windows 3.1 was running like crap on 4 megs and only decently on 8, I had 6 megs on my Amiga and didn’t really know what to do with all of it. So I left 3 megs available to the system, ran a 3-meg ramdisk, and all was well with the world. Until Commodore’s raw dead fish marketing caught up with it and pulled it and the company under.
Under Linux, KDE and GNOME look good, but they run slower than Windows on my PCs. And I like the idea of my P120 being a usable box. I can do that under Linux, but not with KDE as my Window manager. There’s IceWM, which is nice and lean, and there’s xFCE, which resembles HP’s implementation of CDE (and also resembles OS/2, bringing back fond memories for me–why is it everything I like is marketed as raw dead fish?), and now, two years after its release, I’ve discovered AmiWM.

AmiWM (http://www.lysator.liu.se/~marcus/amiwm.html) is a clone of the Amiga Workbench, the Amiga’s minimalist GUI. It’s small and fast and reminds me of the good old days when computers were computers, and didn’t try to be CD players, dishwashers, toaster ovens, televisions, and the like. For an aging PC (or for a new one that you want to run as quickly as possible–hey, you must be mildly interested in that, seeing as you’re reading my site and that’s my specialty), this one’s hard to beat.

Sound card and hard drive troubleshooting

Sound card woes. Gatermann recently ran into some problems with sound cards forcing his Internet connection to drop. It had literally been six years since I’ve seen a problem like that before, but he kept running into it. Finally, it dawned on me: Try changing slots to force it to use a different interrupt. Therein was the silver bullet. The problem didn’t go away completely, but the culprit arose: the Sound Blaster 16 emulation. So I had him go into Device Manager and put the SB16 emulation on a different interrupt, and the problem went away.
It’s been forever since I’ve seen an honest-to-goodness interrupt conflict. This particular PC has every expansion slot filled with something or other, which is why he ran up against it. Keep that in mind: Just because we have PCI and plug and play these days, doesn’t mean you won’t ever see an interrupt conflict. On a well-expanded system, this ancient problem can occasionally rear its ugly head (while Microchannel required their cards to be capable of interrupt sharing; PCI only *recommends* it–so not every PCI device can share an interrupt, particularly if an ISA device has grabbed it. Alas, Microchannel fell victim to IBM’s greedy overly restrictive licensing terms and raw-dead-fish marketing, so as a result we have cheap PCs today but more headaches than we necessarily need. Speaking of raw-dead-fish marketing, I could mention that the Amiga’s Zorro bus had true plug and play and hundreds of interrupts from Day One in 1985, but nobody wants to hear that. Oops, I said it anyway.)

This problem used to happen all the time when people would put their modems on COM4 and a serial mouse on COM2 (or COM1 and 3). Since those ports by default shared interrupts with one another, you got goofy symptoms like your Internet connection dropping whenever you moved the mouse. People don’t configure their COM ports that way anymore, which is what’s made that problem so rare.

I think I finally got that G4 deployed. Wednesday it decided it didn’t want to shut down, and I had to reinstall the OS to fix it. Then on Thursday, it decided it didn’t want to recognize the mouse button anymore. I still don’t know what exactly I did to fix that–I booted off a spare MacOS 9 partition, ran a battery of disk repair tools and a defragmenter, and the problem went away. So while Mac users can snicker about interrupt problems, their machines aren’t exactly immune to weird problems either.

——-

From: “Gialluca, Tony”

question: RE Optimizing Windows and Temp files

Hi Mr. Farquhar,

In you book on page 112 you discuss placing temp files on a ramdisk. On this page you show an example where:

Set temp=ram disk letter:\temp Set tmp=ram disk letter:\temp

Shouldn’t you also include changing

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Volum eCaches\Temporary files\folder] to “ram disk letter:\temp” also ??

Per the description

([HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\explorer\Volu meCaches\Temporary files\description]) says: “Programs sometimes store temporary information in a TEMP folder. Before a program closes, it usually deletes this information.\r\n\r\nYou can safely delete temporary files that have not been modified in over a week.” The only potential pitfall that I can think of is if windows or programs (say during installations) need this area to remain persistant through reboots, even though the files may be of
a temporary nature…

Your thoughts would be appreciated …

Respectfully,

Tony

———-

To be perfectly honest, I didn’t know that registry key existed (nor did the book’s technical reviewers, evidently). That registry key, too, should be changed, yes. Thanks!

You are correct that if a program does a hard reboot (rather than just exiting to real mode and reloading Windows), you’ll lose the contents of the ramdisk and thus the temp folder. Fortunately, most programs seem to use the temp directory the way they’re supposed to–for temporary, fleeting things. Now if they’d just learn to clean up after themselves…

Of course, this also applies to my advice on creating a temp partition, on page 62.

Thanks much; this is very good information.

———-

From: “Gary M. Berg”

Subject: Maxtor hard drives

Since you’ve been talking about WD and Maxtor hard drives…

I heard rumors just after Win2K SP1 came out that the service pack had problems with machines with Maxtor hard drives. I’ve not been able to find much of anything else on this. What have you heard?

———-

That’s a new one to me. Maybe another reader has heard something, but it sure seems odd. I can’t imagine Microsoft didn’t test SP1 on the major drive manufactuers’ drives (Fujitsu, IBM, Maxtor, Quantum, Samsung, Seagate, and Western Digital), and with Maxtor being one of the Big Two in retail….

Once I get my current big project off my back this weekend, I’m half-tempted to try it just to see. Unless someone already has…

Upgrades, remedies and a diagnosis

(originally from 5/21/00)
Upgrade Central. I got a steal of a deal on a pair of Antec 300W power supplies, so I did the power supply shuffle this weekend. While I was at it, I also threw in bunches of memory while I had the systems open. My dual 366 runs a lot better now with 320 MB of RAM in it. Never skimp on RAM, especially on dual-CPU systems.

I can’t resist. Microsoft Remedies. Someone sent in some complaints about Outlook, viruses and scripting, which I’d love to post but it takes a lot of effort to do that right now. Suffice it to say, Gary, I think you’re right, but I don’t think Microsoft gives a rip about anything but driving competition, real or imagined, out of business using any means possible. Security and quality be damned. (Notice they’re not exactly falling all over themselves to remedy the performance problems Internet Explorer causes, even though it wouldn’t be terribly difficult to do.)

So, proposed remedies… Put Mehdi Ali and Irving Gould in charge. Who? They’re two guys who knew how to chase short-term profits without stifling innovation. You’re still asking who? Ask any Amiga fan who they are, then duck.

And it’s almost official. I’ve been diagnosed (at least, I have a preliminary diagnosis) with the dreaded carpal tunnel syndrome. I don’t know if it’s a matter of psychology, having been hit too many places with reflex hammers, or the Vitamin B6 shocking my system, but whatever it was, I was a mess Saturday.

Expect updates to be brief and less frequent than before for a while. I’ll do my best to answer my mail, but I’m still trying to devise a plan. (I do feel a bit better today, at least I’m using my shift key, unlike yesterday.) And I wrote this much with the two-finger method, rather than touch-typing–I’m a very fast touch-typist when healthy.

Putting the squeeze play on Linux

Want the smallest, fastest OS possible? I stumbled across several Linux assembly language projects today. There’s asmutils, which attempts to give full functionality of various common Linux tools but in smaller, faster assembly language packages, and there’s Tiny ELF, a page of assembly language utilities that are somewhat useful, but the intent appears to be more to just see how small of a program he can write.
If you want to see just how far the insanity can go, check out this, which is about the craziest thing I’ve seen in a long time. I remember that mentality. It was the mentality of an Atari 2600 programmer. As one who replaced most of the standard Amiga commands with smaller, faster versions, I can appreciate these two projects. Maybe I’m just an old-timer or a sicko, but for some reason I get a kick out of seeing that my text editor uses a scant 68K of memory (with a large file open). The scary thing is, the command window that allows you to run all these tiny programs will itself occupy a meg or more. Sigh. Progress.

LoveLetter is just a symptom of worse things to come

The virus parade continues. I saw some really disturbing speculation on BetaNews today. Of course there’s the news of 10 variants on VBS.LoveLetter. Worse yet, there’s speculation of what kind of havoc a trojan horse jumping on ICQ could cause. I don’t know if ICQ is scriptable, but what if someone implemented a program that contacts the ICQ network (possibly by borrowing code from one of the open-source Linux ICQ clones), then sends itself to all of your ICQ contacts? A lot of ICQ users indiscriminately accept and run any file sent to them. Just another conduit. Hopefully it’s beyond most virus writers. (Most virus writers are on my programming level. If I download a real program, you know, like an open-source Linux utility, I’m pretty clueless about four lines in. I can follow virus code, because it’s simple.)
Microsoft really needs to start giving a rip about security. I know it’s fashionable to bash MS, but I was bashing them back in 1990 and never really stopped, so hear me out. There’s just far too much exploitable scripting capability in contemporary MS products. Worse yet, these languages don’t abort on errors anymore, which creates a breeding ground for new viruses. When two viruses merge, the code still executes. The gibberish that in days of old would have stopped the program today gets passed over and the program keeps running. I can see popping up a dialog box that says “Run-time error,” with two buttons (continue and abort). I longed for that years ago when I still aspired to be a programmer. But no, that’s not dummy-proof enough.

Well, guess what? Now our computers are so dummy-proof that they’re time bombs. Thanks Bill. Now we still can’t get any work done. Used to be because it was too hard to figure out. Now it’s because our computers keep getting their system files wiped out.

I saw an Amiga 1200 on eBay for about $75 the other day. Time to throw these MS-infected PCs out the door of a low-flying plane over the Redmond campus, (yes, I know there’s a perfectly good possibility they’ll hit someone) and replace them with real computers that are reliable and not afraid of asking the user a question.

But I know good and well I’ll probably just abandon Windows as a primary OS and just run it in VMWare sessions. At least then, when Windows decides to take a dump all over itself (or let some virus do it), the mess is confined. Not that I have a virus problem because I open things in Notepad before doing anything with them, but we’ve already been through that.

Another observation. This one’s shorter, I promise. Are we so love-starved that we’ll open some attachment called “love letter” without even looking at it? That all of our better judgment gets suspended until it’s too late? (I ask as U2’s “Who’s Gonna Ride Your Wild Horses,” which might as well be about my last serious relationship, comes on over my.mp3.com–very funny.)

Hey, there’s a song in there somewhere. “Love by Outlook.” Hmm. Time to go give the synth a workout.

Oh yeah. That question I asked. I don’t have a good answer for it. An evangelist in Columbia thought he had the ultimate answer. Didn’t work. So I ended up moving to St. Louis to get a new start. New old familiar territory, got a new job, signed a book deal, and life was good again. I doubt that’ll work for everyone else. But it’s a lot better than an e-mail attachment.

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.)