12/21/2000

Athlon and Duron info. Should I buy an Athlon or a Duron? Tough question. Here’s the first good analysis I’ve seen. And Anand has a review of the SiS 730 integrated Athlon/Duron chipset. This won’t be the chipset you choose for your PC, but it might end up in your Aunt Millie’s.

As for motherboards, I’ve read of some people having problems with the Asus A7V; that it’s a decent board once you get it set up, but that it’s very cranky. The number of search engine hits I get with the phrase “Asus A7V” and words like “conflict” and “configuration” lends some circumstantial evidence to this. This troubles me; Asus boards are normally as solid as they come. Yet like I’ve said before, every time I’ve bought something other than Asus I’ve regretted it.

If you’re here looking for help on your Asus A7V, one of Storage Review’s moderators pointed me to the defunct A7V Troubleshooting Board  — I looked there and found no shortage of advice.

I guess if I were going to buy something now — and I admit I’m half-tempted to pick up a Duron and board as a cheap upgrade for my aging K6-2/350 — I’d probably go with a Gigabyte GA-7ZX or GA-7ZX1. The former includes a single ISA slot and built-in Creative audio; the latter includes neither of those. It costs about $35 less than the Asus A7V, and benchmarks nearly as fast. And, for the price difference you can afford to more than make up the performance difference through brute force by buying a faster CPU.

Gigabyte and AMD have a great working relationship lately (AMD often uses Gigabyte boards in their testbed and demo systems), so I have few qualms about going with them.

If anyone out there has some first-hand experience with different current Athlon/Duron boards, I’d love to hear about it — and I’m sure my readers would too. The mail link’s to the left.

We’ll revisit the topic of AMD tomorrow. There’s a lot more to this.

Cloning Mac Hard Drives. I may have covered this before but it bears repeating. From the Finder, drag and drop the old drive icon onto the new drive. It’ll copy all files, including hidden files, to a folder inside the new drive. Open that folder, drag the files out, and you’ve got a perfect clone. I do this very frequently with the Macs I fix at work.
You can also use Apple’s Disk Copy to copy one drive to another, but I find it easier to just use the Finder.

Disk Copy is also capable of saving hard disk images to files, a la Drive Image or Ghost for the PC. So cloning of Macs is possible, though you don’t get the cool multicast facilities of Drive Image or Ghost. But for one-off cloning, Disk Copy works great. You don’t get an exact binary copy of the disk, however, so you’ll still want to rebuild the directory with DiskWarrior and then defragment afterward for absolute best performance.

Presidential questions. Here we go again. I hinted during my previous arguments that I didn’t think Gore necessarily had won the popular vote. Absentee ballots weren’t in, and many of the states that had declared an electoral winner still hadn’t reported 100% of their precincts. It seemed a longshot, but so did a lot of things about this election.

Here’s a story about the wide and varied vote counts (all still putting Gore ahead nationally, but by a margin of as little as 330,000 votes). A coworker sent me the text to another story on the same site that had claimed Bush won by 2 million votes by one total. Unfortunately that story seems to have disappeared.

12/08/2000

~Mail follows today’s post~

It’s my birthday today. Birthdays cease being a big deal at some point; maybe after age 21 (though the big deal about my 21st wasn’t my age; I had a program for my C class due at midnight–all I remember is it involved linked lists, I hate linked lists, and the only good thing you could say about my program was it did compile–and I had copy editing and Irish history finals the next day). I’m going out tonight; last night I ate out and went to a concert, so I guess I’m treating myself right in spite of this not being a big deal.

I realized at one point a few weeks ago that I’d accomplished everything I’d set out to do by age 25, though not always in the way or quantity I’d hoped. That’s a nice realization to come to. Hopefully I’ll have similarly nice things to say about my second quarter-century.

I spent yesterday continuing my dual-boot experiments. For some reason, all of my motherboards want to think my >8.4-gig drives are half-gig jobs. I don’t get it. They’re all reasonably new; but even my year-old Abit BP6 is doing it. Normally not a problem, but some utilities software yells “out of bounds!” when it sees it. Using a UDMA-66 controller solves the problem (the BP6 has an HP366 controller built in, and I have Promise Ultra-66 I keep around), but that alerts me to another problem: XOSL doesn’t want to work with either controller for some reason. I e-mailed the author about that; I know I’m not the only one who uses these things because a lot of people buy the line that they need a UDMA-66 or UDMA-100 controller if they buy such a hard drive. I’m hoping he’s got a workaround of some sort.

I’m hoping I can find a solution before deadline; otherwise the 98/Me dual-boot article will have problems. I can give my editor a different article–there’s certainly a lot about Windows optimization I’ve left unsaid in the seven pages I’ve written so far–but seeing as he specifically asked me to investigate this, I’ll feel bad if I don’t deliver something, or if I deliver something with significant strings attached. Strings are good for guitars, not computers.

And a good question. Someone asked me today about something that I interpreted to be about the build-to-order strategy of PCs, a strategy which Dell and Gateway have ridden to such great success. I held them up as examples that work, and Apple as an example that right now isn’t. They have 11 weeks’ worth of unsold inventory built up at the moment and expect to bleed cash again this quarter. I guess the lesson there is that having huge databases to analyze can help, and computerization of the ordering process can help you buy exactly what you need right when you need it, but computers are no better than humans at predicting the future. I.T. won’t solve all of a business’ problems.

I have no idea if that’s what she was looking for in an answer, but I think that bit about IT not solving all problems is something not everyone gets yet. Computers solve a lot of problems. They also raise expectations greatly, and they (and we) don’t always live up to them.

~~~~~~~~~~

From: “John W. Braue, III” <braue@nospam.ratsnest.win.net>
Subject: For the Greater Good
In your daynotes for 6 December 2000, you quote Chris Miller as saying:  “Lawbreaking is relative. Your greatest presidents, Lincoln and Roosevelt, bent the rules for the greater good[…]”.

Didn’t Hitler and Stalin bend (and, indeed smash all to pieces) rules for the greater good?  What they proclaimed to be the greater good, of course, but it’s difficult to hold a reasoned discussion when the tanks are bearing down on one…

If the U.S. is a democracy, then let us acknowledge , as Mark Bridgers wrote, that the law is the Will of the People (with, granted, a certain time lag), and that opposing it by demonstrations and civil disobedience, even for a “greater good”, is itself Undemocratic and, _ipso facto_, evil (how many people would be willing, in this day and age. to deny the truth of _vox populi, vox Dei_?).  If it is a republic, then let us acknowledge that the law is indeed the law, and then breaking it and getting away with it does not justify either that action or future repetitions of it.  And, if the U.S. neither, let us can all of this election foolishness, and get down to the serious business of coups, revolutions, and civil wars to determine which _caudillo_, machine pistol in hand, is going to enforce his vision of the “greater good”.

John W. Braue, III

~~~~~

Well, I didn’t want to think of it in exactly those terms, but yes, they did.

The best time to make a decision is usually not when we’re caught up in the moment, as that leads to haste. I find myself agreeing with what you say and not really having anything to add.

~~~~~~~~~~

From: Gary Mugford
Subject: My script and Bless the Sound Card

Dave,

“The guys over at Junkbusters have a different solution. Make ’em sweat. They’ve even got a script with questions to ask. Visit them if you’re sick of the bother.
“Print it out, then keep it by the phone. And when you pick up the phone and get that tell-tale delay, followed by an unfamiliar voice who mispronounces your name, pounce. “Is this a telemarketing call?” (That question weeds out the other annoying phone calls, like Chrysler and MCI Worldcom calling up because of billing problems–sorry, you’ve gotta deal with those on your own.) If the answer is yes, then keep going. “Could you tell me your full name please? And a phone number, area code first?” And they’ve got 12 other questions, where those came from.”

For years, I’ve had the dickens to try and talk family members OUT of talking with telemarketers. My mom used to get involved in the talk, apologize profusely for declining and then be mad upon hanging up. I gave her a copy of my script to use:

“I’m sorry, I must interrupt you. We do not accept over-the-phone solicitation. Please feel free to mail us literature. Thank you very kindly for calling, good-bye.” THEN HANG UP. She wouldn’t use it.

This works pretty well, except for the ones that DID manage to get mom to send them something. Long after the parental units were retired and moved down to the Lake, I would still get phone calls at their number. I finally went to the trouble to record the little speechlet and put the file on the toolbar to press whenever I got ONE of THOSE phone calls. Now, it’s answer the phone, realize what’s happening, double-click and hold the phone DIRECTLY over my speaker and then hang-up.

GM

~~~~~

That approach works too. The Junkbusters solution is legally binding in the States, though I’m sure Canadian laws are different so up north your approach is probably at least as good.

Of course, if I were to take your approach and I happened to be listening to some doom-and-gloom Sisters of Mercy or Joy Division when the call happened, that’d make some nice background–serenade them with some music that’s definitely an acquired taste while they get my schpiel.

Another suggestion I’ve heard was to put them on hold for five minutes, then come back on and sing showtunes very badly until they hang up.
~~~~~~~~~~

From: “Michal Kaznowski” <michalkaznowski@nospam.yahoo.com>

Subject: Re[2]: DPMI error while zipping windows

Hello Dave,

Monday, December 04, 2000, 3:06:44 PM, you wrote:

DF> Try downloading this. Put the executable files from this archive into the same directory as your Info-Zip executables. Let me know ASAP if that doesn’t fix it. (This is as painful as some Linux programs’ installations!)

Done.  It will probably work when I have mastered the syntax.  At the moment after running the csdpmi executables I get

ZIP I/O error no such file or directory

with your command line. I have also tried making a windows.zip file for zip to write to.

(MSDOS mode cd to C:zip run cwsdpmi etc then your command line)

DF> Thanks for your encouraging words on Optimizing Windows.

You have a nice line in understatement.  My brother, who is computer tech support for the Norfolk and Norwich Hospital, tells me it is the best reference book he has ever used!

DF>  Unfortunately, O’Reilly cancelled the Linux book, so for now I’m just writing Windows optimization articles for Computer Shopper UK and taking a few months off from book writing while I decide what to do next.

There is an air of Linux taking off here in the UK and just recently {I have been looking for some time) two magazines have appeared catering for Linux use.

Linux Format (Future Publishing) www.linuxformat.co.uk

and Linux Magazine www.linux-magazine.co.uk

as well as the coverage in PCPlus also Future Publishing.

Maybe a series of articles in one or other could be the backbone of your Linux book on the back of the terrific reviews your Optimizing Windows had.

All the best,

Michal Kaznowski

(PS My kids thought the arch was terrific this summer – but I felt awful queasy up there).

~~~~~

What command line are you using? I seem to recall there was a typesetting error on one of the Zip commands in the book, though I can’t remember which one at this point.

I’m very much enjoying working with Computer Shopper UK, which I’ve hopefully expressed to the right people. I think they’ve done an outstanding job on my “Optimise Your PC” series, and I still sound American, even after translating my spellings to the British form. I’m trying to remember it so they’ll have to make fewer changes with the next one.

I’m not sure when I was last up in the Arch–it must have been 10 years ago. The slight sway in the wind always made me think the thing was about to topple over, though it’s survived minor earthquakes without damage so that’s ridiculous. I also remember it being pretty cramped.

Windows keyboard tricks

Those promised keyboard tricks. To get a Windows key, download the Kernel Toys. The keyboard applet, which works under 95 and 98, allows you to remap the caps lock, control, or alt keys to a Windows key. You can also remap the caps lock key to control or alt if you want. 

To assign My Computer to a hotkey, create a new shortcut with the following command line:
explorer.exe /n,/e,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Next, click on the shortcut key and hit a key (I suggest “m” or “c”) and that’ll give you instant two-pane access to My Computer any time you hit ctrl-alt and that key.

If you want single-pane access (I don’t think it’s as useful, but hey), use this command line instead:
explorer.exe /n,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

I finally fixed my firewall. I souped up the firewall a while back, then it never worked again. (I guess that’s the ultimate in security, eh? No one can hack in if you’re offline.) I forgot which ethernet card was outgoing and which was pointing inward, to my LAN. Finally, I tried stopping and restarting PMFirewall, which printed my network configuration. When both NICs were assigned to the address 192.168.0.1, I knew I was in trouble. With that tip-off, fixing it took just a matter of minutes.

Speaking of Linux, a speed tip. If you’re running Red Hat Linux as a NAT/IP masquerade gateway to share an Internet connection, do yourself a favor and install the BIND and caching-nameserver RPMs, then set your first DNS entry on your other PCs to your gateway’s IP address. This will make your proxy server look up DNS addresses for you and store them, reducing network traffic slightly but noticeably. The overhead is minimal; I’ve got Steve DeLassus running IP masquerade and caching nameserver on a 486SX/20 and it’s more than up to the task. For a small home network, a 386SX/16 has enough horsepower as long as it meets your distribution’s minimum memory requirements. I’d be more comfortable with a 50 MHz or faster 486 for a small office, but that’s as much due to expected age and reliability as it is to CPU requirements.

If you’re running a close derivative of Red Hat (Mandrake is certainly close enough, and I believe even Caldera and TurboLinux are as well), go ahead and download Red Hat’s caching nameserver RPM. It’s just a couple of short text files, but it’s easier to download and install an RPM than it is to key them in.

Apple. you call this tech support?

This is why I don’t like Apple. Yesterday I worked on a new dual-processor G4. It was intermittent. Didn’t want to drive the monitor half the time. After re-seating the video card and monitor cable a number of times and installing the hardware the computer needed, it started giving an error message at boot:

The built-in memory test has detected a problem with cache memory. Please contact a service technician for assistance.

So I called Apple. You get 90 days’ free support, period. (You also only get a one-year warranty unless you buy the AppleCare extended warranty, which I’m loathe to do. But I we’d probably better do it for this machine since it all but screams “lemon” every time we boot it.) So, hey, we can’t get anywhere with this, so let’s start burning up the support period.

The hold time was about 15 seconds. I mention this because that’s the only part of the call that impressed me and my mother taught me to say whatever nice things I could. I read the message to the tech, who then put me on hold, then came back in about a minute.

“That message is caused by a defective memory module. Replace the third-party memory module to solve the problem,” she said.

“But the computer is saying the problem is with cache, not with the memory,” I told her. (The cache for the G4 resides on a small board along with the CPU core, sort of like the first Pentium IIs, only it plugs into a socket.) She repeated the message to me. I was very impressed that she didn’t ask whether we’d added any memory to the system (of course we had–Apple factory memory would never go bad, I’m sure).

I seem to remember at least one of my English teachers telling me to write exactly what I mean. Obviously the Mac OS 9 programmers didn’t have any of my English teachers.

I took the memory out and cleaned it with a dollar bill, then put it back in. The system was fine for the rest of the afternoon after this, but I have my doubts about this system. If the problem returns, I’ll replace the memory. When that turns out not to be the problem, I don’t know what I’ll do.

We’ve been having some problems lately with Micron tech support as well, but there’s a big difference there. With Apple, if you don’t prove they caused the problem, well, it’s your problem, and they won’t lift a finger to help you resolve it. Compare this to Micron. My boss complained to Micron about the length of time it was taking to resolve a problem with one particular system. You know what the Micron tech said? “If this replacement CPU doesn’t work, I’ll replace the system.” We’re talking a two-year-old system here.

Now I know why Micron has more business customers than Apple does. When you pay a higher price for a computer (whether that’s buying a Micron Client Pro instead of a less-expensive, consumer-oriented Micron Millenia, or an Apple G4 instead of virtually any PC), you expect quick resolution to your computer problems because, well, your business doesn’t slow down just because your computer doesn’t work right. Micron seems to get this. Apple doesn’t.

And that probably has something to do with why our business now has 25 Micron PCs for every Mac. There was a time when that situation was reversed.

The joke was obvious, but… I still laughed really hard when I read today’s User Friendly. I guess I’m showing my age here by virtue of getting this.

Then again, three or four years back, a friend walked up to me on campus. “Hey, I finally got a 64!” I gave him a funny look. “Commodore 64s aren’t hard to find,” I told him. Then he laughed. “No, a Nintendo 64.”

It’s funny how nicknames recycle themselves.

For old times’ sake. I see that Amiga, Inc. must be trying to blow out the remaining inventory of Amiga 1200s, because they’re selling this machine at unprecedented low prices. I checked out www.softhut.com just out of curiosity, and I can get a bare A1200 for $170. A model with a 260MB hard drive is $200.  On an Amiga, a drive of that size is cavernous, though I’d probably eventually rip out the 260-megger and put in a more modern drive.

The A1200 was seriously underpowered when it came out, but at that price it’s awfully tempting. It’s less than used A1200s typically fetch on eBay, when they show up. I can add an accelerator card later after the PowerPC migration plan firms up a bit more. And Amigas tend to hold their value really well. And I always wanted one.

I’m so out of the loop on the Amiga it’s not even funny, but I found it funny that as I started reading so much started coming back. The main commands are stored in a directory called c, and it gets referred to as c: (many crucial Amiga directories are referenced this way, e.g. prefs: and devs: ). Hard drives used to be DH0:, DF1:, etc., though I understand they changed that later to HD0:, HD1:, etc.

So what was the Amiga like? I get that question a lot. Commodore released one model that did run System V Unix (the Amiga 3000UX), but for the most part it ran its own OS, known originally as AmigaDOS and later shortened to AmigaOS. Since the OS being developed internally at Amiga, Inc., and later at Commodore after they bought Amiga, wasn’t going to be ready on time for a late 1984/early 1985 release, Commodore contracted with British software developer Metacomco to develop an operating system. Metacomco delivered a Tripos-derived OS, written in MC68000 assembly language and BCPL, that offered fully pre-emptive multitasking, multithreading, and dynamic memory allocation (two things even Mac OS 9 doesn’t do yet–OS 9 does have multithreading but its multitasking is cooperative and its memory allocation static).

Commodore spent the better part of the next decade refining and improving the OS, gradually replacing most of the old BCPL code with C code, stomping bugs, adding features and improving its looks. The GUI never quite reached the level of sophistication that Mac OS had, though it certainly was usable and had a much lower memory footprint. The command line resembled Unix in some ways (using the / for subdirectories rather than ) and DOS in others (you used devicename:filename to address files). Some command names resembled DOS, others resembled Unix, and others neither (presumably they were Tripos-inspired, but I know next to nothing about Tripos).

Two modern features that AmigaOS never got were virtual memory and a disk cache. As rare as hard drives were for much of the Amiga’s existance this wasn’t missed too terribly, though Commodore announced in 1989 that AmigaDOS 1.4 (never released) would contain these features. AmigaDOS 1.4 gained improved looks, became AmigaOS 2.0, and was released without the cache or virtual memory (though both were available as third-party add-ons).

As for the hardware, the Amiga used the same MC68000 series of CPUs that the pre-PowerPC Macintoshes used. The Amiga also had a custom chipset that provided graphics and sound coprocessing, years before this became a standard feature on PCs. This was an advantage for years, but became a liability in the early 1990s. While Apple and the cloners were buying off-the-shelf chipsets, Commodore continued having to develop their own for the sake of backward compatibility. They revved the chipset once in 1991, but it was too little, too late. While the first iteration stayed state of the art for about five years, it only took a year or two for the second iteration to fall behind the times, and Motorola was having trouble keeping up with Intel in the MHz wars (funny how history repeats itself), so the Amigas of 1992 and 1993 looked underpowered. Bled to death by clueless marketing and clueless management (it’s arguable who was worse), Commodore bled engineers for years and fell further and further behind before finally running out of cash in 1993.

Though the Amiga is a noncontender today, its influence remains. It was the first commercially successful personal computer to feature color displays of more than 16 colors (it could display up to 4,096 at a time), stereo sound, and pre-emptive multitasking–all features most of us take for granted today. And even though it was widely dismissed as a gaming machine in its heyday, the best-selling titles for the computer that ultimately won the battle are, you guessed it, games.

Mac mice, PC data recovery

A two-button Mac mouse!? Frank McPherson asked what I would think of the multibutton/scroll wheel support in Mac OS X. Third-party multibutton mice have been supported via extensions for several years, but not officially from Ye Olde Apple. So what do I think? About stinkin’ time!

I use 3-button mice on my Windows boxes. The middle button double-clicks. Cuts down on clicks. I like it. On Unix, where the middle button brings up menus, I’d prefer a fourth button for double-clicking. Scroll wheels I don’t care about. The page up/down keys have performed that function just fine for 20 years. But some people like them; no harm done.

Data recovery. One of my users had a disk yesterday that wouldn’t read. Scandisk wouldn’t fix it. Norton Utilities 2000 wouldn’t fix it. I called in Norton Utilities 8. Its disktool.exe includes an option to revive a disk, essentially by doing a low-level format in place (presumably it reads the data, formats the cylinder, then writes the data back). That did the trick wonderfully. Run Disktool, then run NDD, then copy the contents to a fresh disk immediately.

So, if you ever run across an old DOS version of the Norton Utilities (version 7 or 8 certainly; earlier versions may be useful too), keep them! It’s something you’ll maybe need once a year. But when you need them, you need them badly. (Or someone you support does, since those in the know never rely on floppies for long-term data storage.) Recent versions of Norton Utilities for Win32 don’t include all of the old command-line utilities.

Hey, who was the genius who decided it was a good idea to cut, copy and paste files from the desktop? One of the nicest people in the world slipped up today copying a file. She hit cut instead of copy, then when she went to paste the file to the destination, she got an error message. Bye-bye file. Cut/copy-paste works fine for small files, but this was a 30-meg PowerPoint presentation. My colleague who supports her department couldn’t get the file back. I ride in on my white horse, Norton Utilities 4.0 for Windows in hand, and run Unerase off the CD. I get the file back, or so it appears. The undeleted copy won’t open. On a hunch, I hit paste. Another copy comes up. PowerPoint chokes on it too.

I tried everything. I ran PC Magazine’s Unfrag on it, which sometimes fixes problematic Office documents. No dice. I downloaded a PowerPoint recovery program. The document crashed the program. Thanks guys. Robyn never did you any harm. Now she’s out a presentation. Not that Microsoft cares, seeing as they already have the money.

I walked away wondering what would have happened if Amiga had won…

And there’s more to life than computers. There’s songwriting. After services tonight, the music director, John Scheusner, walks up and points at me. “Don’t go anywhere.” His girlfriend, Jennifer, in earshot, asks what we’re plotting. “I’m gonna play Dave the song that he wrote. You’re more than welcome to join us.”

Actually, it’s the song John and I wrote. I wrote some lyrics. John rearranged them a little (the way I wrote it, the song was too fast–imagine that, something too fast from someone used to writing punk rock) and wrote music.

I wrote the song hearing it sung like The Cars, (along the lines of “Magic,” if you’re familiar with their work) but what John wrote and played sounded more like Joe Jackson. Jazzy. I thought it was great. Jennfier thought it was really great.

Then John tells me they’re playing it Sunday. They’re what!? That will be WEIRD. And after the service will be weird too, seeing as everybody knows me and nobody’s ever seen me take a lick of interest in worship music before.

I like it now, but the lyrics are nothing special, so I don’t know if I’ll like it in six months. We’ll see. Some people will think it’s the greatest thing there ever was, just because two people they know wrote it. Others will call it a crappy worship song, but hopefully they’ll give us a little credit: At least we’re producing our own crappy worship songs instead of playing someone else’s.

Then John turns to me on the way out. “Hey, you’re a writer. How do we go about copyrighting this thing?” Besides writing “Copyright 2000 by John Scheusner and Dave Farquhar” on every copy, there’s this.  That’s what the Web is for, friends.

~~~~~~~~~~

Note: I post this letter without comment, since it’s a response to a letter I wrote. My stuff is in italics. I’m not sure I totally agree with all of it, but it certainly made me think a lot and I can’t fault the logic.

From: John Klos
Subject: Re: Your letter on Jerry Pournelle’s site

Hello, Dave,

I found both your writeup and this letter interesting. Especially interesting is both your reaction and Jerry’s reaction to my initial letter, which had little to do with my server.To restate my feelings, I was disturbed about Jerry’s column because it sounded so damned unscientific, and I felt that he had a responsibility to do better.
His conclusion sounded like something a salesperson would say, and in fact did sound like things I have heard from salespeople and self-promoted, wannabe geeks. I’ve heard all sorts of tales from people like this, such as the fact that computers get slower with age because the ram wears out…

Mentioning my Amiga was simply meant to point out that not only was I talking about something that bothered me, but I am running systems that “conventional wisdom” would say are underpowered. However, based upon what both you and Jerry have replied, I suppose I should’ve explained more about my Amiga.

I have about 50 users on erika (named after a dear friend). At any one moment, there are anywhere from half a dozen to a dozen people logged on. Now, I don’t claim to know what a Microsoft Terminal Server is, nor what it does, but it sounds something like an ’80s way of Microsoft subverting telnet.

My users actually telnet (technically, they all use ssh; telnet is off), they actually do tons of work is a shell, actually use pine for email and links (a lynx successor) for browsing. I have a number of developers who do most of their development work in any of a number of languages on erika (Perl, C, C++, PHP, Python, even Fortran!).

Most of my users can be separated into two groups: geeks and novices. Novices usually want simple email or want to host their domain with a minimum of fuss; most of them actually welcome the simplicity, speed, and consistency of pine as compared to slow and buggy webmail. Who has used webmail and never typed a long letter only to have an error destroy the entire thing?

The geeks are why sixgirls.org got started. We all
had a need for a place
to call home, as we all have experienced the nomadic life of being a geek
on the Internet with no server of our own. We drifted from ISP to ISP
looking for a place where our Unix was nice, where our sysadmins listened,
and where corporate interests weren’t going to yank stuff out from underneath us at any moment. Over the years, many ISPs have stopped
offering shell access and generally have gotten too big for the comfort of
geeks.

If Jerry were replying to this now, I could see him saying that shells are
old school and that erika is perhaps not much more than a home for  orphans and die-hard Unix fans. I used to think so, too, but the more novice users I add, the more convinced I am that people who have had no shell experience at all prefer the ease, speed, and consistency of the shell
over a web browser type interface. They’re amazed at the speed. They’re
surprised over the ability to instantly interact with others using talk and ytalk.

The point is that this is neither a stopgap nor a dead end; this IS the
future. I read your message to Jerry and it got me thinking a lot. An awful
lot. First on the wisdom of using something other than what Intel calls a server, then on the wisdom of using something other than a Wintel box as a server. I probably wouldn’t shout it from the mountaintops if I were doing it, but I’ve done it myself. As an Amiga veteran (I once published an article in Amazing Computing), I smiled when I saw what you were doing with your A4000. And some people no doubt are very interested in that. I wrote some about that on my Weblogs site (address below if you’re interested).

I am a Unix Systems Administrator, and I’ve set up lots of servers. I made
my decision to run everything on my Amiga based upon several
criteria:
One, x86 hardware is low quality. I stress test all of the servers I
build, and most x86 hardware is flawed in one way or another. Even if
those flaws are so insignificant that they never affect the running of a
server, I cannot help but wonder why my stress testing code will run just
fine on one computer for months and will run fine on another computer for
a week, but then dump a core or stop with an error. But this is quite
commonplace with x86 hardware.

For example, my girlfriend’s IBM brand FreeBSD computer can run the stress testing software indefinitely while she is running the GIMP, Netscape, and all sorts of other things. This is one of the few PCs that never has any problems with this stress testing software. But most of the other servers I set up, from PIIIs, dual processor PIIIs and dual Celerons, to Cyrix 6×86 and MII, end up having a problem with my software after anywhere from a few days to a few weeks. But they all have remarkable uptimes, and none crash for any reason other than human error (like kicking the cord).

However, my Amigas and my PowerMacs can run this software indefinitely.

So although I work with x86 extensively, it’s not my ideal choice. So what
else is there? There’s SPARC, MIPS, m68k, PowerPC, Alpha, StrongARM… pleanty of choices.

I have a few PowerMacs and a dual processor Amiga (68060 and 200 mhz PPC 604e); however, NetBSD for PowerMacs is not yet as mature as I need it to be. For one, there is no port of MIT pthreads, which is required for MySQL. Several of my users depend on MySQL, so until that is fixed, I can’t consider using my PowerMac. Also, because of the need to boot using Open Firmware, I cannot set up my PowerMac to boot unattended. Since my machine is colocated, I would have to be able to run down to the colocation facility if anything ever happened to it. That’s
fine if I’m in the city, but what happens when I’m travelling in Europe?

SPARC is nice, but expensive. If I could afford a nice UltraSPARC, I
would. However, this porject started as a way to have a home for
geeks; coming up with a minimum of $3000 for something I didn’t even plan to charge for wasn’t an option.

Alpha seems too much like PC hardware, but I’d certainly be willing to
give it a try should send me an old Alpha box.

With MIPS, again, the issue is price. I’ve always respected the quality of
SGI hardware, so I’d definitely set one up if one were donated.

StrongARM is decent. I even researched this a bit; I can get an ATX
motherboard from the UK with a 233 mhz StrongARM for about 310 quid. Not too bad.

But short of all of that, I had a nice Amiga 4000 with a 66 mhz 68060, 64
bit ram, and wide ultra SCSI on board. Now what impresses me about this
hardware is that I’ve run it constantly. When I went to New Orleans last
year during the summer, I left it in the apartment, running, while the
temperatures were up around 100 degrees. When I came back, it was
fine. Not a complaint.

That’s the way it’s always been with all of my Amigas. I plug them in,
they run; when I’m done, I turn off the monitor. So when I was considering
what computer to use as a server when I’d be paying for a burstable 10
Mbps colocation, I wanted something that would be stable and consistent.

 Hence Amiga.

One of my users, after reading your letter (and, I guess, Jerry’s),
thought that I should mention the load average of the server; I assume
this is because of the indirectly stated assumption that a 66 mhz 68060 is
just squeaking by. To clarify that, a 66 mhz 68060 is faster per mhz than
any Pentium by a measurable margin when using either optimised code (such as a distributed.net client) or straight compiled code (such as LAME). We get about 25,000 hits a day, for a total of about 200 megs a day, which accounts for one e

ighth of one percent of the CPU time. We run as a Stratum 2 time server for several hundred computers, we run POP and IMAP services, sendmail, and we’re the primary nameserver for perhaps a hundred machines. With a distributed.net client running, our load average hovers arount 1.18, which means that without the dnet client, we’d be idle most of the time.

If that weren’t good enough, NetBSD 1.5 (we’re running 1.4.2) has a much
improved virtual memory system (UVM), improvements and speedups in the TCP stack (and complete IPv6 support), scheduler enhancements, good softdep support in the filesystem (as if two 10k rpm 18 gig IBM wide ultra drives aren’t fast enough), and more.

In other words, things are only going to get better.

The other question you raise (sort of) is why Linux gets so much more
attention than the BSD flavors. I’m still trying to figure that one
out. Part of it is probably due to the existance of Red Hat and
Caldera and others. FreeBSD gets some promotion from Walnut
Creek/BSDi, but one only has to look at the success of Slackware to
see how that compares.

It’s all hype; people love buzz words, and so a cycle begins: people talk
about Linux, companies spring up to provide Linux stuff, and people hear
more and talk more about Linux.

It’s not a bad thing; anything that moves the mainstream away from
Microsoft is good. However, the current trend in Linux is not good. Red
Hat (the company), arguably the biggest force in popularising Linux in the
US, is becoming less and less like Linux and more and more like a software company. They’re releasing unstable release after unstable release with no apologies. Something I said a little while ago, and someone has been using as his quote in his email:
In the Linux world, all of the major distributions have become
companies. How much revenue would Red Hat generate if their product was flawless? How much support would they sell?

I summarise this by saying that it is no longer in their best interest to
have the best product. It appears to be sufficient to have a working
product they can use to “ride the wave” of popularity of Linux.

I used Linux for a long time, but ultimately I was always frustrated with
the (sometimes significant) differences between the distributions, and
sometimes the differences between versions of the same distribution. Why
was it that an Amiga running AmigaDOS was more consistent with Apache and Samba docs than any particular Linux? Where was Linux sticking all of
these config files, and why wasn’t there documentation saying where the
stuff was and why?

When I first started using BSD, I fell in love with its consistency, its
no bull attitude towards ports and packa
ges, and its professional and
clean feel. Needless to say, I don’t do much linux anymore.

It may well be due to the people involved. Linus Torvalds is a
likeable guy, a smart guy, easily identifiable by a largely computer
illiterate press as an anti-Gates. And he looks the part. Bob Young is
loud and flambouyant. Caldera’s the company that sued Microsoft and probably would have won if it hadn’t settled out of court. Richard
Stallman torques a lot of people off, but he’s very good at getting
himself heard, and the GPL seems designed at least in part to attract
attention. The BSD license is more free than the GPL, but while
freedom is one of Stallman’s goals, clearly getting attention for his
movement is another, and in that regard Stallman succeeds much more than the BSD camp. The BSD license may be too free for its own good.

Yes, there aren’t many “figureheads” for BSD; most of the ones I know of
don’t complain about Linux, whereas Linux people often do complain about the BSD folks (the major complaint being the license).

I know Jerry pays more attention to Linux than the BSDs partly because Linux has a bigger audience, but he certainly knows more about Linux than about any other Unix. Very soon after he launched his website, a couple of Linux gurus (most notably Moshe Bar, himself now a Byte columnist) started corresponding with him regularly, and they’ve made Linux a reasonably comfortable place for him, answering his questions and getting him up and going.

So then it should be their responsibility, as Linux advocates, to give
Jerry a slightly more complete story, in my opinion.

As for the rest of the press, most of them pay attention to Linux only because of the aforementioned talking heads. I have a degree in journalism from supposedly the best journalism school in the free world, which gives me some insight into how the press works (or doesn’t, as is usually the case). There are computer journalists who get it, but a g

ood deal of them are writing about computers for no reason in particular, and their previous job and their next job are likely to be writing about something else. In journalism, if three sources corroborate something, you can treat it as fact. Microsoft-sympathetic sources are rampant, wherever you are. The journalist probably has a Mac sympathy since there’s a decent chance that’s what he uses. If he uses a Windows PC, he may or may not realize it. He’s probably heard of Unix, but his chances of having three local Unix-sympathetic sources to use consistently are fairly slim. His chances of having three Unix-sympathetic sources who agree enough for him to treat what they say as fact (especially if one of his Microsofties contradicts it) are probably even more slim.

Which furthers my previous point: Jerry’s Linux friends should be more
complete in their advocacy.

Media often seems to desire to cater to the lowest common denominator, but it is refreshing to see what happens when it doesn’t; I can’t stand US
news on TV, but I’ll willingly watch BBC news, and will often learn more
about US news than if I had watched a US news program.

But I think that part of the problem, which is compounded by the above, is
that there are too many journaists that are writing about computers,
rather than computer people writing about computers.

After all, which is more presumptuous: a journaist who thinks that he/she
can enter the technical world of computing and write authoritatively about
it, or a computer person who attempts to be a part time journalist? I’d
prefer the latter, even if it doesn’t include all of the accoutrements
that come from the writings of a real journalist.

And looking at the movement as a whole, keep in mind that journalists look for stories. Let’s face it: A college student from Finland writing an operating system and giving it away and millions of people thinking it’s better than Windows is a big story. And let’s face it, RMS running
around looking like John the Baptist extolling the virtues of something called Free Software is another really good story, though he’d get a lot more press if he’d talk more candidly about the rest of his life, since that might be the hook that gets the story. Can’t you see this one now?

Yes. Both of those stories would seem much more interesting than, “It’s
been over three years and counting since a remote hole was found in
OpenBSD”, because it’s not sensationalistic, nor is it interesting, nor
can someone explain how you might end up running OpenBSD on your
appliances (well, you might, but the fact that it’s secure means that it’d
be as boring as telling you why your bathtub hasn’t collapsed yet).

Richard Stallman used to keep a bed in his office at the MIT Artificial Intelligence Lab.

He slept there. He used the shower down the hall. He didn’t have a home outside the office. It would have distracted him from his cause: Giving away software.

Stallman founded the Free Software movement in 1983. Regarded by many as the prophet of his movement (and looking the part, thanks to his long, unkempt hair and beard), Stallman is both one of its most highly regarded programmers and perhaps its most outspoken activist, speaking at various functions around the world.

Linux was newsworthy, thanks to the people behind it, way back in 1993 when hardly anyone was using it. Back then, they were the story. Now, they can still be the story, depending on the writer’s approach.

If there are similar stories in the BSD camp, I’m not aware of them. (I can tell you the philosophical differences between OpenBSD,  NetBSD and FreeBSD and I know a little about the BSD directory structure, but that’s where my knowledge runs up against its limits. I’d say I’m more familiar with BSD than the average computer user but that’s not saying much.) But I can tell you my editor would have absolutely eaten this up. After he or she confirmed it wasn’t fiction.

The history is a little dry; the only “juicy” part is where Berkeley had
to deal with a lawsuit from AT&T (or Bell Labs; I’m not doing my research
here) before they could make their source free.

Nowadays, people are interested because a major layer of Mac OS X is BSD, and is taken from the FreeBSD and NetBSD source trees. Therefore, millions of people who otherwise know nothing about BSD or its history will end up running it when Mac OS X Final comes out in January; lots of people already are running Mac OS X Beta, but chances are good that the people who bought the Beta know about the fact that it’s running on BSD.

And it’s certainly arguable that BSD is much more powerful and robust than Windows 2000. So there’s a story for you. Does that answer any of your question?

Yes; I hope I’ve clarified my issues, too.

Neat site! I’ll have to keep up on it.

Thanks,
John Klos

10/31/2000

I know there’s a word for this
I know ’cause we’ve all at some time said it
like when we were little kids
we’d fight each other ’til someone would give in
and you’d make him tell you ‘uncle’
  –Aimee Mann, “I Know There’s a Word” (Whatever, 1993)

Those lyrics came to mind the instant I read this.  My talkback is #22. There’s little point in reproducing any of it here.

I had a run-in with Mr. Darren (I recognize his style) the summer before last. Typical story Jerry tells. Jerry talks about Apple attack dogs who leap on anyone who dares write anything negative about Apple. Same principle here. Eventually you reach the point where you get sick of it and therefore don’t write anything at all about the subject to avoid the attack dogs.

The ignorance these people display about how computer journalism and the computer industry itself operate is unbelievable. Is it so unusual to learn something about a subject before opening your mouth about it?

This kind of crap makes me glad that now I’m not writing a book about Linux and Windows that might actually suggest that some people might have reason to run Windows. Oh, hell. I’ll go ahead and say it. Attention zealots: You know what software your beloved O’Reilly uses to write and edit its manuscripts? Microsoft Word!

On to a more pleasant subject. Good thing there’s a whole lot more to life than just computers. A friend called me up and told me to make sure I picked up the November issue of Vanity Fair because of a brief Aimee Mann/Michael Penn feature in it, plus Elvis Costello’s Top 500 recommended CDs. Good stuff. The issue kept me distracted from my article (due ASAP) for the better part of an hour.

Elvis’ best line: “As for the hit records of today, maybe some of them will sound just fantastic in 20 years’ time. It’s your life. So! No Marilyn, Korn, Puffy, Eddie Money–sorry, Kid Rock–Limp Bizkit, Ricky, Britney, Backstreet Boys, etc., etc.”

Here here!

Mail later. Probably. Assuming I bother.

It’s later. In March of 1999, Jerry was having some or another Linux problem, he got mail-bombed, and I sent him a letter, addressing him but also the Linux zealotry, asking, “What do you want? Do you want to be a punk computer like the Amiga, that no one uses? Repeat after me: Criticism of Linux is not a personal attack on me.” Jerry printed it, the result was a lot of mail.

One of them was this letter, to which I started writing a response but never got around to finishing because I couldn’t figure out what he wanted from me. This is, I’m pretty certain, the same “Darren” who wrote the “Jerry Pournelle finally admits he’s a Microsoft shill” headline at Linuxtoday.

I believe that what he and others like him are calling for is not journalism, nor is it editorial (which is where you call it like you see it–technically, that’s what Jerry Pournelle does. He’s a columnist, not a journalist) but rather, sheer advocacy.

I present it here. Opinions welcome–the mail link’s to the left, and you can leave comments by clicking on the skull icon at the end of the message (that’s what that’s for–I just haven’t gotten around to changing it).

From: Darren [SMTP:PCTech1018@netscape.net]Sent: Thursday, March 11, 1999 11:09 AM
Subject: RE: Your letter on Chaos Manor

Dave,

You asked the question “What do Linux Users want?”.

We want ACCURATE reporting.  This does not mean that we do not accept negative commentary.  This means that we are sick and tired of people with obvious Microsoft slants propagating unsubstantiated FUD while claiming journalistic objectivity.

Jerry Pournelle has a long history of being pro-microsoft.  His negative comments about Linux have a history of being based in ignorance. When he first started working with Linux and complaining about the lack of usability of Linux, he hadn’t even gotten a Linux system up and running. Why does he want Linux to continue to exist? So that Microsoft will continue to improve and dominate. These are demonstrable facts.

Journalists have continually spread anti-Linux FUD from Microsoft most often without any basis in fact. Until recently, the “difficult to use” argument was the predominant position. KDE, FVWM and other “easy-to-use” interfaces have existed for YEARS. This FUD has only recently been dying off after Microsoft’s demonstration of Caldera in court. There is the “lack of support” FUD argument. This FUD is finally dying off now that IBM, HP, Compaq, et al, have joined in the Linux “support” bandwagon. What is really ironic is that they are simply repackaging and using the same support mechanisms that have existed since the introduction of Linux 1.0 in 1994. Now we have a concentration of the “lack of applications” FUD. As more people become aware of HOW to use the sites such as www.linuxapps.com and www.metalab.unc.edu, this argument will also become apparent for the FUD that it is.

What do Linux users want? We want techno-journalists who do more than simply repeat the latest FUD out of Redmond.  They claim to have a certain level of expertise in the technical arena, but are most often only successful at demonstrating their own ignorance.

You obviously feel that we have been out of line in our treatment of certain journalists.  Would you care to give me an example of negative Linux reporting that was accurate from Jesse Berst, Jerry Pournelle or Ben Elgin? How about you give me any example at all from ANY journalist?

I am confident that I will be able to take any example you give me and show you how it is slanted, inaccurate, and not worthy of being published by professional journalists.

I do not intend this to be a flame mail, I just want to do my part to kill the bad journalism.

Regards,
Darren

I also have some (very lengthy) mail from someone who I believe is taking a much more constructive approach, or at least whose criticisms are much more valid. That should appear soon.

Scanner troubleshooting secrets

~Mail Follows Today’s Post~

Scanner wisdom. One of the things I did last week was set up a Umax scanner on a new iMac DV. The scanner worked perfectly on a Windows 98 PC, but when I connected it to the Mac it developed all sorts of strange diseases–not warming up properly, only scanning 1/3 of the page before timing out, making really loud noises, crashing the system…

I couldn’t resolve it, so I contacted Umax technical support. The tech I spoke with reminded me of a number of scanner tips I’d heard before but had forgotten, and besides that, I rarely if ever see them in the scanner manuals.

  • Plug scanners directly into the wall, not into a power strip. I’ve never heard a good explanation of why scanners are more sensitive to this than any other peripheral, but I’ve seen it work.
  • Plug USB scanners into a powered hub, or better yet, directly into the computer. USB scanners shouldn’t need power from the USB port, since they have their own power source, but this seems to make a difference.
  • Download the newest drivers, especially if you have a young operating system like MacOS 9, Mac OS X, Windows ME, or Windows 2000. It can take a little while for the scanner drivers to completely stabilize. Don’t install off the CD that came with the scanner, because it might be out of date. Get the newest stuff from the manufacturer’s Web site.
  • Uninstall old drivers before installing the new ones. This was the problem that bit me. The new driver didn’t totally overwrite the old one, creating a conflict that made the scanner go goofy.
  • Buy your scanner from a company that has a track record of providing updated drivers. Yes, that probably means you shouldn’t buy the $15 scanner with the $25 mail-in rebate. Yes, that means don’t buy HP. Up until a couple of years ago, getting NT drivers out of HP was like pulling teeth; now HP is charging for Windows 2000 drivers. HP also likes to abandon and then pick back up Mac support on a whim. Terrible track record.

Umax’s track record is pretty darn good. I’ve downloaded NT drivers for some really ancient Umax scanners after replacing old Macs with NT boxes. I once ran into a weird incompatibility with a seven-year-old Umax scanner–it was a B&W G3 with a wide SCSI controller (why, I don’t know) running Mac OS 8.6. Now that I think about it, I think the incompatibility was with the controller card. The scanner was discontinued years ago (before Mac OS 8 came out), so expecting them to provide a fix was way out of line.
m I’ve ever had with a Umax that they didn’t resolve, so when I spec out a scanner at work, Umax is always on my short list.

And here’s something I just found interesting. Maybe I’m the only one. But in reading the mail on Jerry Pournelle’s site, I found this. John Klos, administrator of sixgirls.org, takes Jerry to task for saying a Celeron can’t be a server. He cites his 66 MHz 68060-based Amiga 4000, which apparently acts as a mail and Web server, as proof. Though the most powerful m68k-based machine ever made, its processing power pales next to any Celeron (spare the original cacheless Celeron 266 and 300).

I think the point he was trying to make was that Unix plays by different rules. Indeed, when your server OS isn’t joined at the hip to a GUI and a Web browser and whatever else Gates tosses in on a whim, you can do a lot more work with less. His Amiga would make a lousy terminal server, but for serving up static Web pages and e-mail, there’s absolutely nothing wrong with it. Hosting a bunch of Web sites on an Amiga 4000 just because I could sounds very much like something I’d try myself if I had the hardware available or was willing to pay for the hardware necessary.

But I see Jerry Pournelle’s point as well.

It’s probably not the soundest business practice to advertise that you’re running off a several-year-old sub-100 MHz server, because that makes people nervous. Microsoft’s done a pretty admirable job of pounding everything slower than 350 MHz into obsolescence and the public knows this. And Intel and AMD have done a good job of marketing their high-end CPUs, resulting in people tending to lay blame at the CPU’s feet if it’s anything but a recent Pentium III. And, well, if you’re running off a shiny new IBM Netfinity, it’s very easy to get it fixed, or if need be, to replace it with another identical one. I know where to get true-blue Amiga parts and I even know which ones are interchangeable with PCs, but you might well be surprised to hear you can still get parts and that some are interchangeable.

But I’m sure there are far, far more sub-100 MHz machines out there in mission-critical situations functioning just fine than anyone wants to admit. I know we had many at my previous employer, and we have several at my current job, and it doesn’t make me nervous. The biggest difference is that most of them have nameplates like Sun and DEC and Compaq and IBM on them, rather than Commodore. But then again, Commodore’s reputation aside, it’s been years since I’ve seen a computer as well built as my Amiga 2000. (The last was the IBM PS/2 Model 80, which cost five times as much.) If I could get Amiga network cards for a decent price, you’d better believe I’d be running that computer as a firewall/proxy and other duties as assigned. I could probably get five years’ uninterrupted service from old Amy. Then I’d just replace her memory and get another ten.

The thing that makes me most nervous about John Klos’ situation is the business model’s dependence on him. I have faith in his A4000. I have faith in his ability to fix it if things do go wrong (anyone running NetBSD on an Amiga knows his machine better than the onsite techs who fix NetFinity servers know theirs). But there’s such thing as too much importance. I don’t let Apple certified techs come onsite to fix our Macs anymore at work, because I got tired of them breaking other things while they did warranty work and having to fix three things after they left. I know their machines better than they do. That makes me irreplaceable. A little job security is good. Too much job sercurity is bad, very bad. I’ll be doing the same thing next year and the year after that. It’s good to be able to say, “Call somebody else.” But that’s his problem, not his company’s or his customers’.

~~~~~~~~~~

From: rock4uandme
To: dfarq@swbell.net
Sent: Wednesday, October 25, 2000 1:22 PM
Subject: i`m having trouble with my canon bjc-210printer…

i`m having trouble with my canon bjc210 printer it`s printing every thing all red..Can you help???
 
 
thank you!!    john c
 
~~~~~~~~~

Printers aren’t my specialty and I don’t think I’ve ever seen a Canon BJC210, but if your printer has replacable printheads (some printers make the printhead part of the ink cartridge while others make them a separate component), try replacing them. That was the problem with the only Canon printer I’ve ever fixed.
 
You might try another color ink cartridge too; sometimes those go bad even if they still have ink in them.
 
If that fails, Canon does have a tech support page for that printer. I gave it a quick look and it’s a bit sketchy, but maybe it’ll help. If nothing else, there’s an e-mail address for questions. The page is at http://209.85.7.18/techsupport.php3?p=bjc210 (to save you from navigating the entire www.ccsi.canon.com page).
 

I hope that helps.

Dave
 
~~~~~~~~~~
 

From: Bruce Edwards
Subject: Crazy Win98 Networking Computer Problem

Dear Dave:

I am having a crazy computer problem which I am hoping you or your readers
may be able to give me a clue to.  I do have this posted on my daily
journal, but since I get very little traffic, I thought your readership or
yourself may be able to help.  Here’s the problem:

My wife’s computer suddenly and inexplicably became very slow when accessing
web sites and usually when accessing her e-mail.  We access the internet
normally through the LAN I installed at home.  This goes to a Wingate
machine which is connected to the aDSL line allowing shared access to the
internet.

My computer still sends and receives e-mail and accesses the web at full
speed.  Alice’s computer now appears to access the web text at about the
speed of a 9600 baud modem with graphics coming down even more slowly if at
all.  Also, her e-mail (Outlook Express) usually times out when going
through the LAN to the Wingate machine and then out over the internet. 
The LAN is working since she is making a connection out that way.

File transfer via the LAN between my PC and hers goes at full speed.
Something is causing her internet access to slow to a crawl while mine is
unaffected.  Also, it appears to be only part of her internet access.  I can
telnet out from her computer and connect to external servers very fast, as
fast as always.  I know telnet is just simple text, but the connection to
the server is very rapid too while connecting to a server via an http
browser is much much slower and then, once connected, the data flows so slow
it’s crazy.

Also, dial-up and connect to the internet via AOL and then use her mail
client and (external to AOL) browser works fine and is as speedy as you
would expect for a 56K modem.  What gives?

I tried reinstalling windows over the existing set-up (did not do anything)
and finally started over from “bare metal” as some like to say.  Reformat
the C drive.  Reinstall Windows 98, reinstall all the drivers, apps, tweak
the configuration, get it all working correctly.  Guess what?  Same slow
speed via the aDSL LAN connection even though my computer zips out via the
same connection.  Any suggestions?

Sincerely,

Bruce W. Edwards
e-mail:  bruce@BruceEdwards.com
Check www.BruceEdwards.com/journal  for my daily journal.

Bruce  🙂
Bruce W. Edwards
Sr. I.S. Auditor  
~~~~~~~~~~

From: Dave Farquhar [mailto:dfarq@swbell.net]Sent: Monday, October 23, 2000 6:16 PM
To: Edwards, Bruce
Cc: Diana Farquhar
Subject: Re: Crazy Win98 Networking Computer Problem

Hi Bruce,
 
The best thing I can think of is your MTU setting–have you run any of those MTU optimization programs? Those can have precisely the effect you describe at times. Try setting yor MTU back to 1500 and see what that does. While I wholeheartedly recommend them for dialup connections, MTU tweaking and any sort of LAN definitely don’t mix–to the point that I almost regret even mentioning the things in Optimizing Windows.
 
Short of that, I’d suggest ripping out all of your networking protocols and adapters from the Network control panel and add back in TCP/IP and only the other things you absolutely need. This’ll keep Windows from getting confused and trying to use the wrong transport, and eliminate the corrupted TCP/IP possibility. These are remote, but possible. Though your reinstall should have eliminated that possibility…
 
If it’s neither of those things, I’d start to suspect hardware. Make sure you don’t have an interrupt conflict (rare these days, but I just saw one a couple weeks ago so I don’t rule them out). Also try swapping in a different cable or NIC in your wife’s machine. Cables of course go bad more frequently than NICs, though I’ve had horrible luck with cheap NICs. At this point I won’t buy any ethernet NIC other than a Bay Netgear, 3Com or Intel.
 
I hope that helps. Let me know how it goes for you.

Dave 
~~~~~~~~~~
From: Bruce Edwards

Hi Dave:
 
Thank you for posting on your web site. I thought you would like an update.
 
I verified the MTU setting was still at 1500 (it was).  I have not used one of the optimizing programs on this PC.
 
I removed all the adapters from the PC via the control panel.  Rebooted and only added back TCP/IP on the Ethernet card. 
 
I double checked the interrupts in the control panel, there do not appear to be any conflicts and all devices report proper function.
 
I still need to 100% verify the wiring/hubs.  I think they are O.K. since that PC, using the same adapter, is able to file share with other PCs on the network.  That also implies that the adapter is O.K.
 
I will plug my PC into the same hub and port as my wife’s using the same cable to verify that the network infrastructure is O.K.
 
Then, I’ll removed the adapter and try a different one.
 
Hopefully one of these things will work.
 
Cheers,
 
Bruce
~~~~~~~~~~

This is a longshot, but… I’m wondering if maybe your DNS settings are off, or if your browser might be set to use a proxy server that doesn’t exist. That’s the only other thing I can think of that can cause sporadic slow access, unless the problem is your Web browser itself. Whichever browser you’re using, have you by any chance tried installing and testing the other one to see if it has the same problems?
 
In my experience, IE 5.5 isn’t exactly the greatest of performers, or when it does perform well, it seems to be by monopolizing CPU time. I’ve gotten much better results with IE 5.0. As for Netscape, I do wish they’d get it right again someday…
 
Thanks for the update. Hopefully we can find an answer.

Dave 
~~~~~~~~~~ 

10/28/2000

~Mail Follows Today’s Post~

Microsoft hacked! In case you haven’t heard, some hackers in St. Petersburg, Russia, had access to Windows source code for three months and the intrusion was only discovered this week. This could end up being a very good thing for you and me, believe it or not. (And this is even assuming the hackers didn’t fix any of the bugs they found.) As security consultant Andrew Antipass told Wired magazine, “It is interesting in a kind of cruel way that Microsoft has been eaten by the monsters it created.”

Microsoft has always been oblivious to security in their products. The only way they were going to learn was to be bitten, and hard. Now something has happened that calls their network infrastructure into question, the security of their products (which they’ve tried to present as more secure than Unix) into question, and even the integrity of the code they’ve produced in the last three months into question–Microsoft can say what they want about it being impossible to change the code. Of course they’re going to say that. Will the public believe it? Some will believe anything Microsoft says. Others wisely will believe exactly the opposite of anything Microsoft says. Still others (like me) will believe the worst no matter what Microsoft says.

If this incident doesn’t force Microsoft to start taking security seriously, nothing will.

The downside, however, is that if the hackers did indeed get Windows and/or Office source code, vulnerabilities become potentially easier to spot (not that access to Linux source code has significantly increased the number of vulnerabilities–remember, most hackers are script kiddies at best, writing in batch languages, and aren’t any more proficient in C++ than you or me).

All of this overshadowed Microsoft’s Internic entry being hacked (Apple’s entry got hacked too, though less creatively), which you can read about in The Register.

Enough of this computer junk. Let’s talk about music.

Review of U2’s All That You Can’t Leave Behind. If U2 were to call it quits right now and we had to pick out U2’s defining album, this would be it. That’s not to say it’s their best album–it’s awfully difficult to match the raw energy and wonder of Boy, the raw power of Achtung Baby, and if this one sells like The Joshua Tree, it’ll only be because there are so many fewer bands making good music in 2000 than there were in 1987.

That said, U2 seems to have finally answered the quintessential question of how to sound like U2 without sounding like selling out. For the past 13 years, every time U2 released an album, people expressed disappointment that it didn’t sound like Joshua Tree. But others would point to the inevitable single track on each album that did sound like Joshua Tree, then wave it in the band’s face: Can’t you do anything original?

You can divide U2’s music into roughly three phases: 1979-1983 (Boy through War), 1984-1989 (Unforgettable Fire through Rattle and Hum), and 1991-1997 (Achtung Baby through Pop). Although the band has reinvented itself with every album — sometimes for the better and sometimes not — they tend to hold on to their sound for a couple of albums at a time before they make major changes.

But the album title might as well be referring to those sonic changes: This album manages to incorporate all of those previous sounds while not sounding too much like any of the previous albums. You could take the defining song off any previous U2 album, drop it randomly into this album’s mix, and it would manage to fit.

The Edge’s jangly guitar? It’s there. Larry Mullen’s precise, militaristic drumming? It’s there. Adam Clayton’s low, thumping bass? It’s there. And of course, there’s also Bono’s wailing vocals. The experimentation? That’s there too, and that’s the bit that always scares people.

Make no bones about it: U2 is a rock band, and this is a rock record. But listen closely, and the experimental elements are still there. The synths are there. The sequencers are there. So is the drum machine. In fact, they lead off the album. But whereas in the past they have sometimes been the focus, now they complement the band’s sound rather than defining it.

They pull out a unexpected tricks as well. Listening to “When I Look At the World” for the first time, I half expected to hear Frankie Vallie filling in on lead vocals. Bono’s soaring falsetto doesn’t reach as high anymore as Vallie did in his prime, but the crafty veteran vocalist makes what he has left work. Meanwhile, in the tracks “New York” and “Grace,” Bono manages to out-Lou Reed the real article, though as a closer “Grace” is just not up there with U2’s great closing tracks of the past (War’s “40,” Achtung Baby’s “Love is Blindness,” Pop’s “Wake Up Dead Man,” or Joshua Tree’s “Mothers of the Disappeared”).

The biggest surprise is track 8. In that track, titled “In A Little While,” U2 finally succeeds in sounding soulful. So much of Rattle and Hum was contrived, a bunch of Irish guys in their late 20s trying to sound like B.B. King or Bob Dylan, and they clearly hadn’t lived long enough yet to pull it off. Now in their early 40s, they nail it.

The opening track and first single, “Beautiful Day,” is a good introduction to the album. That song’s sonic elements are for the most part present throughout. Like most U2 songs, to the casual listener it sounds good immediately. As one who picks apart lyrics, I initially didn’t like the song because it seemed too superficial. So what if it’s a beautiful day? Even a no-talent Kurt Cobain wannabe like Gavin Rossdale can say that! Only upon closer listening does the real meaning surface: the story of someone who has lost everything, yet never felt better. That sounds a lot like me. It probably sounds like you too, or someone you know.

So, how’s it stack up? Most people rank War and The Joshua Tree as U2’s finest albums. I buck convention and place Achtung Baby (their amazing 1991 comeback) and Boy (their 1980 international debut) ahead of those two. At the bottom, I’d rank October, Rattle and Hum, Zooropa, The Unforgettable Fire, and Pop. All That You Can’t Leave Behind definitely blows away the lesser five albums.

However, the album falls a bit flat after the first four delightful tracks. It picks it back up again for a track or two here and there, but the immediate greatness that grabbed you when you first heard The Joshua Tree or Achtung Baby just isn’t there throughout. And the superstrong emotions that drove and held together those great albums aren’t here.

This is probably the album of the year, and many bands go their entire careers without recording anything as good as U2’s worst. This effort borders on greatness, but just doesn’t quite manage to cross over.

Strong points: The first four tracks.
Weak points: “Peace on Earth;” “Wild Honey;” “In a Little While,” though good, doesn’t seem to fit (seems to be there only to settle a bet from 1989); “Grace” is a good track but ill-suited to end a U2 album.

And a survey. I’m considering a one-day-per-page format, like Frank McPherson and Chris Ward-Johnson use. When marking up by hand, a weekly format is much easier. When using Manilla, it really makes no difference.

If you don’t want to join the site in order to vote, feel free to just e-mail me. Members can vote here. (I do wish there was an option to open discussions and voting to non-members. I can see why some people would want to require membership, but that should be optional. So it goes.)

~~~~~~~~~~

From: “Dan Bowman” < DanBowman@att.net >
To: <dfarq@swbell.net>
Sent: Saturday, October 28, 2000 11:03 AM
Subject: Music reviews

Now I’m really glad I spent my discretionary funds yesterday! After reading your review (the class is watching a movie while I make copies),
I’m real tempted to pick up the album.
Then again, I have a Costco run set for after class…

Have a great weekend,

dan

~~~~~~~~~~

Don’t look too hard; it’s not available until Tuesday. I got a chance to hear it a few times and I got sick of seeing reviews from people who just listened to the 15-second clips available on the music store sites and said, “This is the best U2 album ever!” based on that, so I wrote it up. Good practice anyway. I think it’s been 3 1/2 years since I’ve written a music review of any significant length.

I wanted to strike a balance between “this may be the year’s best album” and “this is the best album ever!” because it’s not (it’s not even U2’s best).  Hopefully I did that. But I remember when I wrote up a review of Pearl Jam’s No Code in 1996, people said I was too harsh and shouldn’t have compared it to the past (though looking at that album’s longevity or lack thereof, I’m inclined to think I was right).

Reviews are tricky business but I want to stay in practice, so I may start doing a review a week just to get and stay sharp.

10/27/2000

Poor Windows 98 Network Performance. The MTU once again reared its ugly head at work yesterday. A 1.5 meg file was taking five minutes to copy. Forget about copying anything of respectable size–we’re talking about an all-day affair here. A perplexed colleague called me and asked why. Once again I suspected MTU tinkering. After setting the MTU back to the default of 1500 (the best value to use on a LAN), we were able to copy a 53-meg file in about 30 seconds, which was of course a tremendous improvement.

Once again, don’t run the MTU optimizers on computers that’ll be used on a LAN. The slight increase in modem speed isn’t worth crippling your network performance.

Basic Mac/PC networking. A friend passed along a question about how to build a network either a Mac or a PC could talk on. That can become a complex subject (I wonder if it’s worthy of a book?), but here are the basics.

If all you need is for the Macs to talk to Macs and PCs to talk to PCs, go to the local computer store and pick up a 100-megabit hub with enough ports to accomodate your machines, cables for your Macs, and network cards for your PCs if they don’t already have them. Get a quality hub and cards–the only really inexpensive brand I trust anymore is Netgear, and the general consensus is that 3Com and Intel are better still, though they’ll cost you more. I’ve been bitten by enough failures to decide that $15 network cards and $25 hubs just aren’t worth the trouble.

The Macs should just start talking via the AppleTalk protocol once you direct AppleTalk to the Ethernet port through the AppleTalk control panel. The PCs will need network card drivers installed, then they can use TCP/IP, NetBEUI or IPX/SPX to communicate. Best to use TCP/IP to limit the number of protocols on your network. Assign your PCs and Macs IP addresses in the 192.168.1.x range, with a subnet mask of 255.255.255.0. You don’t need to worry about the gateway or router settings unless you’ll be using the network to provide Internet access as well.

If you want Internet access, you can add an inexpensive cable/DSL router for about $150 that will serve your PCs and Macs without any problems. Assign your router to 192.168.1.1.

Most mid-range HP and Lexmark laser printers will accept a network card capable of talking to both PCs and Macs.

If you want to share files cross-platform, you’re looking at some bucks. You’ll want a Windows NT or 2000 server (AppleShare IP will talk to both, but it’s not as reliable as NT unfortunately), which will set you back about $1000 for the software. Alternatively, you could install DAVE ( www.thursby.com ), a product that makes Macs speak SMB over TCP/IP like Windows boxes will, so they can use Windows file shares and Windows-hosted printers.

I also see that Thursby is offering a program called MacSOHO, at $99, to accomodate PC/Mac networks. This isn’t suitable for large networks but for a small-scale LAN in the home, small business, school computer lab or church, it should suffice. You can download a trial version before you plunk down the cash.

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.