Discussion Locked

Office 2000 made my CD go away ????

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Strange but true, here is what has happened.
A windows NT 4.0 box, running on a network. Running a SCSI CD-RW, running service pack 6; with 256 megs of RAM. The machine was running Office 97 Pro, had been for over 2 years with no problem. We installed Office 2000 upgrade over the network and it installed without a hitch - until we tried to use the CD-RW, now the system says it can't find the CD-RW.

I have another box that is identical except it only had a CD-R, and after the upgrade it is having problems finding the CD-R. This second machine is having other problems too (like it was doing spell check using the French dictionary) it opens Office with error messages that appear to possibly be pointing at fast find.

Anybody run into this problem?

5 replies

by jmatt

Go to Device Manager & enable DMA on all your disks . If they are not capable of staying enabled after a boot up , you may be able to change your bios to allow .
--------------------------------
Try TweakUi , tick all the boxes in the My Computor section of TweakUi . You will gain an extra benefit also , in that you will
now have extra features , when you right click on Start . John .

Download Tweakui complete with install instructions from ,
http://www.microsoft.com/ntworkstation/downloads/PowerToys/Networking/NTTweakUI.asp

by mike.wagoner

Some good ideas here, although they weren't the solution to the problem. There was a problem with ATAPI loading, that was taken care of by installing/re-installing SP 6a. After the SP, life was good again.

by nettek

Have you tried updating a machine straight from a 2000 CD-ROM to see if you have the same problem? I would also scan for viruses with an updated antivirus software. There are known viruses that disable CD-ROM drives. It could be that your network source for Office 2000 is infected.

by mike.wagoner

Thanks for the idea, but we've done hundreds of installations via the network and these were just a couple of flukes. The solution turned out to be to install/re-install NT SP 6 (I installed SP 6a actually - did a complete install, not just an upgrade). Somehow, for some reason the ATAPI driver wasn't loading after the Office install, the install of the SP re-enabled it.

This discussion is closed to new replies.