Thanks for trying. Nev,Geoff
I was looking for info about the /XMEM signal as the manal is not very
informative.
Does anybody know the implementation of it? or has a schematic of the 1Meg
expansion or original Soft Rom board in which this signal is also used ?
Edwin
IIRC, the XMEM line goes low when the external memory area is addressed
(upper 32k of the memory map, with external memory turned on in HMEM).
The external memory addressing is controlled by two latches at ports 128 and
129 (XMEML and XMEMH), which decide which 16k page of the external memory is
Well you did do a lot of fiddling around with it for the Ryan ;)Simon Cooke [EMAIL PROTECTED] wrote:
IIRC, the XMEM line goes low when the external memory area is addressed(upper 32k of the memory map, with external memory turned on in HMEM).The external memory addressing is controlled by two
On Tue, 23 Mar 2004 18:17:18 +0100 Edwin Blink [EMAIL PROTECTED] wrote:
Can anyone access NVG ? 'Cause I Can't.
There seems to be some problems with the ftp server. I'm not sure what
yet.
-Frode
--
^ Frode Tennebø | email: [EMAIL PROTECTED] ^
| Ericsson AS | Isebakkeveien
Thanks for the braindump Simon
But your talking about the decoded signals decoded by the interface.
What i need to know is the ASICs implementation of the /XMEM signal.
ie is it just a bit that can be turned on and off or if it is fully encoded with
A15 /MREQ (//RFS?)
NVG is back online. and I
I've got the technical manual. If it's in there, I can do you a scan, no problem.
Andy
[EMAIL PROTECTED] wrote:
Thanks for the braindump SimonBut your talking about the decoded signals decoded by the interface.What i need to know is the ASICs implementation of the /XMEM signal.ie is it just a
Geoff Winkless wrote:
Hmm. The win32 installer fails on this NT box - complains
about directx =3 being needed even though v5 is installed.
Thanks Geoff! It appears the DirectX version number was stored in a
different registry location in older versions - I'll switch to checking the
DDRAW.DLL
I've also added BeOS R5 and QNX binaries to the download page at
http://homepage.ntlworld.com/simon.owen/sam/simcoupe/ I've got a
provisional OS X version too, but am holding that back until a strange
performance problem is fixed. I'm hoping to have access to a Mac in
work
soon to fix that...
I think you should use official test method (see DX SDK), or don't test DX
version at all. Otherwise you never know when you encounter some problems
again.
I think the only 100% valid solution is to check that the needed COM
interfaces are all present. DX is based on well defined COM interfaces,
It's fully encoded with A15 and MREQ, from what I remember.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of [EMAIL PROTECTED]
Sent: Wednesday, March 24, 2004 3:34 AM
To: sam-users@nvg.ntnu.no
Subject: Antw: RE: /XMEM
Thanks for the braindump Simon
But
Aley Keprt wrote:
I think the only 100% valid solution is to check that the
needed COM interfaces are all present. DX is based on well
defined COM interfaces, while versions are only marketing
names of DX.
I don't use/require specific interface numbers, and use the old (compatible,
non-Ex)
I think the only 100% valid solution is to check that the
needed COM interfaces are all present. DX is based on well
defined COM interfaces, while versions are only marketing
names of DX.
I don't use/require specific interface numbers, and use the old
(compatible,
non-Ex) method of
Decided do some tests with a LED hooked up to /XMEM (with a 330 ohm
resistor in series)
Whenever the /XMEM line gets active low the LED would ilLuminate.
Once bit 7 of HMPR port was set the LED would light up with any combination
with address line 15
high:
I/O ports 8000+
Refresh with I
13 matches
Mail list logo
