Raser Posted February 22, 2002 Share Posted February 22, 2002 Hello We have a problem with the writing of vectorworks files to our netware 4.11 server. It worked fine when we used windows 98 but since we changed to windows 2000 with sp2 the problems started. We use vectorworks version 8.5.2. Alle the client's have the netware client from novell running. If we write a file to the sys volume we get the error "disk io error -36".we already checked the basic stuff like disk qouta and user rights. But those where all ok. We even tried the new 9.x version of vectorworks but this version didn't work either. Has anoyone had this problem and fixed it? Grtz Erik Quote Link to comment
Bill Zeeben Posted March 13, 2002 Share Posted March 13, 2002 I am getting this exact same message under very similar situations, except we are using Netware 5.1. Did you ever find a solution? Quote Link to comment
Guest Posted March 14, 2002 Share Posted March 14, 2002 We have noticed a problem with saving to Novell servers. It is currently being looked into as to why there are problems with saving to Novell networks. Some people have no problems, other people get -36 and - 49 errors when attempting to save to the networks. Until we can find a cure for this, we have a workaround suggestion - Save the files to your local drive and then copy them to the server. Once the files are on the server you can delete the file from your local drive (if you wish) Quote Link to comment
ginger Posted May 3, 2002 Share Posted May 3, 2002 Has anything been resolved since this was posted. We're have the same problem trying to save over the network. Saving and coping doesn't seem to be an acceptable long term decision. Quote Link to comment
Guest Posted May 3, 2002 Share Posted May 3, 2002 Ginger, The engineers are still working on why this is happening. If you would like, I can add your email address to the bug and you will be notifed of changes made to the bug. Quote Link to comment
Peter Raymaekers Posted November 18, 2002 Share Posted November 18, 2002 Has this bug been resolved since the last post? We are having the same problem since we migrated our workstations to W2K. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.