Proper startupcode in asm?

[oRBIT]

Is there such a thing as a 100% proper startupcode that makes your programs work both from shell/Workbench?
I've seen a few during the years and the current one I'm using is working the best. However, it locks asm-one when I run the code so I can only use it when I'm compiling exe's.

Are there better ways of doing this? I've attached the startupcode I'm using (don't know where I got it, it was along time ago)..

[StingRay]

Originally Posted by oRBIT

However, it locks asm-one when I run the code so I can only use it when I'm compiling exe's.

Use a newer ASM-One version (or ASM-Pro) and you won't have this problem any longer.

[oRBIT]

Just tried with 1.49RC2 but still same issue.

[StingRay]

Tried it with ASM-One 1.48 and ASM-Pro 1.16d, no problems. Only tried it with my very own "RunWB" code though but I don't think yours will be much different. Will check later.

Edit: checked your code and as expected it is not much different to mine. I checked my ASM-One/Pro settings now, I have the "Parameters" checkbox ticked, I guess this is what did the trick. Try if that helps.

[Toni Wilen]

		jsr	-378(a6)		;_LVOReplyMsg(a6)
					        ; ***** This line was missing from
  	                                        ; previous articles!!!! **********
		jsr	-138(a6)		;_LVOPermit(a6)

Does the note mean Permit() or ReplyMsg()? AFAIK missing Permit() is correct because it prevents WB from doing any deallocations too early (before task is completely killed by exec).

[Leffmann]

I don't call Permit in my own WB startup for that reason, and it's exactly what Commodore state in their docs.

[thomas]

AFAIK missing Permit() is correct because it prevents WB from doing any deallocations too early (before task is completely killed by exec).

Yes, Permit must not be called after reply of the message, because Workbench will free resources which are still used by the task. After ReplyMsg the program should just fall through to the end of the task.

I think I posted proper startup code here: http://eab.abime.net/showpost.php?p=664723&postcount=18

[oRBIT]

My "Parameters" was already checked.

[thomas]

Originally Posted by oRBIT

However, it locks asm-one when I run the code so I can only use it when I'm compiling exe's.

When you run a program from Asm-one, it probably runs in the context (process) of Asm-one. This means you need to run Asm-one from the shell, because if you run it from Workbench, your program checks whether the process was created by Workbench and then Wait()s for a message which never appears (the message has already been received by Asm-one).

[Photon]

If that's the problem, how come Stingray could run it?