Main

March 13, 2008

Tech Support

I do a lot of tech support for my friends, I've worked in tech support for years. I have noticed there tend to be two types of tech support calls. There are calls about serious problems that need tech intervention. But more often, the calls are from someone who hasn't done a single thing to research their problem. These calls can be frustrating, my friend calls and says "I'm in Photoshop and I can't get the thingummy in the whatchamajigger" (that's a direct quote) and it takes me an inordinate amount of time to figure out he's trying to find a path command in the layer palette. Sometimes I just look in the program's help file, once I figure out what the question is, the solution is easy if you just look in the help files. I don't mind so much that the solution is trivial, I just mind that it takes so long to figure out the question.
I've recently been thinking of my first tech management job, I was Service Manager at ComputerLand of Glendale back around 1981. I told the boss I didn't feel qualified, he said, "don't worry kid, after 3 months you'll have seen it all and know it all." And he was right, the daily grind of repairs and tech support seemed like old hat after a few months. But there were ongoing tech problems, I remember one problem that seemed to take way too much tech effort, or at least, way too much of my effort. When the first memory cards for the IBM PC came out, the technicians could not figure out how to set the DIP switches. All day long, the techs would interrupt me with questions about setting the switches, when they could easily have figured it out for themselves. It was easy, you just set the switches to the binary address of where you wanted the memory to start. But none of the techs knew binary math, so they were always baffled.
I decided to close the shop one morning for a class to teach the techs how memory addresses worked and how to do the binary math. We went through all the fundamentals and they seemed to get it. We went through the manuals and worked out how the cards functioned. I demonstrated the formula to calculate the addresses. I described as many ways to solve the problem as I could figure out, and gave them all the tech support phone numbers I called when I couldn't figure it out. Then I gave them a written exam. The exam was just one question, I didn't even want the solution, I just wanted them to describe at least 4 places to look for the answer, "How do I configure Memory XYZ at location ABCD?" My point was to teach them how to find their own resources to solve problems, before asking me. But I was astonished when the techs handed in their tests. Every single one of their lists started the same way:

1. Ask Charles.

January 22, 2008

A Leopard Trick

One of my favorite obscure MacOS X 10.5 "Leopard" features is the customizable Finder bar. I took a screen cap of the folder with the graphics from my last blog entry.



Look closely under the word "Sony." There's a little round icon, it's not part of the MacOS X icon set. Look over on the left, it's the same little icon as my Downloads G5 folder. If you drag a folder to the Finder bar, it will stick; option-drag it away, it will disappear with a "poof." Click on the icon and you're instantly transported to the folder. I understand you can put other things on the Finder Bar, like apps or Applescripts, but I don't like too much clutter. It is incredibly convenient to put shortcuts there, it's much quicker than searching through the sidebar.
One of the reasons this looks so good is because of the beautiful icon. Its gray tone matches the Finder well, it isn't too intrusive, you'd hardly know it's there. I found it on a Japanese icon designer's website, I'd give him credit if I could remember his name. He made beautiful, subtle icons, which were all totally useless to me except this one.



December 21, 2007

New Old Mac

I just bought a new old Mac. I saw an old Performa 6300 on Craig's List for $15. It had a combination of features I was looking for, it had USB and ethernet, and a floppy. I've looked for a USB floppy drive so I can load and archive some old floppies. But that would cost a lot more than $15. I can buy the whole computer for that price, and pull the data in and out of the Performa with a USB flash drive, or even hook it up on my home network and zap files between machines.
So I drove out in an ice-storm to pick up this old junker computer. Then it occurred to me, the City Sanitation Dept. will bill you more than $15 in disposal charges if you put this in the dump. I told the seller, I'm saving him more than $15 you'd have to pay to get rid of it, you should be paying me! He laughed and said there was a time when this computer was worth $2300 and he was firm on the $15. I said this is a Craig's List deal in cash, so I'd offer a firm $14, that way I could at least feel like I got a deal. We closed on $14.
I need another old Mac like I need a hole in my head, but I decided I needed an old OS 9 machine like the Performa, my Mac Quad G5 has lost the ability to run Classic, since the MacOS X 10.5 upgrade. Classic is dead. Some people have tried running emulators like Sheepshaver, but I just can't get it to work on my Quad. The HowTo files seem to focus on Mac Intel systems that could never run Classic. It seems odd for me to try to run an emulated OS 9 on my CPU that was running native PPC Classic just a few weeks ago.
So I guess it is time to put OS 9 in its grave. I need to migrate some old OS 9 media on SCSI drives. I have an old 80Mb Bernoulli Box, it's an odd cartridge drive, it was designed to work with the Mac Portable, which was notorious for its heavy lead-acid batteries. The Bernoulli drive has a lead acid battery too, but it's been sitting in a closet for about 10 years, I'm afraid to fire it up. But if it blows up when attached to an old $14 junk CPU, I wouldn't mind so much.
Then I have some other miscellaneous media, old 40Mb Syquest carts, 1Gb Jaz carts, I figure I could reduce a two full boxes of floppies and disks, and two boxes full of old hardware, down to maybe 3 or 4 DVDRs.
I need another Mac like I need a hole in my head. Let me see if I recall what old Macs I have, four of them: a IIcx, 8100/110, G3/400U, and a Dual-1Ghz "Wind Tunnel." But none of them had a floppy AND a communications port to move data to new Macs. So I guess I need one more Mac, in order to migrate and get rid of my old Mac junk. And soon I'll be paying the expensive disposal charges on this old crap.

November 28, 2007

Turing Fest

A minor storm has erupted in comments for an article I posted long ago, thanks to a link from Andrew Orlowski at El Reg. He unburied an article I wrote almost a year ago, an essay about DRM and the Church-Turing Thesis. I am still answering comments as they arrive, so I thought I should put a note here, to alert people that all the fun doesn't necessarily happen at the top of the blog.
Turing's math papers have always fascinated me, but everyone seems to have their own interpretation. I try to see it at its most fundamental. I remember seeing an article many years ago, describing the simplest possible Turing Machine. It consisted of a strip of paper and some flat stones that were white on one side, black on the other. The stones represented one bit, on or off. It was suggested that you use a roll of toilet paper, as it was conveniently marked in squares, one for each bit. The human operator flipped the stones and moved the strip of paper left and right, according to the algorithm. It was essentially a cellular automaton in 1 dimension.
And that's how I think Turing saw these problems. I am particularly fascinated by his papers on Morphogenesis, analyzing the spotted patterns in animal fur, and the variegation patterns in plants. Turing conceptualized the growth of the pattern as a 2 dimensional cellular automaton. But Turing always wanted everything to be written as functions, he considered a function as a fundamental unit of computing on a Turing Machine. If it's a function, it runs to completion, if it's not a function, it might be Turing-Incomplete and be incomputable.
Turing's dense forests of functions are way over my head. I wonder if there are even a handful of people who fully understand them. The papers I read that introduced me Turing's morphogenetic pattern functions admitted they barely scratched the surface.

October 17, 2007

Help, my iPhone Won't Ring!

Apple blogs had an outpouring of derision when a prominent, self-declared technology expert could not figure out why his iPhone stopped ringing. Of course this was because he'd flipped the Silence Ringer switch. John Gruber rushed to his defense with this comment:
It’s easy to laugh at, but I think it’s actually a non-obvious design. There’s no icon or visual indication as to what that switch does. You do get a small jolt of vibration when it’s engaged, but that doesn’t naturally imply “silent mode” to me. (Update: Yes, there’s also an on-screen icon, but that only helps if you toggle it while the screen is on.)

But the icon will also appear if your screen is off. If your iPhone is sleeping and has been inactive more than 1 minute, flipping the Silence Ringer switch will turn on the screen, and the big icon of a bell with a slash through it will appear. However, if your iPhone is sleeping but has been used within the last 1 minute, you only get the buzz of tactile feedback, indicating the phone is in vibrate mode. So the only possible way to miss the visual feedback of the Silence Ringer icon is if you turn off your iPhone and then immediately start flipping the switch.
But to me, the bigger question is, what kind of idiot would buy a $400 phone and not know how to operate the buttons? There are only 4 hardware buttons on the iPhone. Apple went to considerable pains to make the Silence Ringer switch functions as obvious as possible, even to technology experts.

September 12, 2007

Price Cut

Yes, I bought an iPhone the first week. Yes, I was mighty irritated when they cut the price $200. Then Apple announced a rebate, a $100 gift certificate to the Apple Store. I thought about it a minute, decided I was half-satisfied, and considered it a glass half full.
Then I thought about it a little longer. I realized that $100 of retail goods at the Apple store is likely to be around $50 wholesale cost, so Apple is covering my $200 loss with about $50 cash. The glass is only one-quarter full, I am now 75% dissatisfied.
I've been there plenty of times. I always tell people, if you want to know when Apple is going to drop prices on something, wait until I buy it. Apple always seems to cut prices right after I buy something. I remember buying my PowerMac 8100/110, I bought it the week it was introduced, figuring it would be a long time before a price cut. It took almost three months to deliver the machine, and they cut the price $300 before I ever received it. No, I didn't get my $300 back.
I've seen it from the dealer's side too, when I worked in computer sales. Customers would sometimes express their irritation when their computers dropped in price, and I would use almost the exact same spiel that Steve Jobs used in his rebate announcement.
There is always change and improvement, and there is always someone who bought a product before a particular cutoff date and misses the new price or the new operating system or the new whatever. This is life in the technology lane. If you always wait for the next price cut or to buy the new improved model, you'll never buy any technology product because there is always something better and less expensive on the horizon.
I would usually try to put it a little more diplomatically than that, but the last sentence is almost verbatim from Apple sales training, and has been conventional wisdom for decades. Most customers would accept this logic, but once in a while, you get a case that is so egregious that you have to do something about it.
I remember when I worked at ComputerLand, around 1985, one of my favorite customers came in just before closing time. She was a young woman with punky purple dyed hair, a college student on a low budget, she'd bought an Apple //c last Christmas. She was so happy with it, she scrimped and saved for months and now she wanted to buy two more computers, one for her boyfriend and one for her mom. I was pleased to help her, a salesman loves nothing more than a happy repeat customer. She paid cash, I loaded them in her car, and left the office for the day with a smile on my face.
The next morning, I arrived at the office and sipped my coffee while reading the morning updates from ComputerLand Headquarters. I was stunned, as of this morning, Apple dropped the retail price of the //c by $200, about 1/3 of the price of the machine. I'd just screwed my customer out of $400. I immediately talked to the store manager, he had the same reaction, "oh crap." We decided we had to find a way to fix this deal, and we better have it in place fast, before she called to complain about it.
Apple traditionally had price protection for dealers, so if inventory in the dealer's warehouse was devalued by a price cut, Apple would write a check for the difference in the wholesale price. But they offered no price protection to buyers. I figured that we should just void the sale from yesterday, so officially the computers would still be in our warehouse, and ComputerLand would get a check for the price protection. Then we would sell the computers to her with a new receipt dated today, at the new lower price. We'd be screwing Apple but they'd never know. Everyone would be happy.
Just as I was on the phone getting final approval from Headquarters to rewrite this deal, the store manager got a phone call.. from the customer's mother. The manager transferred the call to me, so I could look good by proposing the solution we'd already worked out. She said her daughter was so distraught when she heard the news of the price cut, she'd been crying inconsolably for the last two hours, she was so broken up she was unable to speak on the phone. I told her I was surprised and upset when I learned of the price cut, and I'd just spent the last two hours working on a solution, and I was just about to call her. I described the deal, and said her daughter should come in right away and I would take care of her.
Within an hour, the poor girl came in to the store, her eyes were puffy and red, she was still sobbing and crying, but trying to put on a brave face. I told her how upset I was when I heard the news, and that I'd worked hard to recover her money. And besides, you don't think I was the sort of person who would do this deliberately, now do you? If I'd known the price was going to drop, I wouldn't have sold them to you until the next day. She cracked a weak smile, but she was still sobbing.
So I refunded her money and voided the sale, then rewrote the sale on a new ticket dated today, and handed her 4 hundred-dollar bills from the till, the same bills she'd paid with yesterday. I apologized to her for any hard feelings, and said that despite the hassles, she should be happier than ever, since she ultimately paid far less than she ever expected. She said she was happy with how we'd resolved the problem, and thanked me for working on her behalf. But I wondered, why was she still crying?

September 11, 2007

Sol First Run

My first attempt at getting software running on my Sol is not encouraging. I believe the Sol is running correctly and loading the software from tape, but the programs do not execute. I loaded the classic game TARG from GAMEPAC 1 and immediately ran into trouble. Here's a picture of the Sol lab, right in the midst of trouble.



I hooked up a cassette player to my Sol, typed the command "XEQ TARG" and started playing the tape. A couple of minutes later, the tape is done loading, the program runs, and all I get is a memory dump that fills the screen with this:

90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90


This obviously isn't working right. Perhaps it is time to test my memory boards, I have two 16KRA boards, but let's keep it simple and just run one board for now. The boards are marked 1 and 2, I installed Board 1 but I just get the same memory dump.
Time to investigate more closely. I wonder what the code looks like loaded in the Sol memory. Sol apps run from the top of memory at Hex 00 00 and can be started with the command EX 0, you are literally executing the code starting at 00 00. I can load the program from tape with the GET command, and then look at memory before I execute. But there's no data there, it's blank.
I poked around and found a nice screen shot of a memory dump, if the memory is reset, a dump should show a nice little Hexadecimal pattern of FF 00 FF 00. But when I run DU 00 A0 all I get is FF FF FF FF. Aha, there is no memory at that location.
It appears that the memory board is not mapped correctly, so I'll have to reset the DIP switches. So it is time to RTFM. The 16KRA manual is a good place to start, there's a convenient PDF copy at the Sol20.org archives. I reconfigured the switches to run memory at address 00 00, but if I try to write to memory, I can only read FF FF back, it's not working. I reconfigured and tested the second 16KRA board with similar results. I tested various locations and found some usable memory at C9 00, this appears to be on the motherboard. But I need some memory at 00 00 to run programs from tape.
Well this is disappointing, it is far too much work to get some little 8080A programs running. I will have to determine why the RAM isn't working, I hope it's something simple like the power connector problem I solved earlier. I think these old static RAM boards used some higher voltages like 16v that may not be used by the CPU, so maybe there's just no power going to RAM even if the CPU runs OK. But I don't have a voltmeter to test the output, I guess I'll have to buy one.
The First Run of the Sol is a failure, oh well. I think I need to take a break. I think I'll go fly a kite.

September 7, 2007

The Sol Archives: Unboxing

I located my Sol Archives in my storage vault, so I figured I would celebrate by recording the unboxing. Even the cardboard boxes are a trip through microcomputer history.



These two modest boxes enclose all my Sol programs and manuals. One box is labeled "Godbout 8K RAM Assm & Tested $150 SPECIAL" on the top, and "8KRA A&T Processor Tech." Well I don't have either of those products, but just seeing the name Godbout was trip down memory lane, they were one of the earliest manufacturers of S-100 memory boards. But let's see what is in the boxes.



Ah, there's my old cassette tapes, with all the major apps I purchased from Processor Tech and other companies, along with tapes of all the programs I wrote myself. Some of them have intriguing labels in my own handwriting like "3D Graphics." Ooh I wonder what that is. I'll find out soon enough. Let's open the second box and see what's inside.



Manuals. The Extended Cassette Basic manual was my favorite resource for years and years. I wrote a lot of programs in Extended Basic on my Sol, it was sufficiently close to ANSI Basic that I could write and test them locally and then upload them by modem to minicomputers on our campus network. But wait, there's more.



These are my two precious 16KRA memory boards. Larger programs like Extended Basic required more memory than the motherboard of the Sol contained, so bought new memory as I could afford it, finally bringing the total up to a massive 32k. These two boards have the date of manufacture on a label, 3/10/78 and 4/25/78, so I obviously bought these a couple of years after I built my Sol in 1976.



And now the final part of the archives, Sol manuals. There's one particularly good manual, the "Subsystem B User Manual." I don't know why I have this manual since I don't actually own a Subsystem B. I must have gotten it from my Sol dealer. Subsystem B was a set of circuit boards for other S-100 computers like the IMSAI or Altair, it would effectively turn your computer into a Sol. For a brief while, the Sol display and I/O system was a standard, but it was quickly surpassed by other systems with higher resolution and more features. Most of the Sol manuals have been scanned and archived on the web, but not this Subsystem B manual. This is definitely a rarity and may be the only surviving copy.
There are a few bits missing from my Sol archives that are not pictured here. Somewhere in my house is the huge black binder that contains all the assembly instructions. I also have a beautiful advertising poster for the Sol, but it's wrapped up in a bundle of other large artworks that I really don't want to open up right now.
So that's my Sol Archives. Now I have to plug in the memory boards and start fiddling around with the programs on tape. But that story will have to wait for another day.

August 30, 2007

Vintage Computer Swag

While poking around in my vintage computer junk, I found some swag from my old job. I thought I should immortalize it with a photo on the web, and then throw it in the trash.



ComputerLand produced a lot of crappy promotional items, and this can cooler must have been one of the worst. Back in the early 1980s, every major computer manufacturer was dying to associate themselves with ComputerLand, so they'd fund almost any advertising gimmick that put their names together. This cooler has the Hewlett-Packard logo on the back, so I know HP paid for it, ComputerLand paid nothing. This is called "co-op" advertising. I think it barely qualifies as advertising. The world would be a better place without so much of this disposable crap.
Whenever I see some old bits of ComputerLand swag, I always think about the ultimate swag our company ever produced, a surfboard. One of our salesmen was a surfer dude, he somehow conned the boss into funding his new custom surfboard if he'd put a huge ComputerLand logo on it. Everyone would see him riding the Malibu waves on top of a ComputerLand logo, it would associate our company name with the cool surfer image. In return for funding his board, the salesman agreed to prominently display the logo at the beach. To maximize exposure, the salesman was allowed to come in late to work any time the surf was up, which happened with no advance notice, leaving the rest of us to carry his workload. After coming in to work late, he would display the board in our lobby. He must have been a hell of a salesman for the boss to agree to that deal.

August 29, 2007

Sol-20 Restoration Phase 1 Completed

I have successfully restored my Sol-20 computer to working condition. I took special care to insure the repairs were correct, it was difficult, and at times I was certain the machine was completely dead, but ultimately, the restoration was a complete success. Here is a photo of the patient on the operating table, opened up and about to undergo surgery.



When I set up to take this picture, I was suddenly struck with a realization, this is the same chair I sat in 31 years ago when I assembled this computer. Somewhere I have a Polaroid photo of my desk with the Sol in mid-assembly, with this chair in the background. But I couldn't find the picture. Oh well. Anyway, I thought this was a good omen for the project.
At this point, I've cleaned up the computer with cans of compressed air and circuit board cleaning spray. It took me almost an hour to get it all clean, it was especially difficult getting the gunk off the top of the keyboard. It was really grubby and nicotine stained. I used to spend many hours smoking at the keyboard, dropping ashes right into the keys. I used to open it up, lift out the keyboard plane, and dump out the ashes once a week or so. The Sol keyboard seemed impervious to this kind of abuse. But now I had to clean that all up and make it shine.
Here is a closer view of the operating table, you can see the interior of the computer. There are thousands of tiny solder joints on that motherboard, and I made every single one of them. I recall it took about 200 hours to completely assemble the kit. That was pretty slow, but I'd never built any electronics kits before, I was a total novice.



There is one particular component that makes this Sol rare and unique. It has a Graphic-Add daughterboard, which I used to create simple computer graphic images. Without the Graphic-Add, the Sol can only display text. I've never heard of any other Sol equipped with this circuitry.



And now the patient is under the knife. Or more accurately, under a dental pick. I'm picking out the old foam pads, you can see I've got some of them out, they're black and decomposing. Up at the top, you can see the circuit board contacts, shaped like a circle with a line through it. The pads push against the contacts, the mylar will bridge the gap and complete the circuit, indicating a key was pressed.

solrestore3.jpg

And here is the keyboard with all the pads replaced. They're shiny and new, just like the day it was built. Everything is ready to reassemble and test.



This is the point everything went all to hell.

I got the machine assembled and ready to test. I hooked it up to my TV through the video monitor input. I successfully tested the Sol in March 2002, I got a video signal and a cursor, indicating the CPU was operational. But today when I fired it up, I got nothing. No video, no cursor. The CPU was dead.
I was devastated, in shock. My long-planned restoration project was a total failure. In 2002 everything but the keyboard worked; now the keyboard was repaired but everything else was dead. I tried to deduce what happened. I noticed the LEDs on the keyboard wouldn't light up, so there must have been a problem with the power supply. Then I noticed the power supply fan was running, so there must be power, it's just not getting to the motherboard. I started by unplugging and reconnecting the main power connector on the motherboard. And instantly, the computer was restored to life. It was so simple once I figured it out. And here is the computer in operation.



This picture looks a bit fake, but I assure you it is 100% real. I had to enhance the contrast of the TV screen so the text was legible, but other than that, it is unaltered. So now the Sol is operating, the keyboard works, everything is ready to go. But go where?
The next step is reinstalling my memory cards and testing the software. I have a box full of Sol data tapes, my memory boards are in the box, but it's buried somewhere in my storage locker. It may take me a while to unbury it. I have tapes of games like Chess, Targ, and Trek80, and languages like Focal, Basic, and Logo. But even if I can never find my old software, there is an online archive where I can download everything I need. But I really need to find those tapes, they have all the programs I wrote in Basic, and the archive doesn't have programs to run my Graphics-Add. I have offered those programs to the archive, if and when I ever find them, and if the tapes are still readable.
And that is the primary goal of this project, to document and archive my unique pieces of Sol hardware and software, particularly some of the computer animations I exhibited in art shows in 1976. But that will have to wait for Phase 2 of this restoration project.
Today, I am giddy with excitement. Everything works, and I'm ready to rediscover my microcomputer roots. I can't wait.

August 20, 2007

Sol Keyboard Pads

It's like a dream come true, I suddenly acquired a set of new parts for my vintage Sol-20 microcomputer. I've written about this before, someone found that old article from 5 years ago in a web search, and asked me if I'd ever located the parts. I said I gave up, and do you have any? I've hunted unsuccessfully for 10 or 15 years. So he generously offered me a pack of parts, for free. Oh boy.

pads.jpg

I swear this looks just like a bag of pills. They are little foam pads with foil on one side. These pads were used in the keyboard of the Sol, when you hit a key, it pressed on the foam, pushing the foil into contact with the circuit, then when you let go the foam pushed the key back up. It was an inexpensive design, it worked fairly well, but over the years the foam deteriorated, and today every single Sol is surely unusable due to rotted foam pads.
But now I have the parts I need to get my old Sol back up and running. This is going to be a tedious job, I have to painstakingly disassemble every keyswitch, pick out the rotted remnants of the old pads, clean up the circuit contacts, install the new pads, and put everything back in perfect order. Then my Sol should be restored to full function. I can't wait to see my old computer back in action after all these years.

March 16, 2007

The Killer Demo: 1979

I was reminiscing about the good old days with a friend and I told him of my first "killer demo" back around 1979, he insisted I blog it, so here it is.
I used to work at a little computer store called Computers Plus in Dubuque, Iowa, selling Apple and Vector Graphic CP/M computers. My specialty was word processing with Wordstar and the complex form letter system MailMerge. But in those days, even basic word processing was brand new and a hard sell, people just didn't understand how powerful it was. The target market was usually professional secretaries who could bang out a perfect business letter in one pass on a Selectric typewriter, even fancy word processors could barely outperform a skilled typist. But I was determined to beat them at their own game, I would demonstrate just how fast a business letter could be produced.



We had a fancy Vector Graphic MZ demo system with a powerful Z-80 CPU chip running at 4Mhz, a massive 48k of RAM, and two floppy disk drives. It was hooked up to a high speed daisy wheel printer, it could print about 50 characters per second. And the key element, me at the keyboard typing like a demon. I've been clocked at over 100 words per minute, and the Vector Graphic had a really good keyboard, so I could really crank out the text quickly.
I had Wordstar set up with a few macros so I could hit one key and it would create a perfectly formatted business letter, with the address, date, salutation, and "Sincerely, Charles Eicher" at the end, all I had to do was type the content. Usually I typed in something simple like "I present this letter for your consideration" and hit the Print command, and the daisy wheel printer would blaze into activity, hammering the letters out with a noise like a machine gun.
I would set up a sheet of paper in the printer, load Wordstar, then have the customer time me with a stopwatch, from the command to go until the time the finished letter popped out of the printer. Ready, set, GO, bang out the sample text, hit print, wham it's done. I could consistently do this within 15 seconds, including the time it took to type the text. Sometimes the customer couldn't believe what they'd seen, so I had to repeat the demonstration.
As I described this demo to my friend, I wondered how long it would take on modern equipment. I recall that well into the 1980s and the HP LaserJet era, a fast daisy wheel printer could beat a LaserJet on some documents, particularly screenplays with double-spaced text and lots of white space. But for full pages of text, the LaserJet would win the race.
So I just recreated my killer demo on my own system. I used Microsoft Word 2004 on my PowerMac Quad G5 2.5Ghz computer with 4.5Gb of RAM, a 1Tb RAID 0, the printer is an antiquated HP LaserJet 5MP. I figured the bottleneck would be the printer, it's at least 10 years old, but it has a fancy EtherJet module and lots of extra RAM, it should be comparable in speed to an average home-office laser printer. But it is a PostScript printer, which adds lots of processing overhead, so I used a standard Courier font that is resident in the printer, I won't have to transmit custom fonts to the printer. I type as fast as ever, and the sample sentence is so short, so this will be a test of the hardware, not my typing skills.
I set the stop watch and banged out the letter in mere seconds, hit print, and waited for the page to eject. And waited. Total time: 40 seconds. Isn't progress wonderful?

December 22, 2006

IBM System/360 Green Card

I recently discovered a treasured artifact from my earliest days learning computer programming, an IBM System/360 Reference Data card, known as a "Green Card." This card dates back to about 1968, although I probably acquired it around 1970.

gc.jpg

I scanned the card and I'm making it available for download as a PDF (11Mb). It is rather large, both in file size and in dimensions, it would print at full size at over 25 inches wide, although it folded into a nice 14 page format. You could easily tell who was an IBM/360 assembly language programmer because they always had a Green Card tucked in their shirt pocket, right behind their pocket protector.

July 23, 2006

First Look: Microsoft's iPod Killer, iBob

A covert informant at Microsoft sent me a top secret picture of Microsoft's forthcoming digital audio player, the "iPod Killer."

iBob.jpg

Special thanks to Shelley Powers.

May 26, 2006

Apple Lisa Sales Marketing Binder - 1983

I have painstakingly scanned the original Lisa Sales Marketing Binder that was issued to Apple dealerships in 1983, and I am releasing it for download as a 204 page 33Mb PDF file. This was the sales literature I used when I sold Lisa computers at ComputerLand in Los Angeles, and I've kept it in storage for decades. Now it is time for this historic document to reappear and be reappraised.
This document was obviously produced on a Lisa, some pages were printed on a daisy wheel printer, some on a dot matrix, sometimes even a mixture of the two, using scissors and glue, and if you look really close, even some white-out and pen. The information was compiled from various technical and marketing departments, and includes scans of Apple's full-color brochures for the entire Lisa hardware and software line.

LisaOverview.jpg

I thought the most interesting part of this binder was the section on the Lisa's rivals. Apple produced a competitive analysis of the Lisa vs. computer and software systems from IBM, DEC, Corvus, Fortune Systems, and Xerox. It is a snapshot of high-end office computing in 1983, just before the Macintosh was released.
Apple promised a lot more than it could deliver with the Lisa, but it created the model for all modern personal computers. Even today, the Lisa design is still the fundamental user interface used in every personal computer. A lot of computer technology has been released in the 23 years since the Lisa shipped, but in many ways, it has never been surpassed.
Update: Over the first weekend of this document's release, it was downloaded over 46,000 times! Thanks to everyone who was interested in this little slice of history, now this information will live on forever, distributed across the internet.

May 21, 2006

Mac For Sale: PowerMac G3/400 U2W

I am offering the old Disinfotainment server for sale. I bought this machine in 1999 but due to several exceptional features, its performance has remained competitive with modern Macs, and it has been exceptionally reliable. I don't want to sell through eBay so I am offering it for sale directly through my website.

yosemite.jpg

This is a "Yosemite" Blue & White PowerMac G3/400 U2W model, an original Rev 1 model with the rare Apple-supplied Adaptec 2940 Ultra 2 Wide SCSI card, and high speed SCSI hard disk drives. SCSI drives are legendary for their high quality and long lives. These drives have been bulletproof, and still have a long life expectancy. I added an Atlas 10K 8.5Gb hard drive, it has exceptionally high performance due to the 10k RPM speed. It also includes a 9Gb Viking II drive, and an IBM 18Gb drive, for a total formatted capacity of 34Gb. The Atlas 10K drive is an ideal boot drive, giving high performance in server functions. I only have 768Mb of RAM in the machine, but that seems adequate for server use. This machine would make an ideal web server, it can easily saturate a T1 line.
One other unusual feature in this Mac is a GeeThree Stealth Serial Port. This could be useful for remote monitoring of routers. Other than that, this Mac is pretty plain, it has a standard CDROM (4x I think), no CD burner, and no Zip drive or other options.
I can deliver this machine preformatted with MacOS X 10.4, and if you like, I can preconfigure Darwin Streaming Server. Somewhere in storage I have the original keyboard (in good condition, I never used it), and even the terribly unpopular "puck" mouse. You can have the keyboard and mouse if you want, but I doubt you'd want them.
It makes me sad to see such a wonderful piece of Mac hardware go unused, so I'd like to sell it to someone who will give it a good home and put it to good use. I'm not sure what this machine is really worth, I'm sure it's not worth a lot, so I'll consider any serious offer. You can contact me via email at ceicher (at) mac.com if you'd like more information.

April 3, 2006

Computing With A #2 Pencil

For many years, I've told people about how I first learned how to write computer programs by writing on Hollerith Cards with a pencil, but nobody ever believes me. But now, thanks to some research by local computer historian Douglas Jones, I have proof. This card was known as a "Mark Sense" card, you would fill in the little rectangles with a #2 pencil, and the optical card reader would sense the marks.

iowaopt2.jpg

Sometime around 1968, my math teacher got a grant for some computer time on the University of Iowa mainframes and decided to teach a few of us how write simple FORTRAN programs. In those primitive times, computers used Hollerith cards for input, but obviously it was impractical for little kids to use keypunch machines. So we used Mark Sense cards, painstakingly filling out the little cards with a #2 pencil. It was quite difficult to use the cards accurately, we would often spend as much time correcting input errors in the cards as debugging the programs. It was incredibly frustrating to write a whole program correctly, and then receive no output because you filled in one wrong spot and wrote "PRINL" instead of "PRINT."

March 4, 2006

Dead Inkjet

While I'm on a roll, I thought I'd complete the dead hardware trifecta, and whine about my dead inkjet printer. My Epson 1520 died in the stupidest possible way. The printer mechanism works fine, but the safety interlock is broken. The interlock is designed to shut down the printer when you open the lid, so you don't injure your fingers by sticking them into the mechanism while it's printing. Every time I turn on the printer and it complains the lid is open, and refuses to print.
I suppose I could disassemble the printer and bypass the interlock, but I think I'll just toss it in the trash. The 1520 is a wonderful printer, it's the last 11x17 CMYK printer Epson made, so it's perfect for prepress proofs. The new generation of 6 and 8 color printers are way too good for prepress proofs, they don't produce realistic CMYK proofs, they're too saturated and bright.
But there is no sense in beating a dead horse. Epson no longer makes drivers for this printer, you have to use CUPS, which is included free in MacOS X, but it isn't very color accurate. Time to send the old beast to the graveyard.
Fortunately my ancient HP Laserjet 5MP is still going strong. I don't even remember when I bought that printer, I think it dates back to the 1980s.

Dead CRT

My beautiful Sony sf300 20 inch CRT just died. This isn't too surprising, the CRT was acting cranky but I was hoping it would last a few more months before it died. This was the worst possible time for a sudden breakdown. I'm right in the middle of a project, so I had to run out and buy a replacement monitor. Saturday night at 8PM is not a good time to shop for a new monitor. The only place that was open was Best Buy, and I've never ever been satisfied with any product I bought at Best Buy. But I really didn't have much choice, so I bought a cheap 17 inch Samsung LCD.
I hate LCDs, I prefer a CRT for critical color work. Back when I bought the sf300, it was extremely expensive, a top-end monitor designed for color calibrated work. Its color was always very accurate, even up to the moment it died. I think I bought the sf300 around 1993 so I suppose it had a good, long life.
The Samsung LCDs are supposedly the same LCDs used in Apple Cinema Displays, but I've seen the big 30 inch Cinema display and the text is a hell of a lot clearer than this Samsung. You get what you pay for. And this is what is most disappointing, I had to spend money I was reserving for a new system. I've been thinking of buying a new PowerMac Quad G5 and a 30 inch Cinema Display, but I wanted to wait a couple more months. I had a great scheme, I can register as an Apple Developer for $500, and buy a quad G5 and a 30 inch display for a huge discount, I think I recall pricing out systems with discounts as high as $1800. So an Apple Developer registration really pays off if you plan on buying a high-end system, you spend $500 and get back $1800.
But this was an emergency, I wanted to get back up and running fast. I was prepared to buy just the 30 inch Cinema Display, even without the Developer discount, so I called the nearest Apple Store. If they had a video card capable of running the Cinema Display on my old MDD dual-1Ghz G4, I would have bought it and picked it up in the morning. But there is only one video card that can do the job, and they didn't have it. That Radeon 9800 Pro card costs $250, almost as much as this cheap Samsung LCD display. The fastest I could get a 9800 card was Tuesday, by mail order. Oh well, so much for that idea.
I was hoping I'd get over the next few weeks and then splurge on a new system, I figured I should buy one last PowerPC system to get me past the Mac Intel transition. I was hoping to move out of Iowa and buy the system once I got to a new residence, to avoid having to move more hardware, but now I'm not sure what to do. I don't really want to buy a $250 video card for an old machine, when that's almost 10% of the price of a new machine. So Monday, I guess I'll call up Apple and become an official developer, and get a new system, and then I can return this piece of crap LCD to Best Buy.

February 17, 2006

Computers Never Make Mistakes

Back in the early 1970s when I just started learning computer programming, using a computer was a much different process than we use today. First you'd write down your program on paper, then you'd type your program onto punched cards, then you'd hand the deck of cards to the computer operator. In a few hours, you could pick up a printout of your program's results. Quite often your program wouldn't work and all you'd get was a couple pages of incomprehensible error messages. To learn what the error messages meant, you'd go to the desk at the back of the keypunch room, where a 60 foot long rack contained all the documentation for the IBM 360 computer series. Imagine a room with an entire 60 foot long wall lined with tables, and on top, 60 feet of documentation in racks placed side to side.



Trying to find useful, relevant data in this rack was like trying to find a single page in a book 60 feet thick. In fact, that's exactly what it was, and even worse, there were dozens of indexes spread throughout the 60 linear feet of documents, one index could send you to another index, which then referred to specific pages, which might then refer you to updates or errata inserted erratically throughout the rack. When the room was busy, there would often be several people reading different sections of the rack, taking notes, then moving to a different section, taking more notes, etc. Some sections of the rack were more useful than others, and it was common to see people standing in line behind someone, waiting to use that section of the rack.
There were only a few people who knew the entirety of the documentation, a few Comp Sci grad students who had to maintain the racks by inserting the monthly updates and errata. It must have been extremely tedious to insert updated pages throughout the 60 foot rack, but in the process, they learned where all the useful information was.
These same grad students also worked in the "debug room," which was a small office where you could ask for help interpreting your program errors. People would line up in the hall outside the office, waiting to seek advice from "the debugger." The debugger had a short rack on his desk containing a master index of the big 60 foot documentation rack. He would look at your program printout, and if the problem was not obvious, he'd look through the index, and refer you back to a specific document in the big rack. Then you'd go back and read some more documentation, figure out what went wrong, then you'd punch a few cards to correct your program error, search through your card deck to switch a few cards, and resubmit your program. And the cycle would start all over again.
The one thing I remember most vividly about the debug room was a big sign hanging on the wall, it was the first thing you'd see upon entering the room. The sign was written on a computer pen plotter, in an oddly machine-like character set, it said:
Computers never make mistakes. All "computer errors" are human errors.
Even today, this is the hardest thing for computer users to understand. If a computer does not give you the results you expected, it is because you gave it bad instructions. Computers follow your instructions faithfully, and will accurately produce the incorrect answer that you incorrectly specified. In those olden days, computers were not so fault-tolerant, if your program had errors, it would stop and produce nothing but an error message. But modern computer programs anticipate that their users might be idiots, and are designed to gracefully handle even the most stupid, nonsensical requests. I suspect this is a very bad thing. It allows people to get results even if they are imprecise. I think it would be better to be strict, returning no results in response to vague inputs.
At the risk of offending a dear friend, I will use him as a case in point. I have a friend who often asks me for technical support, but his phone calls sometimes take hours, primarily due to his vague descriptions of his problems. He'll phone me up and say things like "I'm trying to print, but I press the whatchamacallit and nothing happens." No, I'm not using the word "whatchamacallit" as an euphemism, he really does say "whatchamacallit." When I object to his vague descriptions, he says I'm supposed to anticipate what he is doing because I know the programs so well. This is precisely NOT how to get good help. If I don't know precisely what you're doing wrong, how can I tell you how to do it right?
To use a computer and get good results, you must operate it with precision. But first, you must think with precision. This is no different than any other complex task in life. Human beings are not used to thinking with precision. This is why it is easier to fix computers than to assist users in operating them. Computers always give you a precise report on what they are doing. Users often don't know what they are doing.
After decades of providing tech support to thousands of computer users, I made an observation that I have formulated as a new law, I call it "The Law of Infinite Stupidity." It states:
There are a finite number of ways to do something right. But there are an infinite number of ways to do something wrong.

January 9, 2006

A Response to Kevin Marks' Anti-DRM Argument

Kevin Marks recently posted an argument against Digital Rights Management on his weblog and apparently has submitted it to a working group in the British House of Parliament. When I read his argument, I was astounded. The entire argument is founded on an error, a miscomprehension of a fundamental theorem of Computer Science.
I could summarize Marks' statement into two basic arguments:
1. DRM is futile, it can always be broken.
2. DRM is a perversion of justice.
Marks opens his argument with a huge misstatement of facts:
Firstly, the Church-Turing thesis, one of the basic tenets of Computer Science, which states that any general purpose computing device can solve the same problems as any other. The practical consequences of this are key - it means that a computer can emulate any other computer, so a program has no way of knowing what it is really running on. This is not theory, but something we all use every day, whether it is Java virtual machines, or Pentiums emulating older processors for software compatibility.
How does this apply to DRM? It means that any protection can be removed. For a concrete example, consider MAME - the Multi Arcade Machine Emulator - which will run almost any video game from the last 30 years. It's hard to imagine a more complete DRM solution than custom hardware with a coin slot on the front, yet in MAME you just have to press the 5 key to tell it you have paid.
Unfortunately, Marks has completely misstated the Church-Turing Thesis. It is a general misconception that the Church-Turing Thesis states that any computer program can be emulated by any other computer. This fallacy has come to be known as "The Turing Myth." This is a rather abstract matter, there is a short mathematical paper (PDF file) that fully debunks the misstatement Marks uses as the fundamental basis of his argument.
To cut to the core of The Turing Myth, there has come to be a widespread misunderstanding that The Turing Thesis means that any sufficiently powerful computer can emulate any other computer. The Turing Thesis is much narrower, in brief, it states that any computable algorithm can be executed by a Turing Machine. This in no way implies that any computer can emulate any other computer. Perhaps Turing inadvertently started this misunderstanding by a bad choice of nomenclature; he labeled his hypothetical computer a "Universal Machine," which we now call a "Turing Machine." However, a Turing Machine is not a universal device except in regards to a limited spectrum of computing functions.
One joker restated the Turing Thesis as "a computer is defined as a device that can run computer programs." This may seem obvious now, but in Turing's day, computers were in their infancy and the applications (and limitations) of computers were not obvious. As one example of these limits, there is a widespread category of "incomputable algorithms" that cannot be computed by any computer, let alone a Turing Machine. For example, a computer cannot algorithmically produce a true random number, it can only calculate pseudo-random numbers. This fundamental application of The Turing Thesis has founded a whole field of quantum cryptography, encoding methods based on incomputable physical processes, such as random decay of atomic particles. Quantum cryptographic DRM would be unbreakable, no matter how much computer power could be applied to breaking it.
I contacted Marks to inform him of the Turing Myth, in the hopes that he might amend his argument, since it all springs forth from a fallacy. He responded briefly by emphasizing the case of emulating MAME, and cited Moore's Law. Apparently Marks is arguing that since computers are always increasing in power, any modern computer can break older DRM systems that are based on simpler computers. He also appears to argue that emulated computers can simulate the output device, and incorporate a device to convert it on the fly to an unencrypted format, for recording.
Unfortunately, Marks chose a terrible example. The original game systems that are emulated by MAME had no DRM whatsoever. It was inconceivable to the game manufacturers that anyone would go to the trouble and expense to reverse-engineer their devices. The code inside these game systems was designed to run on a specific hardware set, any identical hardware set (or emulated hardware set) could run the unprotected code. At best, these devices used "security by obscurity," which any computer scientist will tell you is no security whatsoever.
Ultimately, DRM systems must not be so cumbersome as to be a nuisance to the intended user. This has lead to a variety of weaker DRM systems that were easily broken, for example, the CSS encryption in DVDs. However, this is no proof that truly unbreakable DRM is impossible or unworkable. As computer power and mathematical research advances, truly unbreakable DRM will become widespread.
Having dispensed with Marks' first premise, let us move on to the second, that DRM is a "perversion of justice." I cannot speak to British Law, as does Marks, however it seems to me that his arguments invoke the aura of British heroes like Turing and Queen Anne, to pander to unsophisticated British Parliamentarians. While his remarks are addressed to Parliament, he has attempted to argue from "mathematical truth" that DRM is futile. I would have expected that his legal argument would have attempted to base itself on more universal international copyright agreements, such as the Berne Convention. But I will not quibble over the scope of the argument, and instead attempt to deal with the argument itself. Marks states:
The second principle is the core one of jurisprudence - that due process is a requirement before punishment. I know the Prime Minister has defended devolving summary justice to police constables, but the DRM proponents want to devolve it to computers. The fine details of copyright law have been debated and redefined for centuries, yet the DRM advocates assert that the same computers you wouldn't trust to check your grammar can somehow substitute for the entire legal system in determining and enforcing copyright law.
It appears that Marks' fundamental complaint with DRM is that it puts restrictions in place that prevents infringement before it occurs. Current copyright laws only allow the valid copyright-holders to sue for damages after infringement occurs. Marks asserts this prior restraint is a violation of due process. However, he is mistaken, the DRM end-user has already waived his rights. When a user purchases a product with DRM, he is entering into a private contract with the seller, he explicitly accepts these restraints. If the user does not wish to subject himself to these restrictions, he merely needs to reject the product and not purchase it, and not enter into that contract with the seller.
I can find no legal basis that would prohibit the use of prior restraint in private contracts. It would seem to me that this would be a common occurence. For example, I might sign a Nondisclosure Agreement when dealing with a private company, agreeing that I would not disclose their secrets. A company might even distribute encrypted private documents to NDA signatories.
Ultimately, Marks' arguments do not hold up to scrutiny. They are based on false premises, and thus cannot lead to valid conclusions. Let me close by following Marks' answers to the questions posed by Parliament:
Whether DRM distorts traditional tradeoffs in copyright law. I submit that it does not. It merely changes the timing of the protection afforded by copyright law. It merely prevents infringement before it occurs, rather than forcing the copyright-holder to pursue legal remedies after the infringement occurs.
Whether new types of content sharing license (such as Creative Commons or Copyleft) need legislation changes to be effective. Current copyright laws are effective in protecting individual artists as well as corporate interests. Amendments to private distribution contracts such as CC or Copyleft are unproven in court. There is no compelling reason to change current copyright laws.
How copyright deposit libraries should deal with DRM issues. Since all DRM-encumbered materials originated as unprotected source material, it is up to the owner to archive this material as they see fit. Certainly the creators and owners have no reason to lock up all existing versions of their source material, this would impede any future repurposing of their content. Since a public archive of copyrighted material has no impact on the continued existence of original source material, it is up to the libraries to establish their own methods for preservation of DRM playback systems.
How consumers should be protected when DRM systems are discontinued. How were consumers protected when non-DRM systems were discontinued? They were not. I cannot play back Edison Cylinder recordings with modern equipment, yet I could continue to play them back on original Edison Phonographs. Vendors can not be required to insure their formats continue forever, this would stifle innovation.
To what extent DRM systems should be forced to make exceptions for the partially sighted and people with other disabilities. Disabilities are as varied as the multitude of people who have them, no DRM system could possibly accommodate all disabled persons. Some accomodations make no sense, for example, an exhibit of paintings or photography will always be inaccessible to the blind. "Accessibility" is a slippery slope, there will always be someone who complains they need further exceptions. Forcing owners to provide exceptions for disabilities will only lead to increasingly costly demands for accommodations upon content providers, which would stifle their ability to provide products for mass audiences.
What legal protections DRM systems should have from those who wish to circumvent them. DRM systems should be afforded protections available under whatever private contracts they license their work, just as the law exists today. End-users who are entitled to Fair Use already have the ability to request source material from the owners.
Whether DRM systems can have unintended consequences on computer functionality. This is a design issue, not a legal or political issue. Nobody can doubt that any computer program can have unintended consequences.
The role of the UK Parliament... I abstain. Parliament is not my bailiwick.

In summary, I believe that Marks' argument is based on two fallacies, and that his conclusions are based on a political wish, not a legal or technical argument. DRM is a compromise, some people (even me) may consider it a poor compromise, but I cannot see any technical or legal reason to burden content providers with even more ill-conceived compromises.

December 3, 2005

A Really Great Bad Day

A few days ago, I got a frantic email message from a programmer and blogger I know. She mass-mailed her whole circle of friends with a desperate message, something like "The crossbeam's gone out of skew on the treadle, and it will take several days of work to get the server back working again! I won't be able to answer email until I get this solved! I am having a REALLY BAD DAY!"
You have got to be kidding me, a bad day? Surely this is the sort of technical challenge that some people live for. It is all a matter of perspective. This is when you get to show your true mettle, solving a technical problem that few other people could understand, let alone solve. It should be a great day!

November 25, 2005

QWest Sucks More Than Ever

QWest, as the local telecommunications monopoly, has given me so much grief over such a long time, it is hard for me to remember a time when QWest didn't suck. But today, QWest actually delivered something I spent months begging them to deliver, but was refused. And it clearly shows that QWest sucks more than they ever sucked before.
If you have followed my blog in recent months, you know that I moved my office, and when I arrived at the new location, I discovered that QWest DSL was not available. It never even occurred to me to check availability before moving, since DSL is deployed throughout this entire city.. except in THIS neighborhood.
I did a lot of research, pushing my complaints up through middle levels of QWest management, and was consistently told that DSL would not be available, they COULD provide it, but would NOT provide it. Reports from QWest's DSL technicians indicated there was a new DSLAM installed a mere 8 blocks from my home, but QWest would not connect any users to it. The service was available, DSL techs were ready to install it, but management would not permit anyone to purchase the service and connect to the new DSLAM. The last manager I spoke to at QWest was almost psychotically rude, she took special pains to be as abusive as possible to me, despite my attempts to be as polite as possible (after all, I was begging them for service).
So today, this morning at 9AM, as I was just getting up and making coffee, a bit fuzzy after a late night of work, I get a phone call. Oh joy, it's a QWest telemarketer asking if they can look at my account and see if they can find any way to "serve me better." I bite my tongue to suppress the urge to blurt out all the DSL backstory, and tell the guy, "Look, I never use this land line, I use my cell phone for all my calling, I'm thinking of disconnecting it entirely. The only thing you could do for me is to hook me up with DSL." The guy says he'll check availability, I told him don't bother, I just spent 4 months trying to get DSL and QWest always told me no. He looks it up in his computer, surprise surprise, DSL is available in my location! I refused to believe it, so I went to my computer, looked it up on their website, yes it is available!
Now instead of being happy I can get DSL again, I am absolutely infuriated. It proved that QWest could have hooked me up 4 months ago, but they refused for no reason whatsoever. I'm probably going to move out of here within 2 or 3 months, so I will only be using this service for a short time, when I could have been using it all along.
Now that I am scheduled for DSL installation on December 5, I will be able to restore BlogTV service. I needed DSL with high upstream bandwidth and 2 static IPs, in order to deliver video from my QuickTime Streaming Server. This was impossible with my current cable modem connection. But it is not worth it to restore service if I'm just going to move in a couple of months and go through this all over again. It is time for me to move this blog and the QTSS server to a professional hosting service.
If there is one thing I learned doing years of customer service, the worst thing you can ever do is screw your customers in a way that makes your them look bad in front of THEIR customers. And that is exactly what QWest has done to me. They refused to deliver DSL when they could have, causing my archives of video stories to stop working. Years of my work were taken down, making me look bad. I recently noticed a couple of articles about video blogging cited my website, even after the video server went down. But when readers clicked on the links to my videos, they got nothing but an error message, I looked like an idiot, and the article writers looked like an idiot too, for citing a dead link. This is the sort of thing that makes me totally dispirited about publishing ANYTHING.
But no more. I am now determined to be totally free from QWest and their incompetence. I will be using QWest for my home connectivity, but only for the short term. I am determined to move this blog to a bulletproof hosting service NOT through QWest. And I am determined to resume writing and posting videos as often as possible once the transition is complete. I have several long videos recorded and ready to post, as soon as I can get the video server up and online. But it's going to take a bit longer, if I'm going to do this right. So bear with me, this transition may be a little rough, but this blog will be better than ever. I promise.

October 31, 2005

Thermodynamics

Sometimes you can change a bit and suddenly everything is different. I literally changed one binary bit, I poked one button on my computer, and years of misery ended instantly.
If you are one of the few people who have ever been in my office, you probably remember one thing in particular: it is unbearably HOT. Computers kick out a lot of waste heat, my PowerMac is especially hot. This particular model is known by the nickname "wind tunnel," it is notorious for the noise of the high powered fans it uses to vent all the heat. And all the heat goes out into my tiny office.
I recently moved into a new apartment, and relocated all my computer equipment into my new office in the second bedroom. When I put the utilities account in my name, the company said the August bill for last year was only $50, but when I got my first bill, it was $150! Either the previous tenant was exceptionally frugal and never ran the air conditioning, or else my computers were using a lot more power than I ever suspected.
I did a bit of research, discussed the problem with a few people, and the general opinion was that the computers didn't really consume that much electricity, the big energy cost was the extra air conditioning to cool the excess heat the computers generate.
In the course of this discussion, someone suggested I look at an old software hack for my machine, called CHUD. It is an old Apple developer utility that adds "processor nap mode," it sleeps the processor between cycles during times of low CPU demand, reducing power consumption and waste heat output. I installed it and miraculously the chip temperature dropped by nearly 30 degrees Centigrade, and the exhaust heat dropped to tolerable levels. I just poked the button and suddenly my office was cool again! The air conditioning stopped running all the time, I haven't received my latest utility bill yet but I expect it to be considerably lower.
I rarely reboot my computer, so about a week later when I installed some new software and restarted, I didn't think anything about it. But about an hour later, I felt like I had a fever, I was burning up. At first I thought I caught a cold or flu, but then I checked the computer's temperature sensors and discovered it was running hot again. Nap Mode isn't persistent across reboots, you have to poke the button after every reboot. That's not such a big deal since I usually run for weeks and even months without rebooting.
But alas, this story has a sudden surprise ending, unexpected even by me. As I was writing this story, in the background I was installing the latest update to MacOS X, version 1.4.3. Unfortunately, Nap Mode is now disabled, and my office is getting hot again. I am trying to get CHUD to work again, but it appears to be impossible. Oh well, it was nice while it lasted.
Update Nov 1, 2005: I got it working, and my office is cool again. A few years ago, I wrote a new variant of Murphy's Law I call "The Idiot's Law," and this is a perfect example. I asked for help with CHUD from the Accelerate Your Mac website. They published my plea for help, and then suddenly Nap Mode spontaneously started working again. The Idiot's Law: Whenever you ask for tech help in a public forum, your problem suddenly resolves itself in a way that makes you look like an idiot.

August 27, 2005

MovableType 3.2 Upgrade Completed

I just upgraded the server to MovableType 3.2. It wasn't quite as painless as some upgraders have claimed. I had one little glitch, but that's mostly because my configuration is rather old and crufty, it goes back to the early days of MT, I think even before version 2. Oh well, everything should be running OK now (with the exception of the video server, which is still down).
I am considering moving this blog to a ISP-hosted server, so I can use their video server. I am just waiting for a response from their tech support, to see if I can point my current domain to their server. I think it might be time for me to buy a real domain name for this blog, but I don't want to break any old links, so I'm trying to set up a clever way to forward all the old links to any new domain I register. I know how to do it, I just don't know if the ISP will allow me to do it.

July 26, 2005

Oh Crap, No DSL!

I just rented a new apartment, and while arranging the utilities hookups, I discovered that it's not certified for DSL availability! I wouldn't have rented this apartment if I had known I couldn't get DSL, I guess I should have checked it out in advance. But it never occurred to me that such a common service would be unavailable in the middle of a metropolitan area.
QWest says the apartment might be OK for DSL, but they won't know for sure until they send a lineman to hook up the phones and check the lines. So I might be stuck with a cable modem, which could make it impossible to run this server properly. I might have to migrate the server contents to a professional hosting service, which would not be cheap since there aren't many affordable hosts for QuickTime Streaming Server, one of the key features of this site.
I expect the server to go offline temporarily within the next week, while I move the CPU to my new apartment. There is a possibility that this server may be offline longer than expected, or resume service with some high-bandwidth features disabled. Stay tuned for more developments.
Update August 2, 2005: QWest officially says DSL is not available at my location because I am too far from their switching facility, so they did not even bother to send a lineman to test my lines. However, there are multiple reports from QWest customers on the same block as my apartment that DO have DSL. There is even one report that QWest installed a new DSLAM only 8 blocks from my apartment, so I am definitely not too far away to get service. Everyone says QWest DSL is available, except QWest. I'm still trying to get QWest to recognize that they built new facilities specifically to expand service in my area, but they just don't believe me. The problem is, the QWest offices are in Seattle and Denver, they know nothing about the local network here in Iowa.
Update August 3, 2005: I called QWest DSL tech support under my old account, to see if they could do anything for me. The techs said they can look up my new location in their "circuit database" and it shows my apartment is qualified for DSL, and there is an available "pair" (copper wires) ready to install the service, IF I can get a QWest lineman to go out and check the line quality and give the approval. And they're sure it would work, IF we can just get the "line conditioning" work done. But he also says that the QWest sales database will NOT show the location as OK for DSL, so they won't even send out a lineman to check it out, and on top of that, QWest Sales says they won't do line conditioning anymore. I am at an impasse. QWest CAN sell me DSL, but they WON'T. This is ridiculous.

July 24, 2005

iPod Requires Native USB2

I solved a minor oddity with my iPod Mini. Every time I put my Mac to sleep with the iPod attached via USB2, when I wake the machine, I get an error message that one of the drives (the iPod obviously) was not disconnected properly. This actually corrupted the iPod disk once, but that's not such a big deal, just reformat, reload, and it's back in operation.
I finally figured out that iPods require a native USB2 port. My PowerMac MDD dual-1Ghz only has USB1 so I added an Adaptec USB2 card. Unfortunately, that isn't good enough, you must have a USB2 port that is built in to the machine, an aftermarket USB2 card won't work. The iPod Mini only comes with a USB2 cable, so I bought the inexpensive iPod Firewire cable, not the expensive dual FireWire/USB2 cable, just the plain old FireWire cable.
Now everything works fine. When my Mac goes to sleep, the iPod automatically disconnects, and reconnects when the CPU wakes from sleep. I must have read this somewhere, I don't recall where, it's pretty obscure, so I figured I'd post it so if someone is Googling for info, they could find it out easily.

July 12, 2005

My Email Address is Changing

I am about to lose my oldest email address, an account I have maintained for over 10 years. I just received notice from my ISP that they have lost control of the domain name that contains my address (how did that happen?!?) so I will have to move my account to a new domain. I have other email addresses, so I guess I will discontinue that account entirely. This means I'll probably lose contact with some people that only know my old address, but on the other hand, this account is so old and well-known that it attracts a ton of spam. So you win some, you lose some.
My email address ceicher@inav.net will be deactivated as of July 31. You can continue to contact me at my other account, I'll have to put it up here in a slightly cryptic format so spammers don't harvest it from