[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference hydra::amiga_v1

Title:	AMIGA NOTES
Notice:	Join us in the NEW conference - HYDRA::AMIGA_V2
Moderator:	HYDRA::MOORE

Created:	Sat Apr 26 1986
Last Modified:	Wed Feb 05 1992
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5378
Total number of notes:	38326

2546.0. "starting things up & WB" by FSCORE::KAYE (He who dies with the most toys is dead) Tue May 09 1989 14:11

    I am having a problem with running things in my startup. For instance
    if i try to run MACHII 2.5 as the last line before starting workbench
    it runs MACHII, but doesn't start WB. If i click on the MACHII clock
    and shut it down, WB appears. What am i missing?
    
     mark

T.R	Title	User	Personal Name	Date	Lines
2546.1	Try RUN or RUNBACK	LEDS::ACCIARDI		`Tue May 09 1989 14:35`	6
	Are you RUN'ning MACHII? Some programs will not release the current CLI, in this case, the one that is executing your startup file. Ed.
2546.2		25520::MACDONALD	WA1OMM 7.093/145.05/223.58 AX.25	`Tue May 09 1989 14:39`	4
	You have to run MACHII after the LoadWB command. Also use, RUN >NIL: MACHII -Paul
2546.3	My $0.02 worth...	ATLV5::MCDONALD_J	Surly to bed, surly to rise...	`Tue May 09 1989 20:35`	14
	I say go with Ed's suggestion and pick up RUNBACK. In my book, it's required software. It works just like the RUN command, except it creates a different task (process, windowless CLI, whatever you call it) and runs the specified program in that 'detached process'. So you can RUNBACK a program, the image will get run, and the CLI from which you issued the runback command will be 'freed up' to do the next command. One added bonus for floppy drive users is that you can specify a pause after the RUNBACK command gets executed. This will give your executable time to get through with the floppy before the next statement in your startup-sequence gets executed... speeds up the boot by cutting down on disk contention. John
2546.4	got it working now - thanx	FSCORE::KAYE	He who dies with the most toys is dead	`Tue May 09 1989 23:00`	3
	Thanx, running it after the 'Load WB' command works fine. mark
2546.5	RUN v. RUNBACK	TLE::RMEYERS	Randy Meyers	`Mon May 15 1989 23:35`	19
	Re: .3 >[Runback] works just like the RUN command, except it creates a different >task (process, windowless CLI, whatever you call it) and runs the specified >program in that 'detached process'. A bit of a nit: Both the RUN and RUNBACK commands create new processes (actually a new CLI process, if you want to get specific). The difference is that the RUN command creates a new process that has shared write access to the window of the CLI that issued the RUN. RUNBACK creates a new process with no access to the window of the CLI that issued the RUNBACK command. The important difference is that if you type ENDCLI to the CLI that issued a RUN and the program being RUNned is still active, the window for the CLI will not disappear until the RUNned program finishes (the RUNned program is still using the CLI window, so the window will not vanish until it is closed by the RUNned program).