Roel,
Just to let you know, Bud took the words from my mouth (and he said it
well).
What the whole thing boils down to is that as an application developer we
have no control over third party network solutions. We can not take a
"supported" or "unsupported" stand. It is the network vendor's
responsibility to provide functionality and performance consistent with the
workstation's native operating environment or to document deviations as
"defects" or "improvements".
Jerry
"Roel Westhoff [W4]" wrote in message
news:ef06991.3@WebX.SaUCah8kaAW...
> Bud,
>
> Thanks for your time. I'll have a look at it
>
> Roel
>
> "Bud Schroeder" wrote in message
> news:391EF2B4.3273EC83@sonic.net...
> > Hi Roel,
> >
> > Actually it has nothing to do with what Autodesk supports and everything
> to do
> > with how Novell Implements LFN. For example, OS2NAM used in the older
> versions
> > of Novell has had bugs in it for many years. I refused to use it on my
> > servers for many years because it did not get along with any of my
> programs,
> > not just AutoCAD.
> >
> > The other factor here is if you are using the Novell Client32, or the
> Microsoft
> > Client. There is a pass off between the OS and the Client and AutoCAD
> really
> > has nothing to do with this. You can get quite a combination of test
> cases
> > here. For example, just look at Windows 95 versions.
> >
> > Windows 95, 95a, 95b, 95c, FAT 16, and FAT32. Then add all the
different
> > versions of the Novell Clients. Now through in all the patches from
> Novell for
> > say just the 3.11 or 3.2 servers. Then was the Novell server built
from
> > scratch or was it upgraded, then patched.
> >
> > As you can guess, you could have a tone of variables going on here that
> can
> > cause different problems.
> >
> > Best bet is to have your server and client at the latest version, then
> check
> > with Novell for any known issues.
> >
> > Take care.
> >
> > Bud
> >
> > "Roel Westhoff [W4]" wrote:
> >
> > > Jerry,
> > >
> > > Can autodesk give some information about what versions of Novell (3
and
> 4)
> > > and Microsoft are tested and approved. Searching the other way around
> will
> > > end up in a wild-goose chase, Novell and Microsoft pointing at each
> other
> > > and Autodesk
> > >
> > > Thanks for your effort
> > >
> > > Roel
> > >
> > > "jerry milana" wrote in message
> > > news:ef06991.0@WebX.SaUCah8kaAW...
> > > > Roel,
> > > >
> > > > There are issues on how Netware treats long file names vs how
Windows
> > > treats
> > > > them. This will vary depending on the version of Netware in use on
> the
> > > > server and the Netware client in use on the workstation. So, your
> best
> > > > course of action is to gather up your version numbers prior to
> contacting
> > > > your Novell Support resource.
> > > >
> > > > Jerry Milana,
> > > > Autodesk Product Support
> > > >
> > > > "Roel Westhoff [W4]" wrote in message
> > > > news:ef06991.-1@WebX.SaUCah8kaAW...
> > > > > We are having trouble with accessing long file-names in a mixed
> > > novell-MS
> > > > > network
> > > > > The 8.3 file format does not give any trouble and when stopping
the
> > > > > microsoft-novell client evertything works ok. But after starting
the
> > > > > ms-novell client the the long file name can not be accessed
> > > > >
> > > > > Can anyone help me out the solve this problem
> > > > >
> > > > > Roel Westhoff
> > > > > Ingenieursbureau Westhoff BV
> > > > > www.wesmoll.com/ibwesthoff
> > > > >
> > > >
> >
>