On 6/25/2019 12:52 PM, Jim Hall wrote:
On 6/25/2019 12:23 PM, Joseph Norton wrote:
Hi listers:
Using FreeDOS 1.3 RC1, whenever I use the find command, after it
has finished its work, I get an error which says it can’t read
from the A: drive.
I am running from a virtual machine, and this happenes if there
is no disk in the drive. If there is a disk in the A: drive,
find exits normally.
Has anyone else experienced this?
On Tue, Jun 25, 2019 at 2:33 PM Ralf Quint <freedos...@gmail.com
<mailto:freedos...@gmail.com>> wrote:
Well, no, haven't used find like in decades. What is the contents
of your PATH environment variable and that of COMSPEC?
Ralf
I can confirm this happens. FIND breaks when you search for something.
Doesn't break if you run FIND without arguments. (5k screenshot
attached, should make it through the listserv.)
I'll take a peek at sources to see if I can figure out why.
Well, there are still two options. Either there is a bug in the source
code of FIND or there is an issue with the PATH and/or COMSPEC, which
causes the error actually AFTER FIND terminates. Hence I asked for the
contents of those two env vars to narrow the options down...
Ralf
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
