Re: Lost Server Definition

Some problems here, too.

Just installed SP3 over (not so) fresh install on XP.

I've variously, over the last few weeks, installed/uninstalled WDSC, as
well as WDT (using the Win98 compatibility approach).

I decided to go back to WDSC, cleaned the registry with RegClean RegCleaner
(to remove vestiges of WDT400).

1. When I enter my system name (MAGIC), it makes that the CODE server name
by default. It did not allow me to change that to MAGICBA, as I wanted to
do. (I've had that server name from a STRCODE on MAGIC - not appearing in
the server list, now, tho'.)

2. I then entered the IP address (192.168.1.xxx) and WAS able to enter
MAGICBA, although it had put in AS400A. Got some beeps while doing it, however.

3. I then worked for awhile, then ended CPO and CODE Edit, then shutdown
all servers from the system tray icon. This morning I looked
at  Properties, and AS400A was now in the CODE server name. Changed it to
MAGICBA, and I was able to use it.

4. This time it appears that MAGICBA is sticking.

Is there stuff to clean out of the registry? Like server settings? Or are
they stored in some common files area under Program Files? How do I
completely clean this thing off a computer, in order to start virgin?

>

>Sam,
>
>We believe that this problem is fixed in service pack 3 for WDSc (released
>on Friday.) Since we have not been able to reproduce the problem yet we
>cannot be 100% sure. Please apply the service pack and let us know if you
>still have this problem.
>