That wasn't really a "compilation of MSDOSes". It is still the best and standalone (although not offically) version of MS-DOS in the world (more information is available from this page), but I won't suggest that to anyone in this forum unless very necessary. There isn't an English version of the CDU website yet, but will be probably available in the future.

0

For the machine and O/S you have I would suggest; config.sys ============= SHELL=c:\COMMAND.COM c:\ /E:256 /p device=c:\dos\setver.exe device=c:\dos\himem.sys device=c:\dos\emm386.exe auto dos=high,umb files=30 autoexec.bat ================== @ECHO OFF PROMPT $d$_$t$_$p$g PATH C:\;C:\DOS;C:\PKWARE rem SCANDISK C: /AUTOFIX /NOSUMMARY /NOSAVE rem DEFRAG C: /U /SE LH C:\DOS\SMARTDRV.exe /X LH c:\dos\mouse if not exist c:\temp md c:\temp SET TEMP=C:\temp set tmp=c:\temp SET COMSPEC=c:\COMMAND.COM SET DIRCMD=/A/O/P/V SET COPYCMD=/V/-Y C:\DOS\MSCDEX.exe /D:MSCD001 /M:10 exit The above mscdex line isn't required as you have no cdrom device driver being loaded in config.sys.

0

about the CD: the reason to that is my uncle took out the CD drive before he put it away. i don't know why, and it's very annoying having a fake D drive that the computer thinks is there.

0

Hey Dan Penny ; ) Take no offense at the following nitpicks Couple of points: SET COMSPEC=c:\COMMAND.COM - not needed (it's the default setting) setver could be loaded high if placed later in the list - 9 times out of 10 it's not even needed smartdrv loads high on its own the 'auto' parameter on emm386 doesn't really do anything since there's a DOS=high,umb statement using shell to set the environment space to 256 - (I believe that's the default for M$-DOS 5 & 6xx) so it either can be removed or else set higher, if needed don't really need an 'exit' command I agree, definitely don't need mscdexe if there's no CD drive - waste of memory I would think that loading drivers for a missing CD drive would generate errors Big improvement over the original though - all those set statements would really chew up environment space

0

Hey jboy! ~I~ certainly take no offence. You've taught me a few things over the last couple of years and it's much appreciated. You're correct on all counts. ("But of course!") ;>) I had taken what he had and crossed it with what I use in my files. (Posted in the Mouse in dos topic by Bryco). My comspec is on D: hence the statement. I just "automatically" put it in and changed the path. Setver I've only used once in 23 years. But since it was there...... I'd forgotton smartdrv loads high automatically. (I've since removed the LH from my autoexec.bat smartdrv lines. Thanks for the reminder.) Also, I don't use the /x switch but...... emm386 - I don't use the auto setting, but I figured the setting would be good for any "old" programs he may have on this "old" machine which may call for expanded memory. From the old MSDOS EMM386.exe Help; "Auto mode enables expanded-memory and upper memory block support only when a program calls for it." I wasn't aware the dos=high,umb statement over-rides this. My shell statement is 512, so I changed it (here) to half that not remembering it (256) is the default. The exit statement is the old school coming out again. "Be specific and always leave it clean." Show off. ;>) So thus; config.sys ============= device=c:\dos\setver.exe device=c:\dos\himem.sys device=c:\dos\emm386.exe dos=high,umb files=30 autoexec.bat ================== @ECHO OFF PROMPT $d$_$t$_$p$g PATH C:\;C:\DOS;C:\PKWARE C:\DOS\SMARTDRV.exe /X LH c:\dos\mouse if not exist c:\temp md c:\temp SET TEMP=C:\temp set tmp=c:\temp SET DIRCMD=/A/O/P/V SET COPYCMD=/V/-Y Jemuzu, I forgot to mention, I can't remember if dos 6.22 contains the deltree command but if it does (look in c:\dos for it) then you can/should remove those program directories/files which are no longer used. ie; (from the dos prompt) deltree c:\vm386 will remove the directory and all files in it.

0

okay, i didn't do any of that because of this. when i have already started my computer and it's been on, if i type autoexec.bat it only does everything up to the defragging or whatever. so what happens happens before dos itself loads. i've tried looking at the BIOS but it isn't the problem either. it says MS-DOS 6.22 startup setting. i set it for no. 2, and it does the normal autoexec.bat stuff.

0

Jemuzu, once you start the system and it's done booting, there is no need to run autoexec.bat again. Dos loads right after the POST screen. (Power On Self Test.) The io.sys and msdos.sys files are your dos operating system. The config.sys and autoexec.bat files are there to load commands/programs (which you deem necessary) to make your dos session easier. You stated in your original posting that you want to get rid of the old programs etc. on this machine. The way to do this has been stated in the responses above. Which is remove the directories/files of that software, and remove the entries pointing to it in autoexec.bat. The rest of the info is to help you get the most out of the machine and operating system. If you do what has been posted here, you will no longer be prompted to enter a 1 or 2 or 3 setting. The system will be done booting and be ready for whatever you want to do/run.

0

okay, if you look crafully, i said that i had deleted the software and i wanted to get rid of the selections. below is a chronological list of what my computer does. energy star BIOS junk shows, tests memory and stuff shows DOS configs asks question, i answer autoexec.bat begins after seeing this, i think it may be similar to an OS boot program only it loads the same OS three times with different settings.

0

Hey Dan Penny Oh yeah, nothing there would have hurt - you know how obsessive I get concerning DOS neatness ; ) If you don't have a lot of 'set' statements, likely the default value of 256 is fine - M$ radically enlarged environment space for DOS7+ Haven't used setver in years, but it grabs less than 1 K, so that's bearable. Deltree should be there, it's a 6.22 file (one never knows though) I've worked on a few of these 386 machines owned by schools or businesses - they always seem to have a pile of clunky commands in the startup files - like defragging every boot! - and a million set statements. *note* defragging at every boot really makes it difficult or impossible to recover deleted files. Why M$ always set the temp directory to 'DOS' is beyond me - messy. From the autoexec.bat, it looks like it was setup for multiple configurations (goto %CONFIG% and :end etc), but that's not reflected in the config.sys as posted (no [menu] line) Jemuzu, you can always rename your original autoexec.bat to autoexec.xxx and give Dan's version a try. DOS is your friend (no, really!) A basic intro here as well as Martin's (x86) tutorial page.

0

"okay, if you look crafully, i said that i had deleted the software and i wanted to get rid of the selections." I say again; "If you do what has been posted here, you will no longer be prompted to enter a 1 or 2 or 3 setting. The system will be done booting and be ready for whatever you want to do/run." "Jemuzu, you can always rename your original autoexec.bat to autoexec.xxx and give Dan's version a try." I suggest you try. At the C:\> prompt; ren autoexec.bat autoexec.xxx is the rename command/syntax.

0

okay, the truth is really funny. my uncle found the windows 3.1 and other stuff he was also going to give me, and part of it was a users guide. i figured out what the problem was, it was in my config.sys, believe it or not. the funny part: i didn't see the config.sys in C:\ so i gave you guys the base config.sys from c:\dos. so i fixed the problem, i have three options (again). DOS, WINDOWS, and DIAGNOSTIC(it does the defragmenting and stuff). thanks for trying to help me!

0

Glad it all sorted out.

0

... told you they didn't match - heh

0

I thought the config.sys file he posted looked fairly vanilla with no config statements in it.

0

Yeah, but the autoexec.bat was structured to work with the multiple configuration feature of DOS6xx (goto %config%) and the various labels :normal :vm386 :dial The real config.sys would likely have a [menu] line as well as [normal], [vm386] and [dial] to reference the labels. That would explain the 'menu' at the startup - which was not supported by the config.sys etc as posted i gave you guys the base config.sys from c:\dos What use is a config.sys file in C:\dos? No biggy, just an "aha!" moment Jemuzu, the DOS 'help' program that comes with 6.22 explains all of that (& much more) - I still refer to it from time to time to refresh my memory.

0

Yeah, that's what I meant by no config statements. The autoexec.bat file had the "follow-up" statements for a config.sys menu and reference labels, but they weren't there. (In config.sys.) I think the logic of c:\dos\config.sys is for backup purposes. (I mean "safety", not MS BACKUP utility.) My existing files are built this way. (They're in the forum somewhere, you've seen them.) And that's exactly what I thought when I read his "resolution" post. "AHA!"

0

Ah, I misread the emphasis. The inadeqacies of textual communication. What, backup an itty bitty config.sys like that one? Pshaw - just make a new one ; ) (I do have mine archived - 76 lines, admittedly, not all strictly necessary) Multi-config, best thing ever when that little DOS feature was implemented.

0