|
PureBytes Links
Trading Reference Links
|
On the surface, a workable solution, however; you may be assuming that SC and TS
will co-exist on the same system - an assumption I would not make.
When I was running SC21 and upgraded to SC3 (after doing a full backup), I
instructed it to install to a new structure in \Omega30. The install was
completed in \Omega30, however my \Omega21 was totally trashed. In order to run
both, I had to 1) restore \Omega21, 2) identify all OS directory SC21 files
changed by the SC3 install, and 3) use a batch file to swap nearly a dozen dll
and ini files in the OS directories. FWIW, I've read that installing SC disables
Analyst, Omega's entry level product. Unless you obtain good evidence that
installing TS will not do in SC, I would plan on installing TS to a different
sytem than the one on which you are running SC -or- on a different operating
system partition. I'm certain both SC5 and TS5 - you'll undoubtably need both
for ELA compatibility - will make extensive use of the registry and you can't
swap it around like you can swap ini files.
Earl
-----Original Message-----
From: greene@xxxxxxxxxxxxxxx <greene@xxxxxxxxxxxxxxx>
To: Frederick H. <srqblue@xxxxxxxx>
Cc: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Date: Thursday, February 26, 1998 4:25 PM
Subject: Security Block Issues
>can input (or develop) your systems, indicators, whatever in TS - and
>then import them into SC. Which would eliminate day-to-day problems and
>concerns about passwords, dongles and the like (they're something I'd
>worry about both on the road - and at home - when I'm home I usually run
|