Well, the saga of my new office PC continues.
For
Yesterday I achieved the following:
- Connected my PC to the network (many thanks to Jon, our local, networking hero)
- Transferred all my backed-up data from external drive to new PC
- Had one of the techies come over to the office to install Microsoft Office 2003 over the network
- Installed most of my other software
- Successfully transferred my Outlook PST file over
By this point it was about 18:45, and I thought: I’ll just stay a bit longer, get the graphics card moved into my new PC, install the drivers, and that’ll be me.
I just wanted to be able to return to the office on Monday morning and get to work with my new PC in its faster, larger capacity, three-monitor goodness … a positively “techy heaven”, as Doug might say.
Against
Sadly it didn’t feel much like techy heaven last night at 20:45 while I was still in the office struggling to get my new PC to recognise the second graphics card from my old PC.
It works perfectly in the IBM 8172-CTO but not the newer 8215-CTO. Very bizzare.
When I boot up I get an error like this:
Error 1806: PCI Plug ‘n Play Resource Conflict
or something similar. And if I didn’t get that then it was a reboot cycle:
- Reboot
- Windows loading splash screen
- Blank screen
- Repeat
In the end I gave up around 21:00 and came home. Bah!
Somewhere around that error message I’d be taking a dive into the BIOS to play with the PCI IRQ allocation settings – there’s normally some kind of “reset, back to square zero, let the BIOS sort them all out” kind of setting in there somewhere.
This might or might not help 🙂
Aye … tried that. Reset the BIOS back to factory settings. No difference: still wouldnae work. A job for the in-house techies, methinks.
Thanks for the advice, Tim, though. 🙂
I know this may sound naive but is it maybe becasue it’s a second graphics card from an old PC?
Hope you reach 3 monitor techy heaven soon 😀
It was a Radeon 9250 PCI graphics card taken from an IBM 8172, put into an almost identical, although newer IBM 8215.
It should have worked, in theory.
It didn’t. So eventually I got a replacement 8172. Worked straight away. No questions asked.
Very interesting… thanks.