home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.ibm.pc.soundcard
- Path: sparky!uunet!cs.utexas.edu!geraldo.cc.utexas.edu!portal.austin.ibm.com!awdprime.austin.ibm.com!hartmann.austin.ibm.com!lance
- From: lance@hartmann.austin.ibm.com (Lance Hartmann)
- Subject: GUS memory map correction?
- Summary: Need correct memory map used by GUS.
- Sender: news@austin.ibm.com (News id)
- Message-ID: <BzoDH5.1rDp@austin.ibm.com>
- Date: Tue, 22 Dec 1992 19:15:05 GMT
- Reply-To: lance%hartmann.austin.ibm.com@ibmpa.awdpa.ibm.com
- Organization: IBM, Austin
- Keywords: gravis ultrasound gus memory map address conflict diamond video
- Followup-To: poster
- Lines: 33
-
- Yesterday I thought I had a possible I/O address conflict between my GUS
- and the Diamond Stealth/VRAM video adapter. The tech-rep at Gravis
- (didn't get his name) stated that the memory map on p. 69 in the manual
- was correct and that I would have a conflict.
-
- After talking with Diamond today, I called Gravis again. This time
- I reached a "senior" person by the name of Harry Skibbe. "Harry"
- seemed infinitely more knowledgable than the guy with whom I spoke
- yesterday and was, actually, quite entertaining. When I asked him
- about the memory map in the manual (version 1.1 by the way), he stated
- that it was WRONG particularly the range 2X2-3X2. "There's no way",
- he said that they use such a large range. Of course, this would
- tromp all over most of the COM ports. Harry said the correct addresses
- should be in the README file. Now, I have the 1.21 disks, but I don't
- recall seeing a memory map in the README -- I'll definitely check when
- I get home, BUT.... in the interim, if anyone out here happens to
- have this information handy, PLEASE send me a copy!!!
-
- Harry also commented about the available base ports. On p. 16 describing
- the jumper settings, the manual infers that only base addresses
- 210, 220, 230, 240, 250, and 260 are available. However, on p. 69
- describing the memory map, the manual infers that the 'X' can
- represent 0-F hexadecimal. Harry confirmed that, indeed, the card CAN
- be configured to all of those (200, 210, ..., 260, 270, ... , 2F0) though
- the ones shown on p. 16 are recommended as the others are much more
- likely to cause a conflict.
-
- Regards,
- Lance Hartmann (lance%hartmann.austin.ibm.com@ibmpa.awdpa.ibm.com)
- Yes, that IS a '%' (percent sign) in my network address.
- ------------------------------------------------------------------------------
- All statements, comments, opinions, etc. herein reflect those of the author
- and shall NOT be miscontrued as those of IBM or anyone else for that matter.
-