04/24/2001

A sense of wonder. It must have been almost 20 years ago, I read a short story in a magazine involving a wondrous new tool. I don’t exactly remember the plot line, but it was something similar to this: a preteen boy comes into a sum of money under questionable circumstances. He’s uncomfortable going to his parents about it, or even his peers. Not knowing where else to go, he turns on his dad’s computer and types his story into it–whether this was a built-in Basic language interpreter like a Commodore or Atari, or a command line like CP/M or MS-DOS, it didn’t say. At the end of the story he hits Return, or Enter, or whatever that key’s supposed to be called, and the computer responds with one sentence:

Sorry, can’t compute.

That line gave the story its title.

I don’t know why I remember that story, except maybe for the technical inaccuracy. At any rate, I seem to recall he left without turning the computer off, so his dad came home, noticed the computer was on, read what was on screen, and confronted him. And that was pretty much the end, at least how I remember it.

Last night I was making up a batch of barley and mushroom soup from a recipe I found over the weekend. I know when I’m out of my element, and trying new recipes without any help at all is among them. The recipe called for 4 tablespoons of dry sherry. Now, I’m not a wine drinker, unless drinking wine twice a year counts. I was pretty sure that sherry is a type of wine. But white wine? Red wine? I didn’t know. As I was picking up the other ingredients I needed, I went to the wine and liquor section of the local grocery store and wandered around a while. I couldn’t find any sherry.

So I went home. I figured I was probably in the minority as far as not knowing anything about dry sherry, but I also figured I probably wasn’t the first one to have questions about it. I fired up a Web browser, went to Google, and typed a question: What is dry sherry? I was able to infer very quickly from the site hits that, indeed, dry sherry is a wine. But I couldn’t find any. So I typed in another search phrase: “dry sherry substitute.” That put me in business. A lot of people have asked that question. One of the first documents hit offered several suggestions, marsala among them. I have a little bottle of marsala in one of my kitchen cabinets. So I made the soup, and it wasn’t bad.

The moral of that short story remains unchanged: A computer still can’t answer questions on its own, particularly questions of ethics–the experiments of www.mindpixel.com notwithstanding. What Mindpixel is doing is storing and cross-referencing the answers to millions of simple questions in hopes of one day being able to answer complex ones. (The results of that are fairly impressive–last night I asked it several simple questions like, “Was Ronald Reagan president of the United States in 1981?” and “Is Joe Jackson the name of both a famous musician and a famous baseball player?” and it answered all of them correctly.) But what Mindpixel, or for that matter, any good search engine can do effectively is gather and retain information. And that in itself is extremely useful, and the idea of search engines indexing a global database and answering simple–and not-so-simple–questions was unthinkable to most people just 20 years ago.

And I found a sale. I’m suddenly in need of a large number of network cards, as regular readers know. Just out of curiosity, I checked CompUSA’s pricing on Bay Netgear FA311 NICs, and–drum roll–they’re $14.99 with a $5 mail-in rebate. That’s a steal. It’s not quite as striking as the deal I found on D-Link cards at Circuit City back in January, but I like the Netgear–or at least its predecessor, the FA310TX–better anyway.

04/22/2001

The times they are a-changin’. I made the pilgrimage to north St. Louis, to visit my church’s sister congregation, to see their new PCs. I spotted some Compaq Deskpro EXs at Insight for an insanely low price, and I wanted a respectable name brand, so that was what I had them order. I set one up and let it run, and was surprised to see it came up with a standard AMI BIOS. No more Compaq disk partition-based BIOS? Nope. Not even a Compaq logo. Just an AMI logo, like a clone. The case was a standard microATX case with a Compaq case badge on it. I popped open the case. I couldn’t tell for certain if it was an Intel-made board or not (the AMI BIOS suggests yes) but it’s a standard microATX board. No weird Compaq drive rails either. Seagate hard drive. The CD-ROM firmware says Compaq. But it’s a standard ATAPI CD-ROM. It looks like a Hitachi, but I could be mistaken.

This is good. While the quality may or may not be up to the standards of an oldschool Compaq, in the event of a failure after the warranty period, off-the-shelf parts will work to keep these things running. I can get microATX power supplies and motherboards.

Oh, how do they run? Well, after I cleaned up the root and Windows directories, put in my usual msdos.sys parameters, and replaced emm386.exe with umbpci.sys–they paid for that shadow RAM, so they might as well use it as RAM–the system boots in 20 seconds. That’ll slow down after adding the network card and installing more software, of course, but at least we’re starting out really strong.

I thought I read in the system specs that they’d have built-in Ethernet, but I may be mistaken. That’s fairly easy to remedy. I can pick up a 5-pack of Netgear FA-311s at Mwave for about $70. Two of those will put us in business. I’m disappointed that the FA-310TX, an old favorite of mine, seems to be discontinued; hopefully the 311 uses the same or a similar chipset. In a lab situation I’d prefer Intel or 3Com cards, but the Netgears sell for much less, and I have lots of experience with Netgears in Linux. I’ve occasionally had problems with Intels and 3Coms in Linux, and since there’ll be one or possibly two Linux servers in the lab, and I’d rather start out with standardized parts all around, I’ll give Netgear the nod.

Bloatbusters. I believe I mentioned this site before on my old site, but maybe not. These guys look at utilities, tell you what’s wrong with them, and sometimes provide a tightly-coded alternative. For instance, here’s a Windows CD player. It’s 3K in size. Personally, I prefer the play button on the front of my CD-ROM drives, but not every CD-ROM drive has one.

I can’t stand their site navigation and layout, but their essays are often entertaining to read.

Along the same lines, there’s Radsoft , who plays host to Bloatbusters. Radsoft’s product is Extreme Power Tools, a $47 collection of over 100 tightly written utilities, including a 25K file manager that claims to pack in more features than any of Microsoft’s file managers. Evidently they used to provide a demo download, but the only demo I can find now contains just their task management tools, which are interesting but certainly not the most generally useful.

Troubleshooting Mac extensions

Troubleshooting Macintosh extensions. An extensions conflict is where you lose your innocence with fixing a Mac. Not all extensions and control panels get along, and certain combinations can have disastrous results.

Here’s my method. Create a folder on the desktop. Drag exactly half the extensions out of System Folder:Extensions and drop them in the folder. Select all the extensions in that new folder and give them a label, so they stand out (it makes them a different color). Now reboot and see if the problem goes away. If it doesn’t, create another folder, move the remaining extensions into it and give them a label. Move the first batch back into the extensions folder and reboot.

Now, add half your extensions back from the folder on the desktop to the extensions folder. If the problem comes back, move that half back into the second folder on the desktop and move the now-known good half into the extensions folder. After each test, remove the labels from the extensions in the extensions folder. Just keep swapping halves until you narrow it down to one bad extension, using labels to keep yourself from getting lost.

I don’t recommend Conflict Catcher because all it does is move the extensions around for you–it’s no easier than this method, and this method doesn’t cost $50.

This is how we build ’em in St. Louis. Neither Gatermann nor I are really in the habit of naming our PCs unless a name is just painfully obvious. In the case of his Linux gateway, the name was painfully obvious. One name and one name only fits: Mir.

This is how we build computers in St. Louis. This is Tom Gatermann’s Linux gateway: a Micronics P75 board with a Cirrus Logic PCI SVGA card, a Kingston PCI NE2000 clone connecting to the Internet, and a Bay Netgear 310TX PCI 10/100 (DEC Tulip chipset) connecting to the local LAN. Yes, that AT case was as cheap as it looks. Maybe cheaper.

Inside the case, there’s an IMES 8X IDE CD-ROM, an ancient 1.44 MB floppy drive of unknown origin, and a 1.2 GB Quantum Bigfoot HD, of which about 1.5 MB is used (booting’s much faster off the HD than off the floppy).

“>

Mir is made from, well, a pile of junk. A Micronics P75 board. A Cirrus Logic PCI SVGA card. Whatever 72-pin SIMMs we had laying around. A Quantum Bigfoot 1.2-gig HD. A really trashed 3.5″ floppy drive. The cheapest-looking AT case ever. But we did skip the Linksys NICs. The NICs are a Kingston PCI NE2000 clone and a Bay Netgear 10/100 based on the DEC Tulip chipset.

We assembled it outside the case because we had so much trouble getting it going correctly–it’s much easier to swap components when they’re accessible. Once we got it going, we never bothered to put everything back inside the case. Maybe we’re trend-setters and this is the next fad in computing. After all, what’s the logical next step after translucency?

Early experiments in building gateways

Gateways. I worked with Gatermann last night after I got back from church (three Macs and an NT server died yesterday–I needed it last night) on trying to get his Linux gateway running under FloppyFW . We were finally able to get it working with dual NICs, able to ping both inside and outside his LAN (I finally found an old Pentium-75 board that didn’t have compatibility issues). But we weren’t able to actually get his Web browsers working.

I suspect something about the IP masquerading configuration just isn’t right, but it’s been so long since I wrote one of those by hand (and it was really just copycating an existing configuration), so since I have working Linux boxes at home I finally just gave up and downloaded the shell script version of Coyote Linux and ran it. It’s not foolproof because you have to know what kernel module your Ethernet cards use, but assuming you know that (make it easy on yourself–get a pair of Netgear 10/100 cards, which use the Tulip module), but it’s definitely a two-edged sword. It makes it a little harder to configure, but it means it’ll work with a much wider variety of cards. If Linux supports it, so does Coyote, whereas a lot of the other single-floppy distributions just support the three most common types (NE2000, 3Com 3c509, and DEC Tulip). So an old DEC Etherworks3 card will work just fine with Coyote, while getting it to work with some of the others can be a challenge.

I’m disappointed that Coyote doesn’t include the option to act as a caching DNS, because you can fit caching DNS on the disk, and it’s based on the Linux Router Project, for which a BIND tarball is certainly available. I’ll have to figure out how to add BIND in and document that, because there’s nothing cooler than a caching nameserver.

I was messing around briefly with PicoBSD , a microdistribution of FreeBSD, but the configuration is just different enough that I wasn’t comfortable with it. FreeBSD would be ideal for applications like this though, because its networking is slightly faster than Linux. But either Linux or FreeBSD will outperform Windows ICS by a wide margin, and the system requirements are far lower–a 386, 8 megs of RAM, floppy drive, and two NICs. Can’t beat that.

Rarely used trivia department: Using Linux to create disk images. To create an image of a floppy under Unix, use this command: dd if=/dev/fd0 of=filename.img bs=10k . There’s no reason why this command couldn’t also be used to clone other disks, making a single-floppy Linux or FreeBSD distribution an alternative to DriveImage or Ghost, so long as the disks you’re cloning have the same geometry.

Test this before you rely on it, but the command to clone disk-to-disk should be dd if=/dev/hda of=/dev/hdb while the command to clone disk-to-image should be dd if=/dev/hda of=filename.img and image-to-disk should be dd if=filename.img of=/dev/hda .

And yesterday. While the computers (and I’ll use that phrase loosely when referring to those Macs) were going down all around me at work, the mail was pouring in. Needless to say, some people agree and others don’t. We’ll revisit it tomorrow. I’ve gotta go to work.

12/23/2000

The presidency again. The story that won’t die. I thought it was over! When will it end? This is the most ridiculous recount story I’ve heard yet.

New adventures in Linux. I was trying last night to make a Linux gateway out of a single-floppy distribution for the first time. I looked at a number of distributions and finally settled on floppyfw. Why that one in particular, I never decided completely.

Gatermann and I put a minimalist system together: a vintage 1994 Socket 5 Pentium mobo, a P75, 24 MB of 72-pin SIMMs, a floppy drive, a 2 MB PCI Trident video card, and two Bay Netgear 310TX NICs in a beat-up case. Neither of us normally names our computers, but looking at it, we decided this computer’s name was most definitely going to be Mir.

It booted up and seemed to detect the two cards, most of the time. Once it told me eth0 was sitting at IRQ 149 and had a MAC address of FF FF FF FF FF FF, which disturbed me greatly for obvious reasons. Fortunately, this board’s AMI BIOS allows you to manually assign resources to the PCI slots, so I went in and did that: PCI slot #1 got IRQ 9, up through PCI slot #4, which got IRQ 12. That gave me some consistency, but I never did get it to successfully ping any address except 127.0.0.1, the loopback address.

We may be dealing with a hardware problem. We’ll tackle it again soon, possibly with a more complete distribution. I have no shortage of small hard drives. I also have no shortage of other parts.

These projects never go smoothly but I always get them running eventually.

Picking a single-floppy distribution. The big thing is finding one that supports the hardware you have. There’s not enough room on a floppy disk to support every kitchen sink and hairdryer that you might want to use in a Linux box, so any old distribution might not work with your hardware. When Steve DeLassus and I were making a gateway out of his 486SX, we couldn’t find any distribution that didn’t require a math coprocessor, for instance. (There are some now.) If you’re using NICs based on the DEC Tulip chipset or NE2000 clones, you shouldn’t have any trouble, but if you’ve got exotic NICs, not every distribution will support them.

Plus, some of these projects have to be built under Linux. Gatermann doesn’t have a working Linux box at the moment. Others build on any old PC running DOS or Windows. Each distro has its own specialty, so you just have to find one that matches your hardware.

This search over at Freshmeat can give you a headstart if you’re interested in this kind of thing.

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

Abandoned intellectual property

Abandoned Intellectual Property. I read a piece on this subject at OSOpinion over the weekend, and I’ve been thinking about it ever since. There are, of course, a lot of people calling for abolition of copyright or radical changes. This is, believe it or not, one of the tamer proposals I’ve read.

I’m definitely of two minds on this one. Take my first ever publication for money, in 1991. Compute Magazine, before Bob Guccione had managed to totally ram it into the ground, opted to buy my spring break project I collaborated on with a friend. We were writing a video game for the Commodore 64 and 128 and we were getting tired of trying to draw the title screen manually with graphics commands (bad enough on the 128 which had Basic commands to do such things, but on the 64 you were talking peeks and pokes all over the place–someone really should have written this thing back in 1982!) so we wrote a program to do the work for us. You loaded the sprites, moved ’em around, hit a key, and it gave you the Basic code to re-create the screen, suitable for inclusion in your program. We never finished the game, but we got a cool $350 and international recognition (OK, so it was a dwindling audience, but how many high school kids can say they’re published authors at age 16?).

Now, the problem. General Media whittled Compute down until it was basically just another PC mag, abandoning the multiplatform support that made it so great (I read about my beloved Commie 8-bits but still got the opportunity to learn about Macs, Amigas and PCs–what could be better?), market share continued to dwindle, and eventually Guccione and GM sold out to Ziff-Davis, who fulfilled your subscription with a choice of mags (I remember I opted for PC/Computing). So the copyright went to Ziff-Davis, who never did anything with the old Compute stuff. A few years later, Ziff-Davis fell on hard times and eventually hacked itself up into multiple pieces. Who owns the old Compute stuff now? I have no idea. The copyrights are still valid and enforcable. I seriously doubt if anyone cares anymore whether you have the Nov. 1991 issue of Compute if you’re running MOB Mover on your 64/128 or emulator, but where do you go for permission?

The same goes for a lot of old software. Sure, it’s obsolete but it’s useful to someone. A 68020-based Mac would be useful to someone if they could get software for it. But unless the original owner still has his/her copies of WriteNow, Aldus SuperPaint and Aldus Persuasion (just to name a few desirable but no-longer-marketable abandoned titles) to give you, you’re out of luck. Maybe you can get lucky and find some 1995 era software to run on it, but it’ll still be a dog of a computer.

But do we have an unalienable right to abandoned intellectual property, free of charge? Sure, I want the recordings Ric Ocasek made with his bands before The Cars. A lot of people want to get their hands on that stuff, but Ocasek’s not comfortable with that work. Having published some things that I regret, I can sympathize with the guy. I like how copyright law condemns that stuff to obscurity for a time. (Hopefully it’d be obscure in the public domain too because it’s not very good, but limiting the number of copies that can exist clinches it.)

Obscurity doesn’t mean no one is exploited by stealing it. I can’t put it any better than Jerry Pournelle did.

I don’t like my inability to walk into record stores and buy Seven Red Seven’s Shelter or Pale Divine‘s Straight to Goodbye or The Caulfields’ Whirligig, but I couldn’t easily buy them in 1991 when they were still in print either. But things like that aren’t impossible to obtain: That’s what eBay and Half.com are for.

For the majority of the United States’ existence, copyright law was 26 years, renewable for another 26. This seems to me a reasonable compromise. Those who produce content can still make a living, and if it’s no longer commercially viable 26 years later, it’s freely available. If it’s still viable, the author gets another 26-year-ride. And Congress could sweeten the deal by offering tax write-offs for the premature release of copyrighted material into the public domain, which would offer a neat solution to the “But by 2019, nobody would want WriteNow anymore!” problem. Reverting to this older, simpler law also solves the “work for hire” problem that exploits musicians and some authors.

All around, this scenario is certainly more desirable for a greater number of people than the present one.

From: Bruce Edwards

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

~~~~~~~~~~

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.