Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
2181 views

Real Problem with Short 8.3 Filenames in Windows 7

I have a real problem with Netware Client's inability to deliver 8.3 short file names. We have several users (including me) who still use some old DOS programs under Windows 7. Using the newest Novell clients (just upgraded to the latest on Friday) there is no ability to find the true short file names.

How do we work around this? It is very difficult to run the older programs, but they still have great utility for us. We cannot just "guess" what the filename should be, because sometimes Windows delivers some really funky filenames.

Any help would be much appreciated.

Running Windows 7, Netware 5.1, newest NW Client.

Thanks.
Alan
Labels (1)
0 Likes
4 Replies
Cadet 1st Class Cadet 1st Class
Cadet 1st Class

Considering the array of DOS garbage-ware we still run, on Windows 7, with the recent client, all of which work, I'd like some specific example of what you are talking about. Also, please tell us more about the server you are using... NetWare 5.1 SP what? Is the volume being accessed TFS or NSS? If TFS, what name spaces are in use on the volume?

Is this a regression? I.e. did it work perfectly under a prior version of the Novell Client for Windows 7? If so, which one?

-- Bob
0 Likes
Absent Member.
Absent Member.

Please open a SR on this issue. It's one of the not supported things,
which were removed from functionality although Windows itself and SAMBA
do support that feature.

I had a SR open because of this lack of functionality and they
confirmed that as not working.

That's my last information on this (copy of last e-mail by NTS on this
issue):

Hey Wolfgang,

We have a written TID#7007348 that this issue is reported to
engineering, This problem may be fixed in a future release of the
Client, depending on its impact on customers, available engineering
resources, etc. When and if it is fixed, it will be available as part
of a future Client build posted on the Novell download website. so as
many customers will complain about it its priority will increase.

Thanks & Regards,

Nilesh Nikam

>>> "Dr. Wolfgang Prindl" <wp@twb.at> 12/9/2010 5:39 PM >>>

Hi Nilesh,

I completely understand your position and thanks for opening a bug. So
lets hope for a fix.

Regards

Wolfgang Prindl

>>> <nnikam@novell.com> schrieb am 09.12.2010 um 08:23 in Nachricht

5c88827b4049e22f5e278a9ec9378996:
> Hey Wolfgang,
>
> Hope you are doing great!
>
> I understand it completely, I have opened a bug for the issue, bug

number is
> 658102, Development will address this in next release, I hope you

understand
> that I am a frontline support engineer, I have tried the best I can

do for
> this 😞 so opened a bug. Hopefully they will fix it soon.
>
> Please feel free to contact me if you have any questions
>
> your's faithfully
>
> Nilesh Nikam
>
>>>> "Dr. Wolfgang Prindl" <wp@twb.at> 12/7/2010 5:03 PM >>>

> Hi Nilesh,
>
> ok, if this is by design, that's bad news.
>
> In my opinion the Novell Client has only value - and without Novell

Client
> the whole Novell OES is of absolutely no value - if he has a par or

even
> better functionality than native file access to Windows or Linux/Unix

Samba
> file servers. So any functionality delivered by the Windows client

has to be
> copied to the Novell Client to be competitive and useable in my

opinion. If
> the Client degrades to a crook for accessing files in some limited

way,
> instead of being a tool delivering full functionality like a native

client
> (which client 4.91 for WinXP is), people changing to Win7 will have

to
> consider, if it is wise to use Novell NCP and Novell servers as
> server-platform for Win7 clients. If there are omissions and errors

and
> those are repaired, one can - even if it really takes a very long

time, to get
> those sorted out - plan to rely on that product for the next furure;

but if
> the omissions are by design, which means that there is no plan to

deliver a
> fully functional client (what other functionality will never be

delivered by
> design???), every sensible IT manager has to rethink it's reliance on

Novell
> OES servers for file serving thoroughly and look for alternatives.

BTW I
> would have dumped the Novell Client for Win7 already because of all

sorts of
> issues, if Samba or Cifs to OES servers would give a reasonable

performance -
> but unfortunately they are outperformed by any simple Windows WS -

and by NCP.
>
> Regards
>
> Wolfgang
>
>>>> <nnikam@novell.com> schrieb am 07.12.2010 um 06:48 in Nachricht

> 24539a2cd116ef0536e69be4a4a6e17b:
>> Hey Wolfgang,
>>
>> Hope you are doing great!
>>
>> This mail is regarding to SR#10665208261, where you were facing the

issue
>> with the dir /x. I can duplicate the issue. It appears that the
>> functionality delivered by "dir /x" is not contained in the shipping

Novell
>> Client 2 SP1 release. you are welcome to open an enhancement

request, since
>
>> the functionality is not included, rather than not working properly.

I made
>> confirm with the backline and the development
>>
>> Thanks & Regards,
>>
>> Nilesh Nikam




--
W. Prindl


ostrowlaw wrote:

>
>I have a real problem with Netware Client's inability to deliver 8.3
>short file names. We have several users (including me) who still use
>some old DOS programs under Windows 7. Using the newest Novell
>clients (just upgraded to the latest on Friday) there is no ability
>to find the true short file names.
>
>How do we work around this? It is very difficult to run the older
>programs, but they still have great utility for us. We cannot just
>"guess" what the filename should be, because sometimes Windows
>delivers some really funky filenames.
>
>Any help would be much appreciated.
>
>Running Windows 7, Netware 5.1, newest NW Client.
>
>Thanks.
>Alan


W. Prindl
0 Likes
Absent Member.
Absent Member.

I just got into this web page, for some reason for the last week I was locked out of community support. I am using my Linux desktop, maybe Windows is trying to keep me from Novell ( :))

Anyway, I am running Netware 5.1 with the latest and greatest client, but I don't think it matters, based upon your post and the postings Novell discontinued short filename support.

How do I open a SR and I will do it immediately.

Thanks
Alan

W_Prindl;2146621 wrote:
Please open a SR on this issue. It's one of the not supported things,
which were removed from functionality although Windows itself and SAMBA
do support that feature.

I had a SR open because of this lack of functionality and they
confirmed that as not working.

That's my last information on this (copy of last e-mail by NTS on this
issue):

Hey Wolfgang,

We have a written TID#7007348 that this issue is reported to
engineering, This problem may be fixed in a future release of the
Client, depending on its impact on customers, available engineering
resources, etc. When and if it is fixed, it will be available as part
of a future Client build posted on the Novell download website. so as
many customers will complain about it its priority will increase.

Thanks & Regards,

Nilesh Nikam

>>> "Dr. Wolfgang Prindl" <wp@twb.at> 12/9/2010 5:39 PM >>>

Hi Nilesh,

I completely understand your position and thanks for opening a bug. So
lets hope for a fix.

Regards

Wolfgang Prindl

>>> <nnikam@novell.com> schrieb am 09.12.2010 um 08:23 in Nachricht

5c88827b4049e22f5e278a9ec9378996:
> Hey Wolfgang,
>
> Hope you are doing great!
>
> I understand it completely, I have opened a bug for the issue, bug

number is
> 658102, Development will address this in next release, I hope you

understand
> that I am a frontline support engineer, I have tried the best I can

do for
> this 😞 so opened a bug. Hopefully they will fix it soon.
>
> Please feel free to contact me if you have any questions
>
> your's faithfully
>
> Nilesh Nikam
>
>>>> "Dr. Wolfgang Prindl" <wp@twb.at> 12/7/2010 5:03 PM >>>

> Hi Nilesh,
>
> ok, if this is by design, that's bad news.
>
> In my opinion the Novell Client has only value - and without Novell

Client
> the whole Novell OES is of absolutely no value - if he has a par or

even
> better functionality than native file access to Windows or Linux/Unix

Samba
> file servers. So any functionality delivered by the Windows client

has to be
> copied to the Novell Client to be competitive and useable in my

opinion. If
> the Client degrades to a crook for accessing files in some limited

way,
> instead of being a tool delivering full functionality like a native

client
> (which client 4.91 for WinXP is), people changing to Win7 will have

to
> consider, if it is wise to use Novell NCP and Novell servers as
> server-platform for Win7 clients. If there are omissions and errors

and
> those are repaired, one can - even if it really takes a very long

time, to get
> those sorted out - plan to rely on that product for the next furure;

but if
> the omissions are by design, which means that there is no plan to

deliver a
> fully functional client (what other functionality will never be

delivered by
> design???), every sensible IT manager has to rethink it's reliance on

Novell
> OES servers for file serving thoroughly and look for alternatives.

BTW I
> would have dumped the Novell Client for Win7 already because of all

sorts of
> issues, if Samba or Cifs to OES servers would give a reasonable

performance -
> but unfortunately they are outperformed by any simple Windows WS -

and by NCP.
>
> Regards
>
> Wolfgang
>
>>>> <nnikam@novell.com> schrieb am 07.12.2010 um 06:48 in Nachricht

> 24539a2cd116ef0536e69be4a4a6e17b:
>> Hey Wolfgang,
>>
>> Hope you are doing great!
>>
>> This mail is regarding to SR#10665208261, where you were facing the

issue
>> with the dir /x. I can duplicate the issue. It appears that the
>> functionality delivered by "dir /x" is not contained in the shipping

Novell
>> Client 2 SP1 release. you are welcome to open an enhancement

request, since
>
>> the functionality is not included, rather than not working properly.

I made
>> confirm with the backline and the development
>>
>> Thanks & Regards,
>>
>> Nilesh Nikam




--
W. Prindl


ostrowlaw wrote:

>
>I have a real problem with Netware Client's inability to deliver 8.3
>short file names. We have several users (including me) who still use
>some old DOS programs under Windows 7. Using the newest Novell
>clients (just upgraded to the latest on Friday) there is no ability
>to find the true short file names.
>
>How do we work around this? It is very difficult to run the older
>programs, but they still have great utility for us. We cannot just
>"guess" what the filename should be, because sometimes Windows
>delivers some really funky filenames.
>
>Any help would be much appreciated.
>
>Running Windows 7, Netware 5.1, newest NW Client.
>
>Thanks.
>Alan
0 Likes
Absent Member.
Absent Member.

How do I open a SR and I will do it immediately.

If you have maintenance with Novell http://www.novell.com/center/eservice
Otherwise Support: Submit a Service Request: Details

Andrew C Taubman (Sorry, support is not provided via e-mail) Opinions expressed above are not necessarily those of Micro Focus.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.