Re: [Freedos-user] after

2017-05-06 Thread BLAMETROI
From: BlameTroi <blamet...@gmail.com> 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

[Freedos-user] after find

2017-05-06 Thread BLAMETROI
From: BlameTroi <blamet...@gmail.com> 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 .

Re: [Freedos-user] after

2017-05-06 Thread BLAMETROI
From: BlameTroi <blamet...@gmail.com> 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

[Freedos-user] after find

2017-01-17 Thread BlameTroi
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

Re: [Freedos-user] after

2017-01-17 Thread BlameTroi
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

Re: [Freedos-user] after

2017-01-17 Thread BlameTroi
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

Re: [Freedos-user] after find, Error reading from drive A: DOS area: general failure.

2017-01-16 Thread 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, at least from a

Re: [Freedos-user] after find, Error reading from drive A: DOS area: general failure.

2017-01-16 Thread BlameTroi
> 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

Re: [Freedos-user] after find, Error reading from drive A: DOS area: general failure.

2017-01-16 Thread 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 that sound

[Freedos-user] after find, Error reading from drive A: DOS area: general failure.

2017-01-16 Thread 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 area: general