home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!torn!news.ccs.queensu.ca!slip206.telnet1.QueensU.CA!dmurdoch
- From: dmurdoch@mast.queensu.ca (Duncan Murdoch)
- Subject: Re: VIRTUAL MEMORY
- Message-ID: <dmurdoch.271.725776192@mast.queensu.ca>
- Lines: 19
- Sender: news@knot.ccs.queensu.ca (Netnews control)
- Organization: Queen's University
- References: <6500.115.uupcb@cutting.hou.tx.us> <1992Dec31.020312.26280@proto.com>
- Date: Thu, 31 Dec 1992 04:29:53 GMT
-
- In article <1992Dec31.020312.26280@proto.com> joe@proto.com (Joe Huffman) writes:
- >>I'm looking for a caching mechanism for virtual memory in 'C'. Any
- >>suggestions.
- >
- >Get a 32-bit compiler and a good 32-bit DOS extender that has virtual memory
- >built in. This will make VM totally transparent to you the programmer.
- >
- >Suggestions for DOS extenders with VM include:
- >
- >Flashtek's X-32VM
- >Pharlap's 386
- >Rational System's DOS 4G
-
- Borland's extender included with Borland Pascal also offers virtual memory,
- though it's only a 16-bit extender. I'm not sure what the limitations are;
- it's not well documented.
-
- Duncan Murdoch
- dmurdoch@mast.queensu.ca
-