1
Applications / Solved: Warp 4/4.52 under Virtualbox: can't unzip, emx, warpin, ... - SYS3170
« on: January 02, 2023, 07:37:59 pm »
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
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