I've got one class tomorrow (Friday) and then three days of class next week (Monday through Wednesday). After that, the school's scheduled two "reading days" for Thursday and Friday where students are supposed to be studying for finals which will occur the next week, but most people (including myself) are calling it a four-day weekend.
I won't be on campus for the long weekend, but I'm sure there will be plenty of partying. I'll be at home that weekend, probably trying to study or just catch up on sleep.
[ add comment ] ( 1604 views ) | permalink
[ add comment ] ( 1019 views ) | permalink
I haven't gotten fooled yet today, but it's still early. I do plan on trying to pull something off later, but I'll have to play it by ear and see how things work out later today...
In other news, males here get to go through the room selection process for next year. Today is the main day, and this morning, I chose a number in the room selection lottery. I chose number 50 out of 500, so I'll get a very early (and hopefully good) choice of where I want to live next year. I already have a good idea of where I want to room next year, so I'll have an easy room selection session tonight.
[ add comment ] ( 1319 views ) | permalink
When I checked Paul Thurrott's WinSupersite, I discovered that five audio drivers were causing issues with SP1, and at the end of the list was my driver.
What went wrong?
You may be curious about which device drivers were causing issues with SP1. (I certainly was.) The list includes certain versions of five audio drivers (RealTek AC'97, two versions of SigmaTel, Creative Audigy, and Conexant HD Audio), two biometric fingerprint sensors (AuthenTec and UPEK), Intel Display, a Texas Instruments Smart Card Controller, the Sierra Wireless AirCard 580 with the Watcher.exe application, and the Symantec software driver for the Symantec Endpoint Protection and Symantec Network Access Control clients. The complete list is available on the Microsoft Knowledge Base.
So like Microsoft tells me, I check "Chdart64.sys" and I see version 188.8.131.52, which is well below what is listed in the Microsoft KB article. So I head back to Windows Update, and I find an updated driver for the Conexant High Definition sound driver. I install the new driver, reboot, and check the Device Manager, and the driver version is 184.108.40.206, so I figure I'm clear to install SP1...
I once again head back to Windows Update, and check for updates. No SP1. WTF? I check "Chdart64.sys" again. What do I see? Version 220.127.116.11.
If I updated the driver via Windows Update, and the Device Manager lists the newer version, shouldn't the SYS file get updated as well?
So no SP1 for me for now. I hope the update process on my desktop will be much smoother.
[ 1 comment ] ( 3008 views ) | permalink
This computer was given to the family back about 10 years ago. For the last ten years or so, it has been sitting in our garage. After playing with an old 286 machine last weekend that was given to the family by a relative, I decided to dig out this computer.
Until I saw it a few hours ago, I had no idea it was an IBM PS/2. I just knew we had an old computer buried somewhere under the large magnitude of junk in the garage.
I knew at some point it was on my dad's workbench, but I didn't know where. I sorted around all the clutter to find nothing like a computer (only a bunch of junk he dragged home from work over the years). Then I decided to venture upstairs to the garage attic. I pulled the string to turn on the light, and the string ripped. So I go over to the other light on the far side of the garage and turn that one on.
I look around, and in the very corner, past my old Huffy and a bunch of old tires, I see something white sticking out. It had to be the computer, but there were a whole bunch of junked radios sitting in top of it (again my dad dragged these home from work). I eventually make it to the computer, and see the little silver IBM logo.
Then I get it inside and up to my room and examine it. It turned out to be an IBM PS/2 Model 55 SX. I decide to hook up a monitor, keyboard, and mouse to it, and power it up. I hear two beeps, and then this screen greets me:
Not knowing what to do, I start hitting keys on the keyboard. One of the first I try, F1 gets me into some kind of "IBM Personal Computer Basic:"
Anyone know if I can do anything with this computer? Install DOS or OS/2 on it possibly? Let it sit around in the garage for another ten years? Or just sit it in my room hoping it will somehow do something else?
I've done some more research into this computer and it appears to have a 16MHz Intel 80386 processor, and I believe somewhere between 2 and 8 MB RAM.
The error codes I get on bootup, 161 and 163, according to this post at techrepublic.com states that the two error codes are related to a dead or faulty battery on the motherboard. And I've learned that when any error code appears, it shows the screen with the crossed out :OK" and the IBM manuals then defaults to the IBM Basic program when F1 is hit.
[ 2 comments ] ( 4525 views ) | permalink