On Sun, 18 Apr 2021 at 12:34, Eric Auer <[email protected]> wrote: > > If you have only autoexec.bat and config.sys then FreeDOS > will use those. The reason why FreeDOS first tries fdconfig.sys > is that you can install FreeDOS and MS DOS on the same drive > with a boot manager and people wanted to be able to have two > different sets of config files in that case :-) But again, you > can simply use the classic MS DOS style config file names with > FreeDOS as well if you do not need the distinction.
One of the _very_ annoying things about attempting to discuss the differences between OS implementations (e.g. PC DOS vs MS-DOS vs DR DOS vs FreeDOS), or Linux distros, or Linux vs *BSD * SCO Xenix/Unix, is that people assume that one's knowledge level is lower than their own. I've been using DOS for 36 years, professionally implemented, supported and maintained it for ~20 years starting 33 years ago, and still use it for fun. *PLEASE* do not patronise me by attempting to explain small stuff like this to me. Assume I know what I am talking about. Try to imagine that you're talking to someone whose knowledge level is the same or greater than your own. I occasionally put FreeDOS onto a USB stick to flash BIOSes. I tried v1.0 when it came out, to wipe some old PCs I was donating to Computers4Africa: https://www.ictforeducation.co.uk/details/computers-4-africa.html I was startled to discover that my name was in the credits. I was peripherally involved in the FreeGEM project, I wrote and translated some docs, debugged the installation batch files for Shane Coughlan's OpenGEM, and so my name was in there. I do not claim to be a FreeDOS expert. I could, though, claim to be a PC, MS and DR DOS expert. Your messages, along with Tom Ehlert's, are making me very very angry and it with real effort that I am typing a calm and reasonable response. As an example of how I do not like changes to DOS, I avoided 4DOS back in the day, because it broke some of my batch files. I displayed messages in AUTOEXCEC.BAT telling my customers, for example... Drive A: is the 5.25" disk drive Drive B: is the 3.5" disk drive This does not work in 4DOS, because 4DOS insists that text output with the `ECHO` command has matching single or double quotes, whereas in COMMAND.COM, it echoes unquoted text without break characters before quotes. If a product breaks compatibility with existing config files or scripts without offering a *substantial* benefit in return, then I will not use it. FreeDOS commands are different in places; output is different in places. That is fair; it is a community effort and an unauthorised copy of a long-obsolete OS. I have no right to demand 100% compatibility, and I don't. But I was surprised and annoyed by the differences, and since at present I only use DOS for fun, then I will not use something that annoys me. > In that case, which small classic drivers do you recommend? I don't. *Particularly* in the light of this: > PS: No, I do not need downloads of other copyrighted DOSes. Which I find *highly* offensive, annoying, and is in fact inaccurate, unfair and unrepresentative. I will not reply as I want to. I am trying to be polite. You do not appear to be interested; you only seem to want to needle me. I am not rising to it. You do not seem to want to know. You seem to want to falsely accuse me of piracy. If you want to know, I have given you the clues. Go find out for yourself. The next impolite email I receive from you will result in a block. Ditto for Ehlert. This will not inconvenience you, but unless you actively like attacking strangers on the internet who are trying to offer help, guidance and advice free of charge, _modify your tone_. -- Liam Proven – Profile: https://about.me/liamproven Email: [email protected] – gMail/gTalk/gHangouts: [email protected] Twitter/Facebook/LinkedIn/Flickr: lproven – Skype: liamproven UK: +44 7939-087884 – ČR (+ WhatsApp/Telegram/Signal): +420 702 829 053 _______________________________________________ Freedos-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-user
