conclusion: don't use FreeDOS as a 'server' machine.
Sure, that's the obvious easy way out.
But wouldn't it be better overall (and wiser) to 1). actually find
out what MS-DOS does, and 2). fix it in FreeDOS' kernel?;-)
sure. as always: talk is cheap
good luck
Tom
Hi,
On Thu, Jun 14, 2012 at 9:07 AM, Kenny cheeseylem...@gmail.com wrote:
I've been having a problem with the edit command. Nothing big or anything,
but every time I open the editor, the word wrap is turned off. I tried using
the save options button, but it just won't work. It resets
conclusion: don't use FreeDOS as a 'server' machine.
Sure, that's the obvious easy way out.
But wouldn't it be better overall (and wiser) to 1). actually find
out what MS-DOS does, and 2). fix it in FreeDOS' kernel?;-)
If you are indicating that you want to volunteer... ;-) (... if that
Whatever the issue is, it is apparently not that easy to find or fix. Reading
RBIL for INT 21.5C, it seem to indicate that DR-DOS never was able to figure
out how to do it, and it wasn't until Novell got involved that it actually
started working correctly.
(E)DR-DOS could be another
Thanks. Here's some comments if you care to read them. Not all of them are
particularly relevant to our thread's topic.
MSDOS, and presumably FreeDOS, does not natively provide a framework for
safe filesharing and file locks, this needs to come from the server
software
working in
Whatever the issue is, it is apparently not that easy to find or
fix.
whatever the issue is, nobody is going to fix it anyway
Reading RBIL for INT 21.5C, it seem to indicate that DR-DOS
never was able to figure out how to do it, and it wasn't until
Novell got involved that it actually
On Mon, Jun 18, 2012 at 6:25 AM, Tom Ehlertt...@drivesnapshot.de wrote:
conclusion: don't use FreeDOS as a 'server' machine.
Sure, that's the obvious easy way out.
But wouldn't it be better overall (and wiser) to 1). actually find
out what MS-DOS does, and 2). fix it in FreeDOS' kernel?
Hi all,
I am happy to announce that some very annoying problems with running FreeDOS as
guest in VirtualBox have been fixed.
Jack R. Ellis has fixed the Virtual floppy change problem this list has
talked about.
Eric Auer has written the free VBOX-FIX.COM, a workaround for a VirtualBox bug
