A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » General
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Truncation of long filename



 
 
Thread Tools Display Modes
  #1  
Old September 28th 04, 11:20 AM
plxjb
external usenet poster
 
Posts: n/a
Default Truncation of long filename

I came across the following problem:
I have an archive including files having long filenames. When I run
the self-extracting archive, Windows 98 truncates the names of files
to 8 char, without ~n sign (as usually done at command prompt).
  #2  
Old September 28th 04, 11:30 AM
Jeff Richards
external usenet poster
 
Posts: n/a
Default

It's the archiving program, not Windows that is doing the truncating. Use
an archiving utility that fully supports long filenames, or search for an
option within the current utility to enable long filename support.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"plxjb" wrote in message
om...
I came across the following problem:
I have an archive including files having long filenames. When I run
the self-extracting archive, Windows 98 truncates the names of files
to 8 char, without ~n sign (as usually done at command prompt).



  #3  
Old September 29th 04, 05:17 AM
plxjb
external usenet poster
 
Posts: n/a
Default

I did that by uninstalling the program and reinstalling it. Untill I
did some research on direct cable communication with two Win 98
stations linked with a parallel cable, it did work. The archiving
program is called WinImp. It doesn't have any option of long name
support. When I check the archive with the program, the filenames are
OK. If I do extraction from within the program it works fine. But I
need the self-extracting capability of the archive.
"Jeff Richards" wrote in message ...
It's the archiving program, not Windows that is doing the truncating. Use
an archiving utility that fully supports long filenames, or search for an
option within the current utility to enable long filename support.
--
Jeff Richards
MS MVP (Windows - Shell/User)
"plxjb" wrote in message
om...
I came across the following problem:
I have an archive including files having long filenames. When I run
the self-extracting archive, Windows 98 truncates the names of files
to 8 char, without ~n sign (as usually done at command prompt).

  #4  
Old September 29th 04, 06:40 AM
Jeff Richards
external usenet poster
 
Posts: n/a
Default

This program has always had a problem with long filenames and the
self-extractor. It was supposedly fixed in revision 1.21 but I have never
been able to make it work properly with W98 systems. AFAIK 1.21 is the
newest version. You might be able to contact the manufacturer for
assistance.
http://www.technelysium.com.au/winimp.html
--
Jeff Richards
MS MVP (Windows - Shell/User)
"plxjb" wrote in message
m...
I did that by uninstalling the program and reinstalling it. Untill I
did some research on direct cable communication with two Win 98
stations linked with a parallel cable, it did work. The archiving
program is called WinImp. It doesn't have any option of long name
support. When I check the archive with the program, the filenames are
OK. If I do extraction from within the program it works fine. But I
need the self-extracting capability of the archive.
"Jeff Richards" wrote in message
...
It's the archiving program, not Windows that is doing the truncating.
Use
an archiving utility that fully supports long filenames, or search for an
option within the current utility to enable long filename support.



  #5  
Old September 29th 04, 12:52 PM
plxjb
external usenet poster
 
Posts: n/a
Default

Funny thing: I had that archive checked out on another computer. It
works the self-extraction. But doesn't work on my computer and the
computer I connected on with a parallel cable, though.
"Jeff Richards" wrote in message ...
This program has always had a problem with long filenames and the
self-extractor. It was supposedly fixed in revision 1.21 but I have never
been able to make it work properly with W98 systems. AFAIK 1.21 is the
newest version. You might be able to contact the manufacturer for
assistance.
http://www.technelysium.com.au/winimp.html
--
Jeff Richards
MS MVP (Windows - Shell/User)
"plxjb" wrote in message
m...
I did that by uninstalling the program and reinstalling it. Untill I
did some research on direct cable communication with two Win 98
stations linked with a parallel cable, it did work. The archiving
program is called WinImp. It doesn't have any option of long name
support. When I check the archive with the program, the filenames are
OK. If I do extraction from within the program it works fine. But I
need the self-extracting capability of the archive.
"Jeff Richards" wrote in message
...
It's the archiving program, not Windows that is doing the truncating.
Use
an archiving utility that fully supports long filenames, or search for an
option within the current utility to enable long filename support.

  #6  
Old September 29th 04, 11:39 PM
Jeff Richards
external usenet poster
 
Posts: n/a
Default

That is the symptom I have seen. It's to do with the specific version of
certain supporting files installed on the particular PC, but I have no idea
which ones. Originally, the problem only appeared on NT machines, but as
W98 machines are upgraded and service packs etc installed, the problem then
appears on more and more W98 machines. For instance, it works perfectly on
my W95 portable, but not on either of the W98 machines (which are kept fully
up to date). The manufacturer might be able to advise what versions of the
supporting files you should be using:
http://www.technelysium.com.au/winimp.html
--
Jeff Richards
MS MVP (Windows - Shell/User)
"plxjb" wrote in message
m...
Funny thing: I had that archive checked out on another computer. It
works the self-extraction. But doesn't work on my computer and the
computer I connected on with a parallel cable, though.
"Jeff Richards" wrote in message
...
This program has always had a problem with long filenames and the
self-extractor. It was supposedly fixed in revision 1.21 but I have
never
been able to make it work properly with W98 systems. AFAIK 1.21 is the
newest version. You might be able to contact the manufacturer for
assistance.
http://www.technelysium.com.au/winimp.html
--



  #7  
Old September 30th 04, 06:36 AM
plxjb
external usenet poster
 
Posts: n/a
Default

I don't remember doing any upgrades to W98, although I am connected to
the net. Checking W98 version, it says "4.10.1998". I guess that means
it's not "SE". If I do any updates, will the version number change?
"Jeff Richards" wrote in message ...
That is the symptom I have seen. It's to do with the specific version of
certain supporting files installed on the particular PC, but I have no idea
which ones. Originally, the problem only appeared on NT machines, but as
W98 machines are upgraded and service packs etc installed, the problem then
appears on more and more W98 machines. For instance, it works perfectly on
my W95 portable, but not on either of the W98 machines (which are kept fully
up to date). The manufacturer might be able to advise what versions of the
supporting files you should be using:
http://www.technelysium.com.au/winimp.html
--
Jeff Richards
MS MVP (Windows - Shell/User)
"plxjb" wrote in message
m...
Funny thing: I had that archive checked out on another computer. It
works the self-extraction. But doesn't work on my computer and the
computer I connected on with a parallel cable, though.
"Jeff Richards" wrote in message
...
This program has always had a problem with long filenames and the
self-extractor. It was supposedly fixed in revision 1.21 but I have
never
been able to make it work properly with W98 systems. AFAIK 1.21 is the
newest version. You might be able to contact the manufacturer for
assistance.
http://www.technelysium.com.au/winimp.html
--

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
WinME (OEM) MS-DOSreports windows invalid long filename entry Randy General 5 September 23rd 04 12:50 PM
Long Wait-Time to Connect to Internet ? James Nipper General 3 August 16th 04 03:18 PM
can someone tell me why my OE is taking so long to boot up? Doug General 4 July 9th 04 07:23 AM
long filename recogition lost baffulled General 5 June 28th 04 04:04 PM
Long file name Problem Canapril General 1 June 12th 04 03:36 AM


All times are GMT +1. The time now is 07:41 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.