>> 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,
Below is a message I received from the DataPerfect discussion
group.
Regards,
Marcos
--
Marcos Fávero Florence de Barros
Campinas, Brazil
Date: Tue, 19 Jun 2012 13:54:57 +1000
From: "Brian Hancock"
To:
Subject: Re: [Dataperf] Networking DP
Hi Marcos,
Hi,
On Thu, Jun 14, 2012 at 9:07 AM, Kenny 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 itself every
> time t
On 6/18/2012 11:00 PM, Rugxulo wrote:
> Hi,
>
> On Mon, Jun 18, 2012 at 6:25 AM, Tom Ehlert 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
>> 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... ;-)
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 possibilit
> 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.
The DR-DOS discrepancy described in RBIL evidently indicates that the
owner and applicability seman
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 combi
> 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 s
>> On Mon, Jun 18, 2012 at 6:25 AM, Tom Ehlert 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
11 matches
Mail list logo
