delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/05/15/21:36:12

From: jb3207 AT eclipse DOT co DOT uk (Jason Barstow)
Newsgroups: comp.os.msdos.djgpp
Subject: Creating PIFs (WAS Re: Allegro problems)
Date: Thu, 15 May 1997 23:07:33 GMT
Organization: Jabber Interactive
Reply-To: jb3207 AT eclipse DOT co DOT uk
References: <Pine DOT SUN DOT 3 DOT 91 DOT 970511122350 DOT 27751P-100000 AT is>
NNTP-Posting-Host: p07.dione.eclipse.co.uk
Message-ID: <337b9736.0@ispc-news.cableinet.net>
Lines: 26
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>You should enlarge the amount of DPMI memory that Windows lets you
>use.  The DJGPP FAQ (available as v2/faq210b.zip from the same place
>you get DJGPP) explains how to do that in section 15.6.


A related issue:

Does anyone know how to create .PIF files compatible for Win31 and Win95
which can be distributed with an exe so that the correct DPMI settings
(plus other stuff) is correct when it's run?

My understanding is that when Win95 runs an exe, if it finds a .PIF of the
same name in the exe directory it (working directory?) it will use it.

Problem is, when I create a .PIF it gets written with whole paths in it.
It's pretty unlikely my end users are going to use the same path as
me (W:\WIP\...) I've tried hacking the .PIF in a bineditor but this just
causes explorer to crash!

I guess a Win31/Win95 PIF editor would be useful - anyone know the format?





- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019