We've had to re-install our Amaya software after our little workhorse finally broke down. Doing so has proven a bit troublesome however. Currently I've got a Windows XP computer freshly done with all Window's updates (and nothing else installed).
First I installed the dongle's drivers (first step when the installation CD activates), then updated to the latest Sentinel drivers. Rebooting each time.
Then I installed the software, I now get a single error when installing the Amaya OS saying it can't find the network (which is fine as it continues anyway). Everything continues to install fine, and after reboot, I can start Design Shop Pro+, ENS, and the Amaya OSv10.
Now I had OSv10 check for updates, install those (only 5 minutes worth). Started it back up and is still fine (haven't gotten to connecting the machines). Then I run the "establish amaya network compatibility" as requested, and OSv10 will not start. Trying to run it just gives me an hourglass next to the mouse and makes "explorer.exe" use a lot more memory. It can sit like this for a long time, though I can end the process and restart it to get things going again.
My guess is the "establish amaya network compatibility" has been the culprit on the other 3 machines I've tried installing this software on, as I did noticed it worked if I had NOT run that shortcut. For reference, the 1st machine I tried this with, I DID have the machines hooked when running this.
So is there a way to reverse this process? Something in the registry that get's removed? Or am I totally missing what's messing me up? Any and all help appreciated!
First I installed the dongle's drivers (first step when the installation CD activates), then updated to the latest Sentinel drivers. Rebooting each time.
Then I installed the software, I now get a single error when installing the Amaya OS saying it can't find the network (which is fine as it continues anyway). Everything continues to install fine, and after reboot, I can start Design Shop Pro+, ENS, and the Amaya OSv10.
Now I had OSv10 check for updates, install those (only 5 minutes worth). Started it back up and is still fine (haven't gotten to connecting the machines). Then I run the "establish amaya network compatibility" as requested, and OSv10 will not start. Trying to run it just gives me an hourglass next to the mouse and makes "explorer.exe" use a lot more memory. It can sit like this for a long time, though I can end the process and restart it to get things going again.
My guess is the "establish amaya network compatibility" has been the culprit on the other 3 machines I've tried installing this software on, as I did noticed it worked if I had NOT run that shortcut. For reference, the 1st machine I tried this with, I DID have the machines hooked when running this.
So is there a way to reverse this process? Something in the registry that get's removed? Or am I totally missing what's messing me up? Any and all help appreciated!
Comment