If Wise Package Studio Professional version is installed locally on an XP box and the network is disconnected, Wise Package Studio cannot find a configured repository when the application is launched.
When the network connection is disabled XP cannot resolve a local UNC path for some reason.
For example, if the machine name is XPPRO, then the share point is \\ XPPRO\SHARE POINT. Through Windows Explorer c:\wise share point can be found with or without the network connection, but \\xppro\wise share point can not if the network is not connected.
The problem is that laptops user will find the product does not work when undocked (or less frequently, desktop users will find it doesn't work if disconnected from the network).
When the network connection is disabled, even though our product doesn't rely on the network, XP cannot resolve a local UNC path for some reason. Because of this, and since WPS creates a UNC path in the config.ini AND in a few registry locations (SharePoint and FieldDataSharePoint keys), WPS can't find the Share Point.
Symantec can confirm that you will be able to launch Wise Package Studio by changing the following registry keys and section of the config.ini file, however some other functionality within Wise Package Studio may not work correctly. The reason for this is Wise Package Studio Professional version was intended to be used in a client server environment, and has only been tested to be used as designed.
To have a server means it is connected to a network.
WPS 6 Pro: Update these two registry keys to use non-UNC pathing: