home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!mips!swrinde!elroy.jpl.nasa.gov!ames!haven.umd.edu!darwin.sura.net!news.duc.auburn.edu!ducvax.auburn.edu!hank
- From: hank@ducvax.auburn.edu
- Newsgroups: comp.binaries.ibm.pc.archives
- Subject: Re: Review of The Last Byte (again)
- Message-ID: <1992Jul21.105016.1@ducvax.auburn.edu>
- Date: 21 Jul 92 15:50:16 GMT
- Sender: usenet@news.duc.auburn.edu (News Account)
- Organization: Auburn University, AL
- Lines: 32
- Nntp-Posting-Host: ducvax
-
- My apologies to the net: I thought I had posted a followup to
- "The Last Byte" memory manager review; apparently I just posted a copy
- of the original article. I hate my newsreader.
-
- In short, I said:
-
- 1. I am a registered user of ver 1.20 (the review was on 2.02). I used
- it for several months on a 386SX and Windows. I now use OS/2, so I
- haven't had to bother with all this stuff.
-
- 2. I had no problems with TLB and Windows 386enh mode.
-
- 3. I like the extra utilities and the complete documentation.
-
- 4. The price comparison with an extra 1M of extended memory is somewhat
- misleading. Perhaps the reviewer means to say:
- If EMM386 is an acceptable way to provide UMBs, then an extra meg
- of extended memory is more cost-effective than TLB.
-
- 5. The reviewer gives some situations where TLB may be useful. In
- context, his statements are correct, but the review may leave the
- impression that hardware EMS is required to obtain UMBs. TLB can
- provide UMBs on any 286 or 386 with shadow ram and a supported memory
- chipset (TLB includes a program to test for compatibility). emm386
- can provide UMBs on a 386, but there are some penalties for using
- emm386.
-
- 6. The fact that the "hole" feature is not in the unregistered
- version was documented in ver 1.2. The use of F0000 may be
- machine-dependent: I could use this area on my machine.
-
- --darrel hankerson hank@ducvax.auburn.edu
-