Not a real exciting weekend at my house. Like I said, Liz made it back from Austin, but we had a pretty low key weekend just relaxing and hanging out around the house. Liz had been pressing some flowers and ferns for some homemade artwork to put in our bathroom and she was working on that this weekend a bit. The flowers pressed very nicely and they actually look good in my homemade frames. I wish the joints had turned out a bit more smooth, but it'll do, I guess. Regardless, Liz seemed pretty happy with the results.
I spent a good chunck of my day on Sunday on the phone with Nate. He got his new computer up and running, but not without its problems. :( It always seems to go that way when you build a new computer - mine even had a similar problem. First of all, he was having problems running video games online, but he tracked that back to a problem in which the video card was sharing an IRQ with his network card. He got that fixed, but he's still experiencing some degree of instability - when he runs games, they'll run for a bit and then bomb with a system check expection - from that, I would expect it has something to do with memory, but I can't be sure.
When I put my computer together, I was having a similar problem. Any application that I'd run that were graphic intensive (3-D Gaming, Flash, Photoshop, etc.), the system would run fine for a while and then just bomb out. To try to fix it, I tried changing video card drivers, running at different setting and even flashing my BIOS (which is not a lot of fun, let me tell you). In the end, my fix was to "underclock" my processor. Right now, I have a 1.2 GHz processor running at 900 MHz because I changed the clock ratio in my BIOS settings. That fixed it for me, so I'm wondering if Nate is experiencing something similar.
We tried reducing the bus speed on his system and have even gone as far as flashing his BIOS, but, last I heard, we hadn't made any real progress. He was planning on working on it some more last night, but I haven't heard from him yet as to how it is working. I'll probably check in with him again tonight, though.
If none of that made any sense to you, don't sweat it. In short, Nate's computer isn't working and we can't figure out what's wrong. That's about all it boils down to.
In happier news, I did get a new photo of my favorite nephew. I seem to remember sitting in that same stool when I was just a wee lad. :)
Today at work, I got no real work done. Rather, Todd called me at about 7:30 this morning and told me to wear grungy clothes because we were going to spend the day remodeling. We pulled out the existing ceiling in our office and aer putting in a suspended ceiling. It's actually coming along pretty nicely now. We've got one half of the room done and have a good start on the other half. I'm guessing a half-days work should finish off the ceiling for us. Of course, we worked on it all day today.
The NCAA basketball tourney turned out to be a big disappointment this weekend. The Badgers played horribly down the stretch against Pitt and coughed up the game (actually, much like they coughed up all those offensive rebounds at the end of the game). So, the Badgers are out and, as if to add insult to injury, my tournament predictions have gone right out the window. After a rather nice 24-8 showing in the first round, I went 8-8 in the second round and Kentucky, who I picked to win the entire tournament, got ousted by UAB. *sigh* Apparently, being a basketball analyst is not my gig.
In the NCAA hockey world, though, the seedings for the tourney were announced yesterday and the Badgers picked up a 3 seed (there are only 4 seed per bracket). They'll be playing #2 seeded Ohio State on Friday. Just for reference, the Big Ten doesn't exist in NCAA hockey so this isn't really a conference game, as you'd expect. Rather, the Badgers are part of the WCHA conference, while Ohio State is part of the CCHA conference. If the Badgers win that game, they'll be playing the winner of the Maine and Harvard game. The winner of that bracket will move on to the Frozen Four, which gets played out the following weekend.
Anyway, that's about all I've got for now. Catch y'all later.
I spent a good chunck of my day on Sunday on the phone with Nate. He got his new computer up and running, but not without its problems. :( It always seems to go that way when you build a new computer - mine even had a similar problem. First of all, he was having problems running video games online, but he tracked that back to a problem in which the video card was sharing an IRQ with his network card. He got that fixed, but he's still experiencing some degree of instability - when he runs games, they'll run for a bit and then bomb with a system check expection - from that, I would expect it has something to do with memory, but I can't be sure.
When I put my computer together, I was having a similar problem. Any application that I'd run that were graphic intensive (3-D Gaming, Flash, Photoshop, etc.), the system would run fine for a while and then just bomb out. To try to fix it, I tried changing video card drivers, running at different setting and even flashing my BIOS (which is not a lot of fun, let me tell you). In the end, my fix was to "underclock" my processor. Right now, I have a 1.2 GHz processor running at 900 MHz because I changed the clock ratio in my BIOS settings. That fixed it for me, so I'm wondering if Nate is experiencing something similar.
We tried reducing the bus speed on his system and have even gone as far as flashing his BIOS, but, last I heard, we hadn't made any real progress. He was planning on working on it some more last night, but I haven't heard from him yet as to how it is working. I'll probably check in with him again tonight, though.
If none of that made any sense to you, don't sweat it. In short, Nate's computer isn't working and we can't figure out what's wrong. That's about all it boils down to.
In happier news, I did get a new photo of my favorite nephew. I seem to remember sitting in that same stool when I was just a wee lad. :)
Today at work, I got no real work done. Rather, Todd called me at about 7:30 this morning and told me to wear grungy clothes because we were going to spend the day remodeling. We pulled out the existing ceiling in our office and aer putting in a suspended ceiling. It's actually coming along pretty nicely now. We've got one half of the room done and have a good start on the other half. I'm guessing a half-days work should finish off the ceiling for us. Of course, we worked on it all day today.
The NCAA basketball tourney turned out to be a big disappointment this weekend. The Badgers played horribly down the stretch against Pitt and coughed up the game (actually, much like they coughed up all those offensive rebounds at the end of the game). So, the Badgers are out and, as if to add insult to injury, my tournament predictions have gone right out the window. After a rather nice 24-8 showing in the first round, I went 8-8 in the second round and Kentucky, who I picked to win the entire tournament, got ousted by UAB. *sigh* Apparently, being a basketball analyst is not my gig.
In the NCAA hockey world, though, the seedings for the tourney were announced yesterday and the Badgers picked up a 3 seed (there are only 4 seed per bracket). They'll be playing #2 seeded Ohio State on Friday. Just for reference, the Big Ten doesn't exist in NCAA hockey so this isn't really a conference game, as you'd expect. Rather, the Badgers are part of the WCHA conference, while Ohio State is part of the CCHA conference. If the Badgers win that game, they'll be playing the winner of the Maine and Harvard game. The winner of that bracket will move on to the Frozen Four, which gets played out the following weekend.
Anyway, that's about all I've got for now. Catch y'all later.
posted by MC at
Monday, March 22, 2004
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home