FindFirstFile API and Novell's MS-DOS name...


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 4 of 4

Thread: FindFirstFile API and Novell's MS-DOS name...

  1. #1
    Jeff Knapp Guest

    FindFirstFile API and Novell's MS-DOS name...

    Group,

    I have been using Randy Birch's excellent FileExists routine for what seems
    like forever and have just come across an interesting quirk and I'm not
    sure if anyone might know of a workaround. (The FileSystemObject and
    Dir$() suffer from the same fate...)

    We have a Novell 4.11 file server with long name support. We auto generate
    documents and we use a naming scheme of A000001.txt, A000002.txt, A000002 -
    Part 2.txt ...

    In the above example, I have three files:

    A000001.txt
    A000002.txt
    A000002 - Part 2.txt

    I use a routine that searches for the first 8 letters in the last file in a
    directory, and increments the number by one, so "A000002 - Part 2.txt"
    should result in a A000003.txt

    However, when I pass A0000003.txt to the FileExists() routine, it comes
    back as TRUE since Novell is storing an MS-DOS name of A000003.txt for
    "A000002 - Part 2.txt"

    Any ideas on how to get around this limitation?

    Thanks,

    Jeff

  2. #2
    Randy Birch Guest

    Re: FindFirstFile API and Novell's MS-DOS name...

    I don't know if this applies, but ...

    Suggested File Name Is Truncated When Saving to Novell Server

    ----------------------------------------------------------------------------
    ----
    The information in this article applies to:

    a.. Microsoft Windows NT Server versions 4.0, 4.0 SP4, 4.0 SP5, 4.0 SP6,
    Terminal Server Edition
    b.. Microsoft Windows NT Server, Enterprise Edition versions 4.0, 4.0 SP4,
    4.0 SP5, 4.0 SP6, 4.0 SP6a
    c.. Microsoft Windows NT Workstation versions 4.0, 4.0 SP1, 4.0 SP2, 4.0
    SP3, 4.0 SP4, 4.0 SP5, 4.0 SP6, 4.0 SP6a
    d.. Microsoft Windows NT Server versions 4.0, 4.0 SP4, 4.0 SP5, 4.0 SP6,
    4.0 SP6a

    ----------------------------------------------------------------------------
    ----


    SYMPTOMS
    When you save a new Microsoft Office document in a default location on a
    Novell NetWare 4.11 server with the Long.nam namespace installed, the
    suggested file name for saving the file may be truncated to a short (or
    "8.3") file name instead of a long file name.



    CAUSE
    NetWare 4.11 introduced the Long.nam namespace, which supersedes the OS/2
    namespace (Os2.nam). According to Novell TID 2929574, you must use the
    Novell client to ensure long file name support when you are saving to a
    NetWare drive.



    RESOLUTION
    To resolve this issue, obtain and install the latest Novell Client software
    from the Novell Web site.

    Additional query words:

    Keywords : kb3rdparty kbnetwork
    Version : winnt:4.0,4.0 SP1,4.0 SP2,4.0 SP3,4.0 SP4,4.0 SP5,4.0 SP6,4.0 SP6a
    Platform : winnt
    Issue type : kbprb
    Technology : kbvcSearch


    Last Reviewed: June 16, 2000

    --

    Randy Birch
    MVP Visual Basic


    Take the vb.net poll at:
    http://www.mvps.org/vbnet/
    http://www.mvps.org/ccrp/



    "Jeff Knapp" <jknapp@jephens.com> wrote in message
    news:9010BB6EFjephens121344@209.1.14.192...
    : Group,
    :
    : I have been using Randy Birch's excellent FileExists routine for what
    seems
    : like forever and have just come across an interesting quirk and I'm not
    : sure if anyone might know of a workaround. (The FileSystemObject and
    : Dir$() suffer from the same fate...)
    :
    : We have a Novell 4.11 file server with long name support. We auto
    generate
    : documents and we use a naming scheme of A000001.txt, A000002.txt,
    A000002 -
    : Part 2.txt ...
    :
    : In the above example, I have three files:
    :
    : A000001.txt
    : A000002.txt
    : A000002 - Part 2.txt
    :
    : I use a routine that searches for the first 8 letters in the last file in
    a
    : directory, and increments the number by one, so "A000002 - Part 2.txt"
    : should result in a A000003.txt
    :
    : However, when I pass A0000003.txt to the FileExists() routine, it comes
    : back as TRUE since Novell is storing an MS-DOS name of A000003.txt for
    : "A000002 - Part 2.txt"
    :
    : Any ideas on how to get around this limitation?
    :
    : Thanks,
    :
    : Jeff



  3. #3
    Randy Birch Guest

    Re: FindFirstFile API and Novell's MS-DOS name...

    More info ...

    In reading several novell 4/win kb articles in the msdn, the following
    points were mentioned in relation to varying file problems, most commonly
    with Office.

    - long filename support failure might be due to the to Novell OS/2 Namespace
    : recommend server patch (Mixmod4.exe) or upgrade to Novell client ---
    "NetWare 4.11 introduced the Long.nam namespace, which supersedes the OS/2
    namespace (Os2.nam). According to Novell TID 2929574, you must use the
    Novell client to ensure long file name support when you are saving to a
    NetWare drive."


    - the windows os is unable to determine if the os running novell that hosts
    the file supports long filenames, so the short name is used.

    - the filename contains spaces. Suggest trying with names such as
    A000002_Part 2.txt

    --

    Randy Birch
    MVP Visual Basic

    Take the vb.net poll at:
    http://www.mvps.org/vbnet/
    http://www.mvps.org/ccrp/



    "Jeff Knapp" <jknapp@jephens.com> wrote in message
    news:9010BB6EFjephens121344@209.1.14.192...
    : Group,
    :
    : I have been using Randy Birch's excellent FileExists routine for what
    seems
    : like forever and have just come across an interesting quirk and I'm not
    : sure if anyone might know of a workaround. (The FileSystemObject and
    : Dir$() suffer from the same fate...)
    :
    : We have a Novell 4.11 file server with long name support. We auto
    generate
    : documents and we use a naming scheme of A000001.txt, A000002.txt,
    A000002 -
    : Part 2.txt ...
    :
    : In the above example, I have three files:
    :
    : A000001.txt
    : A000002.txt
    : A000002 - Part 2.txt
    :
    : I use a routine that searches for the first 8 letters in the last file in
    a
    : directory, and increments the number by one, so "A000002 - Part 2.txt"
    : should result in a A000003.txt
    :
    : However, when I pass A0000003.txt to the FileExists() routine, it comes
    : back as TRUE since Novell is storing an MS-DOS name of A000003.txt for
    : "A000002 - Part 2.txt"
    :
    : Any ideas on how to get around this limitation?
    :
    : Thanks,
    :
    : Jeff



  4. #4
    Jeff Knapp Guest

    Re: FindFirstFile API and Novell's MS-DOS name...

    "Randy Birch" <rgb@mvps.org> wrote in <3a421be9$1@news.devx.com>:

    >More info ...


    Can't thank you enough.

    >- the windows os is unable to determine if the os running novell that
    >hosts the file supports long filenames, so the short name is used.


    That seems to be the one.

    I'll have to look into the Novell client APIs and see if there's a
    ShortToLong name function of some sort.

    Thanks again.

    Jeff



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center