Bad Command or filename with zip2exe executable

  • Thread starter Thread starter Bob Unger
  • Start date Start date
B

Bob Unger

We routinely create a zip file using the old PKZIP for DOS
programs, and convert them to an executablen self
extracting EXE using the ZIP2EXE program. We just
experienced a problem on a W2K server when we try to
execute the EXE and get the message "Bad command or file
name". It unzips fine on my W2k workstation, and on our
NT4 servers. On the W2k server, one of these files we
created unzipped fine in June, but will not unzip now,
after applying service pack 4... Any Ideas what the root
cause is and can we repair?
 
Bob Unger said:
We routinely create a zip file using the old PKZIP for DOS
programs, and convert them to an executablen self
extracting EXE using the ZIP2EXE program. We just
experienced a problem on a W2K server when we try to
execute the EXE and get the message "Bad command or file
name". It unzips fine on my W2k workstation, and on our
NT4 servers. On the W2k server, one of these files we
created unzipped fine in June, but will not unzip now,
after applying service pack 4... Any Ideas what the root
cause is and can we repair?
Click to expand...

Try to open the file with winzip or some other zip-program.
If the file isn't corrupted to much it can be opened.
There is also a program called pkzipfix to repair. I don't
know if it works also on .exe files.

hth
 
In said:
We routinely create a zip file using the old PKZIP for DOS
programs, and convert them to an executablen self
extracting EXE using the ZIP2EXE program. We just
experienced a problem on a W2K server when we try to
execute the EXE and get the message "Bad command or file
name". It unzips fine on my W2k workstation, and on our
NT4 servers. On the W2k server, one of these files we
created unzipped fine in June, but will not unzip now,
after applying service pack 4... Any Ideas what the root
cause is and can we repair?
Click to expand...

No answer regarding SP4.

But why not use Info-Zip command-line (or GUI) programs for Win32
(free) instead of an old DOS program?
http://www.info-zip.org/pub/infozip/
It might eliminate the problem (perhaps).
 
The ZIP file is fine, it opens with WinZip and self
extracts on my W2k workstation and on an NT4 server....

We wanted to continue to use the old because we've always
done it that way <grin>. Actually, the real reason is we
needed an unzip which did not ask for any user input... it
is extracted from a batch file. I will look at Info-Zip.

But I think I found the problem. When you try to run a
nonexistant program on W2K you get the message "xxx is not
recognized as an internal or external command, operable
program or batchfile". When we run this we get "Bad
Command or file name" so the program exists and trys to
run. I looked at the directory using the /X switch. Our
self extracting zip file name was 9 characters
(XSOFTWARE.EXE), but the directory listing did not show an
8.3 name (XSOFTW~1.EXE) like it does on the W2k desktop
where the extract works. I renamed the file to conform to
an 8.3 name (XSFTWARE.EXE) and LO AND BEHOLD, it runs and
extracts.

I guess I'll research on the changes to the automatic
creation of 8.3 names by Windows...

Thanks everyone!
 
In said:
The ZIP file is fine, it opens with WinZip and self
extracts on my W2k workstation and on an NT4 server....

We wanted to continue to use the old because we've always
done it that way <grin>. Actually, the real reason is we
needed an unzip which did not ask for any user input... it
is extracted from a batch file. I will look at Info-Zip.

But I think I found the problem. When you try to run a
nonexistant program on W2K you get the message "xxx is not
recognized as an internal or external command, operable
program or batchfile". When we run this we get "Bad
Command or file name" so the program exists and trys to
run. I looked at the directory using the /X switch. Our
self extracting zip file name was 9 characters
(XSOFTWARE.EXE), but the directory listing did not show an
8.3 name (XSOFTW~1.EXE) like it does on the W2k desktop
where the extract works. I renamed the file to conform to
an 8.3 name (XSFTWARE.EXE) and LO AND BEHOLD, it runs and
extracts.

I guess I'll research on the changes to the automatic
creation of 8.3 names by Windows...
Click to expand...

Yes, that may have been disabled on the server.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\
NtfsDisable8dot3NameCreation=
a DWORD value
But check that beforehand.

I recommend Info-Zip, but it may be too much change for diehard DOS
pkzip fans. :-)
 
Back
Top