My Duron: It’s alive! It’s alive!

Solving the boot problem. I don’t know how I managed to forget this stuff. But I’m getting way ahead of myself.
I used an external SCSI hard drive to build up this system so I could get up and running without touching my old hard drives. I’ll want to juggle my data a bit. Of course it’s a lot more elegant to keep everything on a server drive. I never said I did everything right in this project. Actually I don’t think I said I did anything right in this project.

Well, the SCSI drive wouldn’t boot, no matter what I did. I even swapped out controllers. At one point I started wondering about termination. The drive worked, it just wouldn’t boot. So I recabled everything, making sure I had a terminator block installed, and using cables and terminators that I knew worked.

Rule #1: When a system acts goofy and there’s SCSI involved, always suspect cables and termination first.

That didn’t fix the problem, so I gave up on SCSI for a while. I tried several different hard drives in my new system. I’ve got a collection of smallish drives, most of which have some old DOS installed. None would boot. I disabled boot sector virus protection in the BIOS, and then one of the drives finally booted.

Rule #2: When building a system, find the boot sector virus protection option in your BIOS and disable it. If you want that feature, re-enable it after you get your OS installed. Just about every OS diddles with the boot sector during installation, which will make your BIOS very upset. Evidently, changing hard drives midstream can make your BIOS upset as well.

So then I put another drive in, one whose contents I totally didn’t care about. It wouldn’t boot. Finally I came to my senses and ran FDISK. It immediately gave me a warning: No partitions are set active. So that’s why endless SYSing wouldn’t make that drive boot, even after disabling the boot sector virus paranoia!

Rule #3: Whenever a disk acts funny, immediately run FDISK or Partition Magic or some other disk partitioning utility and look for goofy stuff, like no active partition set.

Then I took a look at my external SCSI drive. I’d forgotten I formatted that drive as one big extended drive–it didn’t have a primary partition. That’s why it wouldn’t boot. That’s a sneaky trick for adding a drive to an existing system without throwing off other drive letters, but then of course the drive won’t boot or anything. That kind of setup is great for portable data storage, but it makes the drive unbootable.

Rule #4: See rule #3.

Rule #5: Usually when you do something goofy to a seldom-used component, you have a perfectly good reason for doing it but you’ll forget what you did and why by the time you need to use it again. Write yourself notes and put them on oddly-configured hardware so you don’t rip your hair out the next time you try to use it.

Oh yeah, one more thing: This Duron-750 with 256 MB and an ancient SCSI hard drive (I think it’s a 4500 RPM model) running Windows 2000 really smokes. It boots in about a minute and everything’s silky smooth. Literally the only thing that keeps me from ordering a 10,000 RPM SCSI drive for it this second is noise.

Building my Duron

I broke my own rule last night. Twice. You should never take down a working system to build its replacement. Get the replacement system working, then take down the system to be upgraded. If you’re cannibalizing parts from the old system, get the new one going as much as you can before you start stealing parts from the old.
Well, I never got around to ordering more cases and video cards, and I had this really fast board and CPU sitting here doing nothing while a decrepit K6-2 that’s needed reinstalling for two and a half years (another thing I never got around to) sat around taking up space. So I took down the K6-2, only to find it had PC66 SDRAM in it. I vaguely remember how that came about. So I took down my Celeron-400, which I thought had PC133 SDRAM in it. I was half right. It had a 128 MB Crucial PC100 stick and a 128 MB Crucial PC133 stick. Decisions, decisions. I put the PC66 SDRAM in the Celeron (it wasn’t happy about that–it took me 15 minutes to get those DIMMs to seat properly) and took both 128s and put them in the new PC.

I re-assembled the Celeron and hoped for the best. It powered right up and booted. It’s not as nice of a system now, with 128 megs instead of 256, but the speed doesn’t matter due to the Celeron’s 66 MHz bus.

So I tore down the K6-2, lifted out the old motherboard, dropped in the new FIC AZ-11 freshly configured with a Duron-750 and 256 MB of SDRAM set to run at 100 MHz (if I’d had two PC133 sticks I could have clocked it at 133 MHz and still set the FSB to 100 MHz–this AZ11 BIOS is very nice). I reinstalled my PCI SCSI, network, and sound cards and my STB Velocity 128 video card–yeah, it’s ancient but I love that card, and it’s still fabulous for a lot of tasks–and connected up all the front panel LEDs and switches. While I had the system open I decided to pull the CD-RW so I could put it in an external enclosure. Since I didn’t have the faceplate anymore for my PCP&C midtower, I scrounged around for something to put in that bay. A 12X NEC SCSI CD-ROM? Marginally useful. What else have I got? Hey, is that a 5.25″ 1.2MB floppy drive I spy? Why not? I haven’t had a 5.25″ drive in a production system in about seven years. And hey, I like retro. So I installed that drive.

I plugged the system into my KVM switch, crossed my fingers, applied power, and got nothing. So I ripped the system back apart and double-checked everything. It looked good to me. But wait… Why do I have two leads marked “Power Switch?” My manual for my case is long gone, so I went to PCP&C’s web site. That brown/white lead is reserved for future use. OK, ignore it. Hook everything up, still dead. So I crack out the manual, since the silkscreen on the board obviously is either not enough or wrong. Oh. The speaker and power connect one way, and the others, including power, connect perpendicular to that. How odd. I reconnected the leads, powered up, and everything sounded normal. Nice.

I connected up an external SCSI hard drive, because I didn’t want to touch any of the old drives until the system was up and running. I made a DOS boot disk with my SCSI drivers on it (since this SCSI card can’t boot off a SCSI CD), but I didn’t get too far getting a modern OS installed. The SCSI drive kept acting weird and refusing to boot.

Instead of really troubleshooting it, I opened up my drawer of 5.25″ floppies and started playing around. I found my old DOS 3.2 floppy. I went into the BIOS, swapped the floppy drives, threw in DOS 3.2, and… to my amazement, that disk still worked. My fire-breathing dragon booted into MS-DOS 3.2. So then I tried my Commodore-branded MS-DOS 3.3. That worked too. It was funny seeing Commodore copyrights all over the place…

I’ll have to see if I can get things working right later this weekend.

It’s just about upgrade time.

Well, I’ve got a new FIC AZ-11 board and Duron-750 CPU waiting for me to do something with it. The AZ-11 is $65 (up $5 from when I bought it) at www.gpscomputersvcs.com; the Duron-750 retail is $50 (down $5 from when I bit) but the OEM chip is 33 lousy bucks. I think the retail kit is a good deal, since you get a longer warranty and you know you have an AMD-approved fan. Shipping was $10.50. Nice deal.
Over at Directron.com, you get a good selection of cases and power supplies. And you can get a Diamond Stealth S540 video card for $28 (my forum readers already knew that–hint hint). So, let’s see. Figure $200 for a case, power supply, motherboard, CPU, fan, and video card. All you need is memory, hard drive, floppy drive, and incidentals like an OS, keyboard and mouse and maybe a NIC. So you can have a perfectly respectable system for around $400, but it’ll scale nicely too if you want more. I know my P2-350 at work tends to hover at around 60% CPU usage, so a Duron-750 is way more than necessary for much of what I do, but it’s nice to have some CPU power in reserve.

First impressions of the AZ-11: It’s obviously a modified microATX design. There’s a placeholder for onboard video, which the KT133 chipset lacks (but the KM133, usually used on microATX boards, has). The leftmost 1.5″ of the board is mostly unfinished. Chop that off and it looks like a standard microATX board. It’s not the ideal board, but at $65 you’re getting FIC respectability at a PC Chips price. What do you want for 65 bucks?

With the Gigabyte GA-7DX now selling in the $150 range and Crucial PC2100 memory selling at PC133 prices, DDR makes sense if you’re building an entirely new system. If you want to upgrade something old on the cheap, an AZ-11 and a low-end Duron is a mighty big step up for $125-$150. It wasn’t that long ago that a 4-meg stick of memory cost that much.

And on another note (the CPU): What they say about the fans is true. Be very careful clipping on the fan, and once you get it on, leave it alone. It’s a really tight fit, so I can see why the hardware sites warn against crushing the CPU core. Frankly I’d be afraid to take the fan off the chip.

I’m also a little concerned about the known VIA KT133 problems. There are reports of data corruption on high-speed IDE drives, and apparently use of an SB Live! card makes them worse. And of course I’m going to keep my SB Live! in my fastest system in case I want to do voice recognition.

I just read today that the newest VIA 4-in-1 driver fixes that problem. But I’m thinking seriously about avoiding the problem by putting a SCSI controller and drive on the system. I wonder how many of the infamous IBM 75GXP problems may not have been caused by this. I know the KT133, SB Live!, and IBM 75GXP were an extremely compelling and popular hardware combination because it gave you so much bang for the buck.

Even if I don’t use a SCSI drive and controller, I’ll probably put a Promise Ultra66 in there since it’s known to be a stable, mature, and robust solution and I’ll have plenty of PCI slots available for it.

A small favor…

For those of you who are praying people, I have a favor to ask. My good friend Jennifer e-mailed me tonight and asked me to pray for her sister, Erin, who is pregnant with her first child and having complications. I don’t know very many details and I wouldn’t understand them if I did. They’re doing a c-section in the morning, but they’ve got her on monitors all night. Please join me in praying for the safety of both of them, and for reassurance and sanity for her husband, Duane, and their extended family.

Kaycee has passed on…

We’ll miss you, Kaycee. “The word ‘goodbye’ doesn’t accurately convey my feelings right now. I think the best I can do is au revoir. We’ll see you again.” -Richard Nixon.
Kaycee died Monday. Old news, but I can’t think about anything else right now. I just found out, because I’ve been away from my e-mail for the past five days. Her post for that day started with, “I woke up to hear the birds singing.” I smiled as I read that. The last words of someone else I admire were “Now I can hear the birds singing.” But this guy wasn’t in Kaycee’s league. Not by a long shot.

I won’t go on and on about this. Truth be told, Kaycee and I never met (of course). I read her stuff, admired her courage, her sincerity, and her transparency, and was inspired by her. I still am. In talk amongst friends, I cited her as a good example of strong faith.

And she did something I’m not sure any writer has ever done. She broke my heart. Her story did that to a lot of people.

I’m sure that someday, after my day has come and gone and God has called me home, Kaycee and I will finally meet. I’m not sure what I’ll say to her. Seeing her trust God helped me to trust God. Reading her stuff reminded me that personal stuff is often more compelling than talk about machines. When I retold her story to some friends who don’t have Internet access, they found her inspiring and I think she helped to strengthen their faith in God. Her courageous stories goaded this 26-year-old to grow up a bit.

But I think I’ll just start with something simple. Like, “Thank you for sharing.”

School’s out, school’s out!

School’s out, school’s out, teacher let the monkeys out! Those that didn’t leave on their own free will, thta is. I’d do a comprehensive review of the class, and maybe I still will, but I think this says it all. There were 36 people enrolled. By the time the second afternoon break was over, 14 remained.
I got addresses of a few useful Web sites, but they’re in my car and I’m not. I’ll post those later this week.

I’d post all the new secrets I learned so my readers didn’t have to take the class, but frankly I didn’t learn anything that isn’t already common knowledge. I think I’ll post some of the things that were left out though.

Like this: If you don’t want a particular NT/2000 workstation to participate in browser elections or force elections, shut off the Computer Browser service. This will reduce network traffic and give a very slight increase in workstation performance. Remember, you need to have one browse master and three backup browsers per network segment, so be sure to leave the service enabled on four machines per network segment.

If you don’t want your 95/98/Me PCs participating, go into the properties of the File and Print Sharing for Microsoft Networks and clear the Participate in Browser Elections checkbox. You don’t want one of those machines serving as a browse master.

Classes are for appeasing middle management.

Argh.. Classes. Well, my first day of Windows 2000 school is over. All we did was talk about how MS assimilated certain features from other products (NDS, Win98) into Windows 2000. The longest time we spent on any single topic was TCP/IP. Now granted I’m not an expert on TCP/IP, but I know more than most, and all I need to do my job (and hobby). That which I don’t need to know off the top of my head I can find in 15 minutes or less. I did pick up a couple of tricks I’d forgotten about, but memory’s a funny thing. Frequently a problem will trigger the memory.
I kinda feel bad for wasting my employer’s money on this thing. But I want to move up, so I do what I have to do.

Hello from the land of great barbecue

I’m in KC. Home of barbecue, the Kansas City Royals, and way too many country music stations. I miss the barbecue and the Royals. So. I’m gone. Gatermann’s in charge.
What am I saying!?

Actually I’ll be checking in periodically. I may even write some stuff up the couple of days I’m gone. Not sure yet. I won’t be checking mail though, so if you have questions, use the comments here or the forum.

It was a decent drive up. I stopped at my usual place, Biffles BBQ in Concordia, Mo., for some brisket. The Royals game was on the TV in the bar, so I stayed and watched an inning. They ended up winning the game 12-4. I don’t get it. The Royals can beat the first-place Twins about as well as anyone, but they can’t beat any other team.

Windows and Outlook

Outta here. I’m off to a Windows 2000 class in Kansas City later today. Class actually starts Monday, but I’m making an extended weekend out of it, leaving this afternoon, and coming back sometime on Tuesday.
No e-mail while I’m gone, but I’ll have Web access of course, so if you’ve got something to ask me, go ahead and use the comments here or the forum. I won’t be able to read mail until Wednesday.

Windows and Outlook. An old friend wrote in this week. She was implementing some of the advice in the first chapter of Optimizing Windows, and she got to the place where I said to uninstall anything you don’t use. So, logically, she said to herself, “I don’t use Outlook Express since I have Outlook,” so she uninstalled Outlook Express.

Then her contacts list stopped working.

If you use Outlook, you use Outlook Express because Outlook uses code from Outlook Express (and Internet Explorer) extensively. It makes no sense, and you’d think Windows would leave the DLLs from Outlook Express that Outlook needs when you uninstall Outlook Express, but evidently it’s not that smart. A shame, but typical.

More Like This: Optimizing Windows Windows Outlook

Short takes

AMD. According to the latest rumors on Ace’s Hardware and The Register, the Palomino core, when released, will be known as the Athlon 4. This is a marketing move; the Palomino is a less radical change to the core and the architecture than Thunderbird was. I think it’s a good marketing move, but it won’t do anything to make people less confused.
Tech support story of the day. A user one of my colleagues supports received an LS-120 superdisk in the mail. This user had no LS-120 drive, only a floppy drive. So my colleague went up to look at the disk and locate an LS-120 drive to read the disk. When he hunted down an LS-120 drive, he stuck in the disk, looked at it, and found a single file on it–a Word document. The file size? 32.5K!

But I guess it could have been worse. At least it wasn’t a 4K file…

Discussion groups. I’m not the least bit happy with how they look, and the performance isn’t so grand (an upgrade next week should help that), but I’ll go ahead and open up my forums. They’re at https://dfarq.homeip.net/cgi-bin/yabb/YaBB.cgi. At the moment they’re totally open. I’ll bolt them down if spam, flame wars, or other things become a problem. I tend to be very open until that openness is abused, then I become a dictator.

I believe you can register without giving a true e-mail address, so you can use a spam filter if you’re afraid of that. Cookies are just used for automatic login and for timeouts–they’re good cookies.

The board is powered by YaBB, a free bulletin board written in Perl. Some things about it I like better than UBB, which is what most forums out there seem to use. I don’t like its color handling, but I’ll sacrifice that to gain other features.

Go ahead, take a look around, start posting stuff, and offer suggestions.

Why the forums when we’ve got comments? Well, I assume people want to talk about more than just what I talk about on a given day. This is preferable to e-mail because I have more options for reading it and it’s already online. Plus there’s always the chance someone else could pipe in with an answer.

More like this:AMD YaBB