From:	Colin w Glenn <cwg01 AT gnofn DOT org>
Newsgroups:	comp.os.msdos.djgpp
Subject:	RE: DJGPP under Windows 98... (to ELI)
Date:	Sat, 24 Oct 1998 17:41:16 -0500
Organization:	Greater New Orleans Free-Net
Lines:	33
Message-ID:	<Pine.GSO.3.95.981024173950.28364A-100000@sparkie.gnofn.org>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 981022103016 DOT 2797C-100000 AT is>
NNTP-Posting-Host:	sparkie.gnofn.org
Mime-Version:	1.0
In-Reply-To:	<Pine.SUN.3.91.981022103016.2797C-100000@is>
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Is the PIF set up right?  I've had a few NON-djgpp programs cause this
error before adjusting the pif to 'hard-code' the program's memory.


On Thu, 22 Oct 1998, Eli Zaretskii wrote:

->
->On Thu, 22 Oct 1998, Diego Dominguez Cazorla wrote:
->> 
->> > 	Mine is that Windows 98 complaints about being accessed in a restricted 
->> =
->> > block memory if I run a *.exe file inside a *.bat file. Anyway, it =
->> > *usually* just complaints and nothing else happens.
->> 
->> Does *every* DJGPP program triggers this message, or only some?  Does GCC
->> itself trigger it when you compile (if you invoke the compiler via a .bat
->> file)?
->> Yes. Here it is (hola == hello ;-)
->
->Thanks for the info.  Seems like some strange bug in Windows.
->
->Does anybody else use Windows 98 and can try this?
->
->Does anybody know a solution to this hassle?
->
->> (Offtopic, do you know how to tell windows not to 
->> use a especific range of mem??????)
->
->No, I don't know.  Anybody?
->
->

- Raw text -