Active1 year, 6 months ago
- Ms Dos 6.22 Cd Rom Driver
- Ms Dos 6.22 With Cd Rom Driver
- Ms Dos 6 22 Boot Disk
- Dos 6.22 Cd Rom Driver For Windows 7
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.
I have Compaq Presario 5220 with Win 98 installed. I made a clean install with DOS 6.22 original Diskette's. I then installed Windows 3.1 with no problem. Now i am trying to install Win 95. I have the 95 upgrade CD but 3.1 will not 'see' the CD-ROM drive to install. I do not have enough Floppy Disk's to have 95 floppy install. Agreed, 7.1 CD would be much better for this purpose. It includes 'native' CD and Mouse drivers, unlike 6.22. Although it is your choice, MS-DOS would probably not be a very good use of that computer. My suggestion would be to install Windows 2000 or even (shudder) Millenium Edition to truly experience the computers of old. › Serial Port Communication Under MS-DOS 6.22 › ms dos 6.22 cd won't boot if sata controller is in ahci mode › Cannot get DOS to see second HDD › Sound in DOS 6.22 › sata controllers not seen by dos 6.22 › Solved MS DOS 6.22 Bootable CD › Installing MS-DOS 6.22 from DVD to IDE HDD via ext adaptor. Originally 86-DOS, written by Tim Paterson of Seattle Computer Products, DOS was a rough clone of CP/M for 8086 based hardware.Microsoft purchased it and licensed it to IBM for use with Microsoft's IBM PC language products.
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
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.
Ms Dos 6.22 Cd Rom Driver
LawrenceCLawrenceC61.8k1212 gold badges109109 silver badges188188 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.
Opening zip files windows 7 free. How to unzip files on Windows 10Windows 10 supports zip natively, which means that you can just double-click the zipped folder to access its content — and open files.
Maybe not a long term solution, but that could help to determine where the stability issue exists.
Try making the first line of AUTOEXEC.BAT this:
And the second line this:
Ms Dos 6.22 With Cd Rom Driver
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.
Seamless web browser for previewing the content of your HTML document or Java applet without leaving the editor. Highlights URL and e-mail addresses in normal text files and lets you activate them with a single keystroke (F8) or 'Ctrl + double-click'. Also, you can create your own syntax file to support other programming languages.Main features:. Browser window also has common browser commands so you can browse Internet web sites as well as local HTML files. FTP (also sftp and FTPS) feature for uploading your local files to FTP server or for editing remote files directly. Editplus 5 serial.
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.
HennesMs Dos 6 22 Boot Disk
60.1k77 gold badges9494 silver badges143143 bronze badges
TOOGAMDos 6.22 Cd Rom Driver For Windows 7
TOOGAM11.8k33 gold badges2626 silver badges4949 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.
realmadmartian
Distinguished
- Jul 22, 2006
- 117
- 0
- 18,680
- 0
I have an Intel motherboard D975XBX and a Plextor PX-755SA SATA DVD drive. I need to boot to DOS to run an old CDROM game. And before you mention it, DOSBOX does not support SATA.
Normally you would run OAKCDROM.SYS in the config.sys file and MSCDEX.EXE in the autoexec.bat file. No go with a SATA DVD drive. I tried a GCDROM.SYS file I got from the Gigabyte site, but it doesn't work, most likely because it is made for a different SATA chipset. Any idea where I can find a SYS file for mounting the DVD drive in DOS for my Intel mobo? Intel just says they don't support DOS. Plextor doesn't know how but thinks it should be possible. I also checked the Silicon Image web site and it says 'Operating Systems that are not listed above are not supported'. I tried DOSBOX but it doesn't appear to support SATA. I would have given up already were it not for the existience of the Gigabyte driver. Clearly someone has gotten this working. Am I SOL for Intel or is there a solution?
Normally you would run OAKCDROM.SYS in the config.sys file and MSCDEX.EXE in the autoexec.bat file. No go with a SATA DVD drive. I tried a GCDROM.SYS file I got from the Gigabyte site, but it doesn't work, most likely because it is made for a different SATA chipset. Any idea where I can find a SYS file for mounting the DVD drive in DOS for my Intel mobo? Intel just says they don't support DOS. Plextor doesn't know how but thinks it should be possible. I also checked the Silicon Image web site and it says 'Operating Systems that are not listed above are not supported'. I tried DOSBOX but it doesn't appear to support SATA. I would have given up already were it not for the existience of the Gigabyte driver. Clearly someone has gotten this working. Am I SOL for Intel or is there a solution?