You really need to be more clear when you write your posts, as I for one have no idea what you are talking about. 😒

How to Ask Questions the Smart Way

In MS-DOS you had to reboot quite often because of issues causes by games\programs. He wants the capability in DOSBox where that is not required.

Instead of a developer trying to analyze every possible way for a DOS program to screw things up it would probably be easier to revert DOSBox back to the same state it was when DOSBox was first started.....problem is when would DOSBox know when to do this.....

A Z: drive "reboot" command initiated by the user would likely be the easiest solution.

SVN already has something like that for restarting: config -r [parameters]

DosFreak wrote:

In MS-DOS you had to reboot quite often because of issues causes by games\programs.

Oh. I have to say that is the first time I have ever heard of this. (Short of programs that just completely hung the system, of course. And there were those that screwed up the video mode upon exit, but those were rare.) Is there a specific example that is common?

I guess "often" depends on what crazy programs you were running and how many. heh.

I wish I had kept a list but never did....easier just to reboot.

Yup config -r appears to work fine.

Jorpho wrote:

Is there a specific example that is common?

I've had Quake progressively cause segfaults everytime I quit eventually affecitng other parts like sound, particularily version 1.00 (not 1.01), on a real system.

Not to mention that so many games needed custom autoexec/config that I found myself rebooting often enough to never encounter that...

well, dosbox could pause/unpause leasurely, surely it counts as something that real system can't do ?