Text 1446, 77 rader
Skriven 2010-02-18 14:46:54 av Mike Luther (1:117/3001.0)
   Kommentar till text 1445 av Mark Lewis (1:3634/12.0)
Ärende: T42P ThinkPad request
=============================
Thanks Mark..

 ml> have you checked the properties for the command 
 ml> prompt? IIRC, i had to specifically enable EMS and i 
 ml> think also give it an amount... that's Warp3Connect 
 ml> though...

Yes. And interestingly, a VERY thoughful post from Viet Kannegeiser in the OS/2
Newsgroup has jumped this way forward.  His PMVDMCC system tool does, in this
case, enable the '2K" PATCH that is 'normally' required of many of the IBM
ThinkPad units to enable the addition of extra memory to the 'standard' DOS-VDM
memory beyond the roughly 650K basic amount you see in the MEM report at a DOS
prompt.  A 'normal' way of enabling EMS memory is to go into the DOS Session
setting commands for DOS-VDM windows and to enable EMS Memory Limit, which
defaults to 2048 Bytes. to use 'AUTO' for the EMS Frame Location.  At which
time you then see the 'normal' EMS memory show up when you do a MEM command.

Well, I didn't know this, but he taught me that if you use, for example:

   EMS Memory Limit = 2000
   EMS Frame Location = NONE

you may see the EMS memory pop up in the MEM report!  But also that without a
defined Frame Location, some programs will not be able to see that EMS memory
even if it does exist!  After which he posted:

   "Gives EMS, but I am not sure if program using graphics will
    crash, because the ATI BIOS cuts off after 32KiB.."

And curiously, after I tried this the Btrieve product I use for secure file
handling work *DOES* load, even without a defined Frame Location! But
absolutely *NOT* will any of my compiled executables run with the needed EMS,
in that all of them are graphics oriented, I guess, from what he posts.

OK, he also advised that I try.

   EMS Memory Limit = 2000
   MEM Include Regions = C8000-D7FFF
   EMS Frame Location = C800

That sure enough also provided what looks like fully normal EMS service in the
DOS-VDM with his PMVDMCC enable extra memory of the needed 600K plus 'standard'
DOS memory and all I normall see.  Even with this the Btrieve system loadhigh
in the AUTOEXEC style custom file I use works just fine.  But every program of
the about 100 DOS Power Basic executables I use smashes on opening with a
SYS3170 error!

Looking with OS/2 SYSinfo and other memory analysis programs I use for research
I notice that in the case of the T42P, the Video Bios is an AMI Mobility Radeon
7500 chip with 32MB of video memory.  The T43P here is an AMI Mobility Radeon
X300 with 64MB of video memory. Everything I have works beautifully with the
T43P that is here for tests.  Viet posts that the issue is:

   "Problem is the PCMCIA and the waste of address space by the
    System and VGA BIOS."

Which I'm now trying to learn about.  Apparently, if we see the ATI chipset and
less than 64K of video memory, maybe this will never work? I asked for opinion
on that issue in the OS/2 Newsgroup.  At this point,I have had no answer to
that question.

I have now tried manually choosing every possible variance of Frame Location by
hand as well as manually going in and manually blocking all the known BIOS
address chunks in the IBM memory use documentation for this latest 2007 BIOS
update for the T42P.  No help.  It does change the SYS3170 error in some cases
to SYS3176 in some cases though.

Anyone with any help here?


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001


--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)