Regarding /command and -w switch in win2K.
[1/6] from: depotcity:telus at: 30-Apr-2001 1:55
With win2K, if you create a shortcut to reb/command like so... c:\rebol.exe -w The only way to kill it is by rebooting? Is there anyway to have a command script run in the background, call a view script and... a. Get rid of the ugly command prompt box behind the view window. b. Hide the command's script window, yet able to kill both? (Preferably from a view button and without a reboot!) Thanks TBrownell
[2/6] from: brian:hawley at: 30-Apr-2001 15:57
Hi! TBrownell wrote:
>With win2K, if you create a shortcut to reb/command like so... > >c:\rebol.exe -w > >The only way to kill it is by rebooting?
You can kill a process from the Processes page of the Windows Task Manager.
>Is there anyway to have a command script run in the background, >call a view script and...
Can your task be done with /View/Pro? It would be simpler... Brian
[3/6] from: depotcity::telus::net at: 30-Apr-2001 15:27
Hello. Firstly, there is no process to kill with the -w switch. Next, View doesn't have a runtime yet, so? TBrownell
[4/6] from: brian:hawley at: 1-May-2001 11:31
Hi Terry, I rearranged things to show the threads of conversation... Terry Brownell wrote:
>Brian Hawley wrote: > > TBrownell wrote:
<<quoted lines omitted: 7>>> > Windows Task Manager. >Firstly, there is no process to kill with the -w switch.
Sure there is. Processes show up on the Processes page. In WinNT/2k, processes don't show up on the Applications page unless they have a non-hidden window that shows up on the task bar, but they still show up on the Processes page. You can kill them from there with the "End Process" button. Alas, I don't recall how to kill processes from the command line on NT or 2k, just from Task Manager. Oh well...
> > >Is there anyway to have a command script run in the background, > > >call a view script and... > > > > Can your task be done with /View/Pro? It would be simpler... > >Next, View doesn't have a runtime yet, so?
It was a reasonable question. I thought you were going to say database support, but I forgot about the runtime. Does your app need database support or are you using the runtime as a cost-saving measure? I'm just curious - we may have the same problems here at my job. As for your problem, perhaps the /Command script can call the /View script through the Windows start command. There may be some combination of the /wait refinement to both the call function and the start command that might work. When the /View program exits, the call will return and the /Command script can continue. If you try this, please tell me if it works... Beyond that, I can only suggest that the /Command script be a server program and the /View script be the client. That's the general approach we use here, at least when we need functions that aren't in /Core, /View, or their /Pro equivalents. Brian Hawley
[5/6] from: depotcity:telus at: 1-May-2001 12:39
Hi Brian I have a /command runtime script that has a forever loop (below) that calls a /view script randomly. I create a shortcut to this runtime with the -w switch. The /view scripts have a process, but the runtime doesn't. If i kill everything with the name rebol attached (via the task manager/process), it will still randomly popup view windows till a reboot. ;The runtime script... rebol  random/seed now forever [ a: random 100 if a = 34 [call "view-script.r"] wait .1 ] As for the runtime, it's a cost saving measure, and hides the script from curious eyes. Terry Brownell
[6/6] from: brian:hawley at: 1-May-2001 15:36
Hi Terry, Not currently having /Command runtime, let me ask a few questions about it: How is the script bundled with the runtime? Are the runtime and script bundled into a new executable? If so, what is the name of that executable? Did you look for that name in the processes list? Does the executable take the same command line parameters as the standard Rebol, and can you specify certain ones to be used by default? Can the runtime be used as an extension language or is it just for bundling? If the process is really not showing up in the Task Manager process list, I would be curious to find out how they managed that. Might come in handy some day. Brian At 12:39 PM 5/1/01 -0700, you wrote:
>Hi Brian >I have a /command runtime script that has a forever loop (below) that calls
<<quoted lines omitted: 19>>>Sent: Tuesday, May 01, 2001 9:31 AM >Subject: [REBOL] Re: Regarding /command and -w switch in win2K.
- Quoted lines have been omitted from some messages.
View the message alone to see the lines that have been omitted