Hi Eric,
>Note: SHCDX33A now in conventional memory, thaks to Eric Auer for advice.
Did you found SHCDX33A have any problem when loaded high? Can you
share your experience with us?
Also Did you tell dima Jack's version was smaller? Then he can save
more base memory.
Rgds,
Johnson.
--
On Sat, 15 Apr 2006 17:09:33 -0500, you wrote:
Hi Sir,
>QHIMEM is a totally new and alternate -- utterly superfluous in my opinion
>-- memory manager that can have nothing to do with your problem, and I do
>not recommend it's use for debugging here.
For trouble shooting purpose, is there any p
>> I tried compiling my code with Watcom. I got extremely strange behaviour
>> -
>> the compiler planted stack checking calls, and the stack checks were
>> *convinced* I needed vast amounts of stack space to proceed with even
>> the
>> first function call out of main(). (I make very little use of
> I tried compiling my code with Watcom. I got extremely strange behaviour -
> the compiler planted stack checking calls, and the stack checks were
> *convinced* I needed vast amounts of stack space to proceed with even the
> first function call out of main(). (I make very little use of the stack.)
QHIMEM is a totally new and alternate -- utterly superfluous in my opinion
-- memory manager that can have nothing to do with your problem, and I do
not recommend it's use for debugging here.
There is no correlation between the HIMEM-style memory manager and an
application's use of upper memor
>
> Hi, did you already try Linux, with your software running
> as root so that it can access all I/O ports directly?
> Or maybe RTLinux to get better "realtime" performance?
My concerns with Linux:
1) It has to have some sort of processing in the background to handle
ethernet and serial ports -
On Sat, 15 Apr 2006, John Hupp wrote:
> MEM /C /P for all 3 machines shows that DISPLAY, NLSFUNC, KEYB and
> LBACACHE are all loading in conventional memory even though they are
> loaded with LH.
Try to use fdxxms.sys + umbpci.sys instead of himem.sys + emm386.exe.
> Have these programs all be
On Sat, 15 Apr 2006 09:42:34 -0400, you wrote:
Hi John,
I got some "new" drivers from my friend Jack, he did code them to save
memory and keep DOS running with the latest hardware (also thanks to
Uwe Sieber, he provide source code of UMBPCI.SYS).
My PC have 620K base memory (including NANSI.SYS,
I'm looking for an OS to run on an embedded system (a 586 based PC104)
board. What I need is pretty simple:
1) Access to ethernet, TCP and UDP. (Waterloo should do it.)
2) The ability to hook interrupts.
3) I need to be able to handle serial ports via interrupts; potentially
more than 4 ports some
Download here:
http://johnson.tmfc.net/freedos/qhimem.html
NEWS
2006-04-16 [ QHIMEM V1.2 ] Fixed 1 major and 2 minor "bugs".
2006-04-13 [ QHIMEM V1.1 ] Added 4-Gigabyte capability and most XMS
V3.0 logic.
2006-04-11 [ QHIMEM V1.0 ] Original Release.
QHIMEM -- DOS XMS Manager
QHIMEM -- DOS XMS Manager, V1.2
===
QHIMEM is a DOS driver that functions as an XMS memory manager. It
is a replacement for HIMEM, FDXMS, and other XMS managers, and it is
meant to complement the UMBPCI Upper-Memory Manager driver. QHIMEM
supports up to 4-Gigabytes o
On Sat, 15 Apr 2006 16:57:18 +0200 (MEST), you wrote:
Hi Eric,
>I finally merged the dosfstools 2.10 -> 2.11 patches into
>my DOS port of DOSFSCK. Actually I had been planning to
>do this since 8/2005, shame on me...
Thanks. You got your own works and daily life, nice to know you spare
time to
At 09:29 AM 4/15/2006 -0400, you wrote:
So I added back a range exclusion, thus: NOEMS X=A000-EFFF VDS NOALTBOOT.
This booted up in unstable condition, locking altogether (or with
Ctrl-Alt-Del still not working).
I increased the exclusion to the range that one of you had recommended:
NOEMS X=A0
Hi all,
I finally merged the dosfstools 2.10 -> 2.11 patches into
my DOS port of DOSFSCK. Actually I had been planning to
do this since 8/2005, shame on me...
http://www.coli.uni-saarland.de/~eric/stuff/soft/by-others/dosdosfsck-2.11.zip
has the sources and the DOS binary (needs a 386 or better
On 3 different old computers (486 to Pentium 100 -
all with at least 16 MB), I installed the new Service Release 2 from the
bootable installation CD. I installed on either FAT16 or FAT32 partitions
(1 to 2 GB) created by FreeDOS. All of the installations were
error-free.
MEM /C /P for a
Hello, all!
On 3 different old computers (486 to Pentium 100 -
all with at least 16 MB), I installed the new Service Release 2 from the
bootable CD. I installed on either FAT16 or FAT32 partitions (1 to 2 GB)
created by FreeDOS. All of the installations were error-free.
On all 3 machine
Thanks to Michael, Chris and Eric for replying to the list or directly.
The number of permutations of a half-dozen command options is rather large,
so I didn't test every possibility. But I think I hit all of your
suggestions:
In my test configuration, I had no AUTOEXEC.BAT and this 3-line CONF
17 matches
Mail list logo
