🚀 go-pugleaf

In article <8811161843.AA28461@postgres.Berkeley.EDU> dillon@POSTGRES.BERKELEY.EDU (Matt Dillon) writes:
>
>	You want to disconnect a program such that when you RUN <nil: >nil:
>	(using the new 1.3 RUN) you can then EndCLI the cli.

[stuff deleteted]

>	So, you must set pr_ConsoleTask to some other valid device.  Guess
>	what?  Any device will do except NIL: which isn't a real device.  For
>	example, RAM: :

Better yet, use null:

It's functionally identical to NIL:, but is a *real* dos-device with it's
own message-port. I've posted it to the moderator for comp.sources.amiga

>		extern APTR DeviceProc();
>		proc->pr_ConsoleTask = DeviceProc("ram:");
>
>		(assuming RAM: exists)

Do this instead:

		proc->pr_ConsoleTask = DeviceProc("null:");

>	But the ultimate goal is achieved ... you can kill the CLI window
>	and still arbitrarily run programs from the detached program with
>	impunity.
>
>	The only possible problem which I have yet to test is when several
>	programs try to access RAM:* as their console at the same time.  
>	Since the file is openned 1006, other programs trying to Open() it
>	will fail while the first programs is still running.  What happens?

God knows what happens. With null: this is no problem since everybody
can open it as many times as he wants, just like with NIL:

I've used null: for half a year now, with no problems at all.
In my version of AmiCron I set pr_ConsoleTask to DeviceProc("null:")
and now it doesn't requires a window to run!

>							-Matt

  - Gunnar

SNAIL: Gunnar Nordmark          VOICE: (+46) 8 - 755 42 52
       Nora strand 5
       S-182 34 DANDERYD        EMAIL: gno@stacken.kth.se
       SWEDEN                          gno@SESTAK.BITNET

"Words, words, words."  William Shakespeare