Couple of error code questions...

[VicViper]

Soo in my never ending noob quest, i got my hands on a mint tape drive. I've encountered a couple of trip ups. I did get the one Moonbeam tape to load (Moon Vasion) but with Strike Force 99 got an error, something along the lines of ERROR I/O 54? another one of my fathers old tapes has a few programs hand written on the cassette; ASPIC 0-58, KNIGHTS TOUR 59-88, LOST RUINS 90-133, COUNTY FAIR 135-172. Attempts to load ASPIC (whatever that is) gave me an "ERROR MEMORY FULL IN 290. OK. Was unable to load any of the other files on the tape using the counter on the tape player to space where on the tape i should start it. I imagine that is what the numbers are referring to. So, figuring perhaps i need to use the Extended Basic cart, i put that in and press 2 for EXTENDED BASIC. uh oh, here is where things got really scary. The light one my expansion box in the slot where the 32K is lights up, turns off, and i get nothing but scrambled data on the screen. hope my 32K isnt messed up. I DID get a tape with "San Fransisco Tour" to load up, but i wish i hadn't. Thoughts on any of these various disasters?

[+arcadeshopper]

scrambled screen could be either the cart is dirty/not seated right, the sideplug/firehose is dirty/not seated right or a issue with 32k card..

 

if you are loading tapes you may have to experiment with volume on the tape drive to get it to work, try high and work your way down in volume till it works

 

if you listen you can here where each program stops and the next one starts they all start with a single tone..beeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeet

 

I'll look up the error code when I get home

 

Greg

[+arcadeshopper]

5 is attempt to read past eof so may be a volume issue

[PeBo]

This might not answer your question directly, but it has helped me figure out what went wrong through the BASIC error codes nearly every time...

 

The two digit I/O error is not a single number like "54" it is actually a two part code (in your case 5 & 4)

 

The first digit is what caused the error:

 

0 - open
1 - close
2 - input
3 - print
4 - restore
5 - old
6 - save
7 - delete

 

While the second is what actually happened:

 

0 - Device name not found
1 - Device write protected
2 - Bad open Attribute
3 - Illegal operation
4 - Out of space
5 - End of file
6 - Device error
7 - File error

 

 

 

As Greg said, there are a few things that could cause screen corruption, and yup, could be your 32K card (when one of mine died, I just kept getting a blank screen), but I've found the usual suspect is either the cart or the firehose not being seated properly,

 

Hope you discover it is the latter.

Edited September 1, 2017 by PeBo

[+RXB]

If you have RXB you can use my CALL IO command that has Cassette READ and move that data into VDP, from there using RXB you

can make a copy into Lower 8K with RXB command CALL MOVES to move that VDP data to Lower 8K then use RXB command

CALL BSAVE to save the lower 8K to a file. Then you can use look at that file.

 

Anyway you go at is RXB has a way to read the file into memory no matter what it is, the CALL IO does not care what the file is for as

it just reads the data to where you want it to go, so this works no matter if a Program, DATA or LIST.

Edited September 2, 2017 by RXB

[PeBo]

The light one my expansion box in the slot where the 32K is lights up, turns off, and i get nothing but scrambled data on the screen. hope my 32K isnt messed up.

 

So, did you figure out if it was a bad connection to the console or your 32k card. I only ask because I had a very similar thing happen on my nanoPEB the other day, where FG99 was having trouble loading any 32k software (scrambled screen) while all the 8k stuff worked fine.

 

Turned out to be the speech synth (which the nanoPEB is plugged into) had been ever so slightly dislodged when I moved the console over a bit on the desk. a not-so-gentle push back into place and everything was fine. I have extra 32k cards for the PEB, but if the memory went on the nanoPEB it would be down for a while, so was happy it was just the connection.

[VicViper]

My 32K works fine, just ran the "Dont Mess With Texas" demo from my new FinalGROM99 the other day. did wiggle around my connections, might have been the problem. Have to try the Extended Basic cart again.