To: opendos AT delorie DOT com X-Comment-To: "Matthias Paul" References: <8490A580ED4 AT reze-1 DOT rz DOT rwth-aachen DOT de> Message-Id: <2.07b7.1685D.G4JP4S@belous.munic.msk.su> From: "Arkady V.Belousov" Date: Fri, 24 Nov 2000 23:05:16 +0300 (MSK) Organization: Locus X-Mailer: dMail [Demos Mail for DOS v2.07b7] Subject: Re: Optimizing CONFIG.SYS... Lines: 66 MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Reply-To: opendos AT delorie DOT com X-Comment-To: Matthias Paul Hi! 24-ξΟΡ-2000 16:32 PAUL-MA AT reze-1 DOT rz DOT rwth-aachen DOT de (Matthias Paul) wrote to opendos AT delorie DOT com: MP> On Thu, 23 Nov 2000 Arkady V.Belousov asked: >>> Chicago's ENHANCED and SINGLE arguments are accepted, >>> but ignored because they make no use under DR-DOS. MP> ^^^^ MP> err, "sense" is what I meant... >> What mean these arguments? MP> As far as I remember they switch internal flags to control some of MP> the auto-loaded drivers, but right now, I cannot remember what it MP> was exactly, sorry. I do remember that I found them meaningless for MP> DR-DOS when I implemented the other additions. I would have to MP> look up this stuff, if you really need this info. And where else I can get such info? :( MP> Anyone? MP> MULTITRACK=ON is faster, of course, and this is the default chosed MP> by the system when no MULTITRACK= directive was found in CONFIG.SYS MP> (apparently the system runs with MULTITRACK=OFF until this moment). ? =ON is default or systems runs with =OFF? >>>> [common] >>> I would move this directive down to the end of the CONFIG.SYS file. >> Why? MP> Many setup programs look for the MS-DOS style [COMMON] group to place MP> their CONFIG.SYS changes there. Other programs just append their MP> changes to the end of the CONFIG.SYS file. [...] Good reason. :) >>> BREAK=OFF >> =on is much better in my taste: by MS-DOS specifiaction >>differences between ON and OFF are in handling ^Break at disk IO >>time. I.e. if program uses console IO then you can break it even >>with BREAK=OFF, but if program don't access console or disk in long >>time periods then even with BREAK=ON you can't break it. MP> The same is true for DR-DOS (AFAIR: BREAK=OFF means check for break MP> flag only during INT 21h standard I/O, BREAK=ON means check for break MP> flag on *any* INT 21h). MP> Well, since I feel bad about breaking programs any non-offical way, MP> in particular when they are doing disk I/O, I prefer BREAK=OFF MP> (for special purpose exceptions see below). I usually try to avoid MP> anything that could possibly cause corruption of the disk system. MP> This is just a matter of personal taste, and there's nothing wrong MP> in general with using BREAK=ON. [...] MP> Well, I know CTRL+C is sometimes used to break hanging programs during MP> development, but I don't need this, because Axel's and mine's advanced MP> keyboard driver FreeKEYB (as well as its pre-decessor K3PLUS) provides MP> several extended break methods being more adequate for this purpose: I use special purpose program for this. :) MP> Oh, I forgot, BREAK=OFF makes the system slightly faster... ;-) How much this makes system faster? Does this mean =OFF changes INT 21 handler code to bypass BREAK checking? If not then speedup almost virtual. P.S. Thank you for info.