X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
From:	"Rod Pemberton" <dont_use_email AT xnothavet DOT cqm>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Working with bash and cat
Date:	Mon, 03 Mar 2014 14:53:41 -0500
Organization:	Aioe.org NNTP Server
Lines:	46
Message-ID:	<op.xb5v7rn56zenlw@localhost>
References:	<528996CE DOT 9020803 AT codespunk DOT com> <528A4CED DOT 8030200 AT codespunk DOT com>
	<f3c86248-7e22-4106-8b24-2236027e48b1 AT googlegroups DOT com>
	<f6cf9ddf-cbe6-4b8f-a188-ceec82c9b7d1 AT googlegroups DOT com>
	<a6e46859-c0db-45d2-96c8-b54b07e443f6 AT googlegroups DOT com>
	<a2145c9a-c5c5-4b7f-a7b4-208dfdf534a4 AT googlegroups DOT com>
NNTP-Posting-Host:	CNsg4fVcCsvs3UaOgZtQCw.user.speranza.aioe.org
Mime-Version:	1.0
X-Complaints-To:	abuse AT aioe DOT org
User-Agent:	Opera Mail/12.16 (Linux)
X-Notice:	Filtered by postfilter v. 0.8.2
Bytes:	2478
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Mon, 03 Mar 2014 05:30:53 -0500, palxex <palxex AT gmail DOT com> wrote:
> On Monday, March 3, 2014 2:36:07 PM UTC+8, rug DOT  DOT  DOT  AT gmail DOT com wrote:

>> Is this on native hardware or inside a VM?
>>
> Native Hardware. A 1st-generation i7 CPU with 8G DDR3 - other hardware  
> detail can be find by google Quanta TW9 barebone.

I'm not sure what the problem is, but I'm wondering if
the huge amount of memory, 8GB, is a factor.  DJGPP -
specifically, the DPMI hosts - might have problems with
more than 4GB.  Windows 98 does not like more than 1GB.


Have you tried an XMS host that can restrict memory?
E.g., Japheth's HIMEMX, in config.sys, with 1GB limit:

   DEVICE=HIMEMX.EXE/MAX=1048576


Or, could it be some other DOS setup issue?

Are you using a RAMDISK with known memory limitations?
E.g., Franck Uberto's XMSDSK has a 2GB limit.  If using
this, disable it completely.  In fact, disable any ramdisk.

Is LASTDRIVE set to 'Z'?  What is your FILES setting
in config.sys?  If it's low, perhaps try 50 or 120.

Are you using a device loader like DEVLOAD or DDL to
load your device drivers?  Try loading them directly
in config.sys or autoexec.bat.

Do you have any USB device drivers loaded?  If so, could
you disable *all* of them?

Also, try renaming your config.sys and autoexec.bat to
backups.  I.e., don't load anything at all in your DOS
config files.


Japheth's HIMEMX
http://www.japheth.de/Jemm.html


Rod Pemberton

- Raw text -