|
General FileBoss has a rich set of command line options that can be used to tailor how the program starts and acts. Most users will never need any of these and fewer still will ever use more than just a few. But when needed they can be very useful.
Normally command line options are entered in the Properties dialog of a shortcut to a program such as FileBoss. (To display the Properties Dialog, right-click on the Program's Icon on your desktop and select 'Properties…' from the menu.)
Note: Modifying start modes at runtime Hold down the Shift and Control keys while starting FileBoss to mimic starting the program for the first time.
Hold down the Control key to prevent the default explorer view from loading. (Note that this does not override any command line arguments.) This can be helpful if the default Explore View is set to a problem network connection and the operating system takes a lengthy time to tell FileBoss that it is not available, i.e. FileBoss waits too long for the folder to become available for browsing.
Restarting Previously Opened Windows /winlist "X:\path\<File containing the WindowsList>" Specifies a file containing a list of windows (i.e. FileBoss Virtual Folders and/or folders to explore) to open when FileBoss first starts. These files can only be created by using the 'File | Save View List...' command from the main menu. e.g.: /winlist "c:\My Documents\Graphics.fbwins" Note that by default when FileBoss first starts it reloads the windows that were open when it last closed (they are stored in a file named FileBoss.fbwins). This behaviour can be changed using the 'Options | Program Options...' command and then selecting the Startup Options pane. Specifying a Defined Virtual Folder to be Loaded on Startup "X:\path\<Virtual Folder definition file>" The name on the command line - enclosed in quotation marks if it contains any embedded spaces. The specified file must be a valid Virtual Folder or Virtual Folder definition file. (By default these files end with the .fbfileset extension.) e.g.: "C:\My Documents\FileBoss\Drive C.fbfilest" If the specified path points to folder rather than a file, that folder will be opened in Explorer view. See Specifying a start folder for Explorer View below. Use Current FileBoss Instance if Available /o Tells FileBoss that if there already is an instance of FileBoss open to send control to that FileBoss instead of opening itself. If the path and folder is also one of the parameters that folder will be opened as a new View in the current instance of FileBoss. If no other instance of FileBoss is available, FileBoss will open just as if this parameter had not been given. This parameter is normally set by FileBoss itself in the registry entries that control its integration with Windows. Specifying a Folder to Open in Explore View "X:\path\<Folder Name>" The name on the command line - enclosed in quotation marks if it contains any embedded spaces. The specified path must point to a folder, not to a file. e.g.: "C:\My Documents\FileBoss" If the specified path points to folder rather than a file FileBoss will attempt to open folder in Explore View. See Specifying a Defined Virtual Folder to be Loaded on Startup above. Forcing a Explorer View to be Displayed on Startup /explore Forces a Explorer view to be displayed. This is normally FileBoss' default behavior, but if a Virtual Folder has been specified on the command line (see the command line option immediately above) no Explorer View will be displayed unless this parameter is specified. See also the /expfolder option below. Preventing Explorer View being Displayed on Startup /noexplore Prevents Explorer view from being displayed when FileBoss starts up. This switch over ride the /explore and /expfolder switches if they appear on the same command line. See also the /expfolder option below. Specifying the Initial Folder for Explorer View /expfolder "X:\path\Explorer start folder" Specifies the startup Folder for an Explorer View. If this is not specified the startup folder will be set according to the settings in the ' Explorer HIDD_OPTIONS_RECON' pane of the options dialog - use the Options | Program Options... command from the main menu. (The default option is to use the last folder.) e.g.: /expfolder "C:\Program Files" Specifying Different Options and Settings /optionsfile "X:\path\options file" This option tells FileBoss to load and save its options and settings from the specified file rather than the one it normally uses. Most of the options and settings used by FileBoss are stored in a file rather than in the registry. Normally the file name is fileboss.fbopts, but where the file is located depends on which version of Windows is installed and how the System Administrator has configured windows. e.g.: /optionsfile "C:\My Documents\FileBoss\FileBoss Options Safe.fbopts" Hide the Splash Screen at Startup /nosplash Prevents the splash screen from being displayed when FileBoss starts. This can also be set in the General panel of the Options dialog. (Use the Options | Program Options... command from the main menu.) Using Default Options /nooptions This will start FileBoss as if it was the first time after installation: no options or settings will be loaded. When you exit FileBoss and this setting has been specified, FileBoss will ask you if you want to save the current options and settings or not. Answer 'No' if you don't want your old options file overwritten. Another way of starting FileBoss in 'No Options' mode is to hold down the Ctrl and Shift keys while the program starts. This is exactly the same as specifying the /nooptions command line argument. Suppressing Auto Help /autohelpoff Prevents all balloon help from being displayed for the current session of FileBoss only (i.e. no permanent changes are made to any options or settings). Note that only balloons providing help is turned off – balloons that point out critical errors or invalid entries in dialogs will still be displayed. Command String /cmdbar "command string" /commandbar "command string" /commands "command string" Executes the commands in "command string" just as if they had been entered in the Command Bar. Note that as in the Command Bar commands can be chained together e.g.: /cmdbar "<curdir> <> show *.bak | *.tmp <> select *.bak | *.tmp <> recycle sel" See The Command Bar for more information about what commands can be used. In fact testing the command string in the command bar can make using them on the command line error free.
Advanced Options FileBoss has a rich set of command line options that can be used to tailor how the program starts and acts. Most users will never need any of these and fewer still will ever use more than just a few. But when needed they can be very useful. Alternate Registry Key /altregkey The default registry key for FileBoss is The Utility Factory\FileBoss. But when the this option is specified FileBoss with use The Utility Factory\FileBoss Alternate. This alternate registration key will also be used when the ESC key is held down while FileBoss starts. Removing File Type Associations /r_types Removes any associations to present linking FileBoss to its standard file types No windows are displayed and no messages are given. This parameter can only be used in conjunction with /r_ctx and /r_mainkeys, all other parameters will be ignored. Removing Window Integration Registry Entries /r_ctx Removes all registry entries that control FileBoss's integration into the Windows Shell, i.e. the registry entries that list FileBoss on the system context menus and/or make FileBoss the default explore application for File Folders. No windows are displayed and no messages are given. This parameter can only be used in conjunction with /r_types and /r_mainkeys, all other parameters will be ignored. Removing Main Options Keys /r_mainkeys Removes FileBoss's main registry keys where options and settings are stored. And then exits the program. No windows are displayed and no messages are given. This parameter can only be used in conjunction with /r_ctx and /r_types, all other parameters will be ignored. Force New Instance of FileBoss /forcenewinstance Forces FileBoss to start a new instance even if the user has set the option to only allow one instance of FileBoss. e.g.: /forcenewinstance Ref: Command_Line_Options | |
|
Have a question about FileBoss or anything else? If this page didn't have what you are looking for or you want to know more just ask us. Please! |
|


