Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!mcsun!ukc!axion!rtf.bt.co.uk!traub From: traub@rtf.bt.co.uk (Michael Traub) Newsgroups: comp.os.msdos.misc Subject: Re: Why is erase *.* slower with 4dos.com than with command.com? Message-ID: <1991May21.074445.14677@rtf.bt.co.uk> Date: 21 May 91 07:44:45 GMT Article-I.D.: rtf.1991May21.074445.14677 References: Organization: BT Customer Systems, Brighton, UK Lines: 22 In article halcyon!ralphs@seattleu.edu (Ralph Sims) writes: >komarimf@spiff.soe.clarkson.edu (Mark Komarinski) writes: > >> akoivuma@finsun.csc.fi (Antti Koivumaki) writes: > >> >I have noticed that when I use 4dos.com, erase *.* works much slower than >> >when command.com is used. I tested this by erasing 100 files using each. > >It may have to do this in conjunction with its other options (confirm a file >deletion or to force a 'y' response to deleting an entire directory). The >DIR command is also slightly different from OtherDOS, and takes longer. >The ability to attach file descriptions may also force a different internal >search routine. 4DOS does more, and that may be the reason it takes a >tad longer on some functions--it's a minor thing, considering everything >it DOES do. Actually I think you'll find that Command.Com uses the old style FCBS while 4DOS doesn't and that is the main cause of the perceived slowness. Michael Traub BT Customer Systems, Brighton Systems Centre. traub@rtf.bt.co.uk