On Jan 20, 2005, at 11:42 am, Dan Dooré wrote:
Gents,
I have now completed trolling through GoodSAMC, my collection and
various others from those who have helped me in this endeavour.
I've just been going through the demobase, which links to nvg for most
of the files, and will upload the
Welcome to the SAM-users and this list !
The manuals should be no problem. Stephen Parry-Thomas did some excellent
PDF-alization of
most of the manuals made for SAM.
To get started I recomend to get the SAM Users' Manual and SAM Drive Users
Manual to
get a understanding of SAM Basic and DOS You
Last week I wrote:
there should be an updated version available sometime tomorrow...
Later than planned, I've updated the source and Win32 builds:
http://www.simonowen.com/sam/simcoupe/
This should fix Dan's problem with the Atom path being forgotton, and the
scanline garbage a few people
Aley Keprt wrote:
I need to move (video) memory on Sam, what's the fastest routine?
Despite its unfinished state, the SimCoupe debugger can be used to time
blocks of code. Whenever you enter the debugger the T-diff value in the
bottom right of the display shows the number of _real_ tstates that
Andrew Collier wrote:
ftp://ftp.nvg.ntnu.no/pub/sam-coupe/disks/demos/MNEMOtech/
MnemotechMnemotextDemo.zip
I don't particularly object to it being up there, but I'd be interested
to know where it came from? It was never exactly released...
It was in GoodSAMC IIRC which means that it
Thanks! I did some tests on my own, and the profiling says that the most
slowest part is the text scroller. I already tried many LDI's and PUSH/POP
system on my own, but unfortunately the process of changing SP makes
PUSH/POP slower than sequence of LDI's. You know, the TASM doesn't support
clever
I think the best one to start with is a Sam Coupe users's Guide. It's
excellent, and it'sa vailable in a PDF format from ftp.nvg.ntnu.no server
(and possibly also www.simcoupe.org - I'm not sure).
/---
Aley
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf
I really miss some features in that debugger, and documentation as well.
U regularly use ZX Spin emulator. It can't emulate Sam Coupe, but contains a
very strong debugger, and also assembler compiler.
But, of course, I use SimCoupe to develop my new demo. It has so tight
timings, that I wonder
Title: Zpráva
Sorry, it should stay **I regularly use...**, obviously not
you.
Aley-Original Message-From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
On Behalf Of Aley KeprtSent: Monday, January 31, 2005 10:20 AMTo:
sam-users@nvg.ntnu.noSubject: RE: Fastest memory transfer (on
Hi Si,
yes I like the new version a lot and it does fix the problem with the Atom
path which I had but I now notice that if you turn off 'Use RGB/YUV Overlay'
then this is forgoten when you exit the program (I haven't checked the other
items in the list). Also although not in 'options' but in
A SimCoupe source code comment says:
// if we are in the main screen area, or one of the extra MODE
1 contended areas:
// CPU can only access memory 1 out of every 8 T-States
// else
// CPU can only access memory 1 out of every 4
On Mon, 31 Jan 2005, Aley Keprt wrote:
A SimCoupe source code comment says:
// if we are in the main screen area, or one of the extra MODE
1 contended areas:
// CPU can only access memory 1 out of every 8 T-States
// else
// CPU
unsubscribe
Scott Macdonald wrote:
unsubscribe
http://www.podboy.demon.co.uk/coupe/maillist.htm
Dan.
I know this is not Spectrum users, but I must ask: how does Spectrum
memory contention work? How is it possible to run Spectrum software on Sam,
when it [Spectrum] definitely uses very different memory contention scheme?
I remember that memory 16384-32767 seemed to be the only contended area.
On Mon, Jan 31, 2005 at 10:41:52PM +0100, Aley Keprt wrote:
I know this is not Spectrum users, but I must ask: how does Spectrum
memory contention work? How is it possible to run Spectrum software on Sam,
when it [Spectrum] definitely uses very different memory contention scheme?
I
16 matches
Mail list logo
