|
PureBytes Links
Trading Reference Links
|
I am sorry to bother you, list members which don't subscribe to AOL:
JUST DELETE THIS MESSAGE.
To the AOL Subscribers on the List;
Does any of you, get those duplicates?
I have been getting them at least once every 2 days, beginning about 4-5
months ago, which coincided with an apparently ordinary AOL automatic update
of their software that resides on my computer.
I have written mostly to AOL for at least the past 3 months, many, many times,
including to their Chairman Steve Case. They have replied to all my dozens of
messages mostly with irrelevant information: Not very different than Omega
Research sometimes answering our questions; although AOL could give lessons of
how to reply to customers' complaints without solving their problems. The only
relevant "stuff" is that they have problems with their e-mail system, & that
they are working the problem.
(In spite of all, like with Omega, I am sticking to them because I think there
is no better value, although I may be wrong in both cases: the future "will
tell").
I am sending the latest duplicate set, in case someone cares to compare notes,
& comment. Note that although the messages are identical, the time stamp & the
"footers" are not & it seems that the List-server is sending the message
twice. I have checked with individuals, source of the message before, & they
have written to me that they have sent only one message. But I have never
checked whether any one else gets duplicates. In the latest reply by AOL, of 2
December, the tech explains that the List-server may not be functioning
properly... Who knows...
Note that I NEVER GET A TRIPLICATE.
TIA.
-Saul
************************ 1st Copy Follows *******************
Subj: Re: YEAR 2000 PROBLEM
Date: 97-12-10 10:48:04 EST
From: dpfcinpa1@xxxxxxxx
To: Kim@xxxxxxxxxx
CC: omega-list@xxxxxxxxxx
Kim,
Thanks for providing the most clear and concise exploitation regarding
this Y2000 problem, and why I should be concerned. Not having the depth
of understanding that you and some others have, it was difficult to
separate the real problem from the hype.
David Chan
>Once again Bob and Ron don't appreciate the problem.
>Believing the year 2000 problem is a only a mainframe COBOL
>problem is quite wrong. As the current version of Tradestation
>currently reads data in the format YYMMDD and NOT YYYYMMDD
>this causes a problem. There is no argument here....
>
>Granted it is not a great problem with Tradestation as we will all
>have
>the fix in a year or so. However, there is a mass of legacy software
>on
>PC's that has dates coded as YYMMDD. There will be a significant
>problem in the PC world unless one is sure that software written
>2000 is OK.....
----------------------- Headers --------------------------------
Return-Path: <omega-list-request@xxxxxxxxxx>
Received: from relay13.mail.aol.com (relay13.mail.aol.com [172.31.109.13]) by
air11.mail.aol.com (v36.0) with SMTP; Wed, 10 Dec 1997 10:48:04 -0500
Received: from mx2.eskimo.com (mx2.eskimo.com [204.122.16.49])
by relay13.mail.aol.com (8.8.5/8.8.5/AOL-4.0.0)
with ESMTP id JAA26513;
Wed, 10 Dec 1997 09:00:46 -0500 (EST)
Received: (from smartlst@xxxxxxxxx)
by mx2.eskimo.com (8.8.8/8.8.8) id GAA07513;
Wed, 10 Dec 1997 06:01:16 -0800 (PST)
Resent-Date: Wed, 10 Dec 1997 06:01:16 -0800 (PST)
From: dpfcinpa1@xxxxxxxx
To: Kim@xxxxxxxxxx
Cc: omega-list@xxxxxxxxxx
Date: Wed, 10 Dec 1997 08:52:29 -0500
Subject: Re: YEAR 2000 PROBLEM
Message-ID: <19971210.085754.3782.1.dpfcinpa1@xxxxxxxx>
References: <7D6A173E7256D111925400203522AE0E92DF@xxxxxxxxxxxxxxxxxx>
X-Mailer: Juno 1.38
X-Juno-Line-Breaks: 0-1,5-22
Resent-Message-ID: <"EbKlF2.0.Ar1.f2gZq"@mx2>
Resent-From: omega-list@xxxxxxxxxx
X-Mailing-List: <omega-list@xxxxxxxxxx> archive/latest/12258
X-Loop: omega-list@xxxxxxxxxx
Precedence: list
Resent-Sender: omega-list-request@xxxxxxxxxx
************************ 2nd Copy Follows *******************
|