Something’s coming over me.
That should have been “which is when.”
Memory problem: Can’t force 3 PC2700 DIMMs to run in dual-channel in any way. Also, the A64 memory controller really dislikes odd-numbers of modules.
Solution: Bullet has been bitten. Graeme will live with 768mb until Wednesday or so, which 1 gig of new PC3200 pyscho ninja-RAM arrives.
Then I’m overclocking everything.
Maybe. (Hey, half of my shit is warrantied against damages caused by overclocking. How cool is that?)


I’m posting this from…FitzSheba 64. Other than one niggling little RAM problem, she’s totally functional. I prefer to say she’s at 90% of optimal.
Do you know what this means? A feature or nine tomorrow!
Wow. As far as features go, this month has really, really sucked.
I blame society.
Just before the final operation
FitzSheba as she appears now, after the failure of the final operation.
The government in exile.
Way to hog the front page! Actually, I don’t really have anything to say, so its okay with me.
Well, it came to that. FitzSheba is desperately awaiting a transplant, already ordered from Newegg. The only main component I didn’t upgrade was the RAM, since I just ordered a ton of that a few months ago, and my wallet is perfectly happy to use PC2700 at the moment even though the new CPU will support PC3200. Hell, I might just try overclocking it. It’s high quality RAM, so I imagine that would work.
Beyond that, FitzSheba Mark II will be an Athlon 64 3200+ in socket 939 (awaiting dual-core goodness), with a PCI-Express 6600GT to back her up. Quite an upgrade from an Athlon XP 2700+ and Radeon 9600 Pro…both of which will be grafted on to Vivian’s computer as soon as the RMA process on my Asus nForce2 board is complete. Actually, the Radeon will probably be added to her computer before that, if I’m not lazy. Which I am.
By the end of the week, I should be able to access my Jux work files and we can get back to business here. I’m sorry for the unexpected delay, good Juxers.