Your CD or DVD drive is not recognized by Windows. Expand DVD/CD-ROM drives, right-click the CD and. To remove and reinstall IDE/ATAPI driver. Microsoft CD-ROM Drivers Download. This page contains the list of download links for Microsoft CD-ROM. To download the proper driver. ATAPI CD-ROM 50X ATA Device. Download the latest version of Acer CD ROM Universal ATAPI IDE drivers according to your computer's operating system. Microsoft CD-ROM Drivers Download. This page contains the list of download links for Microsoft CD-ROM. To download the proper driver. ATAPI CD-ROM 50X ATA Device.
Atapi Cd Rom Drive 52max Driver Download
Download the latest Windows drivers for Panasonic ATAPI CD-ROM Interface Card Driver. Drivers Update tool checks your computer for old drivers and update it. Get latest Panasonic ATAPI CD-ROM Interface Card Driver driver! The Best Free CD & DVD Drivers app downloads for Windows: Adaptec UDF Reader Driver Microsoft CD-ROM Changer Drivers Easy CD Creator Software Update.
Download the latest ATAPI DVD A DH20A4P ATA Device driver for your computer's operating system. All downloads available on this website have been scanned by the latest anti-virus software and are guaranteed to be virus and malware-free.
Find All ATAPI DVD A DH20A4P ATA Device Drivers
Browse the list below to find the driver that meets your needs. To see more matches, use our custom search engine to find the exact driver.
Tech Tip: If you are having trouble deciding which is the right driver, try the Driver Update Utility for ATAPI DVD A DH20A4P ATA Device. It is a software utility that will find the right driver for you - automatically.
DriverGuide maintains an extensive archive of Windows drivers available for free download. We employ a team from around the world. They add hundreds of new drivers to our site every day.
Having trouble finding the right driver? Try the Automatic Driver Update Utility, or you can request a driver and we will find it for you.
Popular Driver Updates for ATAPI DVD A DH20A4P ATA Device
Active1 year, 5 months ago
I have an old MS-DOS computer that I am experimenting with. The computer has an AMD 80386 processor, 1664 KB of RAM, a 50 MB hard drive, and two floppy disk drives: one 3 1/2 inch, the other 5 1/4 inch.
I am in the process of installing a C++ compiler on this computer (see Install C++ compiler on old MS-DOS computer with floppies for more details). In order to facilitate that installation, I am attempting to install a CD-ROM drive. The drive is a Top Glory Electronics BCD G621D. I have found the correct driver (http://www.driverguide.com/driver/detail.php?driverid=349099) and have followed the instructions in the manual (included in the driver download) to connect the drive to the system and install the software.
Currently the CD-ROM drive is hooked up as a slave drive to the HD, and the jumper is set accordingly. The drive is being powered correctly; it opens and closes as it should.
The driver is installed in D:CDROM, while the MS-DOS system files are located in the C: drive. I have added the following lines to the CONFIG.SYS and AUTOEXEC.BAT files, respectively:
and
Ide Atapi Driver Download
The former loads the driver into memory, and the latter configures the MSCDEX.EXE program to interact with the driver, thus allowing the user (me) to access the CD-ROM drive.
However, a problem has occurred. After installing the driver and restarting the system, one of two things happen: 1. Information about the driver is displayed. 2. An unusually large cursor flashes on-screen.
The information mentioned in item 1 is shown here:
In both cases, the DOS prompt never appears, and the system does not accept commands. Thus, the computer is rendered useless.
The problem appears to be caused by the line in CONFIG.SYS. When I boot MS-DOS from a floppy disk rather than the HD and remove that line from the file, the computer works just fine when I reboot from the HD. (Of course, MSCDEX.EXE cannot access the device, as the driver is not loaded).
This leads me to believe that I have the drive and its driver set up correctly. However, that does not help me considering that I am unable to do anything with the computer once the driver loads. Does anybody know how I would be able to gain access to the MS-DOS prompt and use the computer while the driver is loaded?
Thanks in advanced for your help.
Community♦
KyleKyle
5 Answers
I think the clue is in the description box. Odds are, the sound card has an IDE port on it. Many, if no most of them do. Usually it can be disabled by a jumper on the sound card. You could temporarily remove the sound card. Or you could connect the cd drive to the sound cards IDE port.
KneepuckKneepuck
Try using the Oak CD-ROM driver here. Make sure you add
HIMEM.SYS as it directs.
Your system dates from the era when there were often issues with slaving two devices on a single IDE port that weren't from the same manufacturer and didn't explicitly support it. If you still encounter problems, attach to the other IDE port if your motherboard has one, or look on your favorite auction site for an ISA IDE adapter and see if you have better luck with that.
LawrenceCLawrenceC
61.6k1212 gold badges109109 silver badges186186 bronze badges
![]()
I am going to go another direction. Simply rem out the line in the config.sys file that loads cdrom.sys and reboot. If you get a DOS prompt at that point then it is the cdrom.sys and you need to find a different one.
Just what you see on the screen:
Example : DEVICE=CDROM_DRV.SYS /D:MSCD001 [/DMA]/DMA --> Enable PCI Bus Master DMA Mode/UDMA --> Enable PCI Bus Master Ultra DMA Mode
is almost telling you that the command line isn't right. mscdex won't work with the cdrom.sys remed out but it won't affect anything.
I agree with the pause as the first line in the autoexec.bat to see just what the config.sys file did.
It is a very simple way to determing if the cdrom.sys is causing the problem..
ZiggyStardustZiggyStardust
I agree with the comment about removing MSCDEX from AUTOEXEC.BAT.
Maybe not a long term solution, but that could help to determine where the stability issue exists.
Download patch cyberlink powerdvd 13 ultra. CyberLink PowerDVD 13 13 Ultra. You can use the free trial version of CyberLink PowerDVD 13 for 30 days after the download For further details about CyberLink. CyberLink PowerDVD 13 Ultra is a very capable media player, able to play just about any content, wherever it's located. It's not overweight, though, loading quickly on our test PC, so if you need a very powerful player - and you don't mind the price - we'd give it a try. Here you can download cyberlink powerdvd 13 patch shared files: CyberLink PowerDVD 13 Patch.rar from 4shared.com 120.2 MB, download cyberlink powerdvd 13 - ultra 3d (852172).rar from 4shared.com 700.36 KB, CyberLink PowerDVD 13 Ultra.rar from mega.co.nz 125.76 MB, Cyberlink powerdvd 12 patch rar from mediafire.com (43 KB).
Try making the first line of AUTOEXEC.BAT this:
And the second line this:
If the problem is the CONFIG.SYS driver, try changing it. I don't know just what DriverGuide offered you, but there are some drivers that tended to work on almost all drives, and use up far less conventional memory than most other CD drivers. See:TOOGAM's Software Archive: CD drivers for DOS for details. Because conventional memory was often important in DOS, I would be fairly try those drivers in just about any case, even if official manufacturer's drivers weren't causing stability issues. Confix.sys can also be useful, allowing you to echo messages and pause bootup during config.sys processing. This may really help you confirm that the config.sys line is what is causing stability issues.
If you're using MS-DOS 6 (or perhaps newer alternatives, like FreeDOS), then try holding F8 or Shift-F8 when booting. You may find that's an easier way to skip lines from the CONFIG.SYS file.
Your sample config.sys output shows quite a lot of IRQ info. Hardware conflicts can cause symptoms like what you describe: where the second time the computer boots then things don't initialize as desired. If you continue to have problems with different drivers, make sure that there's no conflicts of I/O address or IRQs (or DMA). That was a common source of problems with computers in that era, and can typically be fixed for free by just figuring out what hardware (or possibly driver) needs to have settings be changed.
Hennes
60k77 gold badges9494 silver badges144144 bronze badges
TOOGAMTOOGAM
11.8k33 gold badges2626 silver badges4848 bronze badges
This behavior can occur if any of the following conditions exist:
To access a CD-ROM drive when you boot to a Windows command prompt or restart the computer in MS-DOS mode, you must load the real-mode CD-ROM driver in the Config.sys file and the MSCDEX driver in the Autoexec.bat or Dosstart.bat file. If your CD-ROM drive is supported in protected mode in Windows, the real-mode CD-ROM and MSCDEX drivers are most likely not being loaded in the Config.sys and Autoexec.bat or Dosstart.bat files on the hard disk. In addition, if you boot from a floppy disk, the CD-ROM and MSCDEX drivers will not load unless you manually configure the Config.sys and Autoexec.bat files on the floppy disk to load them.
for resolve them see :
mohammad moeinimohammad moeini
Not the answer you're looking for? Browse other questions tagged driverscompact-discms-dos or ask your own question.Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |