Sorry about the Outook Express, but I'm AFH just now....
----- Original Message -----
From: "Daniel V. Smith" <[EMAIL PROTECTED]>
Sent: Monday, January 03, 2000 7:55 PM
Subject: [netconnect] Re: Microdot NC2 Y2K bug
> On 1 Jan 2000, Daniel Thornton said:
>
> > Can us NC=II users have a Y2K fix for our release of MD2? I'm having to
> > use the 1.4 version in demo mode until NC-3 arrives, and it's very
> > annoying having to wait a minute for the program to unlock, and
> > closedown every thirty minutes.
>
> On 3 Jan 2000, Bablos said:
>
> > ... but the new MD-II isn't a part of
> > NC2. NC2 software was specifically compiled - you couldn't just
> > download the latest Vapor release and plug it in - you had to wait
> > until Olli was kind enough to send Chris an NC specific one.
>
> So, if the new MD-II isn't a part of NC2, how is Mr Thornton using
> it "until NC-3 arrives" ???
No point in being nasty and picky here. Mr Thorton is using it in Demo
mode. _ANY_ Amiga owner can use it in Demo mode. If you only need to have
your mailer open for 30 minutes at a time, it's possible, but not very nice
;)
> I only bought NC2 in August, so I shouldn't have to upgrade to NC3 when,
> apart from this date problem, I'm happy with the rest of it.
I agree completely, but in order to upgrade every application for both NC2
and NC3 will take time. Users of NC3 obviously take precedence as they can
use the latest versions. There /may/ in the future be specific Y2K fix
releases for NC1.1 (unlikely) and NC2 (possibly). Check with Active/Vapor.
Software is sold as-is with no warranty for a specific purpose. If you
bought a PC in January 1999 which wasn't Y2K compliant (sadly this was
possible), you have no recourse in January 2000, as the problem is software,
and most PC manufacturers only provide 14 or 28 days of software cover.
> People have been going on about the so-called millennium bug for ages now,
> so such a STUPID error should never have been made in the first place.
It's actually pretty hard to make software date compliant. Even simple
things can knock it out of whack, and 4-digit dates are 'only' good for
another 8000 years, if you think about it. I was taught /very/ non-Y2K
compliant practices in a higher-level computing course back in 1991/92. The
'standard' methods of calculating leap years, differences in days between
two events etc. can easily pop up non-Y2K events. If YOU think it is
stupid, you should have been writing 1999 on every cheque you've ever
written, every time you quoted your DOB etc. Taking a date and subtracting
1900 from it to make a two digit representation is standard practice, so
2000=100 is inevitable unless the coder is on his toes. It has _always_
been 19xx from a computing perspective, until 3 days ago!
Totty <8^)
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
