Re: [Freedos-user] after
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 that sound somewhat similar after running some searches, but nothing quite seemed to be this problem. Not a huge deal for me, there's no 15 seconds of drive A: clanking to deal with :) -- 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 --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- 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] after
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 the drive status init or in findfirst / findnext and to be honest I think that has happened before? 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? Regards, Eric -- 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 --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- 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] after
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.drivesnapshot.de/freedos/findtc21.com of course this can be a kernel bug, but as well a turbo library bug, or some sort of interference between them. 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 --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- 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] after
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, at least from a user perspective. This is FD 1.2. Thanks again. >>> 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 and in which not, for example with/without having > DOSLFN loaded :-) It could still be a bug caused by kernel > limitations which affect LFN file listing more than 8.3? -- 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 --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- 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] after
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 bug does happen and in which not, for example with/without having DOSLFN loaded :-) It could still be a bug caused by kernel limitations which affect LFN file listing more than 8.3? Cheers, Eric -- 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 --- Internet Rex 2.29 * Origin: capcity2.synchro.net - 502/875-8938 (1:2320/105.99) --- * BgNet 1.0b12 = CCO * KY/US * 502/875-8938 * capcity2.synchro.net --- Synchronet 3.15a-Linux ListGate 1.3 * Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net -- 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] after
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.drivesnapshot.de/freedos/findtc21.com of course this can be a kernel bug, but as well a turbo library bug, or some sort of interference between them. 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 -- 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] after find, Error reading from drive A: DOS area: general failure.
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/freedos/findtc21.com of course this can be a kernel bug, but as well a turbo library bug, or some sort of interference between them. 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] after
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 the drive status init or in findfirst / findnext and to be honest I think that has happened before? 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? Regards, Eric -- 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 -- 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] after
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 such that sound somewhat similar after running some searches, but nothing quite seemed to be this problem. Not a huge deal for me, there's no 15 seconds of drive A: clanking to deal with :) -- 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 -- 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] after
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 problem, at least from a user perspective. This is FD 1.2. Thanks again. >>> 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 and in which not, for example with/without having > DOSLFN loaded :-) It could still be a bug caused by kernel > limitations which affect LFN file listing more than 8.3? -- 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 -- 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] after
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 the bug does happen and in which not, for example with/without having DOSLFN loaded :-) It could still be a bug caused by kernel limitations which affect LFN file listing more than 8.3? Cheers, Eric -- 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 -- 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] after find, Error reading from drive A: DOS area: general failure.
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 user perspective. This is FD 1.2. Thanks again. >>> 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 and in which not, for example with/without having > DOSLFN loaded :-) It could still be a bug caused by kernel > limitations which affect LFN file listing more than 8.3? -- 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] after find, Error reading from drive A: DOS area: general failure.
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 and in which not, for example with/without having DOSLFN loaded :-) It could still be a bug caused by kernel limitations which affect LFN file listing more than 8.3? Cheers, Eric -- 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] after find, Error reading from drive A: DOS area: general failure.
> 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 commands are available. I remembered Find so that's what I used :) -- 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] after find, Error reading from drive A: DOS area: general failure.
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 somewhat similar after running some searches, but nothing quite seemed to be this problem. Not a huge deal for me, there's no 15 seconds of drive A: clanking to deal with :) -- 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] after find, Error reading from drive A: DOS area: general failure.
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 like a bug in the kernel, either > in the drive status init or in findfirst / findnext 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. But I personally just avoid Find and use Xgrep instead. -- 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] after find, Error reading from drive A: DOS area: general failure.
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 init or in findfirst / findnext and to be honest I think that has happened before? 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? Regards, Eric -- 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] After PG 1.14
[...] >> . 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, does the author still care about it? >> > No idea, who made it? > START was written by Joe Cosentino <[EMAIL PROTECTED]> -- I'm sorry my president's an idiot. I didn't vote for him. --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] After PG 1.14
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 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, does the author still care about it? No idea, who made it? Bernd --- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] after fdos boot : Kick!
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 back in and turn the laptop > on. Problem went away. On an older laptop I would have pushed the > reset button in back but this newer thinkpad does not have a reset > button. > i didn't found a reset button, but after opening the case i found something that looked like a battery. after "desoldering" it from the board the "kick" went away too, seems it was really just getting into "suspend". kinda surprising for a laptop that is that old. but thanks a lot for the idea. tassilo --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] after fdos boot : Kick!
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 show me the memory test or this > "bios message" or the first blinking of fdd or hdd when u > usualy tun on the pc... >> another solution is to remove the METAKERN.SYS from the >> diskette, and rename KERNEL.SYS into METAKERN.SYS that should >> allow you to boot the diskette. > 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 back in and turn the laptop on. Problem went away. On an older laptop I would have pushed the reset button in back but this newer thinkpad does not have a reset button. -- Best regards, BWMarcotte Using The Bat! v2.12.02 on Windows 2000 5.0 Build 2195 Service Pack 3 pgp980XcVWQmk.pgp Description: PGP signature
Re: [Freedos-user] after fdos boot : Kick!
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 diskette? > kernel.sys is present > can you please try a newer version? > http://fdos.org/ripcord/beta9-final/test/B9BOOT01.IMG > 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 show me the memory test or this "bios message" or the first blinking of fdd or hdd when u usualy tun on the pc... > another solution is to remove the METAKERN.SYS from the diskette, and > rename KERNEL.SYS into METAKERN.SYS > that should allow you to boot the diskette. > doesn't work to. see above :) have a nice day markus --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] after fdos boot : Kick!
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 newer version? http://fdos.org/ripcord/beta9-final/test/B9BOOT01.IMG another solution is to remove the METAKERN.SYS from the diskette, and rename KERNEL.SYS into METAKERN.SYS that should allow you to boot the diskette. Perhaps Eric used some 386+ code in his bootloader, don't know. Bernd --- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php ___ Freedos-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-user
