Tag: Windows

Nomenclature

I have come to absolutely loathe it when people refer to the Web as "the Internet" -- as in, "E-Mail's not working, but the Internet is."

This is, of course, like so many problems in the wonderful world of computers, entirely Microsoft's fault.

Seriously. Internet Explorer? What the fuck is that? It's an effing Web browser. I guess I can get "Explorer" as a synonym for "Browser" (remember, these are the same guys who had to change "Trash" to "Recycle Bin" and "Bookmarks" to "Favorites"), but "Web" and "Internet" are not synonymous, and fuck you guys for making everybody think they are.

Do you know how many people don't know what a Web browser is thanks to that nonsense? If I had a nickel for every time I'd told somebody to open her browser and heard "How do I do that? ...Oh, you mean I go to the Internet," I'd probably have enough money to buy Windows Vista Ultimate Limited Numbered Signature Edition (though not nearly enough to buy hardware to run it on).

And guess what? Microsoft is now trying very hard to obfuscate things even further by slapping the word "Windows" in front of everything. So now it's not just Internet Explorer anymore, it's Windows Internet Explorer (ironically, they picked this name right as they decoupled the program from Windows Explorer -- which, oh yeah, they repeatedly claimed was impossible during that whole antitrust suit thing).

I used to work at a university computer store, and not a day went by but somebody came in who didn't know the difference between Windows and Office. And it's shit like this -- like Windows Internet Explorer -- that is directly responsible for people not being able to understand the difference between an operating system and a fucking Office Suite -- or, in this case, an operating system, a Web browser, and the Internet.

At least they're not calling it Windows Office -- yet.

Tunnel. Light.

Think I'm finally done fixing Grandma's computer. Well, in point of fact, it's working just fine now, but until it's sitting on her desk and still working, I'm not going to jump the gun and call it finished. "It should be finished by the end of the day" has been my battlecry for the past three weekends, and this time I'm going to exercise caution rather than get my hopes up. Something could somehow go horribly wrong between now and my next trip to Scottsdale (which I'm figuring for Saturday).

I found that, even wiping the drive, I could not get Windows to boot. Error loading operating system, every time. And, as previously mentioned, the disk was flagged as bootable.

So yesterday, for shits and giggles, I tried installing Linux on it instead.

And it worked. It booted, no trouble.

Yet, when I reinstalled XP again, it was back to refusing to boot.

So I hatched a plan. I decided, y'know, Grandma only used about 8GB of her 80GB hard drive even when she had it packed to the gills with 8 years of files, so on a clean install, I can easily set a few gigs aside for a Linux partition. I decided to set up a Linux partition (well, two, really, one ext3 and one swap) at the front of the drive -- I could've done a Puppy-sized 256MB, but decided to stretch it out to 5GB just so I could stretch out and have a good, full Linux install for troubleshooting the next time Windows goes haywire -- and fill the other 75GB with Windows. I figured I'd set GRUB up to automatically boot Windows and leave the Linux boot invisible.

Turns out I didn't even have to reconfigure GRUB -- when I installed XP, it overwrote GRUB with its own bootloader, and this time, for reasons which I cannot fathom, it actually worked. I mean, this points to some kind of oddity with the MBR and/or boot sector, but beyond that I have no idea why adding a dual-boot fixed the problem.

And that, I think, is the most important dirty little secret among people who fix computers -- half the time we don't know why what we just did worked. Hell, I consider myself lucky that I even know what I did this time, even though I don't know why it worked. Frequently I find that something starts working again and I don't even know what I did to change it.

I'm half-convinced this is some sort of Uncertainty Principle thing and I just have the touch. Which sounds cool, but I'd rather computers -- and Windows in particular -- just behaved rationally.

Stay Grounded

The latest hilarious chapter in the Fixing Grandma's Computer saga is that the new CD-RW drive I bought her at Fry's turned out to be bad. I exchanged it for a good one, but discovered on getting home that I had left my Knoppix CD in the one I returned. Which is probably all right, since it was Knoppix 3.9 and I'm overdue for an upgrade anyway.

But the whole process is just one disaster after another, and I don't have the tools I need. This must be how Fred Flinstone felt when he tried to fix his computer. With, I can only assume, some sort of small bird with a skinny beak -- possibly a hummingbird; I imagine that a hummingbird would be a very difficult bird to use as a screwdriver, but "very difficult" is sort of what I'm going for with this analogy -- and, assuming Fred is a Mac user like everybody else on TV, a paper clip.

I am, of course, burning a new copy of Knoppix; I tried to use the ExpressCD program that came with my old copy of Ultimate Boot CD but it had approximately the worst interface I have ever seen in a CD burning program (yes, worse than xcdrecord -- much worse). It kept putting folders in places I didn't tell it to, and wouldn't let me move them.

I do believe my Windows XP disc is trashed, meaning that even once I back up Grandma's files, I can't install a new OS on her computer. (Well, I could install 98, but that would rather defeat the purpose of this whole exercise. Or I could install 2000, but the reason I'm switching her from 98 in the first place is that it's now unsupported, and 2000 is next on the chopping block.)

All in all, considering that Grandma doesn't do any kind of online banking or credit card transactions, really the worst-case scenario if her unsecure installation of Win98 had gotten a nasty malware infection would be...basically what's happened anyway. (Though I suppose her CD-ROM was going to die no matter what.) Live and learn, I guess. I'm never doing a Windows update again. I mean it this time. Fool me once, shame on, shame on you... ... ... ... ...fool me can't get fooled again.

Oh, by the way, I've disabled trackbacks, since nobody but spammers was using them anyway. If you really really want me to bring them back for some reason, let me know.

(Also, is it bad that my favorite part of work is now driving?)

Keep Hydrated

Yeah, this is going to be one of those where I talk about living in the desert.

There's a lot I love about the desert. Oh, sure, it's a hostile environment, particularly to pigment-challenged individuals of Irish Honky descent such as myself, and sure, those same honkies who have the least resistance to the sun's rays have decided for some reason to fill this region with concrete and asphalt to make it that much more unbearable, but there are still some very pretty things to be seen.

I've spent a few hours over the past couple of weeks handing out flyers for our company. I hate to be one of those guys who waves his degree around, but that's really not what I got it to do. But we need business, and there are a hell of a lot of new businesses opening within a mile radius of here, and the boss thinks I should be the guy who hands flyers out, so that's part of what I've been doing.

The first day, I overdid it: I thought I had sunscreen, but it turned out I didn't. Must not have packed any when I moved in February (which, all things considered, makes sense). So I went out and handed out flyers for three hours and got good and sunburned and chafed. I spent Memorial Day Weekend unable to walk comfortably. I am amused by the mental image of the tableau of a very sunburned guy going up to the counter at Target with sunscreen, aloe gel, and talc in his basket -- no explanation necessary.

Since then, I've limited myself to 90 minutes of flyering a day, and of course it goes without saying that this 90 minutes must be complete before 10 AM because I'm not going out when there's an excessive heat warning in effect. But I haven't been out there the past few days because things have been so busy at the shop. Mixed blessing -- I'd rather not be out there handing out flyers, but at the same time if I don't find time for it soon the boss is going to yell at me again.

I don't like sunscreen. It's greasy, smelly, and invariably gets in your eyes, even if the label proclaims it's non-greasy, unscented, and sweat-proof. But it beats being baked alive.

Dad also leant me a hat which once belonged to a family friend who died of cancer. I think that's pretty cool.

And handing out flyers isn't all bad. I dig the desert landscaping surrounding most of the buildings. Often I will hear a rustling in the bushes and see a large lizard come out.

Meantime, I haven't had much time to relax when I've been home from work -- work on a computer all day, go home and work on a computer. See, my grandma's been rocking Windows 98 for the past 8 years, and since Microsoft has ended support for it, I decided I should probably upgrade her to XP.

Have you caught the mistake in my thinking?

That's right: the word upgrade.

Let me explain something. I have never had a Windows upgrade go well. 95 turned out to be incompatible with my processor, 98 hosed my filesystem (which is why there is no complete extant copy of KateStory IX), and XP hosed my partition table. ME...actually upgraded smoothly and gave me no trouble, but I think the fact that it installed Windows ME on my computer means it still did serious harm to my system.

So I should have known better. I shouldn't even have attempted the upgrade. I should have backed up her files to CD, wiped the drive, and done a clean install.

But I didn't. I attempted an upgrade. Which went fine until the reboot, at which point the installation hung. No error, just a hang at boot time.

So then I made my second mistake: I tried to use Recovery Console.

Specifically, I used fixboot. Which hosed my partition table. I wound up with what looked like a 10MB FAT12 partition with only one file on it. Knoppix showed more files, but they were all gibberish.

Daunted, I retreated to lick my wounds and study the problem before going back the next weekend to attempt a fix. I found a useful MBR tool on UBCD4Win, which got the filesystem looking good enough to run a chkdsk on. After that, the files were visible, but the damn thing still wouldn't boot no matter what I did or how many times I installed an OS on top of it. (And yes, the partition is set bootable.)

It was about this point where I hit the Eject button on the CD-ROM drive and it launched my CD across the room. It bears noting that this is not even a slot-loading drive, it's the kind with a tray. I have never seen anything like it in my entire life.

There comes a point in a project where you know you need to stop for the day. Seeing your Windows XP disc fly across the room is such a point.

So I brought the computer home to work on it here. (Grandma's is thirty miles from here, meaning I logged roughly 120 in my two round-trips this past weekend.) So far I've made little progress -- my flying WinXP disc does not look to be in very good shape; I made a copy of it last night but it took hours to do, so I'm betting there was some serious trouble reading the data on it. Hopefully it somehow made a good copy anyway. I haven't tried it today because I've been busy trying to revdep-rebuild my Gentoo install, because I can't upgrade KDE until I recompile a bunch of programs that used to have ungif support, which is now deprecated because the patent on the GIF algorithm finally expired. (You see what software patents do? Do you see?)

Also I bought Grandma a new CD burner. Now I'm trying to figure out how to get the mail-in rebate on it. It is possible that I did not pick up the appropriate form and will have to go back to Fry's to get it. The fun never ends.

All in all, it's been a stressful month. But on the plus side, I haven't been mugged by a hooker at knife-point, so I guess that means I know at least one guy who's had a worse month than I have. Hey, count your blessings.


Also, I don't intend to make a habit of mixing business with this blog, but I've been working on a website for a local musician named Devon Bridgewater at nuancemusic.org. Nuance Music (AKA Nuance Jazz Trio) is a local jazz group consisting of Devon, Dick Curtis, and Joel DiBartolo, director of jazz studies at my alma mater.

Anyway, I'm just throwing that link out because Devon's looking to drum up some publicity to his site, and unfortunately his Google page rank is pretty low right now, so he needs all the links he can get. So spread the word around, and, most importantly, link to his site. (I might add it to my links page if I ever drum up the courage to dust off the cobwebs and update the damn thing.)

Once again, that page is Nuance Music.

Hell, while I'm at it, Google hasn't even listed any of the other pages on the site, so here are links to them too: gigs, press, jazz, weddings, gallery, corporate clients, festivals, contact, Spanish.


Reading: A Scanner Darkly. Hoping the movie doesn't suck.

Playing: Suikoden 5. Basically at this point the series is openly hostile to newcomers -- this game took 7 hours to get interesting (still better than the 30 hours of 3 and the never of 4), and there's no way anybody would play that far without having a tremendous amount of goodwill left over from the first two games.

The Water Here Tastes Funny

As I near the close of my first week living in north Phoenix, I have made a few observations. The first is that the water here tastes funny.

Now, I must first note that I suspect Phoenix tap water is probably among the worst in the nation. Big, polluted city in the middle of the desert with water being piped in from Colorado and California with questionable clean water regulations. I'd probably be more comfortable drinking tap water in NYC (and I think I did at the drinking fountain in the Times Square Toys R Us), or pretty much any other major American city except LA.

As you might guess from the above presumably silly and useless "rant", I filter my water. But it still tastes funny. I expect I'll get used to it soon.

The other thing I've realized is that I hate going to Fry's. I hate driving there, I hate driving back, and I especially hate shopping there. In fact I think the only satisfying part of the whole experience is walking out the front door with my bag of purchases and taking it to my car.

What was particularly unpleasant about last night's trip to Fry's -- aside from the atrocious drivers I had to fight to get there and back -- was simply trying to find things. I recently got me an HDTV, and I'm trying to set it up with HD connections for my cable and my Mac Mini. My cable box has a DVI port rather than HDMI, so I picked up a DVI-to-HDMI adapter. Of course this only transfers video and not audio, so I needed to hook audio up separately. And apparently the HDMI connections on my TV only have digital coax inputs for separate audio.

There's a Radio Shack nextdoor to my apartment complex, so of course I poked my head in there on the off chance that they'd have a digital coax audio cable for under $30. No such luck, of course. Fucking Monster.

So I went to Fry's. Where they also primarily stock Monster, but at least seem to have a better selection than their Tempe counterpart. Not that I could tell at first, because I couldn't find the audio cable aisle, which is inexplicably in the section with a giant sign that says "VIDEO" above it, rather than the section with the "AUDIO" sign. It took me probably 10 or 15 minutes to determine this, as there were no available employees anywhere to be found and I wouldn't talk to them if there were. (I learned at the Tempe location only to speak with employees as an absolute last resort; it's possible that this location actually hires competent people but I'm not going to bet on it.)

Once I finally found the aisle with the audio cables, I was faced with the even greater difficulty of actually locating the cables I wanted. This was hard enough to do by sight, as composite video, composite audio, component video, and digital audio are only distinguished by the number of connectors, and sometimes not even that. (Color doesn't immediately help anymore, as apparently coloring the entire connector has gone out of style in favor of coloring each and every connector exactly the same but with a thin band of red, white, or whatever for color-coding. And if I'm looking closely enough to see what color the thin band is, I'm looking closely enough just to read the damn label on the packaging.) It took me a close inventory of the entire first wall to find a digital coax audio cable, and it was labeled as a subwoofer cable. I didn't know what the difference is between regular digital audio and subwoofer audio, if there even is one, and that upset me -- I'm not used to being in over my head when it comes to tech, and when I am, I can usually just punch up Google to find an answer. I was not thrilled at the prospect of buying the wrong cable and having to return it later -- Fry's is awesome for returning things, but I still don't like driving there and back.

Fortunately, I finally discovered some that were just labeled "digital audio coaxial cable" at the opposite corner of the aisle. The Monster ones were, obviously, too expensive, but there were some adequate-looking GE cables that were priced very reasonably (6' for $8, 15' for $15). The trouble was that all but one of them had been knocked off their hooks and were lying on the bottom shelf below the hooks at ground level. I almost didn't see them. I'm chalking this up to incompetence rather than malice, but it sure seems convenient that the inexpensive cables were so hard to find compared to the Monsters.

I picked up a copy of Sonic Gems while I was there because it was only $20 for a bunch of games that were released 10-15 years ago and should've been included on Sonic Mega Collection in the first place. It made me feel better about the whole nasty shopping experience, but the way I described it in the previous sentence makes it sound like it shouldn't. Oh well. I never actually had a Sega CD, so the only copy of Sonic CD I ever had was the awful Win95 port (featuring intro and ending movies that look like crap in 256 color but the game refuses to run at any higher color depth, and won't run on XP!), so it's nice to finally have a good working copy. And Sonic the Fighters won't run on MAME so it's nice to finally be able to play it. (I don't know if the game's actually any good, as again, I've never played it, but at least I finally get to check it out.)

Anyway. I'm almost done building furniture and unpacking stuff, so I should be able to turn my attention to getting all my various media devices hooked up any time now, and hopefully figure out how to get my wireless network card working under Gentoo so I don't have to stretch a network cable across the whole apartment.

That and getting used to the funny-tasting water will mean I'm finally home here.

But I still don't know if there's a difference between a digital coax woofer cable and a regular digital coax audio cable, and a quick Google search hasn't helped yet. If you know please feel free to enlighten me.

Mactel

To: David Lazarus, The San Francisco Chronicle

I am curious as to the motivation behind your "Intel inside -- so what?" article: are you really as ignorant and intellectually lazy as you come across in it, or did you just want the attention of being the only guy in the press with a headline saying it's not a big deal?

The point of the article seems to be "Most people don't care how something works, just that it works." Well stop the presses, what a scoop!

But David, SOMEBODY has to worry about the "how" or nothing's going to get done.

So what "what" does this "how" lead to?

There is an ABUNDANCE of information online that can tell you exactly why the Intel switch is important, and what its long-term effects may be, and a competent reporter would probably have done some research rather than consult computer industry experts like the administrator of a San Francisco law firm, a flight attendant from England, or Officer Gary Constantine of the San Francisco Police Department.

But, failing that, I will do my best to explain why the Intel switch is relevant.

I'm going to start out with some extraordinarily basic background on the computer industry here, as your article makes you seem blissfully unaware of it.

Apple makes computers. Macintosh computers.

But most people don't use Macs.

Most people use Microsoft Windows, which runs on Intel (and compatible) hardware.

(Now, you may have already made a connection here: "Oh hey, Apple's going to be running on the same hardware as Windows!")

The MacOS is almost universally regarded as superior to Windows in terms of ease-of-use and security.

So why do people still use Windows?

Well, in-between talking to flight attendants, you might consider walking into a computer store where someone is buying a Windows machine and ask that person why he isn't buying a Mac. I can guarantee you that at some point in the conversation, he will tell you he is worried his programs won't run on a Mac.

This stereotype has dogged Apple for twenty years, and is largely unfair: anything the average user needs, be it Web, E-Mail, or Microsoft Office, will run on a Mac.

However, there ARE some power users whose programs DON'T have Mac versions: engineers who need AutoCAD, for example, or gamers. (And before you pooh-pooh gamers as a niche market, consider that they're the people who buy the most expensive computers -- with the possible exception of movie editors, who are already firmly in the Apple court.)

Now, why isn't there a Mac version of AutoCAD? Why aren't there Mac versions of many popular games? Well, it's largely because of the hassle of porting them to a new architecture.

You get that?

The hassle of porting them to a new architecture.

But with Macs switching to Intel, the MacOS is now running on the SAME architecture as Windows does.

Making it much, much easier for these developers to release their software on the Mac.

And even if they don't release their software for Mac, this makes it far easier for third-party developers to make software which will allow Windows programs to run on a Mac. Take Microsoft's VirtualPC, for example, which has heretofore run programs very slowly and lacked advanced hardware support because it's had to emulate Intel hardware -- that hurdle is now gone. Or take Cedega, a program for making Windows games run under Linux -- a Mac version was impossible on the PowerPC architecture, but many cite it as inevitable now that the MacOS runs on Intel architecture.

And then there are people who may want to dual-boot: to use the MacOS primarily but reboot to Windows when they need to use a program which is not available for Mac. While there are some technical hurdles to jump, it seems obvious that someone will find a way to run Windows and the MacOS on the same computer within a matter of months, if not weeks.

It is even probable that people will figure out how to run the MacOS on non-Apple computers, and, while Apple has said it will not provide support for such an installation, this is still a significant draw to many users.

So, given all this "how", David, we can answer your question of the "what": the Intel chips will almost certainly mean better compatibility between the MacOS and Windows. Which, if you recall, is the primary concern keeping people from buying Macs. Programs which previously ran only on Windows will run on Macs.

But what does this mean for the Apple faithful, the people who have been buying Apples for years and would buy them no matter whose chip was in the box?

You dismiss the idea that end-users won't be able to tell the difference between a PowerPC Mac and an Intel Mac as if it means the difference isn't important -- as if being able to transfer an entire platform to a completely different architecture with such a seamless transition that the average user can't tell the difference is something that doesn't even bear thinking about. That's simply absurd. That Apple has made this dramatic change but managed to make it in such a way that the average end-user won't even notice any change at all is nothing short of amazing.

So, in a way, your vapid, superficial article answers its own question: that Apple has made a fundamental change and you can't, for the life of you, tell that anything has changed at all IS the story here.