Driver not found: 'MSCD001'

December 18, 2013 at 20:56:37
Specs: Windows 7
I have a small problem ...
When starting windows ... Automatically opens the console and get the following ...

Search for USB HDD devices...

UDS support successfully initialized
NWCDEX.EXE Version 2.81 CD-ROM file handler.
Copyright (c) 1992,1997 Caldera Inc, All rights reserved.
Driver not found : 'MSCD001'.
Completed codepage prepare function
Completed codepage select function
NLSFUNC R4.00 National Language Support
Copyright (c) 1988.1998 Caldera, Inc. All rights reserved.

Caldera DR-DOS 7.03
Copyrigth (c) 1976, 1998 Caldera, Inc. All rights reserved.
[DR-DOS] A:\>...

The dotted line in the end asks me a command .. and even Nose which is what I do ... Help please, take four days looking for the solution ...


See More: Driver not found: MSCD001

Report •

#1
December 18, 2013 at 21:14:26
Is it a bootable CD in your CD/DVD drive, that gets autostarted, when windows 7 boots up?

Report •

#2
December 18, 2013 at 21:20:06
I have no idea .. It was working fine, but I had restarted the computer and went out with that problem

Report •

#3
December 18, 2013 at 21:23:30
Check, whether there is a USB-Stick plugged in or a CD/DVD inserted in the CD/DVD drive.
Remove if you've found some and reboot your computer.

Report •

Related Solutions

#4
December 18, 2013 at 23:04:50
You've got DR (Digital Research) dos loading from whatever drive you're booting from. The MSCD001 error means it's trying to load dos cdrom support but isn't finding that the cdrom driver has loaded. Usually that means a driver isn't configured to load or, in your case, you may have a SATA optical drive and are trying to load an ATAPI/IDE driver.

Sometimes DR Dos was used for older restore programs or to setup a new hard drive. WD lifeguard tools and Maxblast used DR dos to set up their drives.

As already mentioned, check to see if you're booting from some other location--optical drive, USB drive, even a floppy drive.

If windows 7 was previously running on this computer, did you make any changes or did anything happen to it between the last time it worked OK and the first time it didn't?

message edited by DAVEINCAPS


Report •

#5
December 18, 2013 at 23:19:37
A couple other things:

Could it be running dos in a virtual PC environment?

If it's looking for a command, type exit and hit enter. What happens?

message edited by DAVEINCAPS


Report •

Ask Question