I possess an previous MS-DOS personal computer that I are experimenting with. The pc has an AMD 80386 processor chip, 1664 KB of RAM, a 50 MB tough commute, and two floppy disk pushes: one 3 1/2 in ., the other 5 1/4 inch.
MS-DOS bootable USB flash is still very useful today. It could be used to access a system that doesn’t have any OS installed. Or, it’s mostly used to flash BIOS or other firmwares from DOS mode. There is an existing document in the sevenforum.com that gives you step by step instruction on how to create. I've tried booting this startup disk, then switched to an MS-DOS floppy, then ran SETUP from there but it then get a message: To install MS-DOS, insert Setup Disk 1 in drive A and press CTRL+ALT+DEL. This will restart your computer and begin the setup program.
I have always been in the process of setting up a C compiler on this personal computer (see Install M compiler on outdated MS-DOS personal computer with floppies for even more information). In purchase to assist in that set up, I feel trying to install a CD-ROM push. The commute is a Top Glory Electronics BCD G621D. I have got found the right motorist (http://www.driverguide.com/driver/detail.php?driverid=349099) and possess implemented the instructions in the manual (included in the drivers download) to connect the drive to the program and install the software program.
Presently the CD-ROM commute is connected up as a servant commute to the HD, and the jumper is certainly set accordingly. The drive is becoming powered properly; it opens and closes as it should.
The driver is set up in N:CDROM, while the MS-DOS program files are situated in the D: push. I have got included the right after ranges to the CONFIG.SYS and AUTOEXEC.BAT files, respectively:
and
The former lots the drivers into memory space, and the last mentioned configures the MSCDEX.EXE program to socialize with the driver, thus allowing the consumer (me) to gain access to the CD-ROM travel.
Nevertheless, a problem has happened. After installing the car owner and restarting the program, one of two stuff occur: 1. Info about the drivers is shown. 2. An abnormally large cursor flashes on-screen.
The information described in item 1 is usually shown right here:
In both situations, the 2 prompt certainly not appears, and the program does not really accept commands. Therefore, the computer is made ineffective.
The issue seems to become triggered by the collection in CONFIG.SYS. When I shoe MS-DOS from a floppy disk rather than the HD and get rid of that line from the document, the pc works simply good when I restart from the HD. (Of course, MSCDEX.EXE cannot entry the gadget, as the car owner is not packed).
This qualified prospects me to think that I possess the commute and its car owner established up correctly. Nevertheless, that will not assist me taking into consideration that I have always been unable to do anything with the computer once the car owner loads. Will anybody understand how I would be capable to gain gain access to to the MS-DOS prompt and make use of the personal computer while the motorist is packed?
Thanks in sophisticated for your help.
Community♦
KyleKyle
5 Answers
I think the clue can be in the explanation box. Odds are usually, the audio card offers an IDE interface on it. Many, if no nearly all of them perform. Usually it can be disabled by a jumper on the audio credit card. You could in the short term eliminate the sound cards. Or you could link the compact disc commute to the sound credit cards IDE interface.
KneepuckKneepuck
Try out using the Oak CD-ROM drivers here. Make certain you addHIMEM.SYSas it guides.
Your system schedules from the period when there had been often problems with slaving two gadgets on a single IDE port that weren'capital t from the same producer and didn'testosterone levels explicitly support it. If you still encounter difficulties, connect to the various other IDE interface if your motherboard provides one, or look on your favorite auction web site for an ISA IDE adapter and discover if you have got better good luck with that.
I are going to move another direction. Basically rem out the collection in the config.sys file that a lot cdrom.sys and reboot. If you obtain a 2 prompt at that stage then it is certainly the cdrom.sys and you require to discover a different one.
Just what you notice on the screen:
Example : Gadget=CDROMDRV.SYS /N:MSCD001 /DMA/DMA -gt; Enable PCI Shuttle bus Grasp DMA Mode/UDMA -gt; Enable PCI Bus Professional Ultra DMA Setting
is almost informing you that the order series isn't right. mscdex gained't work with the cdrom.sys remed out but it gained't impact anything.
I agree with the temporary stop as the 1st series in the autoexec.softball bat to notice simply what the config.sys file did.
It is usually a extremely simple way to determing if the cdrom.sys is causing the problem.
ZiggyStardustZiggyStardust
I acknowledge with the comment about removing MSCDEX from AUTOEXEC.BAT.
Maybe not a long term remedy, but that could help to determine where the balance issue is present.
Test making the 1st series of AUTOEXEC.BAT this:
And the second collection this:
If the issue is certainly the CONFIG.SYS motorist, try transforming it. I wear't understand simply what DriverGuide offered you, but there are some motorists that maintained to function on nearly all runs, and make use of up significantly less typical memory space than many other Compact disc drivers. Notice:TOOGAM's Software program Archive: CD motorists for DOS for information. Because typical memory was often essential in 2, I would end up being fairly try those drivers in just about any case, actually if formal producer's drivers weren't causing balance problems. Confix.sys can also be helpful, allowing you to echo text messages and pause bootup during config.sys running. This may really help you confirm that the config.sys range will be what is usually causing balance issues.
If you're using MS-DOS 6 (or perhaps newer options, like FreeDOS), after that try keeping Y8 or Shift-F8 when booting. You may find that'beds an much easier way to omit outlines from the CONFIG.SYS document.
Your structure config.sys result shows quite a great deal of IRQ information. Hardware conflicts can cause symptoms like what you describe: where the 2nd period the computer boots after that items don'capital t initialize as preferred. If you carry on to possess difficulties with various drivers, create sure that there'beds no conflicts of I/O address or IRQs (or DMA). That has been a typical supply of troubles with computer systems in that period, and can typically be set for free of charge by simply foreseeing out what hardware (or possibly driver) requires to have got settings be changed.
Hennes
59.7k77 silver badges9494 silver precious metal badges144144 bronze badges
This behaviour can occur if any of the following conditions can be found:
To gain access to a CD-ROM commute when you boot to a Home windows command prompt or restart the personal computer in MS-DOS mode, you must insert the real-mode CD-ROM motorist in the Config.sys document and the MSCDEX drivers in the Autoexec.softball bat or Dosstart.bat document. If your CD-ROM drive is supported in guarded mode in Windows, the real-mode CD-ROM and MSCDEX motorists are most likely not really being loaded in the Config.sys and Autoexec.softball bat or Dosstart.softball bat data files on the hard disk. In add-on, if you boot from a floppy disk, the CD-ROM and MSCDEX motorists will not really weight unless you personally configure the Config.sys and Autoexec.softball bat data files on the floppy disk to weight them.
for resolve them notice :
mohammad moeinimohammad moeini
Not the solution you're searching for? Browse other questions marked driverscompact-discms-dos or ask your own issue.