/XMEM
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
RE: /XMEM
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 paged into the section between 32768 and 49151 (XMEML), and 49152 to 65535 (XMEMH). And yes, I wish I could ditch that info from my brain to make room for other stuff - like maybe recipes for interesting kinds of jello. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Edwin Blink Sent: Tuesday, March 23, 2004 2:51 PM To: sam-users@nvg.ntnu.no Subject: /XMEM 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
RE: /XMEM
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 latches at ports 128 and129 (XMEML and XMEMH), which decide which 16k page of the external memory ispaged into the section between 32768 and 49151 (XMEML), and 49152 to 65535(XMEMH).And yes, I wish I could ditch that info from my brain to make room for otherstuff - like maybe recipes for interesting kinds of jello.-Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] OnBehalf Of Edwin BlinkSent: Tuesday, March 23, 2004 2:51 PMTo: sam-users@nvg.ntnu.noSubject: /XMEMThanks for trying. Nev,GeoffI was looking for info about the /XMEM signal as the manal is not veryinformative.Does anybody know the implementation of it? or has a schematic of the 1Megexpansion or original Soft Rom board in which this signal is also used ?Edwin
Re: NVG
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 49 | | N-1788 Halden | Phone: +47 45 24 99 39| | -- Anything added below this line is outside my control --| This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof.
Antw: RE: /XMEM
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 had a look at the SAMSON SRAM PCX files. I noticed /XMEM is used together with /MREQ. I wonder if this is the same with the MGT SOFT ROM. I remember that the MGT SOFT ROM schematic was also in the technical manual. Does anyone have a scan of it ? Edwin
Re: Antw: RE: /XMEM
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 bit that can be turned on and off or if it is fully encoded withA15 /MREQ (//RFS?)NVG is back online. and I had a look at the SAMSON SRAM PCX files.I noticed /XMEM is used together with /MREQ.I wonder if this is the same with the MGT SOFT ROM.I remember that the MGT SOFT ROM schematic was alsoin the technical manual. Does anyone have a scan of it ?Edwin
RE: SimCoupe 0.90 beta 10
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 version instead. Fixed since that release is a problem that prevented the virtual hard disk from being reset when the SAM was reset. BDOS relies on the register values being restored to their initial states, and when they weren't it booted from floppy instead. If you followed Edwin's instructions for a bootable hard disk, only the first power-on reset would boot correctly. (thanks to Edwin for spotting that). If anyone has spotted anything else, now's the time to shout... :-) 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... Si
Re: SimCoupe 0.90 beta 10
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... An OS X version! Now you're talking my language! Give me a shout if you want a tester. Gavin
Re: SimCoupe 0.90 beta 10
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, while versions are only marketing names of DX. /-- Aley - Original Message - From: Simon Owen [EMAIL PROTECTED] To: sam-users@nvg.ntnu.no Sent: Wednesday, March 24, 2004 7:02 PM Subject: RE: SimCoupe 0.90 beta 10 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 version instead. Fixed since that release is a problem that prevented the virtual hard disk from being reset when the SAM was reset. BDOS relies on the register values being restored to their initial states, and when they weren't it booted from floppy instead. If you followed Edwin's instructions for a bootable hard disk, only the first power-on reset would boot correctly. (thanks to Edwin for spotting that). If anyone has spotted anything else, now's the time to shout... :-) 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... Si
RE: Antw: RE: /XMEM
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 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 had a look at the SAMSON SRAM PCX files. I noticed /XMEM is used together with /MREQ. I wonder if this is the same with the MGT SOFT ROM. I remember that the MGT SOFT ROM schematic was also in the technical manual. Does anyone have a scan of it ? Edwin
RE: SimCoupe 0.90 beta 10
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) method of initialising DirectX instead. I do need the functionality first introduced with DirectX 3, so a quick version check should be fine. It's just a shame the previous method I used (from the NSIS website) didn't quite do the trick! Si
Re: SimCoupe 0.90 beta 10
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 initialising DirectX instead. I do need the functionality first introduced with DirectX 3, so a quick version check should be fine. It's just a shame the previous method I used (from the NSIS website) didn't quite do the trick! Si As I can see, my last e-mail is not fully clear. I wanted to say this: DirectX (DX) is not a centralised version-based system. It is a set of independent interfaces to DX components. So if you use DX, you actually use one or more COM interfaces. DX is just a common name of all these interfaces. If you want to be sure that a particular machine can run your program, you don't need to check the DirectX version. What you actually need is to check that all interfaces you use in your program are supported on that machine. So I think your installer should rather try to obtain all interfaces used in the SimCoupe, instead of using some undocumented tricks to obtain DirectX version. I think the reason of malfunction on NT 4.0 is that it contains a hybrid DirectX version, which is DirectX 2 compliant, with some components supporting several features of DirectX 3. The version probing code probably inadvertently checks some of the DX2 libraries, and complains DX3 is not installed. /-- Aley
Re: Antw: RE: /XMEM
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 Register 80+ Memory 8000 So /XMEM is just the XMEM bit nanded with A15. Just thought I share it and waste your precious brain space for yummy recipies :-) BTW Scans of schematics are still welcome ! Edwin
