forum.defence-force.org

Looks terrific!!!

I know the Oric has tight timings to accommodate three memory accesses in every cycle (2 ULA and 1 CPU), thus the end of 120ns RAM and versions of 6502 capable of running a 2.0 MHz. It is possible to use slower RAMs (I've seen that) but it might be out of spec. Could it be that certain CPU & Mem...

I'm quite sure we made some tests with real floppies... in fact Silicebit did most of them and even published a video about it. With 18 sectors loading times were higher and it was even impossible to transfer the OS to some disks. 19 sectors was definitely unreliable.

Great you sorted this out! Thanks for the info too.

The emulated FDC interface mimics the Microdisc registers and operations, but there is nothing for the LOCI API calls at the moment and it's way down the priority list for myself. Happy to support anyone else who wants to give it a try and perhaps have more emulator experience to start. Edit: yeah,...

Here you have a putchar, puts and print_digit (passed as two BCD numbers in reg A), along with gotoXY and clrscr (and others). https://github.com/Oric-Software-Development-Kit/Oric-Software/blob/master/users/chema/Oricium/auxiliar.s Probably not to be used directly, and may require some adaptation, ...

Printf is a beast, slow and fat. Why not implement a puts yourself? For text mode is quite easy. You can also have a printnum, for printing numbers and so on.

I am quite sure I have my own versions for those in my games' sources.

I think Zaxon once said he mistakenly did something so the second drive here is not DS1, but 2 or 3. Cannot remember. Maybe worth checking. As the interface is a pure Shuggart, you should test a drive that can be configured with jumpers or switches to DS0-3.

I've said several times that I am not super fan of features that were not present in the original machine, nevertheless a 2 color 320x200 mode could be easy to create, and would be invaluable (8 pixel scans at last!). Also a hardware double buffer could be nice and seems doable (by paging the hires ...

The loader address is stared in the floppybuilderscript.txt file. Here is my code in Blake's 7: ; ; Now here is the loader code, that one is Microdisc only ; SetPosition 0 4 WriteLoader ..\build\files\loader.o $fd00 ;$fe00 ; Sector 4 I am sure it ends up in floppy_description.h as the defined tag FL...

Awesome!

I am not sure if I'll be able to clear things up. Dbug is who made the tool. In my sources the loader code starts at $fd00, not at the usual $fe00, because I added the saving routine and some other things. If osdk_end is greater than that value, you run into trouble. From $ffce up what you have is j...

This is getting really impressive.

Memmap is a great utility to show where things may overlap, as soon as you define labels for each section.

https://www.osdk.org/index.php?page=doc ... age=memmap

Nice! Thanks for the release!