Related Files

There are a number of files in the different subdirectory of the XFolder installation directory that might be useful to you:

BOOTMGR.CMD is new with V0.83. This script was supplied by Duane A. Chamblee and will automatically add all the current BootManager choices to the XFolder user-reboot actions for XShutdown. This is done by modifying the XFolder keys in OS2.INI directly. No guarantee that this will actually work on your system!
CROBJxxx.CMD (with xxx being a three-digit language code, as described in National Language Support) are used by XFolder to create the default Configuration Folders. These are just plain REXX scripts which create a number of objects on your desktop.
These scripts are called both after XFolder has been installed (after the first WPS restart) and also whenever XFolder fails to locate its Configuration Folder.
You may modify these scripts to have a different default configuration created. However, you should be very careful in changing the various object settings, especially the OBJECTID keywords, because XFolder might rely on these.
NEWOBJ.CMD was used in previous versions of XFolder (before 0.52) to create objects. This is now done with templates, but this script is still included, for those who got used to it.
It needs the following parameters on the command line:
```
newobj <wpsclass> <name>
```
It will create a new instance of <wpsclass> with the title <name> in the current directory. Please see the "WPS Classes" page for a list of WPS classes. Not all of these make sense when creating objects though.
Here's an example:
```
newobj WPFolder New_Folder
```
will create a new folder called "New_Folder" in the current directory.
Note: Starting with V0.41, XFolder can also create objects from templates. This has the advantage that you can create objects with certain default settings (namely for folders).
NETSCDDE.EXE (The Netscape DDE Interface): see the separate chapter in this documentation.
REPCLASS.EXE is used by the installation script to register the XFolder class and replace WPFolder with it. It needs the following parameters on the command line:
```
repclass <oldclass> <replacewithclass> [<dllname>]
```
<oldclass> is the WPS class that you wish to replace. This is case-sensitive.
<replacewithclass> is the new WPS class that you wish to register and at the same time replace <oldclass> with. This is also case-sensitive.
<dllname> is the dynamic link library (DLL) that contains <replacewithclass>. If the DLL is not on the LIBPATH (as with XFolder), you will need to specify the full path.
If <dllname> is omitted, <replacewithclass> will be de-registered and removed from the replacement list for <oldclass>.
Example for XFolder itself: the classes to be replaced are WPFolder, WPDisk, and WPSystem, the new XFolder classes are XFolder, XFldDisk, and XFldSystem, which all reside in the XFLDR.DLL file.
All action performed with this program will only have an effect after rebooting or restarting the WPS with WPSRESET.EXE (see below).
Warning: Do not attempt to replace single XFolder classes or to undo a certain XFolder replacement manually. The XFolder classes are designed to work together and are depend on each other. If you register / deregister not all of them, the WPS might hang itself up already at boot-up. For registering or deregistering of the XFolder classes, always use the install script.
SOUNDxxx.CMD (with xxx being a three-digit language code, as described in National Language Support) must be started by you to activate the new XFolder system sounds. These little scripts will write a few language-dependent strings into the INI files of the OS/2 Multimedia Subsystem (MMPM/2), which will then be visible in the OS/2 "Sound" object. Only if XFolder finds these, it will play system sounds at all.
SOUNDOFF.CMD will turn sounds off again by deleting the respective entries from the MMPM/2 INI files. XFolder will then stop playing system sounds.
Note: The SOUND files assume that that your MMPM/2 directory is \MMOS2 on your boot drive. If it is not, you must alter the files yourself.
TREESIZE.EXE is used by the new default menu item of the same name and displays the disk usage of a folder and all its subfolders in a Tree view. If Treesize is started with a directory name as a parameter, this directory is displayed, or the current directory otherwise.
After Treesize is done with its calculations, you may drag and drop new WPS folders onto the main window, whose size will be calculated then also.
Treesize offers you some settings using context menus.
All settings are saved when Treesize is closed.
WPSRESET.EXE can restart your WPS without rebooting your computer altogether (see the "Restart WPS" page for details). It is now (V0.71) only used by the install script any more, while XFolder does its own WPS restarting internally. In order to prevent accidental execution, WPSRESET.EXE must be started with a "-D" parameter on the command line. (I have forgotten what "-D" stands for, but I'm sure it used to have a meaning.)
XHELP.CMD is a powerful REXX script which can display language-dependent messages, both in HTML and simple ASCII format. It was taken out of the "OS/2 CommandPak" by the same author, also available at my homepage. In that package, you will find extensive documentation of xhelp.
In XFolder's context, xhelp is only used by the install program and has no further function.
XSHUTDWN.EXE: see the respective separate page.
All the other .CMD files in the XFolder directory are REXX scripts used by the default XFolder configuration to quickly set certain folder settings (they can be found in the "Quick Settings" submenu). The scripts are very similar, varying only in the settings that are applied to a folder. ALWSSORT.CMD is commented, so you can look through it and see what it is doing. Copy ALWSSORT.CMD to some other filename and change the settings that are applied to the folder in order to apply customized settings to folders. See the "WPFolder Setup Strings" page for a list of applicable settings.