System takeover/shutdown

[alpine9000]

Hi,

So I am almost finished my first game which is a trackloaded direct hardware game.

But it would seem kids these days like to load stuff from hard drive so I thought I would do a workbench version also. Luckily the way I wrote the game made it fairly easy to get a version up and running.

I changed all of my sections to chip ram using vlink, so the loader just loads everything into chip ram (the trackloaded version runs in 512kb, but the workbench version loads everything so it takes about 650kb of chip ram). The routines that would track load stuff from disk just copies it around in ram in the workbench version.

I wrapped my entry point using Photon's startup code.

I grabbed the workbench message port handling code from Howtocode5.txt.

And everything seems to save/restore pretty well.

So far I have noticed two things:

(1) If I am playing a module before I run the game, it will not be running when I return. A start and stop on the player will get it going again. Not sure if this is normal or I am not restoring something.

(2) If I launch the game from a floppy in workbench, the drive motor doesn't stop. Not sure how to deal with this one. Any ideas ? I know how to turn of the drive motor, it's just that it could be any drive and when launched from HD wouldn't be needed.

Are there any other tests people can suggest to make sure I am cleaning up correctly ?

[Galahad/FLT]

Originally Posted by alpine9000

Hi,

So I am almost finished my first game which is a trackloaded direct hardware game.

But it would seem kids these days like to load stuff from hard drive so I thought I would do a workbench version also. Luckily the way I wrote the game made it fairly easy to get a version up and running.

I changed all of my sections to chip ram using vlink, so the loader just loads everything into chip ram (the trackloaded version runs in 512kb, but the workbench version loads everything so it takes about 650kb of chip ram). The routines that would track load stuff from disk just copies it around in ram in the workbench version.

I wrapped my entry point using Photon's startup code.

I grabbed the workbench message port handling code from Howtocode5.txt.

And everything seems to save/restore pretty well.

So far I have noticed two things:

(1) If I am playing a module before I run the game, it will not be running when I return. A start and stop on the player will get it going again. Not sure if this is normal or I am not restoring something.

(2) If I launch the game from a floppy in workbench, the drive motor doesn't stop. Not sure how to deal with this one. Any ideas ? I know how to turn of the drive motor, it's just that it could be any drive and when launched from HD wouldn't be needed.

Are there any other tests people can suggest to make sure I am cleaning up correctly ?

To stop the drive motor, you can either write the relevant bits to the drive motor registers, or, just have a small delay after the last floppy access which gives the drive more time to finish and switch off itself.

Waiting 3 seconds should be enough, obviously the delay should occur before you take over the system.

[alpine9000]

Originally Posted by Galahad/FLT

To stop the drive motor, you can either write the relevant bits to the drive motor registers, or, just have a small delay after the last floppy access which gives the drive more time to finish and switch off itself.

Waiting 3 seconds should be enough, obviously the delay should occur before you take over the system.

Cheers, I guess I was wondering more if I can detect that the app was loaded from a floppy so I know I need to turn it off. I guess this is more of a system programming thing, and I know next to nothing about the OS.

[Galahad/FLT]

Originally Posted by alpine9000

Cheers, I guess I was wondering more if I can detect that the app was loaded from a floppy so I know I need to turn it off. I guess this is more of a system programming thing, and I know next to nothing about the OS.

Try this.

lea $bfd100,a5
bset #7,(a5)
bset #6(a5)
bset #5(a5)
bset #4(a5)
bset #3(a5)
bset #3(a5)

[Lonewolf10]

Originally Posted by Galahad/FLT

Try this.

lea $bfd100,a5
bset #7,(a5)
bset #6(a5)
bset #5(a5)
bset #4(a5)
bset #3(a5)
bset #3(a5)

Why are you setting the #3 bit twice? (typo, or a more important reason?)

[alpine9000]

Originally Posted by alpine9000

Hi,

And everything seems to save/restore pretty well.

So far I have noticed two things:

(1) If I am playing a module before I run the game, it will not be running when I return. A start and stop on the player will get it going again. Not sure if this is normal or I am not restoring something.

I think I found out what was causing this. I think there might be a small bug in the P6112 player (not 100% sure if I am reading it right or if my configuration is valid). I am running in mode 2 (interrupt mode, non system friendly). So CIA should not be used? So in P1_Init when I changed:

        ...
        lea $bfd000,a0
        lea P61_timers(pc),a1
        move.b #$7f,$d00(a0)

        ifne p61cia                     ;only affect cia if actually used                                                         
        move.b #$10,$e00(a0)
        endc
	move.b #$10,$f00(a0)
        ...

to:

        ...
        lea $bfd000,a0
        lea P61_timers(pc),a1

        ifne p61cia                     ;only affect cia if actually used                                                         
        move.b #$7f,$d00(a0)
        move.b #$10,$e00(a0)
        move.b #$10,$f00(a0)
        endc
       ...

My music seems to play fine and if ProTracker is playing a mod before I run my game, it will continue playing after I quit my game.

Unfortunately I haven't spent any serious time looking at how P6112 works so I can't really be sure if this is a legit fix, or just a change that makes it work by fluke?

Anyone have any experience with this ?