FrómJamesonline:
D0S-on-USB enables you install MS-DOS 7.1 on your USB memory space key. After format your flash drive, you can install a full working edition of MS-DOS to let you run video games or system utilities. The greatest point about getting a DOS-bootable memory space key can be you can boot into it on any personal computer, simply like a CD.
You'll discover this application excellent for moments you require to perform system upkeep, because you wont constantly possess to burn off a new CD, just copy the system to the USB Commute. With the 2 quick, you can even install Windows 95 or 98. Recommended USB travel dimension: 16MB - 2GN. Edition 2 features an car start for simplicity of the DOS operating system.
Installation instructions. To Install: Insert the first disk into your PC or virtualization software and ensure your BIOS is set to boot from a floppy disk. The setup program will install and ask a few questions about your hardware and whether or not you want to install to floppy or hard disk.
Whát do you need to know about free of charge software?
I have got an previous MS-DOS computer that I was experimenting with. The pc provides an AMD 80386 processor chip, 1664 KB of Memory, a 50 MB hard travel, and two floppy disk forces: one 3 1/2 inches, the other 5 1/4 inch.
I am in the procedure of installing a Chemical compiler on this personal computer (discover Install Chemical compiler on aged MS-DOS computer with floppies for even more details). In order to assist in that installation, I are attempting to install a CD-ROM get. The commute can be a Top Glory Consumer electronics BCD G621D. I possess discovered the proper drivers (http://www.driverguide.com/driver/detail.php?driverid=349099) and have adopted the instructions in the guide (incorporated in the driver download) to link the drive to the system and install the software.
Currently the CD-ROM get is hooked up as a slave get to the HD, and the jumper is usually set accordingly. The travel is being powered properly; it opens and closes as it should.
The drivers is installed in G:CDROM, while the MS-DOS system files are located in the D: push. I possess included the pursuing outlines to the CONFIG.SYS and AUTOEXEC.BAT documents, respectively:
and
The previous a good deal the driver into memory space, and the second option configures the MSCDEX.EXE system to interact with the motorist, thus allowing the user (me) to gain access to the CD-ROM travel.
However, a issue has occurred. After installing the car owner and restarting the system, one of two stuff happen: 1. Details about the driver is displayed. 2. An extraordinarily large cursor flashes on-screen.
The details stated in item 1 is usually shown right here:
In both cases, the DOS prompt by no means shows up, and the system does not accept commands. Thus, the personal computer is delivered worthless.
The problem shows up to be triggered by the line in CONFIG.SYS. When I boot MS-DOS from a floppy disk rather than the HD and remove that series from the document, the pc works just fine when I restart from the HD. (Of training course, MSCDEX.EXE cannot accessibility the device, as the motorist is not really packed).
This prospects me to think that I have the get and its car owner arranged up correctly. Nevertheless, that will not assist me considering that I have always been incapable to do anything with the pc once the car owner loads. Does anybody understand how I would end up being able to gain gain access to to the MS-DOS fast and make use of the computer while the car owner is loaded?
Thanks a lot in sophisticated for your assist.
Area♦
KyleKyle
5 Solutions
I think the clue is usually in the explanation box. Odds are, the audio card has an IDE slot on it. Many, if no nearly all of them perform. Generally it can end up being disabled by a jumper on the sound credit card. You could temporarily get rid of the sound card. Or you could link the compact disc travel to the sound credit cards IDE port.
KneepuckKneepuck
Try out making use of the Oak CD-ROM car owner here. Create sure you include
HIMEM.SYS
as it guides.Your system dates from the era when there had been often problems with slaving two products on a one IDE slot that weren't from the same manufacturer and didn't explicitly support it. If you still encounter troubles, connect to the additional IDE slot if your motherboard provides one, or look on your favorite auction web site for an ISA IDE adapter and find if you have better luck with that.
LawrenceCLawrenceC60.6k1212 platinum badges108108 silver precious metal badges184184 bronze badges
I was heading to proceed another path. Just rem out the line in the config.sys document that a good deal cdrom.sys and reboot. If you get a 2 fast at that point then it is the cdrom.sys and you need to discover a different one.
Just what you see on the display screen:
Instance : Gadget=CDROMDRV.SYS /G:MSCD001 /DMA/DMA -gt; Enable PCI Bus Master DMA Mode/UDMA -gt; Enable PCI Bus Grasp Ultra DMA Setting
is usually almost informing you that the command word range isn't perfect. mscdex gained't work with the cdrom.sys remed out but it received't have an effect on anything.
I agree with the pause as the first line in the autoexec.softball bat to discover just what the config.sys file do.
It is a extremely simple way to determing if the cdrom.sys is causing the problem.
ZiggyStardustZiggyStardust
I agree with the remark about eliminating MSCDEX from AUTOEXEC.BAT.
Maybe not a long term answer, but that could help to determine where the stability issue exists.
Consider making the very first series of AUTOEXEC.BAT this:
And the 2nd collection this:
If the issue is the CONFIG.SYS driver, try changing it. I put on't know just what DriverGuide provided you, but there are usually some drivers that maintained to function on almost all runs, and use up much less regular storage than most other Compact disc drivers. Notice:TOOGAM's Software Save: Compact disc motorists for 2 for information. Because regular memory was often important in 2, I would end up being fairly try out those motorists in simply about any case, actually if recognized producer's drivers weren't causing stability issues. Confix.sys can also be useful, enabling you to echo messages and stop bootup during config.sys running. This may actually help you confirm that the config.sys series will be what will be causing balance issues.
If you're also using MS-DOS 6 (or probably newer options, like FreeDOS), after that try keeping Y8 or Shift-F8 when booting. You may discover that's an much easier method to ignore outlines from the CONFIG.SYS file.
Your test config.sys result shows quite a great deal of IRQ details. Hardware conflicts can cause signs and symptoms like what you explain: where the 2nd time the pc boots then issues don't initialize as preferred. If you continue to have problems with different drivers, create sure that there'beds no conflicts of I/U deal with or IRQs (or DMA). That had been a typical resource of difficulties with computers in that era, and can generally be fixed for free of charge by just figuring out what equipment (or possibly drivers) demands to have settings become changed.
Hennes59.7k77 silver badges9494 gold badges144144 bronze badges
TOOGAMTOOGAM11.6k33 platinum badges2626 gold badges4747 bronze badges
This behaviour can take place if any of the using conditions can be found:
To gain access to a CD-ROM travel when you boot to a Home windows command prompt or reboot the pc in MS-DOS setting, you must fill the real-mode CD-ROM car owner in the Config.sys document and the MSCDEX drivers in the Autoexec.bat or Dosstart.bat file. If your CD-ROM travel is supported in shielded 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 documents on the tough disk. In inclusion, if you boot from a floppy disk, the CD-ROM and MSCDEX motorists will not really download unless you manually configure the Config.sys and Autoexec.bat data files on the floppy disk to insert them.
for answer them observe :
mohammad moeinimohammad moeini