Sopdf
Author: p | 2025-04-24
Automatically exported from code.google.com/p/sopdf - Proggggger/sopdf Linux port of sopdf. Contribute to viric/sopdf-linux development by creating an account on GitHub.
SoPDF/SoPDF.sln at master ststeiger/SoPDF - GitHub
You can open the .exe in a text editor and look at the first two letters to tell if it's compatible with 16-bit DOS. According to the Wikipedia article, if the first two letters are "MZ" or "NE" then the program is 16-bit DOS-compatible. However, that's a little misleading. It might only be able to run in 16-bit mode just well enough to tell you, "This program cannot be run in DOS mode." Unfortunately, this is the case with soPDF (open it in Notepad and see for yourself).Installing Win32s is probably your only hope of getting it to run. However, I'm not sure if you can run Win32s in DOS or if you have to run it from Windows 3.11. I'm also not sure if soPDF has any other prerequisites which have no hope of running even under Win32s.You should be able to test the program in DOSBox. Although I assume it only supports 16-bit DOS applications, I can't find a definitive answer, so setting up a VMware, VirtualBox, or VirtualPC DOS installation (as David suggested) might be the easiest and most surefire way to test it.If it wasn't as simple as opening the .exe in Notepad, you could have used DependencyWalker to see if soPDF was a 32-bit or 64-bit app.Also, if I recall correctly, 16-bit apps run inside a WOW.EXE or maybe WOW16.EXE (Windows On Windows) process, which you should be able to see under the Processes tab in Task Manager if you try to run a 16-bit
sopdf/soPdf.sln at master Proggggger/sopdf - GitHub
SoPDF/.gitattributes at master ststeiger/SoPDF - GitHub
. Automatically exported from code.google.com/p/sopdf - Proggggger/sopdfsopdf/soPdf.suo at master Proggggger/sopdf - GitHub
Sopdf - Sopdf updated their cover photo. - Facebook
viric/sopdf-linux: Linux port of sopdf - GitHub
. Automatically exported from code.google.com/p/sopdf - Proggggger/sopdfComments
You can open the .exe in a text editor and look at the first two letters to tell if it's compatible with 16-bit DOS. According to the Wikipedia article, if the first two letters are "MZ" or "NE" then the program is 16-bit DOS-compatible. However, that's a little misleading. It might only be able to run in 16-bit mode just well enough to tell you, "This program cannot be run in DOS mode." Unfortunately, this is the case with soPDF (open it in Notepad and see for yourself).Installing Win32s is probably your only hope of getting it to run. However, I'm not sure if you can run Win32s in DOS or if you have to run it from Windows 3.11. I'm also not sure if soPDF has any other prerequisites which have no hope of running even under Win32s.You should be able to test the program in DOSBox. Although I assume it only supports 16-bit DOS applications, I can't find a definitive answer, so setting up a VMware, VirtualBox, or VirtualPC DOS installation (as David suggested) might be the easiest and most surefire way to test it.If it wasn't as simple as opening the .exe in Notepad, you could have used DependencyWalker to see if soPDF was a 32-bit or 64-bit app.Also, if I recall correctly, 16-bit apps run inside a WOW.EXE or maybe WOW16.EXE (Windows On Windows) process, which you should be able to see under the Processes tab in Task Manager if you try to run a 16-bit
2025-04-10