Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rutgers!njin!dblack From: dblack@pilot.njin.net (David Alan Black) Newsgroups: comp.os.msdos.misc Subject: Re: 4Dos 3.01a Message-ID: Date: 12 Sep 90 20:49:16 GMT References: <31.26E59853@bohemia.UUCP> Organization: NJ InterCampus Network, New Brunswick, N.J. Lines: 20 Greg, I like 4DOS a lot. On my machine, it does one very odd thing, though. I'd be interested to know if it's done this anywhere else.... The first time I give the command "dir" after booting, I get a memory parity non-maskable interrupt. After I tell the interrupt to go away, everything seems (?) OK. What's strange is that subsequent "dir" commands don't bother it (including those in secondary shells). Also - dir with anything after it doesn't trigger the interrupt (dir *.txt, dir .., dir \bin, etc.). But even if I'm several hours into a session, and have given all sorts of dir commands like these, the first plain "dir" gets the interrupt. Anyway - overall I think it's a major improvement on COMMAND. Some stuff is slow, though; the directory descriptions seem to make deletions and file moving sluggish. David Black dblack@pilot.njin.net