We are anxiously awaiting this fix also.
..Paul
--
At 09:56 AM 10/7/98 -0400, you wrote:
At 09:56 AM 10/7/98 -0400, you wrote:
>Is anyone aware of a workaround for this problem or perhaps the approximate
>date the fix will be available.
>
>Thanks,
>Gerald Siciliano
>Moodys Investors Service
>
>-----Original Message-----
>From: Pete Tanenhaus [mailto:tanenhau AT US.IBM DOT COM]
>Sent: Thursday, September 24, 1998 12:24 AM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Problems with NT MAC volume files
>
>
>APAR IC22037 has been opened on this problem, a fix  should be available
>within
>the next week on the ftp server.
>
>Sorry for the inconvenience ......
>
>Pete Tanenhaus
>ADSM NT Client Development
>---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 09/23/98
>08:54 PM ---------------------------
>
>
>ADSM-L AT VM.MARIST DOT EDU on 09/23/98 02:30:31 PM
>Please respond to ADSM-L AT VM.MARIST DOT EDU
>To: ADSM-L AT VM.MARIST DOT EDU
>cc:
>Subject: Re: Problems with NT MAC volume files
>
>
>Hello,
>
>I am also encountering the same problem with the Macintosh characters on
>NT.  Does anyone have any workarounds for this problem short of renaming
>the directories?
>
>Thanks,
>Gerald Siciliano
>
>
>
>-----Original Message-----
>From: Chad W. Spurley [mailto:CWSpurl AT LANDSEND DOT COM]
>Sent: Tuesday, September 22, 1998 12:25 PM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Problems with NT MAC volume files
>
>
>Hello Pete,
>
>I'm using the same version of ADSM and running into the same problem.
>I've
>tried using the option you said, to no avail.  Does it matter where in
>your
>dsm.opt you put it?  Is there another option that we may be missing?
>Thanks
>for your help.
>
>> -----Original Message-----
>> From: Pete Tanenhaus [mailto:tanenhau AT US.IBM DOT COM]
>> Sent: Tuesday, September 22, 1998 1:20 AM
>> To: ADSM-L AT VM.MARIST DOT EDU
>> Subject: Problems with NT MAC volume files
>>
>>
>> Make sure that the UseUnicodeFilenames option is set as
>> follows in your options
>> file:
>>
>>        UseUniCodeFileNames Yes
>>
>> The Microsoft implementation of Appleshare in Service for
>> Macintosh remaps some
>> mac characters (0 through 255 I believe) which are invalid in the NTFS
>> namespace to a user/application defined area in Unicode,
>> which makes the names
>> containing these characters only accessible in Unicode.
>>
>> The current ADSM Win32 client is not fully unicode enabled so
>> the above
>> mentioned option is required to force the
>> object names to be obtained from the filesystem in Unicode
>> (they are converted
>> to something else internally).
>>
>> Since there are no corresponding code points in non-unicode
>> codepages for these
>> characters, the codepage
>> specific (i.e. non-unicode) versions of filesystem Win32
>> api's replace these
>> characters with ? characters to indicate that
>> the characters are not valid in the namespace.
>>
>> Hope this helps ....
>>
>> Pete Tanenhaus
>> ADSM NT Client Development
>> ---------------------- Forwarded by Pete Tanenhaus/San
>> Jose/IBM on 09/21/98
>> 10:38 PM ---------------------------
>>
>>
>> ADSM-L AT VM.MARIST DOT EDU on 09/21/98 08:33:33 AM
>> Please respond to ADSM-L AT VM.MARIST DOT EDU
>> To: ADSM-L AT VM.MARIST DOT EDU
>> cc:
>> Subject: Problems with NT MAC volume files
>>
>>
>> I am having difficulty with certain files in our NT MAC volume.
>>
>> Example of Folder Name:
>> MAC\users\ht8j\ABA?ABNeca? APNEA?ABOPX
>> (The ?'s are a / in the Mac world)
>>
>> We are receiving the following error messages in our error file:
>>
>> 09/21/1998 05:45:50 ANS1256E Cannot make file/directory
>>
>>
>> From the list I see that this was supposed to be fixed with
>> ptf 5 of the
>> WIN32 client.  It does not appear to be fixed.
>>
>> Has this been fixed in any hotfix?
>> (I have renamed the files to get them backed up, but need to fix the
>> problem)
>>
>>
>>
>> Thanks,
>> Ron Clarke
>