Thanks for all the above, I'm locked in a work call right now, so can't go and look, but I will later.bxdanny wrote: ↑Thu Apr 24, 2025 1:40 pm I misunderstood what you said. I thought you were saying that hitting <return> for memory size caused it to report 9471 bytes free. If it is still saying 7423, then it is not seeing the extra RAM, or it is testing bad. You could go into the Monitor and look at what it shows for location 2000. Try changing the contents, then re-entering the same address to see what it shows, e.g. .2000/AA.2000.
Yes, if you enter D with no disk drive it will hang forever waiting for a response from the drive. Entering a memory size greater than you really have just sets the top-of-memory to what you entered, with no testing. For example, if you entered 8500 but didn't have that much RAM, and you then entered an immediate-mode statement like PRINT "ABC" what would actually be displayed would be !!!, since it would show what it reads at its "top of memory" which is on page 21 hex, or decimal 33, ASCII for "!".
Based on the designations CE0 and CE1 on the schematic, I would also think that U19 and 27, and U20 and 28, would be the locations for the lowest-addressed RAM chips ($2000-$27FF). But looking just at the parts-placement guide, I would guess U51/59 and U52/60 instead. But the enable lines for those are labeled CE16 and CE17, so I guess not.
Could any of the buffer chips or the address-decode logic have been damaged when you connected the board with the bad cable? IIRC, the 8T28 (and 8T26) buffers can be easily damaged; if a good one on one board connects to a bad one on another board, the previously good one becomes bad, and both have to be replaced.
I assumed it was going to be the case that 7423 meant it didn't see the RAM...
I have already tried U51/U59 and U52/U60, same result. I will try and test the RAM in the main machine. Not sure how I can test the 8T28's.
And of course it might be bad RAM.