ZX Computings - OpenLibra
ZX Computings - OpenLibra
ZX Computings - OpenLibra
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
The @*?$1!&£@<br />
RAM pack<br />
Dear <strong>ZX</strong> Computing,<br />
I've read many letters which<br />
mirror my own problems with<br />
Sinclair's 16K memory pack.<br />
I bought a 16K RAM pack,<br />
and — like so many<br />
correspondents — have<br />
suffered with bytes of<br />
information altering<br />
themselves before the<br />
computer crashed. When 1<br />
first encountered the problem,<br />
I sent my 16K pack back as I<br />
thought it was faulty. It was<br />
returned with a note to the<br />
effect that there was nothing]<br />
wrong with it.<br />
I have now relieved the<br />
problem of disappearing data<br />
but at the expense of my<br />
<strong>ZX</strong>80.1 made a number of<br />
'alterations', the first of which<br />
was to abandon the flimsy top<br />
part of the casing. I presumed<br />
that the fault was a heat<br />
problem and hoped this would<br />
cure it. It partly worked and so<br />
I then unbolted the regulator<br />
and heatsink from the board<br />
and left it standing in free air<br />
with an additional heatsink.<br />
This helped greatly, but did<br />
not totally solve the problem.<br />
The final 'modification' was<br />
to remove the casing around<br />
the 16K RAM pack. There are<br />
1 5 chips inside the case which<br />
get quite hot. I now have no<br />
problems with data altering —<br />
except under one condition.<br />
When working on a large<br />
program (3K plus), and<br />
extensively altering the<br />
program, I find there comes a<br />
point where the computer<br />
cannot handle the extreme<br />
alterations.<br />
K Huber,<br />
Hayes End, Middlesex.<br />
* CXPLCMMVr<br />
D A M E I<br />
<strong>ZX</strong>81<br />
Catty wonder<br />
Dear <strong>ZX</strong> Computing,<br />
The wonders or u.C's little<br />
machine never ceases to<br />
amaze me. Did you know that<br />
this program actually works:<br />
10 LETC « 1.5<br />
20 LET A - 4.9<br />
30 LET T = 20<br />
40 LET CAT - 49<br />
<strong>ZX</strong> COMPUTING SUMMER 1962<br />
50 LET CA - 12<br />
60 INPUT X$<br />
70 PRINT VALX$<br />
80 PRINT VAL X$ (TO 2)<br />
Entering either C, CA or CAT<br />
produces the appropriate<br />
answer on line 70, and will<br />
even break down CAT to CA<br />
on line 80 to print 12 as the<br />
answer.<br />
Andrew Field,<br />
Epping, Essex.<br />
And an answer<br />
Dear <strong>ZX</strong> Computing,<br />
Having read about the various<br />
problems with the 1 6K RAM<br />
pack, I am beginning to<br />
wonder if I am exceptionally<br />
lucky, or are all the other<br />
satisfied <strong>ZX</strong>80/81 users too<br />
busy writing long and complex<br />
programs to find the time to<br />
write?<br />
I did have some crashes<br />
with the 3K RAM, so I wrote<br />
to Sinclair and received a letter<br />
which included the following;<br />
"We have found that<br />
lubrication on the contacts<br />
soives the problems of RAM<br />
pack connections. You should<br />
first clean the edge connector<br />
with surgical spirit and then<br />
smear it with Vaseline."<br />
I did this and had no further<br />
trouble, and when my 1 6K<br />
RAM arrived I repeated the<br />
treatment. Again, no trouble<br />
at all.<br />
With regard to Sinclair<br />
service, I can only say that I<br />
am very happy. Like many<br />
others, I received a letter<br />
about the 1 6K RAM delivery.<br />
Mine arrived in four weeks. I<br />
had a keyboard fault on the<br />
<strong>ZX</strong>81 kit that I assembled for<br />
my son. It was replaced by<br />
return post after phoning<br />
Cambridge. We had another<br />
intermittent fault, and as I was<br />
able to go to Cambridge, I took<br />
it to the Sinclair office. I was<br />
directed to the Service<br />
Department where, after<br />
spending some time on it and<br />
failing to find the offending<br />
component, they replaced it<br />
Letters<br />
with an assembled <strong>ZX</strong>81.<br />
Note that I have no<br />
connection with Sinclair,<br />
except as a satisfied user.<br />
D E F Rolfe,<br />
Haslemere, Surrey.<br />
• PLOSIVE<br />
CAiVUB<br />
- <strong>ZX</strong>81<br />
Screen invert<br />
Dear <strong>ZX</strong> Computing,<br />
When writing games for my<br />
<strong>ZX</strong>81,1 find that I sometimes<br />
need to 'inverse' everything<br />
on the screen at a particular<br />
stage in the program. It is<br />
possible to use a BASIC<br />
subroutine to do this but this<br />
is a slow process — half a<br />
minute or so — so I set about<br />
writing a machine code<br />
routine which could be used in<br />
the SLOW mode.<br />
Type in the following<br />
program:<br />
10 POKE 16388. 0<br />
12 POKE 16389, 127<br />
14 FOR C = 32600 TO 32624<br />
16 INPUT N<br />
18 POKE C, N<br />
20 NEXT C<br />
22 NEW<br />
The numbers to be entered<br />
(line 16) are as follows:<br />
42, 14, 64. 6. 22. 126. 254.<br />
118. 32, 8. 5, 120, 254.0, 32,<br />
5, 24, 6, 198, 128, 119, 35,<br />
24. 237, 201<br />
The routine will still remain at<br />
the top of RAM, even after<br />
NEW, so it can be used for any<br />
program LOADed during a<br />
programming session. You<br />
need to include the following<br />
routine in the BASIC program:<br />
9000 PRINT AT 0,0:<br />
9010 LET RR-USR 32600<br />
Line 90Q0 ensures that the<br />
m/c routine starts scanning at<br />
the beginning of the screen.<br />
The routine takes less than an<br />
eighth of a second to RUN and<br />
is relocatable, that is, it can be<br />
placed anywhere in RAM.<br />
John Miller,<br />
Farlington, Portsmouth.<br />
Och aye the 81<br />
Dear <strong>ZX</strong> Computing,<br />
Following an advertisement<br />
and a feature in the local<br />
paper, a <strong>ZX</strong>81 users' club has<br />
been formed in tnverclyde<br />
(Gourock, Greenock and Port<br />
Glasgow). The club is meeting<br />
weekly on Wednesdays at<br />
members' homes in turn.<br />
Our numbers are as yet<br />
small, but they are increasing.<br />
We would be grateful if you<br />
could mention us in '<strong>ZX</strong><br />
Computing', The number to<br />
phone for meeting details is<br />
Gourock 39967.<br />
The club secretary (me) and<br />
one of our other members<br />
attended the <strong>ZX</strong> Microfair.<br />
bringing back the saga of a<br />
day in London neither will<br />
forget. Not that we would<br />
want to. We only hope it will<br />
be possible to arrange<br />
something similar further north<br />
so that all our members can<br />
have the opportunity of seeing<br />
a wide range of both hardware<br />
and software.<br />
Robert Watt,<br />
Gourock, Renfrewshire.<br />
*Eric Deeson, the organiser<br />
of the EZUG (Educational <strong>ZX</strong><br />
Users Group) is planning a<br />
microfair in Birmingham in<br />
September. More details on<br />
that in the next issue of <strong>ZX</strong><br />
Computing. Jo find out more<br />
about EZUG, send a large,<br />
SAE to EZUG, Highgate<br />
School, Birmingham B12 9DS.<br />
TH