Re: [Freedos-user] Command prompt returns without commands executing
Blair Campbell schreef: >> the data from XMS... There might be some code which decides about >> whether restore-from-XMS is needed and which is too optimistic. But >> maybe I am totally wrong about that whole swap/overwrite topic... >> > > >From what I can tell it always swaps back from XMS and there is no > other memory block that I am aware of. > Would your changes to FreeCOM be worthwile to be published at the same time as 2038 (in other words to be included as a new FreeCOM version, included with 2038 release) ?. Bernd -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command prompt returns without commands executing
> the data from XMS... There might be some code which decides about > whether restore-from-XMS is needed and which is too optimistic. But > maybe I am totally wrong about that whole swap/overwrite topic... >From what I can tell it always swaps back from XMS and there is no other memory block that I am aware of. > > If the problem can be avoided by not loading EMM386, the cause might > be that EMM386 allows some area to be used by DOS (and freecom) as > UMB while that area has contents changed by BIOS or because of some > hardware activity (sound, network, usb, disk access etc etc)...? > > Eric > > > -- > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensign option that enables unlimited > royalty-free distribution of the report engine for externally facing > server and web deployment. > http://p.sf.net/sfu/businessobjects > ___ > Freedos-user mailing list > Freedos-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-user > -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command prompt returns without commands executing
Hi Alex, > On Sun, 08 Mar 2009 16:20:40 +0100, I waved a wand and this message > magically appears in front of Eric Auer: > >> Indeed a very annoying bug in FreeCOM 0.84 but nobody has yet found >> a way to predict WHEN it happens. If you can find a way to make it >> happen at a more specific time than "after a while", we could use a >> debugger to find out what exactly happens when things break. Note >> that only running com/exe/... (external commands) breaks, you can >> typically still run internal commands like DIR. Is this the same bug >> that you are experiencing? > > Smells like a stack overflow somewhere, methinks, Another option might be "overwriteable part of FreeCOM overwritten but FreeCOM failed to notice"...? Background: It moves some data to the end of some memory block and when you run a DOS app which does not overwrite that block then FreeCOM can avoid having to restore the data from XMS... There might be some code which decides about whether restore-from-XMS is needed and which is too optimistic. But maybe I am totally wrong about that whole swap/overwrite topic... If the problem can be avoided by not loading EMM386, the cause might be that EMM386 allows some area to be used by DOS (and freecom) as UMB while that area has contents changed by BIOS or because of some hardware activity (sound, network, usb, disk access etc etc)...? Eric -- Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command prompt returns without commands executing
On Sun, 08 Mar 2009 16:20:40 +0100, I waved a wand and this message magically appears in front of Eric Auer: > Indeed a very annoying bug in FreeCOM 0.84 but nobody has yet found > a way to predict WHEN it happens. If you can find a way to make it > happen at a more specific time than "after a while", we could use a > debugger to find out what exactly happens when things break. Note > that only running com/exe/... (external commands) breaks, you can > typically still run internal commands like DIR. Is this the same bug > that you are experiencing? Smells like a stack overflow somewhere, methinks, -- http://www.munted.org.uk Fearsome grindings. -- ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command prompt returns without commands executing
Hi Shane Baggs, > I'm using the FreeDOS 1.0 distribution CD for developers. That is a bit old compared to Rugxulo's but okay... > When I push F3 immediately after booting, garbage characters display. What does F3 do normally? > When FreeDOS has been running for a while, the command prompt will > return without the command executing. Rebooting will "fix" this for a while. Indeed a very annoying bug in FreeCOM 0.84 but nobody has yet found a way to predict WHEN it happens. If you can find a way to make it happen at a more specific time than "after a while", we could use a debugger to find out what exactly happens when things break. Note that only running com/exe/... (external commands) breaks, you can typically still run internal commands like DIR. Is this the same bug that you are experiencing? If you do not need long file name support in internal commands, you can downgrade to the older FreeCOM 0.82pl3 version of command.com, it has never shown the bug you describe as far as I remember :-). You can also use the alternative command shell 4DOS, which became free softare a while ago. Sure, it differs from command.com a bit. > I tried eliminating all use of high memory and UMB. The problem persists. Did you also try not loading (J)EMM386 but only loading HIMEM(X)...? > Not loading a memory manager can make the problem take longer to occur. Okay but it still occurs, not good... And you should loat at least HIMEM(X) and use DOS=HIGH because otherwise DOS uses much more RAM. > I tried using Rugxulo's floppy distribution (disk 1) which is based > on a later kernel -- no difference. The instability is in FreeCOM 0.84 command.com, not in the kernel. > The first computer is a tower with an Intel SE440BX2 mainboard, P3/550, > 256 MB RAM, and an 80GB drive with a 40GB FAT32 partition. > > The second computer is a Compaq Armada 3500 notebook, P2/366, > 128 MB RAM, 6GB HDD with FAT32. Thanks for the details. > The disks were originally formatted with Windows 98 SE. > They now boot to MetaKern. The tower passes MEMTEST86. > > There's not a lot on the internet about this, but I can't be the only > one this has happened to! You definitely are not the only one. As said, the problem is finding a method to reproduce it at a moment while a debugger is pointed at command.com to find out what exactly goes wrong. You can also have a look at the sources, but people have done so before so it does not seem to be anything blatantly obvious. Thanks for reporting :-). Please let us know when you have more ideas on how we could reproduce and possibly fix it in 0.84 :-) Eric -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Command prompt returns without commands executing
On Sunday 08 March 2009 14:40, Shane Baggs wrote: > When I push F3 immediately after booting, garbage characters display. > > When FreeDOS has been running for a while, the command prompt will return > without the command executing. Rebooting will "fix" this for a while. Hi, I experienced similar troubles in the past. It appeared finally that the EMM manager I was using was not-so-compatible with my chipset hardware. Upgrading to the latest JEMM386 fixed all my problems. :-) To upgrade your FreeDOS system easily, you can use FDUPDATE. This program will check in what versions your local packages are, and upgrade them using the repository at http://www.viste-family.net/mateusz/fdupdate/ Of course, it requires a network card with a working packet driver. Best regards, Mateusz Viste -- You'll find my public OpenPGP key at http://www.viste-family.net/mateusz/pub_key signature.asc Description: This is a digitally signed message part. -- Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
