dopamessage.blogg.se - Autoexec bat commands

#Autoexec bat commands how to
#Autoexec bat commands drivers
#Autoexec bat commands manual
#Autoexec bat commands Pc

In case you are going for MS-DOS you should see: And the E: was just logical drive instead of separate partition. That is what shell e:\rescue\dos98\ e:\rescue\dos98 /Pĭoes in the config.sys of mine. That solution was great as even was on the HDD so no speed problems due to booting from floppy. In the past I usually got MS-DOS 6.22 + W9X + W2K on single machine as I got plenty of apps running only in those specific OS that I was not able to part with.Īt one time I even got 5.25" DD Floppy with MS-DOS 6.22 system files (and all the rest was on HDD hence the weird e:\rescue\ path as the floppy did not have enough space. The menu is usually created during Windows installation (as the installer detects OS in the PC) but nowadays HW has usually boot menu directly in BIOS of the MB. The Vista,W7 and latter do not use boot.ini anymore instead they have some kind of boot app (like Lilo boot). IIRC the boot.ini could be edited from msconfig.exe. You also need separate partition per OS so have MS-DOS on separate partition (or floppy) there are also utilities like Lilo boot that can handle multi OS. Multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /usepmtimerĮach line in the represents one OS to boot from. The other answers here cover the MS-DOS menu well enough so I see no point in describing the obvious mechanism.įrom NT,W2K and XP there was no more MS-DOS just console so for those you need to use boot.ini like this: ĭefault=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS Beware that from W95 the MS-DOS is not fully compatible with the old MS-DOS 6.22 so some games and apps will not work properly or at all.

#Autoexec bat commands how to

Taken from: SO/SE: Run Turbo C++ in Freedos where you can find also tips on how to run MS-DOS on newer machines. Shell e:\rescue\dos98\ e:\rescue\dos98 /Pĭevice=e:\rescue\dos98\qemm386.sys RAM BE:Nĭevicehigh=e:\rescue\dos98\emm386.exe rammaxĭevicehigh=e:\rescue\dos98\emm386.exe noemsĭevicehigh=e:\rescue\dos98\ramdrive.sys 32767 /e PATH e:\rescue e:\rescue\dos98 e:\rescue\vcnew e:\rescue\pack e:\rescue\viewsĬonfig.sys devicehigh=e:\rescue\dos98\interlnk.exe

#Autoexec bat commands drivers

So you add menu entry in config.sys with drivers needed (windows has its own drivers but IIRC it needed himem.sys before running win.exe) So up to w9x it can be also used to select OS as the Windows was just an executable on top of MS-DOS. The config.sys is for loading drivers and autoexec.bat is used to set prompt, variables, TSRs and run desired apps. These two files are use by MS-DOS startup. Yes MS-DOS menu is in autoexec.bat and config.sys.

#Autoexec bat commands manual

DR DOS 5 and later implemented its own menu system, in a more manual fashion. the CD-ROM driver, sound card setup with a PCI card, network drivers.)įor older versions of MS-DOS, there were separate boot configuration tools available, including some which allowed for early-boot selection of CONFIG.SYS directives. (you’d need more for a multi-tasking environment this could be what your friend’s “Windows” configuration changed)

the amount of resources assigned to FILES, BUFFERS etc.

the memory manager: HIMEM.SYS only (for games which wouldn’t work with a V86 memory manager), EMM386.EXE with or without EMS (without EMS, you’d get 64K more UMBs).

This kind of menu would typically be used to control the configuration of The AUTOEXEC.BAT can use the %CONFIG% variable to adjust its behaviour depending on the chosen entry: OFF The block is taken into account in all cases, as long as it comes first it can be repeated if necessary. With appropriate settings in the and blocks.

#Autoexec bat commands Pc

Assuming this was a PC running MS-DOS 6 or later, this would typically be implemented using a CONFIG.SYS menu: