|
PureBytes Links
Trading Reference Links
|
Now I have Tradestation running again and I think the solution could be
interesting to share with others.
I never received the SP5 disk from Omega, so I thought I would have to fix
the problem with Tradestation not starting by myself. Others did seem to
have the same problem (I know of at least three). I decided the problem to
be in the registry and searched the registry for Omega definitions. It is
absolutley full of definitions from Omega, they are abusing it really.
Anyhow, this is what have happened to me: I have moved my computer from
being a Windows 98 computer to a Windows XP computer through an upgrade. I
have at the same time moved from running FAT-files to NTFS files. I have
installed the omega developer support kit. Thus I have two directories under
program files that are named omega research... (the Tradestation and the
developer support directories). Before the move, the omega research
directory had the DOS short name "OMEGAR~1" but now after the moves the
omega research development directory has that dos name, and the omega
research main directory is named "OMEGAR~2".
Omega does have a couple of hundred of file path definitions set up in the
registry, and many of them utilises long names. But not all... By some
reason, Omega utilises sometimes dos short names "PROGRA~1" "OMEGAR~1" and
so on. This caused my problem. To the surface everything was ok, but beneath
XP, deep in old dos naming rules, "OMEGAR~1" had now been changed to
"OMEGAR~2". This does not matter to Omegas program in many places, but
curiously enough in some of them.
>From the net I found a very good search and replace utility for the
registry, and I changed all "OMEGAR~1" to "OMEGAR~2" and now it seems to
work again.
> -----Original Message-----
> From: Bengtsson, Mats [mailto:mats.bengtsson@xxxxxxxx]
> Sent: den 9 augusti 2002 13:29
> To: Ryugan Mizuta; omega-list@xxxxxxxxxx
> Subject: RE: Need TS2000i help?
>
>
> I have exactly the same problem and sent a similar question
> two weeks ago. A summary of the responses is as follows:
>
> 1. This does unfortunately happen now and then, the problem
> lies in the registry 2. No one knows, or at least dares to
> suggest, a way to get past this trying to register anything
> in the registry 3. The only known (or at least suggested)
> solution is a reinstall 4. The reinstall can be done from the
> service pack CD 3, but if you got the chance to wait till you
> get an ordered CD 5, take that solution instead.
>
> I am currently waiting for a sp5 cd, since it is suggested
> that the chance not losing settings is higher if installing
> from that Cd instead of from sp3 cd.
>
> > -----Original Message-----
> > From: Ryugan Mizuta [mailto:trend456@xxxxxxxxxxx]
> > Sent: den 9 augusti 2002 09:01
> > To: omega-list@xxxxxxxxxx
> > Subject: Need TS2000i help?
> >
> >
> >
> > I've got some problems using the TS2000i and would like to
> > know if anybody
> > knows the solution to this problem. Everytime I try to open
> > a chart in the
> > workspace I get a message that says,"Failed to create object.
> > Make sure the
> > object is entered in the system registry." This thing pops up
> > and I can
> > never get to the charts. Would anybody kindly explain to me
> > the solution to
> > this problem.
> >
> > Thank you.
> >
> >
> >
>
>
> This message contains information that may be privileged or
> confidential and is the property of the Cap Gemini Ernst &
> Young Group. It is intended only for the person to whom it is
> addressed. If you are not the intended recipient, you are not
> authorized to read, print, retain, copy, disseminate,
> distribute, or use this message or any part thereof. If you
> receive this message in error, please notify the sender
> immediately and delete all copies of this message.
>
This message contains information that may be privileged or confidential and is the property of the Cap Gemini Ernst & Young Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
|