Hi,
On Tue, Jan 17, 2017 at 4:00 PM, Jim Hall wrote:
>> On Tue, Jan 17, 2017 at 11:47 AM, Tom Ehlert wrote:
>>>
>>> to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
>>>
>>> what I did:
>>>
>>> download FD12LGC.ISO
>>>
>>> create a new virtual box machine with 512 MB disk
>>>
> On Tue, Jan 17, 2017 at 11:47 AM, Tom Ehlert wrote:
>>
>> to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
>>
>> what I did:
>>
>> download FD12LGC.ISO
>>
>> create a new virtual box machine with 512 MB disk
>> use FD12LGC.ISO to boot the machine.
>> boot machine.
>>
>> 'Unf
Hi,
On Tue, Jan 17, 2017 at 11:47 AM, Tom Ehlert wrote:
>
> to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
>
> what I did:
>
> download FD12LGC.ISO
>
> create a new virtual box machine with 512 MB disk
> use FD12LGC.ISO to boot the machine.
> boot machine.
>
> 'Unfortunatel
I could reproduce this.
it happens in/after findnext()
this error is related to the compiler.
if the source is compiled using TurboC 2.01 the error occures.
compiling the exact same source with TCPP the error is gone.
try www.drivesnapshot.de/freedos/findtcpp.com and
www.drivesnapshot.de/free
Hi,
to reproduce this FIND problem, I tried to setup a new FD1.2 machine.
what I did:
download FD12LGC.ISO
create a new virtual box machine with 512 MB disk
use FD12LGC.ISO to boot the machine.
boot machine.
'Unfortunately, this method of installation is not supported on this
hardware platfor
Originally to: ALL
Hi Troi,
> C:\ELVIS\DOC>find /i "env" e*.htm
> file list ...
> Error reading from drive A: DOS area: general failure
You mean it FIRST checks all files in the current
directory on C: but THEN tries to jump to the A:
drive? That sounds like a bug in the kernel, either
in
Originally to: ALL
I'm curious as to why FreeDOS is trying to read a:. I've built a VM in
VirtualBox and most things work well, but while digging around looking
for information, I got this after a FIND command.
C:\ELVIS\DOC>find /i "env" e*.htm
file list ...
Error reading from drive A: DOS
Originally to: ALL
Thanks. A new technical term. It would have taken a
long time to get that one.
thanks DS
On Sun, 15 Jan 2017 11:47:17 -0500 perditi...@gmail.com writes:
> On Jan 15, 2017 11:23 AM, "Dale E Sterner"
> wrote:
> ...
>
> what does MITM'd mean.
>
> ...
>
> man in the middle
Originally to: ALL
Eric,
>> C:\ELVIS\DOC>find /i "env" e*.htm
>> file list ...
>> Error reading from drive A: DOS area: general failure
>
> Does the same bug happen with find /i "env" C:e*.htm
> and with find /i "env" C:\elvis\doc\e*.htm by the way?
Yes it does. I've seen a few posts and s
Originally to: ALL
Eric,
In the three cases (mine and your two suggestions) if DOSLFN is loaded
and enabled, there is no sign of a problem.
If DOSLFN is not loaded, I get the error.
If DOSLFN has been loaded, but I disable it (DOSLFN /D), the error returns.
So, DOSLFN seems to "fix" the probl
Originally to: ALL
Hi Rugxulo and Troi,
>> It could be a rare kernel bug, but my guess is some buffer overflow in the
>> IO95 lib. I think this problem is hidden by enabling DOSLFN.
>
> Yes indeed that did either mask or "fix" the problem. Thanks.
In that case please tell in which situations
11 matches
Mail list logo
