
UNSOLVED
Is this normal?
I have never needed to ask this question - until now when it's rather critical. As most of you know by now I have an 8250 and, ever since I acquired it, the BIOS has never reflected the hardware. By this I mean that - despite both IDE channels being full, the BIOS only ever reports the drive (whether hard or optical) on the PRIMARY channel - the secondary has always reported 'NONE'. Whilst this has never been of too much importance, it has now become rather critical, as I'm having some issues (which I will post on another forum, if my experiments do not resolve them). The reason I say it's taken on an added dimension (if you'll pardon the pun) is because I've alwayse used PQ's (OK, now Symantec's) Drive Image software to regularly back up my Windows partition - and have been using it since version one without issue. It's now on v7, and on all my other systems (this is the first system I've owned I've not built myself) it would recognise both drive in 'DOS console' mode. However, and I assume this is because the BIOS is incorrectly reporting my hardware, it only shows the drive connected to the PRIMARY IDE on both channels. I am running the latest BIOS revision (A04) though I've not downloaded the updated revision Cody posted about, because I'm not too sure it applies. Windows Setup reports everything correctly, as does Windows itself, so they can't be too reliant on what the BIOS tells them? I have tried draining the CMOS and trying again, but it doesn't want to know.
Is this a 'known issue' and, if yes (or if no) what in Hades name can I do about it?!
Thanks for any assistance,
Blessed Be,
Perdi
P.S. Please forgive any typos, I'm typing this with an Optiplex keyboard balanced on my knee!
Responses (3)
Solutions (0)
Windows has nothing whatsoever to do with it - DI is NOT being run under Windows, but via the CD, which is bootable and allows you to restore images in a sort of 'DOS console' mode - it simply boots from the CD and runs the console. I did state this in my first post. Now, I don't mean to sound rude, but please read the posts carefully in future, to save people having to repeat themselves ad infinitum.

Perdita
23 Posts
227
0
Posted February 29th, 2004 10:00
OK, answer me this: - if it was a cabling issue, why does Windows and Windows setup correctly identify the drives?! I didn't mention it, but i have tried several cables, including 2 taken from a known working system - so it's highly unlikely to be a cabling issue.
Any other suggestions?