Hi, Bablos ([EMAIL PROTECTED]).
You emailed about "[netconnect] Re: Microdot NC2 Y2K bug".
> But they wouldn't just be getting Y2K fixes - they'd be getting the
> latest updates of the programs they use now, and they'd be getting
> some new ones too.
MD should of been Y2K compliant long before now. To deny an update to
fix a problem that should not of cropped up is. I am not suggesting
giving NC2 users NC3 free but I'm sure they would be happy with a Y2K
fixed version of the MD-2 they are using now.
> >Even NC3 users only got their version of MD-2 fixed days before the
> >new year which is definatly cutting things a bit fine. How many users
> >of NC3 would of been happy to of found the Y2K bug this week?
>
> >Not me for one.
>
> But it's not just NC users - every MD-II user just about got the
> update in time.
>
> >Anyway NC2 users should be able get a Y2K fix for MD2 if no further
> >updates.
>
> Oh, I do agree, but if one isn't forthcoming I wouldn't be the least bit
> surprised.
No I wouldn't either :-(
Simply saying upgrade to NC3 isn't the answer though. I suppose an
option for those on a budget is to register MD-2 with vapor and use
the latest bugfix like the NC3 users are.
--
Jason Watson. ([EMAIL PROTECTED])
========================================================
Towerised A4000 2+64MB, KS 3.1 WB 3.5.
CS-PPC 60Mhz 68060 (OC 50Mhz) , 200Mhz 604e
Flyer4000 Z3, 4GB IDE (PFS2), ATAPI 6x2x2 CDRW, Zip-100.
HCom3Z+ I/O Card. CV64-3D 4MB (CGfx 4.2).
Online using 33.6 modem and NetConnect 3
========================================================
_____________________________________________________________
NetConnect mailing list. To unsubscribe, send an 'unsubcribe'
message to <[EMAIL PROTECTED]>
