Novell NetWare Users - FYI

Patrick,
Good catch. Since Novell seems to have released both totaly new clients and patchs for the clients that are "no longer" the latest, here's what version we experienced the problem with.
4.71 PT2 for NT/2000. I have not actually converted any 95/98 stations to IP yet but currently we have 3.21 PT2 for 95/98 installed on these.
The "Latest" clients now are actually 4.8 for NT/2K and 3.3 for 95/98. I'll give the current "latest" clients a test soon and notify the list if it solves the problem without having to tweak the registry. I'm a big believer in the rule "if it ain't broke, don't fix it" when it comes to service packs, patchs and fixes. I tend to let someone else be the guinea pig these days as I have been bitten several times by installing SP's P&F's as soon as there released.
Famous saying: "Sometimes the 'cure' is worse than the disease!"

Regards,
David

>>> pjw@... 09/14/00 10:38AM >>>

When you say the latest client from novell, what revision level are you
talking about?

Patrick

-----Original Message-----
From: David Crook [mailto:DCrook@...]
Sent: Tuesday, September 12, 2000 02:45 PM
To: vantage@egroups.com
Subject: [Vantage] Novell NetWare Users - FYI



For those of you still running a "real" NOS (Meaning NetWare) here is one
of those gotcha's you may encounter. We upgraded from version 4.11 to
NetWare 5.1 this past weekend. After the change we started seeing errors
when trying to "add" parts to part master (and a couple of others as well).
We discovered that if your using the latest client from Novell and have it
installed as either an IP only or both IP and IPX client. The problem seems
to be that the for whatever reason, the Novell client doesn't recognize the
UNC path of the OCX MessageLabel.OCX. Vantage registers this as
"\\<server_name>\<share_name>\VANTAGE\OCX\MessageLabel.OCX". If you change
the UNC path to this OCX (there may be others affected that we haven't
tripped over yet) to the "mapped drive letter" path, it will work. In other
words, if your mapped drive letter to the vantage share is "F", you can
change the registry data to "F:\VANTAGE\OCX\MessageLabel.OCX". This can be
edited manually or you can write a batch file to do it for you. (See below)

We no longer allow attachments to files. To access/share Report Files, please go to the following link: http://www.egroups.com/files/vantage/
(Note: If this link does not work for you the first time you try it, go to www.egroups.com, login and be sure to save your password, choose My Groups, choose Vantage, then choose Files. If you save the password, the link above will work the next time you try it.)
When you say the latest client from novell, what revision level are you
talking about?

Patrick

-----Original Message-----
From: David Crook [mailto:DCrook@...]
Sent: Tuesday, September 12, 2000 02:45 PM
To: vantage@egroups.com
Subject: [Vantage] Novell NetWare Users - FYI



For those of you still running a "real" NOS (Meaning NetWare) here is one
of those gotcha's you may encounter. We upgraded from version 4.11 to
NetWare 5.1 this past weekend. After the change we started seeing errors
when trying to "add" parts to part master (and a couple of others as well).
We discovered that if your using the latest client from Novell and have it
installed as either an IP only or both IP and IPX client. The problem seems
to be that the for whatever reason, the Novell client doesn't recognize the
UNC path of the OCX MessageLabel.OCX. Vantage registers this as
"\\<server_name>\<share_name>\VANTAGE\OCX\MessageLabel.OCX". If you change
the UNC path to this OCX (there may be others affected that we haven't
tripped over yet) to the "mapped drive letter" path, it will work. In other
words, if your mapped drive letter to the vantage share is "F", you can
change the registry data to "F:\VANTAGE\OCX\MessageLabel.OCX". This can be
edited manually or you can write a batch file to do it for you. (See below)