Problem getting demo starter code to work

[Nightfox]

Ah that makes sense, thanks Photon! I knew your demo starter code was perfect already and it must've been something wrong on my end

[NorthWay]

Would a Forbid() have stopped AsmOne from being creative, or is that an async operation picked up by input.device or something?

[hooverphonique]

Originally Posted by NorthWay

Would a Forbid() have stopped AsmOne from being creative, or is that an async operation picked up by input.device or something?

Yes. Although unlikely, the screen switch could also be performed by the user at the critical point, so finding a fix/workaround is probably a good idea..

[Photon]

The logical assumption is that your assembler IDE sets up the environment options you specify before executing your code. In this case, it should mean that your first line of code is executed in an NTSC screen mode. One of the lines of code turning off the interrupts should reasonably not affect anything, since there's a line of code in the startup that turns off the interrupts already.

[Seboss]

To make sure the program runs in the expected screenmode/resolution, is it required to setup a new Screen via system calls or is there some way to poke the hardware to get it to run the program in - say - PAL mode regardless of the screen mode of the IDE or Workbench?

EDIT: sorry Photon if that's a question you address at some point in AsmSkool. Still working my way up from episode 21, and it's not something that has been mentioned yet at this point, if I'm not mistaken.

[ross]

Originally Posted by Seboss

...is there some way to poke the hardware to get it to run the program in - say - PAL mode regardless of the screen mode of the IDE or Workbench?

Yes, if you have an ECS Amiga you can, after the standard system take over setup, set PAL bit in BEAMCON0.
So a

move.w #$20,$dff1dc

works.

[Leffmann]

BEAMCON0 and the other registers part of the display generator circuitry are black magic best left to be handled by Intuition and Graphics IMO. Make your setup code open a screen, that way you get output on the native video (if Workbench is running on RTG) and can select PAL/NTSC at the same time.

[Photon]

Originally Posted by Seboss

To make sure the program runs in the expected screenmode/resolution, is it required to setup a new Screen via system calls or is there some way to poke the hardware to get it to run the program in - say - PAL mode regardless of the screen mode of the IDE or Workbench?

EDIT: sorry Photon if that's a question you address at some point in AsmSkool. Still working my way up from episode 21, and it's not something that has been mentioned yet at this point, if I'm not mistaken.

Soon in the series, interfacing with the OS is added and in episode 36, this is replaced with a Startup proper. This takes over the system cleanly and shows a PAL screen.

In the first post, the problem turned out to be a combination of an NTSC mode used in Workbench on a PAL machine and one of the options in his Assembler forcing that mode temporarily in the handoff moment from the Assembler to the running demo code. Unchecking the box fixed it (and all other PAL stuff he would like to run from inside the Assembler!)

You can start an Intuition screen and then take over the system as Leffman suggests, but it's not required.