Teradesk "Don't multitask" option

[simonsunnyboy]

What exactly does the option "Don't multitask" do when configured for an application under Teradesk?
I could run TurboAssembler (which certainly does not like XaAES and multitask by default) this way under Mint/XaAES and Teradesk.

[m0n0]

Under MiNT the only way (that I know of) to stop multi-tasking is running the program with Super privileges... but I doubt that this is used... hrm, interesting question!

[Latz]

Hi,
as noted in teradesk.hyp:
"...'No multitasking' option can be set, in which
case the program will be activated as in single-TOS. Note that this
option has not yet been implemented in a completely satisfactory way,
and has some effect only in MagiC."
Latz

[DarkLord]

Stepping back a few years, but Neodesk had a similar option when combined
with Geneva. You could force unruly programs to drop to single TOS and run
there, effectively giving the errant software full focus and freezing the rest.

I used it a couple of times - it does work.

[wongck]

don't jinnee has this as well ?

[joska]

"...'No multitasking' option can be set, in which
case the program will be activated as in single-TOS. Note that this
option has not yet been implemented in a completely satisfactory way,
and has some effect only in MagiC."
Latz

This information is obsolete. Helmut has added proper single-tasking support to MiNT+XaAES since this was written.

[simonsunnyboy]

Does this mean that current versions of Teradesk can run old stuffs more safe this way?
I would probably set most ST progs to use this mode then

[joska]

No, all current versions of MiNT+XaAES can do this. Teradesk can ask the OS to do this, but so can Jinnee and Thing!.

[simonsunnyboy]

Can you explain the "can ask the OS" call? How does this work on GEMDOS level? (Sorry if this is obvious but sofar I only use GEMDOS in the TOS way, not any Mint extensions)

[joska]

This is specified in the parameter wiscr in shel_write().

[simonsunnyboy]

This is specified in the parameter wiscr in shel_write().

Hmm, shel_write() is a call of the AES. I admit I never dug deep into that, esp not the modern incarnations.

[helmut]

This is specified in the parameter wiscr in shel_write().

But XaAES does not have an interface to start something as single-task, you have to set prog-flags as described in the wiki.

-Helmut

[rudis]

here it is

[joska]

This is specified in the parameter wiscr in shel_write().

But XaAES does not have an interface to start something as single-task, you have to set prog-flags as described in the wiki.

Ahh... Sorry, I was sure that this was supported in shel_write(). What do you mean by "no interface" btw? Binaries are started with Pexec(), right? So Pexec() must know about single mode. And shel_write() calls the same code as Pexec(), so I don't think it should be much work to support this single mode in shel_write. That will allow desktops to use this feature without having to set a flag in the executable's header.

[helmut]

Where can I set single-task in teradesk?

Does it check the AES-features?

I once thought I'd do the shel-write-interface, but as I looked at the documentation and saw what MagiC does I found that the differences are too big.

But when everybody is happy with what XaAES does (why not?) maybe it's possible - have to re-learn how it works though ...

-Helmut

[simonsunnyboy]

Where can I set single-task in teradesk?

It is an setting per individual application. I selectt he program and then open the "Set application" dialogue. This has the "Don't multitask" option.

(Even under TOS as shown in my Hatari shot below)

[helmut]

I have set the don't multitask-option and did not find any difference to normal launch in any parameter, using teradesk 4.01.