Don, could you (or anybody else) prepare a virtual disk/floppy where this bug can be reproduced?
If so, I'll give it a shot, as this seems to be the first reproducable memory corruption bug in freecom. Tom am 6. Juni 2016 um 12:42 schrieben Sie: >>So "all my path variables are intact" means there is probably a memory >>corruption issue somewhere?? > Since this happens on every PC (7 total) that is unlikely; and > this does not happen with the regular DOSes. > I am now using a menu (PowerMenu by Brown Bag Software) with the > %WPSHELL%/C command and our current FreeCOM which is working well. >>You mean "SET" within FDCONFIG.SYS?? > > I have a MENU selection in FDCONFIG.SYS pointing to an IF > "%config%" option in AUTOEXEC.BAT which loads my PowerMenu which > takes over from there, this is the "cleanest" way of resolving the issue that > I have found. >>But yes, FreeCOM has various bugs and needs to be cleaned up and >fixed >>(eventually), but so far nobody has stepped up to do it. > Yeah, we need to prioritize that for 2.0. > > On Mon, Jun 6, 2016 at 4:31 AM, Rugxulo <rugx...@gmail.com> wrote: > Hi, > > On Sat, Jun 4, 2016 at 4:34 AM, Don Flowers <donr...@gmail.com> wrote: >> UPDATE: >> So after three or four loads of shell.exe per session, the strings error >> showed up again (Freecom 0.84) > > Even when using "/MSG /P"? So what is the implication, that there's a > memory leak in FreeCOM somewhere? I wouldn't be too surprised. > >> and Freecom 0.80 has some issues (2GB max shown on HD, OGN not recognized) > > Testing an old release for comparison? Why not test 0.82pl3 from SF.net? > > > https://sourceforge.net/projects/freedos/files/FreeCOM/082pl3%20%28use%20xmsswap%20for%20386%2B%20PC%29/ > > But yes, FreeCOM has various bugs and needs to be cleaned up and fixed > (eventually), but so far nobody has stepped up to do it. > >> I discovered one other alternative that seems to be working - I set a >> %config% variable (SET WPSHELL=C:\DP23\SHELL.EXE), > > You mean "SET" within FDCONFIG.SYS?? > >> then %WPSHELL% /C; >> following that I execute a batch file with the same command and the shell >> loads as it should and on exit all my path variables are intact with no >> strings error messages. > > So "all my path variables are intact" means there is probably a memory > corruption issue somewhere?? > > >> On Mon, May 23, 2016 at 5:21 PM, Rugxulo <rugx...@gmail.com> wrote: >>> >>> On Mon, May 23, 2016 at 4:18 PM, Don Flowers <donr...@gmail.com> wrote: >>> > >>> > So /MSG seems to work, more testing needed to be sure, What does this >>> > switch >>> > do, (besides help me of course)? >>> >>> http://help.fdos.org/en/hhstndrd/base/command.htm >>> >>> "/MSG Stores all error messages in memory (requires /P as well)." > > > ------------------------------------------------------------------------------ > What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic > patterns at an interface-level. Reveals which users, apps, and protocols are > consuming the most bandwidth. Provides multi-vendor support for NetFlow, > J-Flow, sFlow and other flows. Make informed decisions using capacity > planning reports. > https://ad.doubleclick.net/ddm/clk/305295220;132659582;e > > _______________________________________________ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > Mit freundlichen Grüßen/Kind regards Tom Ehlert +49-241-79886 ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
