Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Strategies & Market Trends : Tech Stock Options -- Ignore unavailable to you. Want to Upgrade?

To: HairBall who wrote (57278)	11/10/1998 8:16:00 PM
From: Ira Player	Read Replies (1) \| Respond to of 58727

Message 6339741 Ira

To: HairBall who wrote (57278)	11/10/1998 10:16:00 PM
From: Patrick Slevin	Read Replies (2) \| Respond to of 58727

I don't know Chuck T. but Ira and I have corresponded on P-Mail and Tom Trader told me of Ira's solution, but it just does not work for me. At 12:36, for example, Eastern Standard Time, I posted a message and I placed a time on the post of 12:36. It did not "hit" the thread until 12:47. I think it's @Home. Ira had a fix but it does not work for me, and if you have any clue about how I suffer people like Joe Park you will know I am reluctant to call @Home straight away. I do notice the speed slows at 9:30 and resumes somewhat at 4 Eastern Standard. Well, anyway, I don't know Chuck but I buy his service and he does not use @Home. I have a separate service that gives me DBC Data through their own box. The rest of my feeds are very quick. The problem is somewhere else. I doubt Chuck knows, to be honest. It's not a slam, the fact is he has no problem and I do. He's probably on the West Coast and I'm on the East and neither of us work for @Home. Do tell Chuck the DBC data has been very reliable since last January if you think of it, however.