Unzip Version 6.0 hangs when booting to a commandline

[Lars]

I recently had the need to boot to a commandline (hitting F2 on boot) and to use UNZIP to overwrite a couple of files that would prevent proper system operation.
However, when I called the "unzip.exe" version 6.00 that is installed via YUM, the bootup commandline would hang and the unzip help screen would never show up.
When I instead used the "unzip.exe" version 5.52 that is still in my ECS\BIN subdirectory, it would properly work without such a problem. I am sure it is not a DLL loading problem as the LIBPATH setting is the same as for the regular boot, but of course, the newer UNZIP uses different DLLs (gcc, libcn0) than the older version (which directly uses the OS/2 API).

Anyone knows what's going on or how to fix that ?

Lars

[Neil Waldhauer]

I keep around a 2nd copy of unzip.exe for these purposes. This one is statically linked, and requires only DOSCALLS, KBDCALLS, VIOCALLS, NLS and MSG.

5-26-09  13:06         248,768    124  unzip.exe

http://www.os2site.com/sw/util/archiver/zip/unz600.exe

The other course could be to update the libpath for the F2 command line to include the needed DLLs.

[Lars]

As I said, the used LIBPATH is the same for the commandline boot and the operational boot. I also do mot get an error on missing DLLs.

[Dave Yeo]

Could unzip or more likely, one of its dependents have WINDOWAPI declared in a DEF file? I quickly looked at the source of unzip and the def file hasn't been changed in ages and is simply, https://github.com/bitwiseworks/unzip-os2/blob/master/os2/unzip.def

Code: [Select]

NAME WINDOWCOMPAT NEWFILES
DESCRIPTION 'The world-famous Info-ZIP unarchiving utilities'
; SEGMENTS
;   _MSGSEG32 CLASS 'CODE'

Not sure if it is currently used.

[Martin Iturbide]

Hello

I just wanted to test it too. Indeed on the VM (ArcaOS 5.0.7 ), the unzip.exe hangs when you boot with Alt+F1 and F2 for command line.
(It also fails here)

I don't recall which was the config.sys for that F2 boot. config.1 or config.x ?

For what I see on the F2 boot the %LIBPATH% is not recognized, but the config files looks fine. Is there any elegant way to see full the enviroment variables on the command line (image LIBPATH_F2.png )?

Regards

[Tom]

I recently had the need to boot to a commandline (hitting F2 on boot) and to use UNZIP to overwrite a couple of files that would prevent proper system operation.
However, when I called the "unzip.exe" version 6.00 that is installed via YUM, the bootup commandline would hang and the unzip help screen would never show up.
When I instead used the "unzip.exe" version 5.52 that is still in my ECS\BIN subdirectory, it would properly work without such a problem. I am sure it is not a DLL loading problem as the LIBPATH setting is the same as for the regular boot, but of course, the newer UNZIP uses different DLLs (gcc, libcn0) than the older version (which directly uses the OS/2 API).

Anyone knows what's going on or how to fix that ?

Lars

When using the commandline boot with Alt+F1  --> F2, the system boots using ?:\os2\boot\config.x instead of ?:\config.sys .
I would compare config.x and config.sys .

[Tom]

As I said, the used LIBPATH is the same for the commandline boot and the operational boot. I also do mot get an error on missing DLLs.

Is there an entry in \popuplog.os2 ?
Unfortunately it is not possible to use PMDLL when booted to a commandline, and I don't know about an existing VIO-equivalent.

[Tom]

Hello

I just wanted to test it too. Indeed on the VM (ArcaOS 5.0.7 ), the unzip.exe hangs when you boot with Alt+F1 and F2 for command line.
(It also fails here)

I don't recall which was the config.sys for that F2 boot. config.1 or config.x ?

For what I see on the F2 boot the %LIBPATH% is not recognized, but the config files looks fine. Is there any elegant way to see full the enviroment variables on the command line (image LIBPATH_F2.png )?

Regards

For a F2-boot ?:\os2\boot\config.x is used (read the description on the line that starts with F2 when you have used Alt+F1).

LIBPATH is not an environment variable (in config.sys there is a line that starts with LIBPATH=..., but not a line that starts with SET LIBPATH=...).
So trying to use %LIBPATH% does not work.

Seeing all environment variables is easy: on a commandline type

SET | more

(or pipe the output of SET to a file: SET > somefile.name)

[Dave Yeo]

Also the env command will list all variables. env | less

[Andi B.]

Unfortunately it is not possible to use PMDLL when booted to a commandline, and I don't know about an existing VIO-equivalent.

chkdll32.exe. Not tested if it works from ALT-F1.

[Lars]

The problem is not that a DLL could not be found as that should show up as a load error.

The problem is that starting unzip.exe simply hangs the (boot) commandline, a simple "unzip.exe" will not even show the help text (listing the options).

As others have already stated, the older UNZIP 5.52 is linked against the very basic OS/2 DLLs (like DOSCALLS, MSG etc.) and works just fine.

[Lars]

Could unzip or more likely, one of its dependents have WINDOWAPI declared in a DEF file? I quickly looked at the source of unzip and the def file hasn't been changed in ages and is simply, https://github.com/bitwiseworks/unzip-os2/blob/master/os2/unzip.def

Code: [Select]

NAME WINDOWCOMPAT NEWFILES
DESCRIPTION 'The world-famous Info-ZIP unarchiving utilities'
; SEGMENTS
;   _MSGSEG32 CLASS 'CODE'

Not sure if it is currently used.

But the DEF file says WINDOWCOMPAT and that is the correct value to use.
But NEWFILES is suspicious. At least, it should no longer be necessary under OS/2 32-bit.

[Dave Yeo]

I was wondering about the dependencies, which are few. Does bzip2 run under the command prompt?

[Martin Iturbide]

I was wondering about the dependencies, which are few. Does bzip2 run under the command prompt?

On F2 boot mode, bzip2.exe also hangs without giving any message.

Regards

[Doug Bissett]

The modern ZIP.EXE does not work in a command line boot. Use

Code: [Select]

C:\sys\install\ZIP2.EXEwhich is the OLD standalone ZIP.  note that the OLD ZIP cannot do files larger than 2GB (in, or out).