Hi Brian,

I am migrating my installation of SW to a new machine. I'm guessing I will need a new license key; but beyond that, what is the best way to migrate all my existing settings -- sites, templates, destinations, etc. -- so they will be available on the new machine? Are there specific folders and files I can just copy over to the new machine?

Thanks,
Dave

Hi Dave,

Good question. Depending on what features you have used in setting up your recordings, you should take over the following folders from the screenwatch installation folder *after* you have installed the new copy:

menu
site
cdrom
template

These folders are where all the things you define and customize are kept.

Also, you will need a new license key when you change over. Just email to sales@optx.com with your activation requests (In your case for both the full use and live webcasting license), and someone will send your codes back for that machine.

Hope that helps,
OPTX Support

Brian,

Wanted to give you an update on my experience with the migration process. Got the live webcasting working, but only after the following:

1. First, I got the "error detected when recording your job" message as discussed in another recent post. There does appear to be "phony network connections" on my machine so I selected remote computer and "localhost" per your instructions.

2. Not related to SW, but I was not able to successfully install the Osprey 100 video capture card I intended to use. Some sort of motherboard-based PCI conflicts, even after updating the BIOS. I'm currently capturing successfully via the Firewire port.

3. Finally, even though I copied over all the directories you specified above, I was not able to successfully login to the live media server until I created a new Live Destination for the project. I used the same Destination info as the old one, but apparently something did not quite carry over completely there.

Hope this helps,
Dave

Hi Dave,

Thanks for the notes. I was debating on whether to go into detail about pulling over the previous settings for the actual recording project. I didn't do this because the xml file that contains your live site etc, also refers to devices specific to your machine.

In the event that your audio card was different, or something like that, I felt I would lead you down a path of not knowing what was wrong.

Basically, ScreenWatch, every time you save a project remembers the settings by storing them in a file in the lib folder called blank.swj. That way each time you start up, we read in blank.swj and it has all of your last set settings.

I think this is why you had to create the live destination etc.

I would continue to look for some sort of analog card to capture your video. Firewire, if the CPU goes to 100% for any length of time (and it will), will drop samples. This will shorten your video file time length as compared to your screenwatch file time length.

Firewire seems to use alot of cpu to do its work. You might want to try and hour long recording using your firewire and the check out the results. Seek towards the end and make sure it will stay in sync for you.

Thanks,
Brian