When you clone a machine, the unique ID code that is associated with each client is also cloned, making it no longer unique. This causes confusion to Smedge because it thinks that every client that connects is the same client.

To solve the problem on Smedge #33 or later:

1. Open the Smedge INI file:
   C:\Documents and Settings\All Users\Application Data\Überware\Smedge.ini
2. Remove the line that says UID = XXXX

To solve the problem on Smedge #32 or earlier:

1. Open the registry editor and navigate to the key:
   HKEY_LOCAL_MACHINE\Software\Überware\Smedge\Host\
2. Delete the value UID

Smedge will generate a new ID code for the client.

Note: This will make Smedge unable to validate the license code on this client. However, as long as at least one client on your network is left untouched, the license code should automatically re-propogate to every client as it connects. If you have license problems, please contact license@uberware.net.

By default, Smedge uses a UDP broadcast sytem to locate the machine acting as the server. Often, routers block most UDP broadcast packets from travelling between subnets, so Smedge clients on one subnet will not be able to find clients on the other. There are two ways to work around this.

1. If you have a router that is configurable, you can configure the router to allow UDP broadcasts on the Smedge UDP server location port. By default, this port is 4566.
2. You can use a dedicated server, and bypass the whole UDP server location mechanism. Because all other Smedge communication is direct TCP connections, you should have no problems. For more information on setting up a dedicated server, see Specifying a dedicated server in the online manual.

While Smedge may indeed suck sometimes, this is actually a fixable problem. When under heavy processor use, Windows may not be scheduling processor time to the GUI. However, you can set Smedge to launch the render processes at a lower priority. This will keep Smedge happy, because the GUI thread will get priority for the very little processor time it needs to keep itself running over the spawned child processes.

You can find more information about child process priority in the Smedge Options section of the online manual.

I am looking at the Windows process priority API to determine if there is a better solution, but this seems to be the best at this time. This problem only seems to affect certain combinations of hardware and Windows versions. If you experience problems like this, please contact suport@uberware.net. Thank you.