Hi Clutch:
The SBuilderX "active"
SBuilder.ini (a manually editable, pure ASCII text file with a
*.ini extension) is always located in the main root install folder of SBuilder.
SBuilderX project
*.SBP files are by default located in the
[SBuilderX install path]\Tools sub-folder.
IMHO, it is a good idea to always save an extra set of data for one's projects in the form of a
exported "
*.SBX" file,
which preferably might be named identically to the *.SBP project name.
FYI: A '
exported' *.SBX is a manually editable, pure ASCII text file with a *.SBX extension containing all the pertinent info regarding the project including
ex: most if not all vertex coordinate data for poly-lines and/or polygons.
SBuilderX project
*.SBX files are by default located in the
[SBuilderX install path]\Tools sub-folder.
NOTE: Regardless of the path location of one's *.SBP project file at the time it was last worked on, one should be able to load it into SBuilderX and "
Export" a SBX file, then manually edit the paths in the SBX file:
SBuilderX Menu > File > Export > SBuilder SBX...
When the resulting *.SBX file is "
Imported" into an empty SBuilder project (aka a "
SBP" file), the paths should all be pointing to the needed folder and file locations for pertinent source and work data:
SBuilderX Menu > File > Import SBuilder SBX...
[
EDITED]
PS: If the C: drive is getting too full, you may wish to install Hermann Schinagl's excellent "
Link Shell Extension" utility into Windows Explorer:
http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html
On Windows XP / Vista / Win 7 default NTFS file system hard drives, Link Shell Extension allows one to designate a remote folder location as a "Link Source" to '
join' with a "Link Target" folder.
FYI:
Symbolic Link Clone: "Clones are copies of a folder tree from a source location recreated at the destination location, however the files within the new folder tree are Hardlinks or Symbolic Links to the respective files in the source folder tree."
"
HardLink or Symbolic Link Clones are useful if you need to replicate a folder tree at a different location. The disk space required is minimal because the new structure consists entirely of NTFS directory entries with no real amount of actual data storage."
"
With Windows Vista and Windows7/8 this cloning process is also available with Symbolic Links instead of Hardlinks."
http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html#hardlinkclones
For example, suppose your installed SBuilderX
C:\[SBuilderX install path]\Tools folder cannot accommodate large active project sizes and/or storage of older archived projects because your C: drive is too full, but there is a large free storage capacity available on your P: drive.
A "
Symbolic Link" between the 2 folders could 'append' or 'graft' more storage onto the target
C:\[SBuilderX install path]\Tools folder.
After Link Shell Extension is installed in Windows Explorer, one could:
1.) Browse to
ex:
P:\[SBuilderX install path]\Tools
a.) Right-click on that \Tools sub-folder name (context menu opens)
b.) In that \Tools sub-folder context menu, click "
Pick Link Source"
2.) Browse to
ex:
C:\[SBuilderX install path]\Tools
a.) Right-click on that \Tools sub-folder name (context menu opens)
b.) In that \Tools sub-folder context menu, click "
Drop As", ... and select "
Symbolic Link Clone"
NOTE: The above Links would persist until manually deleted as described on the authors web page.
Alternatively, one may wish to use the excellent Mark Russinovich / Windows Sysinternals c/o MS TechNet "
Junction" utility in a batch file to
ex:
1.) Create a (temporary) "Junction Link" between specified folder paths
a.) Run SBuilderX
b.) Exit SBuilderX
NOTE: "
Using Junction" explains that the "–d switch can delete a junction, so with a "Junction -d" [path] command:
c.) Remove the (temporary) "Junction Link" between specified folder paths when the batch file exits
2.) Delete a non-temporary "Junction Link" between specified folder paths outside a batch file from the command prompt
http://technet.microsoft.com/en-us/sysinternals/bb896768
[
END_EDIT]
BONUS: This technology may allow greater control over enabling FSX scenery (
and aircraft ?) package installs to
also run in Prepar3D (aka "P3D")
Hope these ideas might help "re-activate" and allow resumed work with your existing SBuilderX projects.
GaryGB
