As I read the summary of the letter from Richard Balanson, it sounds to
me like a promise to do nothing about the older machines, which are more
likely to have a problem, and to provide responsive service on the newer
machines, which should not have a problem. Perhaps I don't understand what
the problem might be.

By the way, a California Assembly committee last week rejected a measure
to limit the financial liability of designers and manufacturers of
computer systems, programs and software due to problems expected from the Y2K
problem.

Brock Hinzmann

Steve Stewart wrote:
>Oops, forgot to send this to the list!
>
>Kevin Robertson wrote:
>>
>> At 01:58 PM 4/24/98 -0500, Todd Stahlhut wrote:
>> >I was asked the question today if there were any year 2000 (Y2K)
issues
>> >with the SLA process. My immediate response was NO. Has anyone done
any
>> >studies or heard anything to indicate that the SLA process (The SLA
250
>> >in general) and the Maestro software has issues with Y2K.
>>
>> I received a response from 3-D in regards to Y2K compliance. There
position
>> is they will make any modifications on products purchased after August
31,
>> 1997 to make the machines work at no charge. If the machines were
purchased
>> before that, they will provide an upgrade plan if an upgrade is
required.
>>
>> According to the letter received, 3-D will be issuing a Year 2000
Policy
>> Statement by April 30, 1998. Randy Doyle is the Y2K Coordinator for
3-D and
>> the letter was drafted by their President and COO Richard Balanson.
>>
>> If we ever slow down enough we are going to forward date a machine to
see
>> what happens.
>> If anyone else has already done this a posting would be appreciated.
>>
>> Regards,
>>
>> Kevin Robertson
>> VP Business Operations
>> ARRK San Diego, CA
>>
>> For more information about the rp-ml, see http://ltk.hut.fi/rp-ml/>
>This morning I tested the 486 (we upgraded in 5/94) on our SLA-250 with
>a program called TEST2000.EXE. I got the free program from
>http://www.rightime.com - they are out to sell a program that will fix
>your problem machines. TEST2000.EXE works by setting the time to
>23:59:58 on 12/31/99, and letting the machine roll into 2000, then
>rebooting and checking for problems. Our 486 came through with no
>problems. Now the only question is, will 3D's software handle a date
>like 04/27/00? I have set the 250's date forward to 04/27/00, and will
>monitor and let you all know.
>
>Regards,
>
>
>
>--
>\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
> \_ Steve Stewart Phone: 303-252-0212 \_
> \_ protogenic, inc. FAX: 303-252-0223 \_
> \_ 1490 w. 121 ave., suite 101 WebSite:www.protogenic.com \_
> \_ westminster, co 80234 e-mail:steve@protogenic.com \_
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
>For more information about the rp-ml, see http://ltk.hut.fi/rp-ml/>
>RFC822 header
>-----------------------------------
>
>Return-Path: <owner-rp-ml@ltk.hut.fi>
>Received: from bart.lpt.fi ([193.166.66.1]) by mgw-mp.sric.sri.com
> (Netscape Messaging Server 3.0) with ESMTP id AAA15513;
> Mon, 27 Apr 1998 17:07:28 -0700
>Received: from major by bart.lpt.fi with local (Exim 1.90 #2)
> for rp-ml-outgoing@bart.lpt.fi> id 0yTxhk-0007Wk-00; Mon, 27 Apr 1998 23:53:00 +0000
>Received: from www.protogenic.com ([204.133.227.1])
> by bart.lpt.fi with esmtp (Exim 1.90 #2)
> for rp-ml@bart.lpt.fi> id 0yTxhi-0007Ch-00; Tue, 28 Apr 1998 02:52:59 +0300
>Received: from protogenic.com (204.133.227.61) by www.protogenic.com
> with ESMTP (Eudora Internet Mail Server 1.2); Mon, 27 Apr 1998 17:51:57
-0600
>Message-ID: <35451A25.D691066@protogenic.com>
>Date: Mon, 27 Apr 1998 17:52:05 -0600
>From: Steve Stewart <steve@protogenic.com>
>Organization: Protogenic, Inc.
>X-Mailer: Mozilla 4.04 [en] (WinNT; U)
>MIME-Version: 1.0
>To: Rapid Prototyping Mailing List <rp-ml@bart.lpt.fi>
>Subject: Re: SLA's and Year 2000
>Content-Type: text/plain; charset=us-ascii
>Content-Transfer-Encoding: 7bit
>Sender: owner-rp-ml@ltk.hut.fi>Precedence: bulk
>