forum.defence-force.org

OK, so i've worked out the sequence of code leading up to the $B966 instruction: 1. ($b902-$b902) Disable interrupts 2. ($b903-$b905) Disable VIA interrupt 3. ($b906-$b90f) Store the address $0710 into $26b/26c 4. ($b910-$b914) $314 write: - Disable microdisc ROM - Enable ROM - Set bit 2 (?) 5. ($b9...

Some info on the sedoric bug... The disk debug in Oriculator includes the address of the instruction that writes to the disk command register for each disk operation. When booting the toxic slime disk, there are 2 distinct disk routines before the "filling memory" message: A) The microdisc...

@Brana I doubt it works on anything older than Win2000, however, if someone compiles it with an old enough GCC and a version of SDL that works on Win98, it would work. That won't be me, though, I haven't used a Win9x computer in a LOOOOOONG time. @Everyone Thought i'd post an update in this thread s...

if (line 363) the 'if( v->t1run )' is not executed, you still do the v->t1c-=cycles (line 372), is it possible this underflows ? From memory, this is on purpose and should be what the VIA itself does (as described by the MOS datasheet). The t1c field is an unsigned short and it wraps around, which ...

What makes you think of VIA?

You have to put a '$' before numbers in the debugger to specify hex, otherwise it treats it as decimal. You can also use % for binary.

I dunno if i should change it to default to hex.

Anyway, you were probably setting breakpoints at wrong addresses because of this. Please re-try your tests.

Could be. It doesn't crash after the toxic cloud on OS4 either, and that is using a newer GCC than the one from Dev-C++ (3.x.x vs. 4.2.4).

Interestingly, I just compiled Oriculator in Code::Blocks, and it doesn't crash after the toxic cloud in barbitoric for me any more

I don't know. I primarily develop on Amiga. I just happened to already have Dev-C++ installed on my PC, and used it for the windows build.

If the hobbit has a custom loader, it would likely cause problems with the turbo mode, since turbo mode patches the ROM functions for reading from tape. If the hobbit only uses ROM loaders, it is a bug in oriculator that should be fixed. Edit: BTW, do you plan to help debug problems with oriculator?...

I compile it with the mingw gcc that comes with Dev-C++ (although I use the command line rather than the IDE). Here is a step-by-step guide to compiling it with Dev-C++ in the IDE : 1) Download and install Dev-C++ . 2) Once it is installed, install the SDL add-on (if Dev-C++ installed correctly, you...

You're quite right, which is a bit embarrassing since the sole purpose of that flag is to be turned on by BRK

Fixed and in the SVN.

Just checked in some significant changes to the monitor/debugger. I'll take a look at the sedoric bug this lunch time.

I've fixed the STNICCC2000 demo, and the record player in barbitoric. The overflow bit was miscalculated in ADC and SBC.

Sedoric disks still end up in a sea of BRKs, though.

Download SVNr42 for this fix..

Edit: DBug seems i figured this out at the same time as you!

I think the sedoric problem may be the same thing that stops the record player effect working in barbitoric; in both cases it seems to be the copying of data that fails. BTW, I've uploaded a new build of oriculator that has some suggested improvements to the memory watch window in the debugger. Hit ...