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 2). "fix" it in FreeDOS' kernel?;-)
--
Am 18.06.2012 um 22:15 schrieb Aitor Santamaría:
> I suspect JEMM may make the DOS' memory allocation strategy functions less
> robust than they are with other DOSes.
For what it's worth: The problem doesn't occur with JEMMEX v5.61 and started to
occur in JEMMEX v5.62 and all following versio
Am 18.06.2012 um 22:15 schrieb Aitor Santamaría:
> There were in the past conflicts with KEYB 2.00 and JEMM that were apparently
> solved with KEYB 2.01.
> The NOHI option mostly controlls KEYB access to XMS, but reading this thread,
> and knowing what I fixed 2.00 to 2.01, I suspect JEMM may m
Hi,
old thread ;)
There were in the past conflicts with KEYB 2.00 and JEMM that were
apparently solved with KEYB 2.01.
The NOHI option mostly controlls KEYB access to XMS, but reading this
thread, and knowing what I fixed 2.00 to 2.01, I suspect JEMM may make the
DOS' memory allocation strategy f
The highest clock rates that were sold were 200MHz for Pentium, 233MHz for
Pentium MMX, and 300MHz for Mobile Pentium MMX. The late mobile chips were
made with a finer process (250nm IIRC).
On Mon, 18 Jun 2012 11:25:01 -0400, David C. Kerber
wrote:
> Pentium definitely came in a 233MHz ver
Pentium definitely came in a 233MHz version, but I thought the 300MHz version
was Pentium II only.
> -Original Message-
> From: Rugxulo [mailto:rugx...@gmail.com]
> Sent: Monday, June 18, 2012 12:10 AM
> To: freedos-user@lists.sourceforge.net
> Subject: Re: [Freedos-user] Networking
>
> Tom Ehlert wrote:
>> try using MSDOS or linux (or even Windows) for the
>> 'server' machine, and see if the problema go away
> I did the test with MS-DOS in the server and FreeDOS in the
> client.
> The problem vanished.
> I even used "MODE con rate=32" which is the fastest typematic
> rate,
> > Aha! So that's why one of my favorite text editors won't run in
> > some machines; it' the same error message, and it uses the
> > Borland interface too.
> Which editor? An assortment use the Borland interface. Some
> are based on the old Borland Editor Toolkit, but I believe there
> are a f
