Captain Chaos
Member
- Joined
- Feb 11, 2022
- Messages
- 21
Yes, sorry, that's what I meant.I'd expect 256K and 384K to get you all the way to 640K
I had no idea there were that many versions of the card. The settings are correct according to a manual we found for a card that looked identical to the last chip, but maybe there are differences nevertheless. I'll try to find the manual for the exact part number I have and double check.Have you confirmed the starting address jumpers and the amount installed jumpers on the card are correct? There is a document here that show 6 different versions of the sixpak and their jumpers and also it looks like there are PDF versions of many of them versions.
10 DEFINT A-Z: CLS
20 PRINT "Testing 256K to 640K RAM"
30 FOR S = 0 TO &H5FFF STEP 16
40 DEF SEG = &H4000 + S
50 PRINT "Segment " + HEX$(&H4000 + S)
60 FOR I = 0 TO 255
70 POKE I, &H55
80 IF PEEK(I) <> &H55 THEN PRINT "Bad RAM found"
90 NEXT I
100 NEXT S
110 PRINT "Test complete"
60 FOR I = 0 TO 0
If my computer (vintage or otherwise) developed a faulty RAM chip, of the following two behaviors, I expect the first.I disagree that the XT BIOS memory detection method is "flawed." It's simply detecting the amount of usable memory.
The 201 error includes the address.If you know you should have more memory, then it's actually helpful in determining where the bad memory is.
If my computer (vintage or otherwise) developed a faulty RAM chip, of the following two behaviors, I expect the first.
* To be informed by the POST that there is a RAM problem; or
* Have the POST count up the amount of usable RAM.
Remember too that users in the 80's (and now) had varying levels of computer literacy. If they happened to notice one morning that the final number shown on-screen was different to the previous morning, how many would know that it is something they need to contact the company's computer department about. And some users would not notice at all, because after they flicked on the red power switch, they headed straight off to make their coffee.
The 201 error includes the address.
As a novice user in the 80s, my first computer being an XT clone, I knew on an XT compatible BIOS, there was a RAM count displayed and it should display the RAM installed if they were inserted correctly and have the DIP switches set correctly. I can't remember how I learned this. It was either described in the manual that came in the computer, which was fairly detailed as it was then, or I was told by my dad when I assembled the computer. I also knew about POST codes from reading about the computer operation, if any codes were shown, to look in the manual for clues, or just go to the library or bookstore and find a reference. It was just what was done then... the information was just shared and users could read and find this information out. A novice user could learn quickly the process of the boot operation even then.It's not uncommon to have a modern BIOS count and use a reduced amount of RAM due to a badly seated SIMM or DIMM. It's happened to me multiple times.
How would a novice user know what "201" means? I don't find that any more user friendly.
Cool, I hoped something like that might be possible. I'm going to try this.You can use ROM BASIC to test "hidden" memory:
As a novice user in the 80s, my first computer being an XT clone, I knew on an XT compatible BIOS, there was a RAM count displayed and it should display the RAM installed if they were inserted correctly and have the DIP switches set correctly. I can't remember how I learned this. It was either described in the manual that came in the computer, which was fairly detailed as it was then, or I was told by my dad when I assembled the computer. I also knew about POST codes from reading about the computer operation, if any codes were shown, to look in the manual for clues, or just go to the library or bookstore and find a reference. It was just what was done then... the information was just shared and users could read and find this information out. A novice user could learn quickly the process of the boot operation even then.
But hasn't there been something like 'Error: CMOS mismatch' displayed as well, i.e. discovered RAM amount does not tally with RAM amount declared in the CMOS/SETUP configuration ?It's not uncommon to have a modern BIOS count and use a reduced amount of RAM due to a badly seated SIMM or DIMM. It's happened to me multiple times.
I don't consider it user friendly at all. IBM's intention with the IBM 5160 was probably that the accompanying "ERROR. (RESUME = F1 KEY)" would prompt the lay user to contact 'technical support', and the error code be used by technical supportHow would a novice user know what "201" means? I don't find that any more user friendly.