Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!ncar!boulder!bohemia!Greg.Smith From: Greg.Smith@bohemia.UUCP (Greg Smith) Newsgroups: comp.os.msdos.misc Subject: Re: 4Dos 3.01a Message-ID: <37.26F40099@bohemia.UUCP> Date: 16 Sep 90 12:43:00 GMT Organization: The Bohemia BBS System, Boulder, CO (303)449-8946 Lines: 34 -> DA>Greg, I like 4DOS a lot. On my machine, it does one very -> DA>odd thing, though. -> DA>I'd be interested to know if it's done this anywhere -> DA>else.... -> DA>The first time I give the command "dir" after booting, I -> DA>get a memory parity -> DA>non-maskable interrupt. After I tell the interrupt to go -> DA>away, everything -> DA>seems (?) OK. This has never happened due to 4Dos on my computer (XT clone) I have had memory parity failures, but that is due to some faulty connections or chips scattered throughout the machine. Can you use other commands w/o using dir, and still get the failure when the first dir is issued? If so, It could be a possible bug in 4Dos. What version are you running? I am using 3.01a, and am trying to get ahold of 3.02. -> DA>Anyway - overall I think it's a major improvement on -> DA>COMMAND. Some stuff is -> DA>slow, though; the directory descriptions seem to make -> DA>deletions and file -> DA>moving sluggish. I have noticed that too. On my firends AT, it isn't noticable. I think that only shows up on slow computers... -=+Greg+=- --- QuickBBS 2.64 (Eval) * Origin: Bohemia BBS system (303)449-8946 (200:5000/301) -- Greg Smith - via MetroNet node 200:5000/301 UUCP: ...!boulder!bohemia!Greg.Smith INTERNET: Greg.Smith@bohemia.UUCP