From: BlameTroi
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 such
From: Eric Auer
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 th
From: BlameTroi
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 ar
From: Tom Ehlert
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.dr
From: BlameTroi
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 problem,
From: Eric Auer
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 the
Originally to: ALL
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.
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
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
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
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 problem, at least from a u
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 the bug does
happen a
> 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.
> But I personally just avoid Find and use Xgrep instead.
I probably will too as I learn what
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 such that sound somewh
Hi,
On Jan 16, 2017 11:24 AM, "Eric Auer" wrote:
>
> > 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 l
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 the drive status ini
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 area: general failure
[...]
>> . I just look around my old FreeDOS release, START is quite nice to
>> play with.
>> I have an idea to make it better handle undefined file extension,
>> but I cannot compile start.c with its respective compiler -- Turbo C++
>> 1.01 or Borland C 4.0
>>
>> START can be dated back to 2000, d
BA HCL schreef:
> Hello,
>
> I guess most people get sick and tired to see more PG news
not at all, BAHCL, just don't know where to obtain your latest releases
from.
Nice to hear from you, by the way :)
> . I just look around my old FreeDOS release, START is quite nice to
> play with.
> I have an i
Hello,
I guess most people get sick and tired to see more PG news.
I just look around my old FreeDOS release, START is quite nice to play
with.
I have an idea to make it better handle undefined file extension,
but I cannot compile start.c with its respective compiler -- Turbo C++ 1.01
or Bor
Hi
> > doesn't work to. see above :)
>
> I have run into a problem similar to this problem on my Thinkpad - the
> system was refusing to reboot and the power button was putting the
> system into suspend mode. My fix was to remove the battery from the
> laptop for 60 seconds then put the battery
Hi Markus,
> no, since i get "kick!" like i turn the pc on and get "kick!"
> doesn't even try to access the fdd or the hdd i think this
> "kick!" is stored somewhere now in a battery buffered area,
> like even if i remove the power plug and then turn it on again,
> it goes STRAIGT to kick doesn't
hi
> this is Eric Auer's MetaKern bootloader that is being used.
> Option 1 is 386-specific,
> Option 2 is to boot the FreeDOS which is on the diskette.
yup, something like this :)
> There it prints "KICK!" and then expects to find KERNEL.SYS
> are you sure KERNEL.SYS file is present on that
Hello Markus,
this is Eric Auer's MetaKern bootloader that is being used.
Option 1 is 386-specific,
Option 2 is to boot the FreeDOS which is on the diskette.
There it prints "KICK!" and then expects to find KERNEL.SYS
are you sure KERNEL.SYS file is present on that diskette?
can you please try a ne
Hi
i made a boot floppy from fdos1440.img (dd if=fdos1440.img of=/dev/fd0a) and when i
booted from that disket it asked me something (forgot) with 1 or 2 to choose i pressed
2
(since the first one was with 386something) then i just got a "Kick!" on the screen.
i cant use ctr-alt-del , even if i
28 matches
Mail list logo
