CompuServe Thread

#WShell Startup

7 messages in this thread
#34148From: Robert J. FleigApr 12, 1993 2:48 AM
Bill, How would I get to run a program from WShell on startup? Everything seems to run from the original startup shell and then leaves me with the WShell window. In other words, I would like to automatically run commands from the WShell at startup. Is there any way to have the system user-startup sequence run from a WShell window? RJ……….on AutoPilot
#34152From: Bill HawesApr 12, 1993 7:59 AM
Robert, You could change your startup-sequence file to open a WShell window, and then complete the startup (including user-startup) in the WShell window. But in most cases, it's adequate to let the system finish its initialization and then leave you with a WShell. Most of the advantages of WShell apply to interactive work with the shell. The theory behind the user-startup file was to provide an easy way for users to customize their startup without having to mess with the generic boot-time system initialization. -Bill Hawes
#34160From: Robert J. FleigApr 12, 1993 4:15 PM
Bill, Thanks. RJ……….on AutoPilot
#34154From: BILL LEACHApr 12, 1993 8:30 AM
Robert; I'm not certain that I know what you want to do but I think that maybe you want to put something like: newwsh from s:my-startup in your user-startup sequence where "my-startup" contains all the stuff that you want to launch from wshell. Do not change the startup-sequence but put this into user-startup if you wish to not have a miseable time on the next OS upgrade. -bill
#34161From: Robert J. FleigApr 12, 1993 4:15 PM
Bill, I use the AtomClock program to call and set my system clock. It also comes with an Arexx file called "settime.rexx" which will automatically run AtomClock once a month. The docs say if I have Arexx and WShell, to insert it into my startup-sequence. I tried inserting it in my User-startup but it won't run from the startup window (must only run from a WShell window). If I run it from the WShell window, it works. I found if I have the command "newwsh inplace" in my user-startup, the WShell window will run the rest of the user-startup commands including "settime.rexx". The only problem is that once the startup is done, the WShell window closes and I am left without a shell window. I am going to try as you say and try to solve this by doing a "newwhs from s:myshell" ("myshell containing the "settime.rexx"). RJ……….on AutoPilot
#34179From: Mike SchillerApr 13, 1993 12:21 AM
Robert: I have the User-Startup running in the WShell on my system. I simply changed the line in the Startup-Sequence that executed the User-startup to one that called the WShell. Here's my current line: NewWSH from s:User-Startup That's all there is to it. // -Mike Schiller \X/ AMIGA! On AutoPilot in sunny Fort Lauderdale
#34199From: Robert J. FleigApr 13, 1993 7:47 PM
Thanks Mike, that's just what I needed to know. RJ……….on AutoPilot