Re: [Freedos-user] Bug with FreeDOS 1.2 and "find"?

2017-01-20 Thread Ulrich Hansen

> Am 20.01.2017 um 17:21 schrieb Tom Ehlert :
> 
> as stated elsewhere, the bug happens when
> 
>FIND is compiled using TC 2.01
>you have no drive in A:
> 
> it's simply a bug in FIND

Thank you very much. I was just curious. Never came across it before.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Bug with FreeDOS 1.2 and "find"?

2017-01-20 Thread Tom Ehlert

>> Am 16.01.2017 um 13:12 schrieb BlameTroi :
>> I got this after a FIND command.
>> 
>> C:\ELVIS\DOC>find /i "env" e*.htm
>>  file list ...
>> Error reading from drive A: DOS area: general failure
>> 
>> I've triple checked and I have nothing in my autoexec or config that
>> points to drive A:, nor does A: show up in any of the environment
>> variables. Of course, that drive is empty.

> I can verify the problem in FreeDOS 1.2. It doesn’t happen in FreeDOS 1.1.
> Look at the screenshot:
> https://lazybrowndog.net/freedos/files/find-bug.png

as stated elsewhere, the bug happens when

FIND is compiled using TC 2.01
you have no drive in A:

it's simply a bug in FIND

Tom




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user


Re: [Freedos-user] Bug with FreeDOS 1.2 and "find"?

2017-01-20 Thread Ulrich Hansen

> Am 16.01.2017 um 13:12 schrieb BlameTroi :
> I got this after a FIND command.
> 
> C:\ELVIS\DOC>find /i "env" e*.htm
>  file list ...
> Error reading from drive A: DOS area: general failure
> 
> I've triple checked and I have nothing in my autoexec or config that
> points to drive A:, nor does A: show up in any of the environment
> variables. Of course, that drive is empty.

I can verify the problem in FreeDOS 1.2. It doesn’t happen in FreeDOS 1.1. 
Look at the screenshot:
https://lazybrowndog.net/freedos/files/find-bug.png




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user