[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
netbsd 0.9 on a thinkpad 750 -- status report Num Lock Off Microsoft Dos 6.2 Microsoft Dos 6.2 Using QEMM on the tp750 (from Quarterdeck) How to configure QEMM for IBM's Thinkpad computers. Here are the recommended QEMM 7 settings for IBM Thinkpad 750/750C problems. These recommendations may also apply to other computers in the Thinkpad family. Problem: Adding the RAM parameter to my QEMM386.SYS line in my CONFIG.SYS causes my Thinkpad to hang after 10-15 seconds. Solution: Add XBDA:L to the QEMM386.SYS line Re: Microsoft Dos 6.2 New subscriber
- To: tp750@CS.UTK.EDU
- To: James_Grant@novell.com
- To: TP750@CS.UTK.EDU
- To: tp750@CS.UTK.EDU
- To: Joseph Pereira <joseph.pereira@channel1.com>
- To: TP750@CS.UTK.EDU
- Subject: netbsd 0.9 on a thinkpad 750 -- status report
- Subject: Num Lock Off
- Subject: Microsoft Dos 6.2
- Subject: Microsoft Dos 6.2
- Subject: Using QEMM on the tp750 (from Quarterdeck)
- Subject: How to configure QEMM for IBM's Thinkpad computers. Here are the recommended QEMM 7 settings for IBM Thinkpad 750/750C problems. These recommendations may also apply to other computers in the Thinkpad family. Problem: Adding the RAM parameter to my QEMM386.SYS line in my CONFIG.SYS causes my Thinkpad to hang after 10-15 seconds. Solution: Add XBDA:L to the QEMM386.SYS line
- Subject: Re: Microsoft Dos 6.2
- Subject: New subscriber
- From: Keith Moore <moore@CS.UTK.EDU>
- From: Bob.Page@eng.sun.com (Bob Page)
- From: joseph.pereira@channel1.com (Joseph Pereira)
- From: Bob.Page@eng.sun.com (Bob Page)
- From: "John H. Kim" <jokim%jarthur@CS.UTK.EDU>
- From: <TERESASELLIN@delphi.com>
- Date: Tue, 01 Mar 1994 21:46:21 -0500
- Date: Mon, 28 Feb 1994 19:04:30 +0800
- Date: Wed, 2 Mar 94 07:54:00 -0500
- Date: Wed, 2 Mar 1994 03:44:52 +0800
- Date: Wed, 2 Mar 94 9:40:04 PST
- Date: Wed, 02 Mar 1994 12:54:45 -0500 (EST)
- Cc: TP750@CS.UTK.EDU
- Cc: tp750@CS.UTK.EDU
- Explanation: The eXtended BIOS Data Area (XBDA) is a data area normally located at the top of conventional memory, just below the 640K mark. This memory is used to hold BIOS-specific information. By default, QEMM will relocate this XBDA, reclaiming the conventional memory it uses and allowing programs such as VIDRAM to extend conventional memory past 640K. On the Thinkpad, this relocation can result in a crash when the Thinkpad operating system writes data intended for the XBDA into the wrong place. Using the XBDA:L parameter will solve this problem, by telling QEMM to move the XBDA to low conventional memory. The only drawback to using XBDA:L is the loss of 1K of conventional memory. Problem: Sometimes QEMM can't tell what addresses the Thinkpad PCMCIA card is using. Symptoms of this are trouble loading programs high, and hangs or odd behavior by TSRs/Device-drivers or the PCMCIA cards themselves. Solution: Exclude the upper memory range where the PCMCIA card is mapped. The address range should be very easy to find, because a properly configured PCMCIA card should have a line in your CONFIG.SYS file that specifies the correct address. See the explanation below.
- Explanation: The Thinkpad includes slots for PCMCIA cards; these cards will take up up from 0 to 64K of upper memory addressing space, which must be eXcluded from QEMM's use. There is no guarantee that QEMM's autodetection will see the region. If your PCMCIA card is properly configured, there should be a line in your CONFIG.SYS that loads a driver called DICRMU01.SYS; this driver is the resource map utility, which tells the adapter card (among other things) what area of memory it is to use. Check that line for a /MA= parameter; this parameter will be followed by the ranges of memory to exclude with the X= parameter on the QEMM386.SYS line. An example will best illustrate how to do this: If your CONFIG.SYS file has a DICRMU01.SYS line with /MA=D000-D3FF, you would need to add X=D000-D3FF to the end of your QEMM386.SYS device line in your CONFIG.SYS file. Some information on the DICRMU01.SYS driver and on using PCMCIA adapter cards with software EMS providers such as QEMM can be found on pages 2-13 of the IBM Thinkpad 750/750C user's guide. For further information: The QEMM Analysis procedure will help you if you need to confirm what addresses need to be excluded because your hardware is using them. It is discussed in Appendix A of the QEMM manual, under the heading, "Solving a memory conflict with the Analysis procedure." The general technote TROUBLE.TEC is a useful source of other problem-solving suggestions; most QEMM users have a copy of TROUBLE.TEC in the TECHNOTE subdirectory. ************************************************************************ *This technical note may be copied and distributed freely as long as it* *is distributed in its entirety and it is not distributed for profit. * * Copyright (C) 1994 by Quarterdeck Office Systems * ************************ E N D O F F I L E *************************
- ID: TH IBM's Thinkpad 750/750C and QEMM
- In-Reply-To: <9402282240.AA04767@stealth.test.NPD.Provo.Novell.COM>
- In-Reply-To: <40.315116.700.0CE179DC@channel1.com>; from "Joseph Pereira" at Mar 2, 94 7:54 am
- Organization: Channel 1 Communications
- References: <9402282240.AA04767@stealth.test.NPD.Provo.Novell.COM>
- Sender: moore@CS.UTK.EDU
I recently acquired a 750C. Added 16Meg for total 20meg ram & am
using a Maxtor 250 meg 2.5" notebook drive (inside the original
170 meg drive's case). I also picked up the Dock I with CDROM II.
I am running OS 2.1 (just added CSD for ver 2.11).
In general I am thrilled with the machine, but have a few complaints.
Maybe someone has some solutions...
1) $1299 price for 340 meg IBM drive. Any 3rd party vendors for
hardisk drives for ThinkPad? I'd like to get larger than 340 meg
but someone at IBM said the bios wouldn't support that. Is
this a fact?
2) Audio driver for virtual Dos windows is kind of lame. I get
machine hangs and fatal errors in the TPAUDD driver. Is there
a better driver in the works?
3) After the CSD install PMComm video gets screwed and my PCMCIA
modem will no longer connect reliably. Also I have to load the
com.sys driver before pcmcia.sys to get the modem to respond at
all even though the readme with the CSD says to load it after.
All and all a great machine....
-Teresa