'From:
kiyoinc@ibm.XOUT.net (cory hamasaki)
1:53
Subject:
Rail and Banking, was: This NG was so much better 2yrs ago.
On Thu, 20 Aug 1998 19:30:05, phystad@computerpro.com wrote:
> In article <6rhcvh$cs9$1@nnrp1.dejanews.com>,
> cabnab@my-dejanews.com wrote:
> >
> > In fact, I am getting so frustrated with this entire newsgroup. I've only
> > been reading it for a few weeks and am ready to move on because most of it is
> > useless, smart alec remarks. I know a lot of you will probably say, "go
> > ahead, leave! we don't care!" but I was really hoping this newsgroup would be
> > helpful to me and at least a couple of posts have, thank God!
> >
c.s.y2k isn't predigested, if you want that, you should hit the web.
The Cassandra project, CBN, and Citizens for Y2K Recovery offer
information at a personal level. Start at cbn.org and trace
out from there.
If you want hard technical information, check out ibm.com;
IBM is taking Y2K very, very seriously. IBM has links to other vendors,
again, this is very technical.
If you want Edwards 5.0 class information, confirmations that we're
goin' down, it's just a matter of time, head over to
garynorth.com
c.s.y2k is dynamic, raw, and the information that will be common
knowledge in 6 months is being discussed here, now.
> Even if c.s.y2k didn't exist, somebody *probably* would have raised the
> issues of embedded systems, SVC-11, tm_year, the JoAnne Effect (wonder what
> they would have called it?), and Jace probably would have discovered TD
> anyway (but I don't know who he would have told about it, considering that
> the "experts" blew him off as an alarmist amateur).
In addition to the above, power industry, ICBMs, rail, GPS, sea freight,
communications (the Telcos), the FAA, banking, avionics, have all been
c.s.y2k issues, months before the press, websites, or even that industry
itself, have carried the topics. In some cases, I believe the exposure
in c.s.y2k has forced the industry and industry regulators to come
clean. C.s.y2k forced the issue into the open.
For example, 4-6 months ago, there was a huge battle in c.s.y2k on rail.
My office is close to a rail switch yard that CSX closed down about 5
years ago. I ran my keyboard and claimed that the fact that the
physical switchyard had disappeared in to cyberspace was a problem.
About 1980, I had seen the assembler language source of a system that
switched freightcars. If that system dies on Y2K, railfreight stops and
if rail stops, everything stops, I claimed.
This set off a huge flamewar... I loved it, troublemaker that I am.
It got bizarre as only c.s.y2k can get. On one side 'Dyno' Don Scott and
'Bad' Brad Sherman. On the other, 3-4 known troublemakers and a few
specialists who worked on rail systems. Namecalling, butt-head, http:
links, Sherman found webcams of switchyards, Frank eavesdropped on the
rail comms, more than a few Bwahahaha's.
Finally Paul Makinen assembled a complete picture, it took him a couple
weeks but he obtained original source documents that showed that 1)
the RAILINC application was non-Y2K compliant, 2) they were moving the
operations center and the development center to different cities, 3)
RAILINC had outsourced the Y2K work to GEISCO, 4) GEISCO was desperately
trying to hire programmers for the rail project... in the hottest
programmer job market the world has ever seen.
It was a picture of a disaster in the making. After Paul's posting, the
rail issue vanished from c.s.y2k, asked and answered, rail is a big
problem. Now, months later, I regularly see rail information in the
press, on TV, and Senator Bennett is hammering on the rail industry.
It looks like someone fed him portions of the c.s.y2k discussions and
his staff is quizing the rail industry.
> C.s.y2k is only one of many resources available for Y2k help; but so far it's
> the best there is. Posting signal instead of complaining about (contributing
> to) noise would make it even better.
>
> </soapbox>
>
> --
> Pam
> Unofficial c.s.y2k smallish FAQ
> computerpro.com
>
> -----== Posted via Deja News, The Leader in Internet Discussion ==-----
> dejanews.com Create Your Own Free Member Forum
Here's a c.s.y2k heads up. I have a sense that banking is about to blow
up in our faces. Something about the way the news has been running just
doesn't seem quite right. Perhaps someone in the (212) area will call
(212) 902-4644, the security code is 829, and will post a synopsis of
the "Y2K Banking Research Report".
Today's banking post from infomagic was chilling. Somethings up in
banking.
cory hamasaki 498 days. |
