FIXED: Venus The Fly Trap (TRAP #0) & NOVBRMOVE INFO

[Retro-Nerd]

Venus: The Flytrap, SPS #1985

You got the Exception "TRAP #0" at the start? No problems here, it runs flawless into level 1.

[killergorilla]

Originally Posted by Retro-Nerd

Venus: The Flytrap, SPS #1985

You got the Exception "TRAP #0" at the start? No problems here, it runs flawless into level 1.

Check your tooltypes, you have NOVBRMOVE set

[Retro-Nerd]

Originally Posted by killergorilla

Check your tooltypes, you have NOVBRMOVE set

Upps, yes. So no bug, but only F10 works as quit.

I would change the report for games with a default NOVBRMOVE setting. The Slave programmer designed it this way, it is no error. Maybe you find a better description.

[killergorilla]

Well unfortunately NOVBRMOVE removes the option to set your own quit key, so I'll leave them in the list for reference.

If the slave authors don't choose to update it then I'm happy, if they do, I'm happier

[Codetapper]

Originally Posted by killergorilla

Well unfortunately NOVBRMOVE removes the option to set your own quit key, so I'll leave them in the list for reference.

Can we just clear this up! NoVBRMove has nothing at all to do with quit keys, you can specify a different quitkey in the slave and still use NoVBRMove!

[Retro-Nerd]

Originally Posted by Codetapper

Can we just clear this up! NoVBRMove has nothing at all to do with quit keys, you can specify a different quitkey in the slave and still use NoVBRMove!

For all games? I've tried:

Quitkey=$5d

for Venus The Flytrap. But only the default key F10 works, with NoVBRMove activated.

Wepl wrote this in the WHDLoad docs:

QuitKey/K/N

Sets the rawkey code to quit the program, this works only if the VBR is moved by WHDLoad

[killergorilla]

Originally Posted by Codetapper

Can we just clear this up! NoVBRMove has nothing at all to do with quit keys, you can specify a different quitkey in the slave and still use NoVBRMove!

Yes it does. (or at least the authors haven't been as thorough as you)

Take a look at Desert Strike.

Run it without NOVBRMOVE, I can quit with my usual quitkey.

Run it with NOVBRMOVE, I can only quit with F5

[Codetapper]

Originally Posted by killergorilla

Yes it does. (or at least the authors haven't been as thorough as you)

Take a look at Desert Strike.

Run it without NOVBRMOVE, I can quit with my usual quitkey.

Run it with NOVBRMOVE, I can only quit with F5

Bingo! Sloppy installs! If you manually check for the quit key in the slave (like 99% of mine do) then it will always quit, even if the key is changed or the VBR hasn't been moved.

[killergorilla]

Yeah I remember you mentioning it in another thread, so figured that might be the case

Is this related to the fact that some games won't quit on 68000?

[Wepl]

Originally Posted by Codetapper

Can we just clear this up! NoVBRMove has nothing at all to do with quit keys, you can specify a different quitkey in the slave and still use NoVBRMove!

There are two ways to quit. First the Slave itself checks and tells WHDLoad to quit and second WHDLoad itself will independently from the Slave quit.

For the first the Slave will check the keyboard or other stuff in the game and quit as requested. The key to quit maybe hardcoded or it may use the QuitKey provided by WHDLoad. This works also on 68000 and also if NOVBRMOVE is set.

The second works only if there is at least a 68010 and NOVBRMOVE is not set. WHDLoad will hangin all interrupts. It will see the ints before the installed program and check on each interrupt if the QuitKey (DebugKey,FreezeKey,...) is pressed.
So usual WHDLoad will quit because it is the first.

You can check if the games uses hardcoded quitkey by setting a different quitkey and checking if it still quits by key written in the docs.

There should be nearly no installs left with hardcoded quitkey.
But there are several (maybe many) installs without built in quit, these installs can only quit via WHDLoad.

[killergorilla]

Changed status to FIXED as JOTD has updated the install.

Will be included in the next pack.