7900 GTX - Knock On Effect on Drive Image 5.0 - Any Suggestions

I've routinely used Powerquest Drive Image 5.0 to back up my C: Drive, and
its worked fine until I installed a 7900 GTX card today - would welcome any
suggestions about a fix for the problem.

In a bit more detail - I used to boot the PC using the Powerquest CD, which
starts up its own version of DOS. Running Drive Image from the DOS prompt
(with the /ide=on switch to give full speed) worked well and gave fast,
reliable backups. I fitted a Club 3D 7900 GTX card this morning, and it
appears to be working OK in Windows (3D Mark 05 score of 9626 straight out
of the box). However, when I try to start Drive Image from its CD I get a
"Mouse Not Connected" error message (the program installs an Intel mouse
driver as part of its initialisation routine) and a frozen machine. The
mouse works fine in Windows, so it is connected correctly.

Thanks in advance,

Bob,

PS - The previous graphic cards which worked OK have all been made by ATI -
I'm wondering if the Nvidia card defaults to a different interrupt?

DOS requires a mouse.com or equiv. The boot might not so an error
message from it. Is there a mouse.com app on the cd? try running it
to see if you get some error message. Also, might try mouse /loadhi or
get more info from running mouse /?. Old DOS loadhi kind of stuff was
pretty user configurable and you may find a work-around.

Thinking about it further. DOS didn't allow shared interrupts. It
could not normally handle edge trigger interrupts. Look in your
hardware setup and see what interrupts are assigned where. I suppose it
is possible you could do some reassignment either in Window drivers or
the BIOS to also get around the problem.

Thanks for reply.

I managed to get it working by removing the PS2 adaptor from the mouse and
plugging it into a USB port (presume the BIOS runs the mouse from there,
since DOS had no USB support). All seems to working now.

PS - The DOS driver etc. was already included on the Powerquest CD - it
boots to Caldera DOS.



"Ken" wrote in message
news
Thinking about it further. DOS didn't allow shared interrupts. It could
not normally handle edge trigger interrupts. Look in your hardware setup
and see what interrupts are assigned where. I suppose it is possible you
could do some reassignment either in Window drivers or the BIOS to also
get around the problem.