[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: it ain't ready yet



PureBytes Links

Trading Reference Links

Here is what I have experienced with SP4.  I have both patches installed and
am anxiously awaiting the new SP4.  I have W95 on P400 with 192mb and use PC
Quote as a data provider.

SP4 seems to suffer from the same problem as previous service packs have,
and that is it does not like workspaces created in previous SPs.  So we
really need to create new workspaces under SP4 and that will solve a few
problems (a pain).  Another problem I have noticed is that if you shutdown
TS and restart it WITHOUT restarting Windows first you will most likely
encounter the Windows blue screen of death (a royal pain).  These are
completely unacceptable issues that I understand will be fixed with the next
SP4.

I have also experienced the same problem with workspaces opening as a window
instead of in full screen mode as they were saved.  But I had this problem
in SP3 as well, but not in SP2...???

However, I have NOT experienced any of the other problems described below
such as text being slow to draw, mouse pointer being slow, drawing objects
slow or the maximizing/minimizing function being slow.  Those all seem to
work correctly.

Also, make sure you restart Windows after installing SP4 or any of the
patches.  The installation may not prompt you to do that.

Bob




-----Original Message-----
From: ribau@xxxxxxxxxxxxx <ribau@xxxxxxxxxxxxx>
To: omega-list@xxxxxxxxxx <omega-list@xxxxxxxxxx>
Date: Thursday, January 06, 2000 11:43 AM
Subject: Re: it ain't ready yet


>>>Good afternoon,
>>>
>>>My position in Omega Research is the quality assurance test lead for the
>>>Global Server.  I was hoping I would be able to ascertain the exact
nature
>>>of the problem which you have reported.  The message sent by the data
>>>manager 'Error, cannot find receiver on any comm port' is one generated
by
>>>the Signal/Bmi Data manager indicating that the connection to the
receiver
>>>was lost.  This would in turn cause or program to stop updating.  We
should,
>>>however, reestablish the connection as soon as the data manger
reestablishes
>>>its connection with the signal receiver.
>>>
>>>Was your experience different? If you shut the server down and restarted,
>>>did it connect properly to the data manager?  Any assistance you are able
to
>>>offer would be appreciated.  Thank you.
>>>
>>>Giovanni Pugliese
>>>QA Server Test Lead
>>>Omega Research, Inc.
>
>I gave up on the program at that point and simply left it running. It never
>reestablished the connection. I finally shut it down late last evening and
>rebooted the machine...I restarted TS2Ki and it connected. I didn't reset
>the BMI cable box and it never showed a disruption of data collection. The
>bad packets count is very low.
>
>Sometimes the DataManager window reports that Reception and Password are
>"OK", but most of the time it reports Reception and Password as "NONE." I
>often get the error message, "Data Manager is not getting enough time to
>perform its functions..." I don't think you can separate responsibility for
>this into Signal/BMI vs Omega. Omega made the decision to use the
>Rent-a-Server approach and must accept responsibility for its inadequate
>performance.
>
>There are of course, many other shortcomings in the program. Every morning
>when I boot TS2Ki I must resize Tracking Center and Quote Monitor because
>they open as a window rather than full screen as I left them. I must also
>rearrange the charts on each worksheet because they slip to the side of the
>worksheet (four charts per worksheet). This must be redone every time the
>program crashes and is restarted. The NewsMonitor sometimes runs, most
>often not.
>
>There are still major performance problems with TS2Ki SP4. The mouse
>pointer is sluggish when the mouse is moved. Drawn objects like horizontal
>lines and trend lines, are slow to draw and slow to move after drawing.
>Changing between worksheets is very slow. Charts maximize/minimize slowly,
>letters form slowly onscreen as I type.
>
>You guys have a long way to go. If Omega would come clean with their
>customers you would get the help of many people on the Omega List who have
>considerable knowledge about computers and trading, and who want TS2Ki to
>be successful. A good place to start would be an admission that TS2Ki is
>currently unreliable for real time trading.
>
>Many customers, such as myself, feel that Omega has forced us to beta test
>this software because it was not properly developed. Most of us are
>traders, not software engineers, we rely on Omega products for our
>livelihood and resent the hundreds of hours we have wasted over the past 10
>months with this very buggy software and Omega's apparent lack of concern
>for long time customers.
>
>I hope you don't mind my posting this to the Omega List. I have found the
>list members to be very helpful with TS2Ki problems and think we all
>deserve a more open approach.
>
>machines used:
>   500MHz PIII w/ 256Mb, Matrox G400 w/ 32Mb
>   450MHz PII w/ 256Mb, Diamond V770 w/ 32Mb
>   266MHz PII w/ 128Mb, generic video card
>BMI cable
>Win98se
>
>
>>>-----Original Message-----
>>>From: ribau@xxxxxxxxxxxxx [mailto:ribau@xxxxxxxxxxxxx]
>>>Sent: Wednesday, January 05, 2000 2:37 PM
>>>To: omega-list@xxxxxxxxxx
>>>Subject: Re: it ain't ready yet
>>>
>>>I did apply the SP4fix from Omega's web site. They need to recall this
one
>>>as well since it's obviously less stable than SP3 was.
>>>
>>>Guess what it just did...I received a DataManager Notification, "Error,
>>>Cannot find Receiver on any comm port." It simply stopped collecting data
>>>altogether in the middle of the trading session and that required another
>>>reboot. The receiver still shows data coming in, TS2Ki just stopped
seeing
>>>it.
>>>
>>>Omega has four ads in today's IBD. Why don't they stop wasting money
>>>promoting software that doesn't work and spend some of that money on
>>>programmers who can program? If I didn't have three machines running real
>>>time, I sure wouldn't want to have this crap running during the day.
>
>