• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

I did a dumb thing...

Are you saying the new comp doesn't detect the cdrom? If it is in bios, I'd put the win2k cd in, boot from cd, and try a repair. Normally, if I'm transfering a hd from one comp to another, I un-install the bus drivers just before shutting down to install the hd into the next comp, then have the new system re-detect the drivers and reload them. If you can stick it back into the old machine, try that. 🙂
 
Nope... it detects everything.. when I put the hd that was in the Tiger into the VP6, it tried to install all the drivers for the 'new' hardware, but, because I didn't have the CDROM hooked up with the Win2K CD in it, it couldn't install the chipset drivers, including the IDE channel stuff. So, when I boot, the first screen comes up (the one that is black with the white blocks on the bottom), and then the GUI screen comes up and goes through about 75% of the startup (based on the blue progress meter at the bottom of the screen), and then BSoD because it can't access the boot drive (which it is loading all that stuff from). 🙁

Geoff
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top