Problem with Self-extracting DOS Archive
Hi all, currently I have the problem to unpack an archive file which was packed as self extractor in 1998. I guess that this file was created with the operating system W...95. The associated file archiver was ARJ 2.55b ALPHA TESTWARE Copyright (c) 1990-96 ARJ Software. Jul 16 1996. which works/has worked on DOS level. The core problem is apparently now that obviously the created self-extracting archive is not extractable across different operating systems, because the runtime environment is completely different today (e.g. 32-bit --> 64-bit, etc.). Presumably, the self-extracting archive can only be extracted under the operating system. Unfortunately I don't have an old operating system to try this, nor the hardware used at the time of packing to run it. I have now tried to solve my problem with the DOSBox 0.74-3 program. The existing ARJ.EXE packing program can apparently be started normally with it. However, the existing self-extracting archive does not. In DOSBox the following error message is issued: This program cannot be run in DOS mode. Does anyone have an idea how to solve this problem? Mit freundlichen Grüßen / Kind regards Michael Kasimir Be Free, Be Linux
Le 05/02/2021 à 18:11, michael.kasimir@gmx.de a écrit :
Does anyone have an idea how to solve this problem?
freedos?? jdd -- http://dodin.org
Ok, never heard about freedos. Actually I have no empty USB stick at hand. After buying one, I will try it tomorrow...
Le 05/02/2021 à 19:48, Adam Mizerski a écrit :
W dniu 05.02.2021 o 18:18, jdd@dodin.org pisze:
Le 05/02/2021 à 18:11, michael.kasimir@gmx.de a écrit :
Does anyone have an idea how to solve this problem?
freedos??
maybe dosbox?
https://fr.wikipedia.org/wiki/FreeDOS jdd -- http://dodin.org
On Fri, Feb 05, 2021 at 06:11:32PM +0100, michael.kasimir@gmx.de wrote:
Hi all,
currently I have the problem to unpack an archive file which was packed as self extractor in 1998. I guess that this file was created with the operating system W...95. The associated file archiver was ARJ 2.55b ALPHA TESTWARE Copyright (c) 1990-96 ARJ Software. Jul 16 1996.
which works/has worked on DOS level. The core problem is apparently now that obviously the created self-extracting archive is not extractable across different operating systems, because the runtime environment is completely different today (e.g. 32-bit --> 64-bit, etc.). Presumably, the self-extracting archive can only be extracted under the operating system.
Unfortunately I don't have an old operating system to try this, nor the hardware used at the time of packing to run it.
I have now tried to solve my problem with the DOSBox 0.74-3 program. The existing ARJ.EXE packing program can apparently be started normally with it. However, the existing self-extracting archive does not. In DOSBox the following error message is issued: This program cannot be run in DOS mode.
Does anyone have an idea how to solve this problem?
Try using unarj: unarj FILE Ciao, Marcus
in the description at https://software.opensuse.org/package/unarj you will find 'Unarj allows for unpacking of .arj files,...' Preliminary note: as described above, my files are self extracting archive .exe I could find only a community package at: https://download.opensuse.org/repositories/home:/Sauerland/openSUSE_Leap_15.... package executing supplied the follwing result: # unarj x Lager32.exe UNARJ (Demo version) 2.63 Copyright (c) 1991-2000 ARJ Software, Inc. Includes patches applied by SUSE/Novell 2003-2004. Processing archive: Lager32.exe Lager32.exe is not an ARJ archive #
Am 05.02.21 um 18:11 schrieb michael.kasimir@gmx.de:
Hi all,
self extractor in 1998. I guess that this file was created with the operating
Does anyone have an idea how to solve this problem?
This program cannot be run in DOS mode.
1) this indicates that you have to run it on windows. for this i would use "wine" if not installed install it with yast then run: env WINEPREFIX="/home/yourhomename/.win32-test" env WINEARCH=win32 wine yourpackedprogramm.exe it depends if your selfextracting file will extract inside your actual directory, or somewhere inside /home/yourhomename/.win32-test (invisible directory) 2) if you do not get it running and its only one or two files you could send it me private, i have still some win98 runnning (in qemu and on real hardware) i would scan it via virustotal.com and if ok, then extract it for you. simoN -- www.becherer.de
Hi Simon, preliminary note: as above mentioned, the packaging has been carried with DOS-Program ARJ 2.55b. The use with wine I've tried already yesterday. The program run with: WINEPREFIX=~/.wine-new/ wine start /home/username/VT/Lager32.exe supplied the following substantial output: key0009:err:start:wmain Unknown option 'L"/home/username/VT/Lager32.exe" to which I cannot follow...
Am 05.02.21 um 19:52 schrieb Michael Kasimir:
Hi Simon,
preliminary note: as above mentioned, the packaging has been carried with DOS-Program ARJ 2.55b.
i do not think so, if so, it would be working with dosbox or another dos emulation. it ist packed with a windows version of arj. (i used 30 years in past as my first choice packer arj)
The use with wine I've tried already yesterday. The program run with: WINEPREFIX=~/.wine-new/ wine start /home/username/VT/Lager32.exe supplied the following substantial output:
key0009:err:start:wmain Unknown option 'L"/home/username/VT/Lager32.exe"
to which I cannot follow...
i told you the exact wine command: (your wine command is wrong!!!) env WINEPREFIX="/home/yourhomename/.win32-test" env WINEARCH=win32 wine /path/to/your/exe/Lager32.exe do not use the "start" ... maybe i am wrong, but start is for .bat files simoN -- www.becherer.de
On 05/02/2021 18.11, michael.kasimir@gmx.de wrote:
Hi all,
currently I have the problem to unpack an archive file which was packed as self extractor in 1998. I guess that this file was created with the operating system W...95. The associated file archiver was ARJ 2.55b ALPHA TESTWARE Copyright (c) 1990-96 ARJ Software. Jul 16 1996.
which works/has worked on DOS level. The core problem is apparently now that obviously the created self-extracting archive is not extractable across different operating systems, because the runtime environment is completely different today (e.g. 32-bit --> 64-bit, etc.). Presumably, the self-extracting archive can only be extracted under the operating system.
Unfortunately I don't have an old operating system to try this, nor the hardware used at the time of packing to run it.
I have now tried to solve my problem with the DOSBox 0.74-3 program. The existing ARJ.EXE packing program can apparently be started normally with it. However, the existing self-extracting archive does not. In DOSBox the following error message is issued: This program cannot be run in DOS mode.
That error means the program was made for Windows.
Does anyone have an idea how to solve this problem?
Well, you need to emulate windows, either with wine or virtualization. Have you tried on a modern windows machine? I don't think the 32/64 bit issue matters. Or 16 bits? I have forgotten. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
After installing FreeDOS on an USB Stick and starting FreeDOS today, I tried to execute the self-extracting archives I had here. The displayed screen showed: This program cannot be run in DOD mode. What else could I try?
Le 06/02/2021 à 13:33, Michael Kasimir a écrit :
After installing FreeDOS on an USB Stick and starting FreeDOS today, I tried to execute the self-extracting archives I had here. The displayed screen showed:
This program cannot be run in DOD mode. What else could I try?
a windows 95 virtual image?, may be? https://www.reddit.com/r/windows95/comments/8uoefs/windows_95_for_virtualbox... jdd -- http://dodin.org
@jdd Many thanks for the guidance. I downloaded the Windows 95 for VirtualBox.7z file. It contains the following: /Logs /Snapshots Windows 95.vbox Windows 95.vbox-prev Windows 95.vdi In Oracle VM VirtualBox Manager I added the downloaded Windows 95.vbox I see a new virtual button labeled Windows 95 which is switched off. If I hit the Start button, a VirtualBox Error message window appears, telling: No new session could be opened for the Windows 95 virtual machine. Details: The virtual machine 'Windows 95' has terminated unexpectedly during startup with exit code 1 (0x1). Errorcode: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df} and in an additional pop-up window, labeled VirtualBox - Error In suplibOsInit: Kernel driver not installed (rc=-1908) The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing '/sbin/vboxconfig' as root. If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information. where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. What to do next?
On 2/6/21 8:50 AM, Michael Kasimir wrote:
@jdd Many thanks for the guidance. I downloaded the Windows 95 for VirtualBox.7z file. It contains the following: /Logs /Snapshots Windows 95.vbox Windows 95.vbox-prev Windows 95.vdi
In Oracle VM VirtualBox Manager I added the downloaded Windows 95.vbox I see a new virtual button labeled Windows 95 which is switched off. If I hit the Start button, a VirtualBox Error message window appears, telling: No new session could be opened for the Windows 95 virtual machine. Details: The virtual machine 'Windows 95' has terminated unexpectedly during startup with exit code 1 (0x1).
Errorcode: NS_ERROR_FAILURE (0x80004005) Component: MachineWrap Interface: IMachine {85632c68-b5bb-4316-a900-5eb28d3413df}
and in an additional pop-up window, labeled VirtualBox - Error In suplibOsInit:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
'/sbin/vboxconfig'
as root.
If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
What to do next?
I ran into something like this not too long ago. My problem was caused by "Secure Boot" being enabled in the UEFI bios. I normally turn off secure boot, but I tried to install Win-10 first and didn't realize that Win-10 turns on secure boot even if it doesn't know the bios password! See if you can access the bios and turn off secure boot. This will allow the operating system to load unsigned kernel modules. I suppose doing this might decrease your security posture, but its not a big concern for Linux in my humble opinion. You could always turn it back on again after you've solved your archive issue. Good luck! Regards, Lew
Hi Lew, I checked bios preferences: o Secure Boot Configuration is off o Boot Mode is Legacy
Am Samstag, 6. Februar 2021, 17:50:49 CET schrieb Michael Kasimir:
Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
'/sbin/vboxconfi
Did you use the openSUSE Version of Virtualbox? Did you add the user to the group vboxusers? Did you check that kernel drivers are installed? rpm -qa | grep virtual HTH Axel
After a new cold start, I tried again to start the VM. After hit of start button, a VirtualBox Error message window appears, telling: No new session could be opened for the Windows 95 virtual machine. Details: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED). Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} don't know why this has changed. - used openSUSE Virtualbox Version: virtualbox-6.1.18-lp152.2.11.1.x86_64.rpm - installation of VirtualBox extension pack from https://download.virtualbox.org/virtualbox/6.1.18/Oracle_VM_VirtualBox_Exten... - user is added to the group vboxusers - terminal output is: :~> rpm -qa | grep virtual virtualbox-6.1.18-lp152.2.11.1.x86_64 libqt5-qtvirtualkeyboard-5.12.7-lp152.1.1.x86_64 virtualbox-kmp-default-6.1.18_k5.3.18_lp152.60-lp152.2.11.1.x86_64 libqt5-qtvirtualkeyboard-hunspell-5.12.7-lp152.1.1.x86_64 virtualbox-qt-6.1.18-lp152.2.11.1.x86_64 texlive-tex-virtual-academy-pl-2017.134.svn34177-lp152.6.2.noarch :~>
Enable virtualization in BIOS Schöne Grüße Axel -- Written from cell phone - excuses for typos Am 6. Februar 2021 18:41:56 WEZ schrieb Michael Kasimir <michael.kasimir@gmx.de>:
After a new cold start, I tried again to start the VM. After hit of start button, a VirtualBox Error message window appears, telling: No new session could be opened for the Windows 95 virtual machine. Details: VT-x is disabled in the BIOS for all CPU modes (VERR_VMX_MSR_ALL_VMX_DISABLED).
Fehlercode: NS_ERROR_FAILURE (0x80004005) Komponente: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
don't know why this has changed.
- used openSUSE Virtualbox Version: virtualbox-6.1.18-lp152.2.11.1.x86_64.rpm - installation of VirtualBox extension pack from https://download.virtualbox.org/virtualbox/6.1.18/Oracle_VM_VirtualBox_Exten... - user is added to the group vboxusers - terminal output is: :~> rpm -qa | grep virtual virtualbox-6.1.18-lp152.2.11.1.x86_64 libqt5-qtvirtualkeyboard-5.12.7-lp152.1.1.x86_64 virtualbox-kmp-default-6.1.18_k5.3.18_lp152.60-lp152.2.11.1.x86_64 libqt5-qtvirtualkeyboard-hunspell-5.12.7-lp152.1.1.x86_64 virtualbox-qt-6.1.18-lp152.2.11.1.x86_64 texlive-tex-virtual-academy-pl-2017.134.svn34177-lp152.6.2.noarch :~>
Hi Community, Many thanks. The enabling of Virualisation has changed it. The VirtualBox works now flawless! Win95 started! I can now head on with next steps...
Hi, I have now spend several hours to solve the real problem of self-extracting DOS archive with the offered virtual Win95 system. I fail to get the files into the virtual system. I think that I have done this correctly In openSUSE the USB Stick can be found at: Bus 001 Device 007: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB Flash Drive In VirtualBox: o USB-Controller enabled o USB-1.1-Controller (OHCI) o Filter for USB-Devices USBest Technology USB Mass Storage Device [0100] Manufacturer-ID: 1307 Product-ID: 0163 Revision-No: 0100 Manufacturer: USBest Technology Product: USB Mass Storage Device ... After start of Virtual Machine Win95 1) There is no error message related to the USB connection. 2) The following drives are shown: 3 1/2 Floppy (A:) Win95 (C:) 3 1/2 Floppy (D:) 3 1/2 Floppy (E:) 3 1/2 Floppy (F:) (G:) If I click the drives one after the other, a message box appears: 'Drive:\' is not accessible The device is not ready Retry Cancel So I cannot get access to the USB stick. Multiple reading of: https://www.virtualbox.org/manual/ch03.html#usb-support did not supply an answer... I can't figure out, what could be the reason for the behaviour? No Win95 support for USB?
Am 09.02.21 um 15:08 schrieb Michael Kasimir:
No Win95 support for USB?
IIRC USB support was in deed added only for Win98 SE. So you could try SMB to get files into a Win95 VM or mount the HDD image on the host. W.r.t. the latter, this post is a couple of years old, but from quickly glancing over it, it should still work (using qemu-nbd): https://forums.opensuse.org/showthread.php/469942-Mounting-Virtual-Box-Machi... HTH -- Till -- Dipl.-Inform. Till Dörges doerges@pre-sense.de PRESENSE Technologies GmbH Nagelsweg 41, D-20097 HH Geschäftsführer/Managing Directors AG Hamburg, HRB 107844 Till Dörges, Jürgen Sander USt-IdNr.: DE263765024
Em ter., 9 de fev. de 2021 às 11:56, Till Dörges <doerges@pre-sense.de> escreveu:
Am 09.02.21 um 15:08 schrieb Michael Kasimir:
No Win95 support for USB?
IIRC USB support was in deed added only for Win98 SE.
So you could try SMB to get files into a Win95 VM or mount the HDD image on the host.
W.r.t. the latter, this post is a couple of years old, but from quickly glancing over it, it should still work (using qemu-nbd):
https://forums.opensuse.org/showthread.php/469942-Mounting-Virtual-Box-Machi...
Hi, Maybe using a shared folder is simpler but I think it needs the guest addition so its a no-go. Another option is upload the file to some site like wetransfer and download it inside the VM Regards. Luiz
On Tue, Feb 9, 2021, 10:14 Luiz Fernando Ranghetti <elchevive68@gmail.c om> wrote:
Em ter., 9 de fev. de 2021 às 11:56, Till Dörges <doerges@pre-sense.d e> escreveu:
Am 09.02.21 um 15:08 schrieb Michael Kasimir:
No Win95 support for USB?
IIRC USB support was in deed added only for Win98 SE.
So you could try SMB to get files into a Win95 VM or mount the HDD image on the host.
W.r.t. the latter, this post is a couple of years old, but from quickly glancing over
it, it should still work (using qemu-nbd):
https://forums.opensuse.org/showthread.php/469942-Mounting-Virtual- Box-Machine-Images-on-a-Host
Hi,
Maybe using a shared folder is simpler but I think it needs the guest addition so its a no-go.
Another option is upload the file to some site like wetransfer and download it inside the VM .
I would be worried to let Win95 VM anywhere near internet. Using SMB may also be problematic since Win95 is probably pretty insecure SMB1 implementation most likely disabled in modern SMB implementation. If we consider doing all this complex VM dance as acceptable solution to simple task of extracting archive - then creating virtual disk smaller than 2GB with non-GPT fat16 formated partition is perhaps reliable way of transferring data in/out of win95 VM. * One would create the disk image ising virtualBox as raw and attach it to win 95 VM. Then mount it in the windows as another disk and format it. Shutdown the VM. * Mount the disk image in linux, copy the archive.exe to it and unmount it. * Start the VM, unpack the archive. Shutdown VM and access the unpacked data in Linux by mounting the disk image again. That being said, I find this needlessly complex solution to just uncompressing .exe file. Without knowing/seeing the archive - I would first try executing it in wine. If that is something you would like to try: * Install wine: sudo zypper install wine * copy the archive.exe to: .wine/drive_c/users/$USER/Downloads * Then run: wine .wine/drive_c/users/$USER/Downloads/archive.exe and see what happens If that works your extracted files are likely in: .wine/drive_c/users/$USER/Downloads If wine would not help, I would probably be looking for friend with windows to extract the files from the archive before resorting to win95 VM. Hope that helps, one way or the other, Tomas
Le 09/02/2021 à 15:08, Michael Kasimir a écrit :
Hi,
I have now spend several hours to solve the real problem of self-extracting DOS archive with the offered virtual Win95 system. I fail to get the files into the virtual system. I think that I have done this correctly
it's the hardest thing. I only could do it by downloading it from the net :-( jdd -- http://dodin.org
On 2021-02-09 15:08, Michael Kasimir wrote:
I have now spend several hours to solve the real problem of self-extracting DOS archive with the offered virtual Win95 system. I fail to get the files into the virtual system. I think that I have done this correctly
A bit late into the match but if I recall my win/dos days I seem to remember that winzip can handle arj but you need to install arj software. I did a quick recap and downloaded an earlier version of winzip (10.0 had gold standard at winehq) and opened one self extracting arj exe. It listed all the files in it but when I wanted to extract them winzip complained about the uninstalled arj software. So it seems it can be extracted that way. -- /bengan
@Bengt sorry to say that, but I've tried meanwhile almost everything outside the forum related to unpacking, such as 7z, arj, binwalk... But the essential problem is: listing the files contained in the archive does not solve the problem. I want to unzip them. And that has not worked in any of the examined cases...
On 2021-02-09 18:41, Michael Kasimir wrote:
listing the files contained in the archive does not solve the problem. I want to unzip them. And that has not worked in any of the examined cases...
I understand. It was a hint that it might be possible because of the positive result from winzip. And if you installed arj in wine it might work. But, I installed arj, patool, peazip, and engrampa in my tumbleweed. And then I went to dolphin and right clicked and let it guide me to which of them to open the self-extracting archive that I've got. It choose engrampa. Engrampa opened the archive and when I clicked extract it extracted the archive. I also tested peazip and same there. Now, I don't know if it's your archive or something but they can surely extract self-extracing ms-dos/windows archive. This is my archive: $ file arj284.exe arj284.exe: MS-DOS executable, MZ for MS-DOS, ARJ self-extracting archive -- /bengan
Am 09.02.21 um 15:08 schrieb Michael Kasimir:
Hi,
In VirtualBox:
i do not work with virtual box, always use qemu/kvm + virtmanager. but as i know qemu tools should be able to c onvert a virtualbox image to a qcow or raw image, both is easy to mount in linux, then you are able to copy files in, then (if virtual box did not work with raw images) you have to convert back, or start it with virt manager + qemu. here some commands to gave you a idea: =================================== first of all STOP your emulation!! then: ========================================= convert a image with qemu-img maybe look here: https://dannyda.com/2020/06/25/how-to-use-qemu-img-command-to-convert-betwee... =========================================== mounting a qcow image: modprobe nbd max_part=8 qemu-nbd --connect=/dev/nbd0 db1_old.qcow2 # as example, mount first partition mount /dev/nbd0p1 /mnt/ release the image: umount /mnt/ qemu-nbd --disconnect /dev/nbd0 =========================================== mount a raw image / raw disk: losetup -f /dev/loop0 losetup -P /dev/loop0 yourimage.img fdisk -l /dev/loop0 from this output look what partition you want to mount: (here second partition): mount /dev/loop0p2 /path/to/emty/directory/ copy now something in or out umount /path/to/emty/directory/ losetup -d /dev/loop0 ================================== start your emulation ================================== simoN -- www.becherer.de
On 09/02/2021 15.08, Michael Kasimir wrote:
Hi,
I have now spend several hours to solve the real problem of self-extracting DOS archive with the offered virtual Win95 system. I fail to get the files into the virtual system. I think that I have done this correctly
...
After start of Virtual Machine Win95 1) There is no error message related to the USB connection. 2) The following drives are shown: 3 1/2 Floppy (A:) Win95 (C:) 3 1/2 Floppy (D:) 3 1/2 Floppy (E:) 3 1/2 Floppy (F:) (G:)
You can mount a file image of the right size formatted as FAT, as a floppy. If the compressed file fits on it: ]> cer@Telcontar:/data/storage_a/vmware_isos> l floppy.file ]> -rw-r----- 1 cer vmware 1474560 May 27 2007 floppy.file ]> cer@Telcontar:/data/storage_a/vmware_isos> file floppy.file ]> floppy.file: DOS/MBR boot sector, code offset 0x3c+2, OEM-ID ",hMkeIHC" cached by Windows 9M, root entries 224, sectors 2880 (volumes <=32 MB), sectors/FAT 9, sectors/track 18, serial number 0x46596503, label: " ", FAT (12 bit), followed by FAT ]> cer@Telcontar:/data/storage_a/vmware_isos> Another possibility is download the file from the net, but the net being just your own computer, not internet. You run a web server or an ftp on your host and reach it from the virtual machine. Of course, I already have apache running, so that would not be a problem for me. Win95 also has a telnet client (not ssh). However, I would try with Wine again: Simon Becherer has commented on the command line you should try. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
Correction of my previous mail. (do not mount direct to /mnt (if not empty)) Am 09.02.21 um 15:08 schrieb Michael Kasimir:
Hi,
In VirtualBox:
i do not work with virtual box, always use qemu/kvm + virtmanager. but as i know qemu tools should be able to c onvert a virtualbox image to a qcow or raw image, both is easy to mount in linux, then you are able to copy files in, then (if virtual box did not work with raw images) you have to convert back, or start it with virt manager + qemu. here some commands to gave you a idea: =================================== first of all STOP your emulation!! then: ========================================= convert a image with qemu-img maybe look here: https://dannyda.com/2020/06/25/how-to-use-qemu-img-command-to-convert-betwee... =========================================== mounting a qcow image: modprobe nbd max_part=8 qemu-nbd --connect=/dev/nbd0 /path/to/your/image/db1_old.qcow2 # as example, mount first partition mount /dev/nbd0p1 /path/to/emty/directory/ copy files in. release the image: umount /path/to/emty/directory/ qemu-nbd --disconnect /dev/nbd0 =========================================== mount a raw image / raw disk: losetup -f /dev/loop0 losetup -P /dev/loop0 yourimage.img fdisk -l /dev/loop0 from this output look what partition you want to mount: (here second partition): mount /dev/loop0p2 /path/to/emty/directory/ copy now something in or out umount /path/to/emty/directory/ losetup -d /dev/loop0 ================================== start your emulation ================================== simoN -- www.becherer.de
On 2/6/21 1:33 PM, Michael Kasimir wrote:
After installing FreeDOS on an USB Stick and starting FreeDOS today, I tried to execute the self-extracting archives I had here. The displayed screen showed:
This program cannot be run in DOD mode. What else could I try?
Self extracting? Have you tried running unzip something.exe - Adam
On 2/25/21 12:45 PM, Adam Majer wrote:
On 2/6/21 1:33 PM, Michael Kasimir wrote:
After installing FreeDOS on an USB Stick and starting FreeDOS today, I tried to execute the self-extracting archives I had here. The displayed screen showed:
This program cannot be run in DOD mode. What else could I try?
Self extracting? Have you tried running
unzip something.exe
- Adam
Looks like we have broken threads in this discussion.... Always fun. - Adam
Op vrijdag 5 februari 2021 18:11:32 CET schreef michael.kasimir@gmx.de:
Hi all,
currently I have the problem to unpack an archive file which was packed as self extractor in 1998. I guess that this file was created with the operating system W...95. The associated file archiver was ARJ 2.55b ALPHA TESTWARE Copyright (c) 1990-96 ARJ Software. Jul 16 1996.
which works/has worked on DOS level. The core problem is apparently now that obviously the created self-extracting archive is not extractable across different operating systems, because the runtime environment is completely different today (e.g. 32-bit --> 64-bit, etc.). Presumably, the self-extracting archive can only be extracted under the operating system.
Unfortunately I don't have an old operating system to try this, nor the hardware used at the time of packing to run it.
I have now tried to solve my problem with the DOSBox 0.74-3 program. The existing ARJ.EXE packing program can apparently be started normally with it. However, the existing self-extracting archive does not. In DOSBox the following error message is issued: This program cannot be run in DOS mode.
Does anyone have an idea how to solve this problem?
Mit freundlichen Grüßen / Kind regards
Michael Kasimir
Be Free, Be Linux You might give unarj a chance, and run unarj arj.exe in some separate folder.
To find it, install opi and run opi unarj -- Gertjan Lettink a.k.a. Knurpht openSUSE Board openSUSE Forums Team
@Knurpht Also this step with the Sauerland's package I have already behind me... The problem here has been first that the installation of the ancient package lead to a file conflict, because I had installed arj. see here: unarj-2.65-lp152.10.1.x86_64 (Sauerland's Home Project (openSUSE_Leap_15.2)) arj-3.10.22-lp152.3.38.x86_64 (@System) So I had uninstalled arj to check this exam. Nevertheless the result is equal to ZERO. See here: $ unarj stock32.exe UNARJ (Demo version) 2.63 Copyright (c) 1991-2000 ARJ Software, Inc. Includes patches applied by SUSE/Novell 2003-2004. Processing archive: Lager32.exe Lager32.exe is not an ARJ archive Which is NOT true!
participants (16)
-
Adam Majer -
Adam Mizerski -
Axel Braun -
Axel Braun -
Bengt Gördén -
Carlos E. R. -
jdd＠dodin.org -
Knurpht-openSUSE -
Lew Wolfgang -
Luiz Fernando Ranghetti -
Marcus Meissner -
Michael Kasimir -
michael.kasimir＠gmx.de
-
Simon Becherer -
Till Dörges -
TomasK