OT: Why does my system crash when booted from floppy?

On Mon, 16 Dec 2013 20:52:23 -0800, josephkk Gave us:

The cubox-i I suggested is only about 3 watts consumption but proved a complete computer to take him to a whole new level of light control, were that what he wanted. But one would run "DOSBox" emulator in that, and the DOS app inside of that. Or he could write his own code.

Far better than any raspberry give us more money to make it work pi.

and serial ports, using a DOS window in win98. Works fine when run from win98 inside a DOS window, but seems to hang up after a couple hours when run from a floppy that just boots to a command prompt and runs the program from the autoexec file. I wanted to run the program automatically, so I didn't need a keyboard or screen or mouse. Works fine for a couple hours and then hangs up, but not always in the same place.

running a DOS program? But that would require a screen and mouse to turn off the machine. I'm trying to make it automatic so I can just switch it on and off.

Maybe the answer is to just run dos only. (or a text only linux or BSDUnix). A modified RasPi would be overkill in terms of CPU power.

?-)

You could push it higher, but 20 was the default limit.

There are two different issues here. I first noticed these in the late

Failing to free anything that is no longer needed is a serious program bug.

In a system required to run running for days, weeks or years without restart, the dynamic memory fragmentation can become an issue. Unfortunately, this is very hard to analyze.

Properly maintained VAX/VMS machines were quite stable, so the only reason to boot such machines every few years was after some serious HW failure to the CPU or system disk.

We were talking about memory leaks. Memory fragmentation is a different beast, though it will lead to memory starvation as well.

Commodore Basic had a command for garbage collection.