In retrspect, the problem has always been NWFS vs. NSS.

NSS is far more MS-API compliant.

toodles from the future !



> There are quite a few people with the same problem. An Autodesk
> programmer told me that they're using Microsoft API's to lock the file.
> Autodesk has just recently created a patch that a few of us have
> tested and found to work well. I don't believe that it has been posted
> publicly but I think you can get the final patch by asking in the
> Autodesk Architectural Desktop 2004 forum. If you can't get it there
> re-post here and I will send you the test files and instructions I was
> given.
> We have: Netware 5.0 SP6A server, WinXP Pro SP1 workstations w/ file
> caching turned OFF at the server but turned ON at the workstation

(don't
> know why that makes a difference but for us it does).
> Good luck.
>
> Rick Johnston wrote:
>
> > My apologies, in advance, for the length of this post.
> >
> > I have a client that is trying to implement AutoDesk Architectural
> > Desktop
> > 2004 w/Sp2 in a Netware 5.1 SBS Sp6e with TFS file system environment.
> >
> >
> > The problems are related to creating/editing projects. You cannot
> > create a
> > project AND have all of its' fields display correctly. Example -
> > Create a
> > project with a Project Number of "12345" and Name of "Test Project".
> > In the
> > Project Browser, the Current Project will display as "0-Test Project".
> > It
> > should display as "12345-Test Project". There are also many editable
> > fields
> > associated with the project and those will not display properly either
> > and
> > you cannot edit the project fields!
> >
> > If we create the project on the c: drive or a Windows 2000 server,
> > everything works fine. We can even move a properly created project
> > from a
> > local or Win2k server drive to the NW TFS volume and all fields will
> > display
> > properly. But you cannot edit any fields after that. Also, you can
> > only
> > edit a project once, after selecting the project in project viewer.
> > (seems
> > to be a file locking issue)
> >
> > The issue seems to be related to the version of the NW Client that is
> > installed on the workstation. They originally were running Client32
> > v4.83eSp2+postfixes, but this configuration wouldn't even let the
> > project
> > name display in the project viewer, it would display as "unnamed". I
> > have
> > literally tried all versions of NW Client32 from v4.83, v4.83eSp1,
> > v4.83eSp2, v4.90, v4.90Sp1, 4.90Sp1 w/nwfs from 4.90B using both IPX
> > and IP
> > only connections to the server. All configuration setting suggestions
> > found
> > in earlier posts have been double-checked to see that none had been
> > missed
> > (ie-client file caching and oplocks2 are disabled both at server and
> > client). I have tried setting the switch and nic to 10,100,Full
> > Duplex, and
> > Half-Duplex, but nothing helps.
> >
> > The "best" NW Client32 versions I have found is v4.83eSp1 or v4.83eSp2
> >
> > w/nwfs.sys from Sp1, but none of them work correctly.
> >
> > The server is a Compaq ML350 G2 patched with the latest Compaq nic
> > driver
> > and Novell tcpip driver. All other programs and network performance
> > work
> > fine.
> >
> > An Ethereal packet capture shows an "Unauthorized to write to this
> > file"
> > error message, when trying to edit field properties of the ACad2004
> > project.
> >
> > Any ideas other than to switch to a Windows server environment!!!
> >
> > Thanks in advance,
> >
> > Rick Johnston
> > Information Mgmt. Systems
> >
> >
> >
> >
> >

>