Jump to content
IGNORED

Commodore 64 Issue


Recommended Posts

Yes, it should say 38911. Probably you have faulty RAM and the startup routine stops counting.

 

11122 bytes counting from address 2048 would equal 13170 ($3372). If it boots to BASIC, I suppose you could POKE and PEEK around there to see if you get back the values you store. Exactly what it means of actual RAM chips would need to be looked up.

  • Like 1
Link to comment
Share on other sites

Are you sure it is C64 ? Can you show a screenshot of bytes free and if possible a picture of the case and motherboard ?

 

If it is a C64 then see https://retrocomputerverzamelaar.nl/commodore-64-problems/

RAM Problems U9 – U12, U21 – U24

Description
Startup screen problems with:

  • out of memory error,
  • wrong number of memory available,
  • colored random characters.

General
Blank screen, no border. Shorted chips may get warmer (sometimes very hot) than the other RAM chips.

Partial failure: will sometimes produce “garbage” screen, abnormal number of bytes free (lower than 38911)

or “OUT OF MEMORY IN 0” error on startup screen.

Cause

Bad RAM chips or bad socket contacts of the RAM
(M41464) 2 RAM CHIPS (64K X 4 DRAM)

Please see description of the images for the cause

Edited by thetick1
  • Like 1
Link to comment
Share on other sites

Ah.. OK

 

I tried pokes and peeks. I don't seem to be able to use the $ though. I can peek (3371), (3372), and (3373) and get 0,255,0 respectively. When I poke 9 to those 3 locations, I peek a 9 back.

 

I'm not that familiar with BASIC anymore... In my world, leaving the $ off means I am using a decimal number instead of a hexadecimal. Is that the difference here?

Link to comment
Share on other sites

Ahh then you've probably seen my quixotic attempts to make an Atari 2600 become a Commodore 64

 

So yeah its acting funny:

 

poke 255 in peek

13170 055

13171 239

13172 didn't write it down but I think it was 255

13173 132

 

poke 0

13170 055

13171 039

 

What do you think?

Link to comment
Share on other sites

I believe you have a partly damaged RAM chip, unless there is something else that can cause part of the memory to work but part doesn't. The PLA chip is a kind of memory manager I think but it probably would be greater errors if it was the cause.

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...