Yes it recognizes it. 1 to 16 k are valid.
Kind regards Paul
ZX80 trouble shooting
Re: ZX80 trouble shooting
In theory, there is no difference between theory and practice. But, in practice, there is.
-
- Posts: 2169
- Joined: Sat Nov 26, 2016 2:42 am
Re: ZX80 trouble shooting
Thanks. How do I test that it is working? Ideally without trying to type in a really long program....
I’m used to the ZX81 taking extra time to show the K after startup which this isn’t doing. I’m new to the world of ZX80s.
ZX80
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
Re: ZX80 trouble shooting
Here you go Lardo.
I'm almost sure this is courtesy of Mark.
Just tried on my own ZX80 to confirm that you should see 16384 for 16k and 1024 for 1k.
I tried it on a couple of (nameless) emulators and got stupid results so as said above tried on real kit for certainty.
LATE EDIT.
When used with the ZXpand it returns 16382 not 16384 so not sure what's going on there.
I'm almost sure this is courtesy of Mark.
Just tried on my own ZX80 to confirm that you should see 16384 for 16k and 1024 for 1k.
I tried it on a couple of (nameless) emulators and got stupid results so as said above tried on real kit for certainty.
LATE EDIT.
When used with the ZXpand it returns 16382 not 16384 so not sure what's going on there.
- Attachments
-
- RAMTEST.O
- (123 Bytes) Downloaded 123 times
Last edited by Moggy on Wed Oct 02, 2019 9:53 pm, edited 3 times in total.
Re: ZX80 trouble shooting
Searching for ZX80 ramtop with Google found
PRINT PEEK 16388 + 256 * PEEK 16389 NEW LINE
PRINT PEEK 16388 + 256 * PEEK 16389 NEW LINE
In theory, there is no difference between theory and practice. But, in practice, there is.
-
- Posts: 2169
- Joined: Sat Nov 26, 2016 2:42 am
Re: ZX80 trouble shooting
Thanks Moggy - that does give 16384 on my ZX80.Moggy wrote: ↑Wed Oct 02, 2019 9:28 pm Here you go Lardo.
I'm almost sure this is courtesy of Mark.
Just tried on my own ZX80 to confirm that you should see 16384 for 16k and 1024 for 1k.
I tried it on a couple of (nameless) emulators and got stupid results so as said above tried on real kit for certainty.
LATE EDIT.
When used with the ZXpand it returns 16382 not 16384 so not sure what's going on there.
ZX80
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
-
- Posts: 2169
- Joined: Sat Nov 26, 2016 2:42 am
Re: ZX80 trouble shooting
Thanks Paul - that also gave 16384 on my ZX80. But it took me a while to figure out how to get PEEK on the ZX80 though!
PRINT PEEK (16388) + 256 * PEEK(16389) NEW LINE
You actually have to type in PEEK not use a key combo. That really threw me.
Does the ZX80 not do a slow scan to determine how much RAM it has? On the 81 it takes a few seconds before the K appears with a RAM pack plugged in. On my 80 it is more or less instant.
ZX80
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
Re: ZX80 trouble shooting
I can't say I know why this (my 80 is the same) I can only assume it 's because it doesn't use floating point for numbers only integer hence some basic programs run faster then the 81 even in fast mode.
Here's a link to the operating manual just in case you don't have it.
https://www.worldofspectrum.org/pub/sin ... Manual.pdf
Here's a link to the operating manual just in case you don't have it.
https://www.worldofspectrum.org/pub/sin ... Manual.pdf
-
- Posts: 2169
- Joined: Sat Nov 26, 2016 2:42 am
Re: ZX80 trouble shooting
Thanks. That would make sense about the integer maths.Moggy wrote: ↑Wed Oct 02, 2019 10:41 pm I can't say I know why this (my 80 is the same) I can only assume it 's because it doesn't use floating point for numbers only integer hence some basic programs run faster then the 81 even in fast mode.
Here's a link to the operating manual just in case you don't have it.
https://www.worldofspectrum.org/pub/sin ... Manual.pdf
ZX80
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA
ZX81 iss 1 (bugged ROM, kludge fix, normal, rebuilt)
TS 1000 iss 3, ZXPand AY and +, ZX8-CCB, ZX-KDLX & ChromaSCART
Tatung 81 + Wespi
TS 1500 & 2000
Spectrum 16k (iss 1 s/n 862)
Spectrum 48ks plus a DIVMMC future and SPECTRA