david longley

Is there any reason why one should not be able to save long (windows)
filename on netware 3.2 volumes other than SYS:? Someone tells me that
they are getting an 8.3 error when writing to additional DATA volumes,
but that they don't when writing to SYS:
--
David Longley

david gersic

Was the "long" or "os2" name space added to the Data volume? If not, you'll
only get 8.3 names allowed. There also used to be a place that Windows
would cache the information as to whether long names were supported or not,
so even adding the support later would appear not to work until that
particular registry key was killed. I don't know if that's still true or
not.

Go to the server console and type "volumes". That will show you the mounted
volumes, and what name spaces are supported on them.

--
| David Gersic dgersic_@_niu.edu |
| Eagles soar, but weasels aren't ****ed into jet engines! |
| Email address is munged to avoid spammers. Remove the underscores. |

david longley

In message <c28mvg$54f$2@usenet.cso.niu.edu>, David Gersic
<dgersic_@_niu.edu> writes


Thanks for that.

I didn't specifically load the OS2 name space NLM after having created
the two extra volumes. I'd naively assumed that as it was already loaded
for the SYS volume all would be well. How do I ensure it is loaded for
each extra volume?
--
David Longley

david longley

In message <7j8xJYA8TDSAFw+P@longley.demon.co.uk>, David Longley
<David@longley.demon.co.uk> writes

I looked it up, and used ADD NAME SPACE OS2 volumename

Thanks
--
David Longley