Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!mailrus!uunet!bcstec!iftccu!bressler
From: bressler@iftccu.ca.boeing.com (Rick Bressler)
Newsgroups: comp.sys.ibm.pc
Subject: Re: 4DOS 3.0 Bug?
Message-ID: <1470004@iftccu.ca.boeing.com>
Date: 1 Jun 90 00:00:27 GMT
References: <20707@mbf.UUCP>
Organization: Boeing Commercial Airplane Group
Lines: 31

> Some time back someone posted a notice about a bug in 4dos 3.0.  I would
> like to install this but I am reluctant since I don't recall what the
> bug was, only that it was dangerous.
> 
> Could someone please email me the relevant information (or repost it,
> but just once, please, in alt.msdos.programmer)?  Thanks in advance.
> 

The bug that I saw was that the move command would allow you to move a 
file or group of files to NUL, which resulted in deleting the file.  

Actually, while dangerous, it doesn't seem like a bug to me. Dos 
considers its special devices  (con, lpt etc..) to be files, and if you
can copy a file to lpt1, why shouldn't you be able to move it to NUL?
The device belongs to dos, not 4dos.

I've also seen complaints that files with special names like lpt1.xxx
can't be created, but I've also had this problem with command.com.  Dos 
(not 4dos) apparently looks at the filename to see if it matches a special 
device name before it checks the extension, thus lpt1.xxx is equivelent 
to lpt1 which is reserved etc...

I've been using a *registered* copy of 4dos for about 6 weeks now and  have
found no real problems.  It seems like a good product.  There is a 
disclaimer in the documentation to the effect that 4dos is a 
powerful tool, and thus gives you many more ways to get into trouble if you
aren't careful / aware. This is true.  I'd suggest windows or a MAC for the 
faint of heart.  Unix users should love it if they are forced to use dos on 
occasion.

-rick-