osiweb.org

Okay, I seem to have solved the booting problem (at least with the WDC65C02 in place). I found Pin 13 of U73 (the basic2 ROM select line) is connected to pin 8 of U16. Since pin 8 of U16 is the output of an '04 inverter and pin 13 of U73 is the output '138 decoder, they were not seeing eye to eye, s...

Hi Folks, I'm back to this after a little break. I have the 600D finished. Well, almost finished. It's not working 100%. First, the characters are coming up backwards. I'm not sure what chargen rom I have, but it's not right. Can anyone post the right one for the 600D or a link to it? Next, I can ge...

@Bill your memory issues could be the problem writing to the disk do you have the same buffers chips in the 600 and 610 ie 8t28 not 8t26's It is indeed the case that the memory issues are causing at least part of the problem. I can load values in to certain areas, then go back and read them and the...

Thanks Jeff!

I ran your code here on my SB2 and Replica 610 and all I get are 3 rows of asterisks repeating. Is that what is supposed to happen? I have all the memory populated on my 610. Let me know if there is anything else you want me to try. /Jeff That's exactly what you are supposed to see if there are no ...

Well, there is definitely something written in trk1 of the disk I tried to write, but a lot of it is not the same as what was supposed to be written there. There are track headers in subsequent tracks with the odd error, so this may be a media problem. I will now switch to new diskettes and try again.

Thanks a ton folks.

Glad to see I'm not alone with getting these errors. I have a brand new, sealed box of diskettes I'll break out for this purpose.

Well, my luck was short lived. Every time I try to save a track I'm greeted with ERR #9. It's like the disks are not formatting. When I format the disk, everything seems to go as it's supposed to. The SAVE command make the drive step to the right track, then about a second later I get the ERR #9. So...

Okay!

I've made some headway.

You first have to reset your machine and select D to initialize the FD hardware, then reset again, enter the monitor, load the OS code and then things start to work properly.

Onwards and upwards, as they say...

Sigh! :( I'm not having much luck with this. I have tried making boot files from several of the C1P 5.25" images and I get varying results. I can get the A* prompt, either locally (on the OSI) or on the terminal. The routine entry points I have looked at check out, but some versions just go into spa...