Mark wrote: ↑Mon Apr 29, 2024 5:29 pm
NULL8 isn't required for saving, in fact OSI defaults to 10 NULLS between <CR> & <LF>, and the NULL command appends even more after <LF>
After entering or loading your BASIC file, to save to cassette, all you do is type "SAVE", then "LIST". This causes the OSI to output the listing to tape and print "OK" at the end (which generates a syntax error when the data is reloaded). To get out of SAVE mode you have to type "LOAD" and then hit the space bar to exit load mode. BASIC takes care of automatically writing 10 NULLS between <CR> and <LF> at the end of every line, perhaps to give the BASIC tokenizer a few ms to process the input buffer? The BASIC loading process goes through the same routine as entering data from the keyboard, which can cause a couple problems. For instance you can enter lines using ? instead of "PRINT" which can make lines longer than you can load when SAVED to tape, and BASIC will insert a newline if the BASIC statement is longer then 71 chars, breaking loading.
There are a few tips and tricks in Aardvarks First Book of OSI
Such as enter POKE517,0 to turn off SAVE mode without having to do the LOAD <spacebar> thing.
You've seen how to load machine code programs via the monitor <RESET>ML, however OSI provided no way to generate these files. The Aardvark manual has a BASIC program to do this, you can do it with on your PC with OSIALod I used to use a ROMed assembler program to do this on my OSI. I can dig it up if there is any interest.
For various reasons I've not been able to spend much time with the 600D, just too many other distractions. Hopefully I can get back to this soon as I really do want to get the cassette in/out working.
I also need to figure out why the laptop I'm using to record from seems to drop the volume halfway through recording either via aux or tape out.
OK, so I have been trying to load MonMaze from the Monitor but seeing some stuff that doesn't 100% make sense so wanted to run it by the collective brains trust.
So I boot and drop to monitor and press 'L'
As playback (I'm playing back from a Windows 10 Laptop) commences, I see the 2 characters to the left of the memory location block change.
Sometimes there will be a flurry of changes, other times it will sit there for a few seconds before continuing.
The memory block of 4 characters does seem to increment too. I have also seen it flit between memory locations, or at least that's what it looks like.
Does this sound correct? Or should it be a constant stream of updates?
Just a reminder, I have run the tests and adjusted R57 and the pulse width is about 560uS as per the service manual.
Thanks
BTW I am ignoring saving first as that is a simpler circuit, I want to get loading to work and return to saving later.
You should see the address field increment from 0700 to 07ED, then lines of text scrolling up the screen containing data in "checksum loader" format, containing code and data which load into the range $0DD2-$1FFF. These lines begin with a semicolon, then the number of bytes on the line (usually $18, i.e. 24), the data, and a four-character checksum.
I see the file has been downloaded 48 times, so I expect someone would have said something if there were a problem with it, but I can't be sure. Comments from anyone who has tried it are welcome.
Anyway, I'm attaching the text form of the file contents to this message.
No current OSI hardware
Former programmer for Dwo Quong Fok Lok Sow and Orion Software Associates
Former owner of C1P MF (original version) and C2-8P DF (502-based)
bxdanny wrote: ↑Fri Jun 07, 2024 11:34 am
You should see the address field increment from 0700 to 07ED, then lines of text scrolling up the screen containing data in "checksum loader" format, containing code and data which load into the range $0DD2-$1FFF. These lines begin with a semicolon, then the number of bytes on the line (usually $18, i.e. 24), the data, and a four-character checksum.
I see the file has been downloaded 48 times, so I expect someone would have said something if there were a problem with it, but I can't be sure. Comments from anyone who has tried it are welcome.
Anyway, I'm attaching the text form of the file contents to this message.
I don't think it's the file, but I'm for sure not getting what you've put in that text file. It just sits and increments the memory counter as a hex number changes on the right.
I'm using your 48 column ROM BTW, but the results are the same in both 24/48 column mode.
Currently trying different volume variations to see if one works.
You need to be in 24-character mode for the program to work. That''s once it's loaded, of course.
You could try converting the text file I posted this morning back to .wav format using OSIKCS and loading that. Probably the results will be the same, but I'd like to know.
No current OSI hardware
Former programmer for Dwo Quong Fok Lok Sow and Orion Software Associates
Former owner of C1P MF (original version) and C2-8P DF (502-based)
bxdanny wrote: ↑Fri Jun 07, 2024 1:12 pm
You need to be in 24-character mode for the program to work. That''s once it's loaded, of course.
You could try converting the text file I posted this morning back to .wav format using OSIKCS and loading that. Probably the results will be the same, but I'd like to know.
Thanks, I'll have a look at OSIKCS and see if I can figure it out
bxdanny wrote: ↑Fri Jun 07, 2024 1:12 pm
You need to be in 24-character mode for the program to work. That''s once it's loaded, of course.
You could try converting the text file I posted this morning back to .wav format using OSIKCS and loading that. Probably the results will be the same, but I'd like to know.
I converted the file and it's attached here. It isn't actually a ZIP file, I just added that so I could upload it, so just remove.zip from the end and you're good.
