From the help file.........

Version 5.1 includes startup "switches" that you can append to the Reflection executable name to change the way Reflection starts. The startup switch syntax, specified in My Computer or Windows Explorer in the Properties dialog box, is as follows: 
<Program executable> [<option 1 >] ... [<option N>]
The <Program executable> is the name of the Reflection executable file (R1WIN.EXE, for example) and <option 1> through <option N> are the startup switches. The startup switches are:

/N

Suppress the display of the Reflection startup screen (mountain). 

/NOLOADSETTINGS

Specifies that the default settings file, or any other settings file specified, is not loaded. This forces Reflection to load with its factory default values. 

/NOOLE

Disables OLE automation server support in Reflection. This provides a memory savings of around 150K and provides a slight startup speed improvement. Use this switch if you have a lower performance PC and do not plan on using OLE automation. 

/RB <command>

Where <command> is a Reflection Basic command. 

/RBS <script filename> [<script argument>]

Where <script filename> is a Reflection Basic script. You can include an optional <script argument> to be passed to the script when it is executed (you obtain the argument from the script using the COMMAND$ statement). As with other options, enclose the argument in quotes when it contains spaces, for example:

R1win.exe /RBS Login.rbs "My Host Name"

/RCL <command>

Where <command> is a Reflection command language command. 

/RCLS <command language filename> [<command file argument>]

Where <command language filename> is a Reflection command file. See the syntax for /RBS, above.

/S <settings file>

Where <settings file> is the name of a settings file to load. This switch is not necessary for the first settings file specified. For example, the following two entries are equivalent: 

R1win.exe First.r1w /S Toolbar.r1w

R1win.exe /S first.r1w /S Toolbar.r1w

When you specify multiple settings files, each successive one overwrites the previous settings. 

/U

Force the startup folder to be the User subfolder.
For those switches requiring a second argument (/RBS, /RB, /RCL, and /S), a space is required between the switch and the argument. To specify an argument that contains spaces, surround the argument with double quotes. For example: 

R1win.exe /RB "Application.Visible = True"

For example, to load a settings file and execute a script on startup, you would enter a line like the following in the Command Line text box:

C:\Program Files\Reflection\R2win.exe /S Flubber.r2w /RBS Logon.rbs

You can also do this from the DOS prompt¾just precede the above line with WIN to start Windows.
In versions prior to 5.0, you could append settings file and RCL file information using this syntax:

R2win.exe [<settings file.] [,rcl file]

In general, Reflection version 5.1 still supports the older syntax (you'll receive an error if you do not include a settings file when specifying either an RCL or RB file).

© 1987-1995 Walker Richer & Quinn, Inc.

>>> David T Darnell <[log in to unmask]> 15/10/01 17:16:38 >>>
How can I set up my reflection1 shortcuts or .R1W files to startup Reflection without the
graphic (large bitmap with lake, mountains, etc.) being displayed?

I allow myself to be impatient when starting Reflection over Timbuktu, and this is an
undecessary waste of bandwidth, my time,....

Thanks,

Dave

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *