Bryan Rubingh wrote to Will Honea on 10-28-1999
Bryan Rubingh wrote to Will Honea on 10-28-1999

BR>  WH> Two major problems, Bryan.  The most obvious is that Warp 3 is not
Y2K
BR>  WH> compliant without at least fp32 and it takes up to fp38 to straighten
BR>  WH> some of the PMMERGE problems.  Personally, I'd suggest fp40 and be
BR> 
BR> I think there is a 41 (and maybe 42) available now.  Any reason
BR> not to just go all the way?

Best one I can think of is that they will not install on your
configuration without cheating.  You appear to be using standard Warp
3 with LS 3 over it while fp41/42 specifically check for Warp Server
in syslevel.os2.
 
BR>  WH> done with it.  That will also tweek the IBM1S506 to a level that
should
BR>  WH> handle the 20g drive.  Just to be on the safe side, throw a copy of
BR>  WH> DANIS506.ADD in your kit - easier than chasing the IBM1S506.ADD revs
BR>  WH> all over the place.
BR> 
BR> I haven't checked DANIS506.ADD at all, but from messages I've been
BR> seeing, isn't that just for the VIA chipset or does that work with
BR> any IDE chips?

According to Daniela, it is pretty much a tossup with Intel chips but
with SIS, ALI, VIA, etc it's a much better solution.  Reason I suggest
it as a 'just in case' is that the last version she put out (on the
Hobbes site) should cover the 20gb drive without a hassle.

BR>  WH> The other problem is not so simple.  As far as I can tell, there has
BR>  WH> never been a fixpak released that brings LS 3 up to Y2K compliant and
BR>  WH> I know that there are parts of the IP stack that will die from 
BR> When you say IP, I assume you mean Internet Protocol.  We are
BR> using NetBeui as the protocol and there are no internet connections,
BR> so is there still a problem?  We actually did a test back in July of
BR> last year by advancing the date to 12/31/99 and letting it rollover.
BR>  We only spent a couple hours with it that way, but everything
BR> seemed to work correctly.

I seem to recall several fixes that called out Y2K related NetBeui
problems that mostly involved logon and session integrity issues,
especially if there were any other servers involved.  There were a
couple of odd account problems as well.  It would be worth a little
research time, certainly.

BR>  WH> timestamp problems.  LS 3 is long out of support but you might be
able
BR>  WH> to find the lastest updates at the IBM sites.  The most current
listing
BR>  WH> I have are at:
BR> 
BR>  WH> http://service5.boulder.ibm.com/pspfixpk.nsf/3f5d9c073e8a667
BR>  WH> 8625662800691e9b?OpenView
BR> 
BR> Thanks.  I was wondering if there were any updates available for
BR> it. However we really haven't had any problems with it.  I have some
BR> customers with Novell and NT and this one with LAN Server and you
BR> can easily guess which one has the least problems.

Yes, I work in an environment with multiple servers and that does seem
to be the case.  One other consideration would be the number of
nagging memory leaks that have been fixed over time.  BTW, the fixes
for NetBeui and TCP/IP are essentially inseperable since both are
actually protocol elements of what was still LAPS at the time 3.0 was
current.  They have merged the transport functionality into a single
overall package that supports all NetBeui, Novell, and TCP/IP protocols
and call the whole thing MPTS now.

Will Honea 
--- Maximus/2 2.02