Re: MLDL2000 Manager software: new BETA version Message #7 Posted by Vieira, Luiz C. (Brazil) on 10 Jan 2010, 2:50 p.m., in response to message #6 by Monte Dalrymple
Hi, Monte;
once I loaded pages 0, 1 and 2 of the CX mainframe in a CV mainboard through MLDL2000, I considered that the O.S. reads page #3 as it addresses it through the system software. Fact is when I first used MLDL2000 (some years ago) I loaded page #3 of some CV units (coco- and halfnut) with some different ROM images. These ROM list their contents with CAT 2 (hence the system 'sees' it) but once you try to execute anything there you get NONEXISTENT.
When I loaded the CX ROM set (few weeks ago) in the MLDL2000 and powered a coconut CV without the ROM IC´s with it, it behaves accordingly, as a CX, except that the time functions return blank display and X-memory functions either return file-not-found errors, as expected, or no reaction at all (EMDIR, for example, always returns [124.0000] to the X-register and no message at all, like [DIR EMPTY]). Many features, like program size in CAT1, ROM headings in CAT 2 and the fully-operating CAT 6, were observed.
When I decided to test the extended functions that might work, the following ones did not work at all:
ANUM
AROT
CLKEYS
CLRGX (CX only, right?)
GETKEY
PASN
PCPLPS
POSA
PSIZE
STOFLAG
X...NN (none of these)
These ones worked fone:
ALENG
ATOX
SIZE?
RCLFLAG
REGMOVE
REGSWAP
X<>F
XTOA
SigmaREG? (also a CX-only, and works!)
I could see no pattern that might connect each of the working (or the nonworking) functions with each other. The only thing I could think of is the use of RAM scratch area that was not there. You see, I never accepted too well the concept of X-Memory discontinuity as physical, I aways took it as existing RAM area for system scratch in some X-Function/Memory 'maneuvers'. I'd gladly accept any other concise explanation, though.
This is all I can remember now. I did not have the time to test the emulation in an actual CX mainboard this weekend, will do it in the days ahead. I am trying to repair a faulty one for ages (I actually have it waiting for an actual definitive go-nogo repair procedure), and will soon post about the results here.
Cheers.
Luiz (Brazil)
Edited: 10 Jan 2010, 2:57 p.m.
|