🚀 go-pugleaf

Unfortunately, it appears that the fix to DPMI.SYS doesn't make the
virtual memory support part of DPMI work yet. Still, if you have 16
meg ram on your system...
-- 
Dave Feustel N9MYI <feustel@netcom.com>
---
What's the different between a Salem Witch Hunter and a modern day
Drug Warrior? - 3 centuries.

I discovered late last night that increasing the DPMI memory limit in
the dos settings got rid of what I thought was a VM error.
-- 
Dave Feustel N9MYI <feustel@netcom.com>
---
What's the different between a Salem Witch Hunter and a modern day
Drug Warrior? - 3 centuries.

In article <=!jmdvp.feustel@netcom.com> feustel@netcom.com (David Feustel) writes:
>I just got the X-32VM 32-bit dos extender from Flashtek. This item was
>accompanied by an IBM update of VDPMI.SYS. With this software I
>successfully ran a ZTC 32-bit dos application in an os/2 dos box.
>Very nice and very fast!

So does the DOS extender that comes free with Watcom Fortran 9.0/386 (and,
I am sure, also Watcom C 9.0).  It's called DOS4GW and it's a
subset of DOS4G from Rational Systems, Inc.

Luc B

A number of UNIX programs I have ported to OS/2 using emx or gcc
choke on binary files, unless I modify them.

for example:
f = fopen(name,"r") must be changed to f=fopen(name,"rb")
etc.

I was wondering just what happens when you don't open as binary.
Will it return EOF when it sees ^Z or what?

This is sort of troubling to me, since EMX is desing to make porting UNIX easier

Was fopen changed to make it more compatible with OS/2 or what. From what I've
read "r" and "rb" are handled the same in UNIX.

jpm


-- 
______________________________________________________________________________
jpm: ochealth@unixg.ubc.ca         
                           Happily using OS/2 2.0 because MS Windows isN'T ___
                                                      Insert VapourFeature ^^^

            <1992Jul25.175848.29166@unixg.ubc.ca>

In <1992Jul25.175848.29166@unixg.ubc.ca> ochealth writes:
> A number of UNIX programs I have ported to OS/2 using emx or gcc
> choke on binary files, unless I modify them.
>
> for example:
> f = fopen(name,"r") must be changed to f=fopen(name,"rb")
> etc.
>
> I was wondering just what happens when you don't open as binary.
> Will it return EOF when it sees ^Z or what?

Opening a file in text mode on OS/2 will cause CR/LF (\r\n) to be turned
into a single LF (\n) character, and will cause the EOF flag to be set
when reading a ^Z (\x1a).

> This is sort of troubling to me, since EMX is desing to make porting UNIX easier
>
> Was fopen changed to make it more compatible with OS/2 or what. From what I've
> read "r" and "rb" are handled the same in UNIX.

The original Unix utilities should *really* have opened files in binary
mode in the first place.  The way that Unix works causes binary mode to
be identical to text mode, so the utilities' authors got away with
reading binary as text on Unix systems -- the two modes are the same, so
it doesn't matter which one you use.  On OS/2, there *is* a difference,
so you have to be more careful.  If the utilities treat files as binary,
then by all means, change the code so that the fopen() call uses "rb".

dave

-------------------------------------------------------------------------
Dave Mooney                                              dmm@vnet.ibm.com
 C Set/2 Development, IBM Canada Lab, 844 Don Mills Rd, Toronto, Ontario
            "If you've got a blacklist, I want to be on it"

In <1992Jul25.175848.29166@unixg.ubc.ca> ochealth@unixg.ubc.ca (ochealth) writes:



>A number of UNIX programs I have ported to OS/2 using emx or gcc
>choke on binary files, unless I modify them.

>for example:
>f = fopen(name,"r") must be changed to f=fopen(name,"rb")
>etc.

>I was wondering just what happens when you don't open as binary.
>Will it return EOF when it sees ^Z or what?

>This is sort of troubling to me, since EMX is desing to make porting UNIX easier

>Was fopen changed to make it more compatible with OS/2 or what. From what I've
>read "r" and "rb" are handled the same in UNIX.

"r" and "rb" are a world apart, although the difference is slight.  "Text mode"
implies that CR-LF pairs are translated to LF on reads and vice-versa on 
writes.  This is due to the hardware, I believe, requiring the CR and LF
to perform a "new line" operation.  Additionally - and I could be wrong here -
text mode does return EOF when Ctrl-Z is encountered, while binary mode does
not.

-- 
Cheers,
Q
-----------------------------------------------------------------------
"If you still choose not to decide,   | "My other account is in the