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.
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).
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.
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.
In XFolder's context, xhelp is only used by the install program and has no further function.