› ›

Error Message on memory test

ADJBADJB
edited November 2008 in Hardware
I have just tried

PRINT PEEK 23732 + PEEK 23733 * 256

on what I think is a 48K rubber key machine and instead of getting either

(a) for a 48k unit - 65535
or
(b) for a 16k unit - 32767

I got

2 variable not found, 0:1

Is this indicative of screwed memory ?
Post edited by ADJB on

Comments

  • Digital PrawnDigital Prawn
    edited November 2008
    Unless of course, PEEK was keyed in character by character instead of using the PEEK single-byte token.

    But I'm guessing you wouldn't have done something trivially silly as that. :D
  • rich_chandlerrich_chandler
    edited November 2008
    Very strange. Did you try the test more than once to see if you could repeat it?
    I wanna tell you a story 'bout a woman I know...
  • ADJBADJB
    edited November 2008
    To be honest it never occurred to me that you could. I just read it as a keyword.

    I see what you mean but no, it was definitely keyword.
  • ADJBADJB
    edited November 2008
    karingal wrote: »
    Very strange. Did you try the test more than once to see if you could repeat it?

    A couple of times, same result.
  • Digital PrawnDigital Prawn
    edited November 2008
    ADJB wrote: »
    To be honest it never occurred to me that you could. I just read it as a keyword.

    I see what you mean but no, it was definitely keyword.

    My suggestion would only apply if brackets were used around the PEEK argument otherwise it would fail the syntax checking stage anyway.

    Tis an unexpected error from that command though.
  • GeoffGeoff
    edited November 2008
    Are both occurrences a keyword?

    Sinclair variables can have spaces so 'peek 23733' is a valid variable name in either upper or lower case. Stick a line number in front so that you can definitely check that the cursor jumps through the keyword when editing.

    10 PRINT PEEK 23732 + PEEK 23733 * 256
    ADJB wrote: »
    To be honest it never occurred to me that you could. I just read it as a keyword.

    I see what you mean but no, it was definitely keyword.
  • gtsamourgtsamour
    edited November 2008
    I had a similar case in which i was getting strange behaviour by the speccy to some commands and some crashes, it turned out to be bad ROM chip.
Sign In or Register to comment.