|
PureBytes Links
Trading Reference Links
|
I am amazed this problem is cropping up in Win/NT.
Everyone said that was the only bulletproof O/S to run TSi2000 !!
I have not experienced the same error under Win98SE.
Anyone care to indicate exactly WHEN this error occurs.....realtime,
backtesting, etc.
Also, which symbols are active....etc.
> -----Original Message-----
> From: hans esser [mailto:he96@xxxxxxxxxxxxxx]
> Sent: Thursday, October 28, 1999 1:13 PM
> To: Omega List
> Subject: Re: TS2K and WIndows NT Fatal Error
>
>
>
> > Someone e-mailed me that Omega was starting to work on some of these
> > significant errors generated by TS 2000. These problems include access
> > violations, the error you reported, plus TS 2000 halts Windows NT
> > frequently for me. Apparently these problems only occur for a few TS
> > 2000 users,
>
> THERE AINT ANY MORE !!!!!! wahhhhhhhh
>
> sorry couldnt resist - will shut up for rest of day..... promise.......
>
> ahhhhhh BTW: TS_BT_HINDSIGHT_CHEATER is STILL long the S&P on
> that famous system and shows a open profit of near some 60 bps......
> unfortunately I SAW it getting stopped and it was a 16bps looser
> - currently a
> small difference of some 75 bps.....GO FIGURE !...... wonder what the
> PERFORMANCE GUESSING REPORT is really worth.......
>
> rgds hans
>
> PS: ......uhhhhhh what is that OM doing at my front door ????
>
>
>
> > so Omega seems to have given a low priority to fixing them.
> > Perhaps Omega has concluded, as the Omega Man says, it's easier
> to tell us
> > to use another product.
> >
> > ----- Original Message -----
> > From: Phil Sih
> > To: omega-list@xxxxxxxxxx
> > Sent: Thursday, October 28, 1999 3:50 AM
> > Subject: TS2K and WIndows NT Fatal Error
> >
> >
> > TS2K running under Windows NT draws the following fatal error
> any time any
> > symbol collection template is enabled. Has anyone else experienced this
> > and/or does anyone have any insight as to the cause and fix?
> >
> > Error message as follows:
> >
> > a critical error occured in GlobalServer. Shutting down. The instruction
> > at 0x5f402181 referenced memory at 0x00000004. The memory could not be
> > "read". Click OK to terminate application.
> >
> >
> >
>
>
>
|