|
PureBytes Links
Trading Reference Links
|
John,
Yes I have tons of experience with DTN Sat/TS2ki with Win2000 and XP
and all the problems you are having. Yes that is very fixable. Sure
I can do it easily. I also remember you demanding I be pitched off
the list.
I love it when the wheel comes around. You have made my day.
Jimmy Snowden
Monday, May 17, 2004, 1:16:02 PM, you wrote:
Jb> Anyone else using Esignal as a datafeed for TS2000i, especially using a Win XP operating system, I'd like to get your suggestions:
Jb> I switched over from DTN satellite about 6 months ago, was running WIN2000, everything working great (except DTN data outages which were their fault).
Jb> About 2 weeks ago I started getting these blue screens of death, spontaneous crashes. I have had some virus attacks, which I cleaned up, inspected registry, ran remote web based anti-virus
Jb> progams, ran 2 local anti-virus programs, etc.
Jb> I have a system with 512 meg of RAM, WIN2000, Athlon 1600 (AMD), 30 gig HD, broadband cable modem feed through a router.
Jb> Switched out harddrives (to eliminate the virus damage possibility) with a new one and loaded Windows XP, went to MS update site and loaded all updates. Then fresh load of TS2000i, upgraded
Jb> through service packs to version 5, (822), as I have done many times before. Using Esignal 7.5 ver. at request of Esignal techs --- less buggy they said.
Jb> I admit I did save the complete server folder from previous TS2000i and copied it over (although I tested copying in the new, bare bones server folder from new almost empty setup in and it even
Jb> crashed regularly).
Jb> Now Windows XP is crashing every 15 min to 60 min., with various messages like:
Jb> 1) cannot find ntfs.sys (I did a restore from Win XP CD),
Jb> 2) Bad Pool Caller,
Jb> 3) Video driver failed to initialize (tried replacing video card and with newer driver)
Jb> 4) Cannot find Win32K.sys, restored from Win XP CD
Jb> 5) The instruction at 0x73dd1351 referenced memory ar 0x00000004. The memory could not be read. Click OK to terminate.
Jb> Updated (flashed) my motherboard bios, no help. Turned off video shadowing in the bios - - - no change.
Jb> Have new RAM ordered, will replace next week and see if RAM is the prob.
Jb> Thought that if this is a hardware problem, maybe I ought to load TS2000i and Esignal on another computer - - - choose a rock solid DELL box I have. Hmmmmmm, a bit more stable but Global Server
Jb> still crashes twice a day or so with same message as other computer:
Jb> The instruction at 0x73dd1351 referenced memory ar 0x00000004. The memory could not be read. Click OK to terminate.
Jb> Just today completed a test on the most unstable PC, by NOT starting global server and TS2000i, instead just downloading a 295 meg. file - - - - took 3 hours on broadband connection - -
Jb> absolutely no problem. Next I'll try running only Esignal datafeed and Esignal charting program - - I'm suspected TS global server is VERY picky about what hardware it's running on . . . . if
Jb> so, could be tough trying to figure out what hardware is best.
Jb> Does anybody have experience with TS2000i running on a Windows XP system using Esignal or other datafeed ? If so, how stable is your system ?
Jb> Any suggestions on what I should try next to diagnose this sucker ?
Jb> Regards,
Jb> John
|