Author Topic: [SOLVED] Warp 4/4.52 under Virtualbox: can't unzip, emx, warpin, ... - SYS3170  (Read 4344 times)

Heinrich

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
I installed Warp 3, 4 and 4.52 as VM under Virtualbox 7.0.4 in Arch-Linux.
All 3 work per se, even with 1600x1200 SVGA.
Under Warp 3 everything else I tried works too (also with SMP), e.g. emx-0.9d.

Under Warp 4 and 4.52, calling unzip results in an unresponsive DOS-window or SYS3170 for all unzip versions I tried (32-bit and 16-bit).
The same is true for some other utilities I've tested.
Warpin-1-0-26 yields "SYS1057 - file or pathname invalid in a DOS session",
when called from an OS2 window. Double-click in PM on warpin pops up a
window for a fraction of a second.

I tried many virtualization options (nested paging on/off,
PAE/NX on/off, Standard/KVM/Hyper, 1-4 CPU's ...): always the same result.

I compared the Config.sys of 3, 4 and 4.52 and found nothing unusual.

I can't install unzip, hence no zipped utilities. All self-extracting exe's that I tried return SYS3170.
Taking unzip552 as an example for the unzip's tried:
- 32-bit unzip.exe results an unresponsive DOS-window
- 32-bit funzip.exe yields SYS3170 (screenshot attached), same for 16-bit exe's.

What surprises me is that under the older Warp 3 everything works (in the case
of jm Graphics for emx only the PM window works (VESADLL=VESA_PM), but still).

Can someone explain to me what's going on?
« Last Edit: January 03, 2023, 01:31:12 am by Martin Iturbide »

roberto

  • Hero Member
  • *****
  • Posts: 820
  • Karma: +3/-6
    • View Profile
Re: Warp 4/4.52 under Virtualbox: can't unzip, emx, warpin, ... - SYS3170
« Reply #1 on: December 22, 2022, 06:26:37 pm »
I think I remember that the W3, used the PKZIP, instead of the Zip Unzip.
saludos

Heinrich

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Warp 4/4.52 under Virtualbox: can't unzip, emx, warpin, ... - SYS3170
« Reply #2 on: December 22, 2022, 07:49:40 pm »
I've installed unzip in Warp 3 and used this to unpack archives
(pkunzip does not work with several archives).

Tom

  • Full Member
  • ***
  • Posts: 197
  • Karma: +5/-0
    • View Profile
Re: Warp 4/4.52 under Virtualbox: can't unzip, emx, warpin, ... - SYS3170
« Reply #3 on: December 23, 2022, 12:52:37 am »
I installed Warp 3, 4 and 4.52 as VM under Virtualbox 7.0.4 in Arch-Linux.
All 3 work per se, even with 1600x1200 SVGA.
Under Warp 3 everything else I tried works too (also with SMP), e.g. emx-0.9d.

Under Warp 4 and 4.52, calling unzip results in an unresponsive DOS-window or SYS3170 for all unzip versions I tried (32-bit and 16-bit).
The same is true for some other utilities I've tested.
Warpin-1-0-26 yields "SYS1057 - file or pathname invalid in a DOS session",
when called from an OS2 window. Double-click in PM on warpin pops up a
window for a fraction of a second.

I tried many virtualization options (nested paging on/off,
PAE/NX on/off, Standard/KVM/Hyper, 1-4 CPU's ...): always the same result.

I compared the Config.sys of 3, 4 and 4.52 and found nothing unusual.

I can't install unzip, hence no zipped utilities. All self-extracting exe's that I tried return SYS3170.
Taking unzip552 as an example for the unzip's tried:
- 32-bit unzip.exe results an unresponsive DOS-window
- 32-bit funzip.exe yields SYS3170 (screenshot attached), same for 16-bit exe's.

What surprises me is that under the older Warp 3 everything works (in the case
of jm Graphics for emx only the PM window works (VESADLL=VESA_PM), but still).

Can someone explain to me what's going on?

Some questions for you.

When you say that you try calling Warpin-1-0-26 from an OS/2 window:
  • what is the exact filename of the excecutable you try to run? Is it warpin.exe or is it warpin-1-0-26.exe?
  • And what is the name of the directory into which that executable resides? Is it warpin or is it warpin-1-0-26?
  • Which filesystem is used inside your Warp 4 and Warp 4.52 VMs? Is it maybe FAT, or is it HPFS or even JFS (Warp 4.52)?

What I find strange in the picture you attached, is that it mentions exception 330d0686. I have never heard of such an exception.

Martin Iturbide

  • OS2World NewsMaster
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 4816
  • Karma: +42/-1
  • Your Friend Wil Declares...
    • View Profile
    • Martin's Personal Blog
Re: Warp 4/4.52 under Virtualbox: can't unzip, emx, warpin, ... - SYS3170
« Reply #4 on: December 23, 2022, 02:51:15 am »
Hi Heinrich

Just as a general comment, it is also interesting to generate a OVA of you OS/2 installations on VirtualBox so you can backup and move arround your VMs.  It is on "File - Export" on VirtualBox. There are some OS/2 OVAs at Archive.org.

Regards

Martin Iturbide
OS2World NewsMaster
... just share the dream.

Heinrich

  • Newbie
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Everything has been settled. As I had secretly feared - it was something really stupid:

I had downloaded all the zip and self-extracting exe files and linux and then picked them up from OS/2 using the ftp program. With Warp 3 this worked. With the Warp 4/4.52 ftp client, however, I should have explicitly switched on binary mode. When a warpin-1-0-22 from an iso image worked and the one I transfered via ftp didn't, it dawned on me that something like this was sometimes necessary in the past. Therefore, with Warp 4.x, all binary files were corrupted in a way that resulted in the obscure error messages reported. With the entry of "binary" at the beginning of the ftp session, everything worked under Warp 4.x.

I've been using ncftp for ftp transfers for a long time. Ncftp automatically switches to binary mode (which Warp 3's ftp client either does, or runs in binary mode by default).

Many thanks to all.

Happy new year,
Heinrich
« Last Edit: January 02, 2023, 07:41:10 pm by Heinrich »