Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Andreas Schnellbacher

Pages: [1] 2 3 ... 35
Here's the version that fixes the misleading output. I had to zip the .cmd file, because of the extension restrictions here.

Code: [Select]
* 2019-10-13  -  Changed error message and reset RC if key was already
*                deleted.
*             -  Fixed typos in the header.

I had many situations where cleanini forces the write of the ini entry, which leads to that bug.

In fact, checkini and cleanini won't help with that. You can use Rich's FPos for that, but have to do it manually.

Having found some old os2world discussions about this I tried running RmDesktopFolderPos.cmd which generated this output and left the Desktop as it was:-

Error: 218466@10 was not found in PM_Workplace:FolderPos.

Does not look like that will help then...
Probably wrong, it works here well. The "Error" message is just a bit misleading. Background:

The entry is written by the desktop not in every session. Therefore the cmd won't find it always, which is a good sign, and gives that error message. I already have a version here, which behaves better in the output, but I also wanted to add installation for that script before releasing the next version. Let's see.

Doug's idea was it to place that script in an XWP shutdown folder. That works well for me since years and sooner or later the problem occurs on systems without that script.

BTW: In the future, IFX might make that utility superfluous, by doing the same.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 28, 2020, 01:04:47 am »
Question: Don't you want to activate the touch option?
Is this an option in your installer package?
Yes, dosbox-createwpi.cmd, line 211.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 26, 2020, 10:59:04 pm »
It works now!

I had to update the .rpm packages again. libc was available in a newer version. (I guess that one contains libcn0.dll, but I wonder why they're not compatible.) I have installed that with ANPM. Due to its package priority list, libc installation forces a reboot.

After that, The next package shows endless repeating that it downloads gmp.

I killed anpm.exe and python.exe and then executed in a command line:

Code: [Select]
yum update
That works. It installs all the remaining 11 packages, including gmp. After that, I started ANPM again and it shows that all packages are recent.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 26, 2020, 10:14:21 pm »
I have two problems:

1) All four program objects close just after start. I see a window flashing. That did't happen with Dave's build. (ANPM showed a few days ago that every .rpm is recent.)

2) The WarpIN installation complains that the file README.OS2 already exists with a newer date. On scanning the archive, I find it only in package 1. I can't explain that, esp. because on the second try, I have wiped the destination dir before. (But the installation marks all existing files with an EA, so that no old files should exist after installation.)
That requires user input. It doesn't matter which option is selected.

Question: Don't you want to activate the touch option?

Here's the command line output from the failed start:
Code: [Select]
epm: C:\Programs\DOSBox > dosbox.exe
DOSBox version SVN
Copyright 2002-2020 DOSBox Team, published under GNU GPL.
CONFIG: Loading primary settings from config file dosbox.conf
Your fullscreen resolution can NOT be determined, it's assumed to be 1024x768.
Please edit the configuration file if this value is wrong.
terminate called after throwing an instance of 'char*'

Killed by SIGABRT
pid=0x065d ppid=0x065b tid=0x0001 slot=0x00a8 pri=0x0214 mc=0x0001 ps=0x0010
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

epm: C:\Programs\DOSBox >

And here's the output from popuplog.os2:

Code: [Select]

05-26-2020  21:53:29  SYS2070  PID 05da  TID 0001  Slot 009f

Interesting, libcn0.dll.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 26, 2020, 08:48:03 pm »
To avoid confusion: netlabs-exp is not required to run that build. According to Silvan and Jochen, it even builds without it.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 26, 2020, 08:45:45 pm »
mount e e:
That works for me both in full screen and in window mode. In your example it's strange that it uses C: instead of the specified E drive letter. Z: is the system drive.

I'm using Dave's build he has posted here.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 24, 2020, 09:32:35 pm »
About the "Recompiling"-Variants: I've found Jochen's answer. Roughly translated:

Jochen wrote: Recompiling is a kind of JIT. This option exists only for the x86 versions of DOSBox. Furthermore he wrote that he decided to create another .exe for that 16 years ago, but had also the idea how to add that feature to the configuration.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 24, 2020, 08:57:30 pm »
... and the .wpi builds, installs and works well. I've just tested my newly-built dosbox074_2020-05-24.wpi. It installs also the .xqs file without modification of the creation script.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 24, 2020, 08:30:07 pm »
Hi Dave,

your build fixes the issue for me as well, great!

What still doesn't work, is dosbox_rec.exe, The "Recompiling" variant of dosbox.exe. I asked Jochen about the difference to the normal version, but can't remember/find his explanation.

BTW: I have a full-featured installer ready since last summer. I have to contact Jochen again.

To your question: No, I don't have tested DOSBox/2 over network. In fact, I don't use DOSBox/2 at all, just made the install scripts.

Utilities / Re: MeShell commandline frontend timetable
« on: May 24, 2020, 08:13:57 pm »
Lots of *nix utilities default to inputting from stdin, and some use a single dash as a parameter for using stdin. Likewise for outputting to stdout if no file name.
Sure, I remember that behavior for all TeX compilers.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 24, 2020, 01:06:52 am »
It is a long time ago that I installed DosBox, I'm not on the latest and I do now that it is important to have a right dosbox.conf. At first it did not start on my system because I didn't have this file correctly.
Sure, that is known. My installation creates a valid one if it doesn't exist.

Here's my README.OS2 version, see the section "Basic configuration":

Code: [Select]


   DOSBox is a DOS emulator that uses the SDL library which makes DOSBox very
   easy to port to different platforms. DOSBox has already been ported to
   many different platforms, such as Windows, BeOS, Linux, MacOS X etc.

   DOSBox also emulates CPU:286/386 realmode/protected mode, Directory
   FileSystem/XMS/EMS, Tandy/Hercules/CGA/EGA/VGA/VESA graphics, a
   SoundBlaster/Gravis Ultra Sound card for excellent sound compatibility
   with older games etc.

   You can "re-live" the good old days with the help of DOSBox, it can run
   plenty of the old classics that don't run on your new computer!

   DOSBox is totally free of charge and open source.



   GNU General Public License (GPL) version 2.


   OS/2 port

   OS/2 package maintained by Jochen Schäfer.
   Icons provided by David Graser.
   Installation scripts and packaging by Andreas Schnellbacher.

   If you have problems with running DOSBOX, please contact me:
   josch (at)


   Web sites

   DOSBox/2 for OS/2 and eCS Web Site:

   DOSBox Official Web Site:



   The WarpIN installation is complex and feature-rich for maximal
   convenience. Usually a log file is created for easier error-catching.

   System DLLs

   Used system DLLs are checked for existence. On the WarpIN 'DLL detection'
   page, all DLLs and their states are listed.

   When missing system DLLs are detected, the package 'DOSBox/2 Support DLLs'
   is activated on the Packages page. Missing DLLs are then installed by a
   call to yum. That requires an RPM/YUM installation.

   This package doesn't provide the support DLLs anymore. If you didn't
   already install the DLLs, or don't use RPM/YUM, you can fetch the DLLs
   from here:

   For maximal compatibility with other applications, please don't use
   outdated DLLs.


   The current version can be installed over an old one without

   The previously installed language package is selected automatically. Note
   that this applies only to systems where at least version 0,74.3 is

   On updating an existing version, old files that don't stem from the
   current installation, are deleted. That applies also to system DLLs within
   the DOSBox installation directory. (Old versions provided the installation
   of all used system DLLs.)

   Language setup

   On selecting and installing a language package, the configuration file
   dosbox.conf is automatically edited. For more details, see the section
   'Basic configuration' below.

   Note that this file is copied from the eng subdirectory to the
   installation directory, if it doesn't exist.

   When multiple languages are selected, then the last one in the list wins.

   Verbosity and Configuration, Installation and Distribution (CID)

   The verbosity during installation can be controlled in three ways: Logfile
   output, messages and error beeps. For configuration, environment variables
   can be used:
      Environment var.  Default  CID
      DOSBOX_INSTCID       0      1 (1 sets all other values)
      DOSBOX_INSTLOG       1      1
      DOSBOX_INSTMSG       1      0
      DOSBOX_INSTBEEP      0      0

   The default installation method is manually. Therefore both log file
   output and messages are activated. 'Messages' means that in case of an
   error, message boxes pop up that need interaction. For an automated (CID)
   installation, these messages are unwanted. To achieve that, set the
   environment variable


   Log files

   The log file is named dosbox_inst.log. It is usually written to the
   directory pointed to by the environment variable LOGFILES. Its value is


   If that directory doesn't exist, it is created in DOSBox\inst. If the
   DOSBox installation directory is not found, it is created in the path of
   the WarpIN archive.

   Three generations of LOG files are kept:

      dosbox_inst.log    (newest one)

   REXX version

   The installation was tested with Classic REXX. It may lead to
   unpredictable results when Object REXX is used.


   Basic configuration

   For configuration, the file 'dosbox.conf' in the directory of 'dosbox.exe'
   (dosbox directory) can be used. For OS/2, an English version is copied
   from the 'eng' subdirectory to the dosbox directory, but only, if it
   doesn't already exist.


   To activate one of the optionally installed .lng or .lang files, ensure
   that dosbox.conf contains the following entry:


   <language_filename> should be replaced by e.g. 'deu.lng'. This file should
   either be placed in the directory of 'dosbox.exe' or the 'language' value
   must also include the subpath or full path of that .lng file. This entry
   must match and the file must exist. Otherwise DOSBox creates a trap on its

   Alternatively, you can also use the 'dosbox.exe' parameters:

     -lang <language_filename>
     -conf <config_filename>


   In the OS/2 version, the keyboard layout is not selected automatically.
   The 'auto' value for 'keyboardlayout', which is the default, doesn't seem
   to work:


   It can be changed by changing the 'keyboardlayout' value. E.g. for using
   German keyboard layout with the default codepage 858 (similar to 850, but
   contains the Euro sign), add this to 'dosbox.conf':


   Alternatively, it can be changed with the 'keyb' command:

      keyb gr

   Some usual keyboard layout values for existing translations:

      us       eng  English
      gr       deu  German
      fr       fra  French
      it       ita  Italian
      no       nor  Norwegian
      ru       rus  Russian
      cz       cze  Czech
      dk       dan  Danish
      es       esp  Spanish
      fi       fin  Finnish
      hu       hun  Hungarian
               kor  Korean (DBCS)
      nl       ned  Dutch
      pl       pol  Polish
      po       prt  Portuguese
      tr       tur  Turkish

   See the table in 'KEYB\layouts.txt', column 'File' for more keyboard
   layouts and section '8. Keyboard Layout' in 'README'.

   Also bundled is mKEYB, a replacement of KEYB, which has the keyboard
   tables compiled in. See the help file in 'mkeyb\README.TXT'.

   Configuration file with NLS comments

   A recent and complete config file with NLS comments can be created as a
   starting point:

      o  Add the language file and the keyboard layout values to
         'dosbox.conf', as described above.

      o  Start 'dosbox.exe' with an existing 'dosbox.conf'.

      o  From the host system, rename 'dosbox.conf' to 'dosbox.conf.bak'.

      o  Export the current configuration, together with NLS comments to the
         dosbox directory:

            config -wcp dosbox.conf

         This new file contains the values of the renamed file 'dosbox.conf'
         from the startup of DOSBox and NLS comments, if the 'language'
         value was configured before.

   You can also use one of the examples in the NLS subdirectories as

   Mount host directories as local drives

   For mounting host directories, use the mount command:

      mount <local_drive_letter> <host_dir>


      mount D F:\Apps\DOSBox

   Further information

   See the detailed descriptions in 'README', sections '4. Internal Programs'
   and '3. Command Line Parameters'.

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 23, 2020, 11:22:13 pm »
Here's the log from trying out my recent .wpi build with the binaries from the last released DOSBOX0.74_30.03.19.EXE. The installation works and finds no DLLs that require installation, but the first startup of dosbox.exe fails:

Code: [Select]
epm: C:\Programs\DOSBox > dosbox.exe
DOSBox version SVN
Copyright 2002-2019 DOSBox Team, published under GNU GPL.

Killed by SIGSEGV
pid=0x0c88 ppid=0x0c86 tid=0x0001 slot=0x009a pri=0x0200 mc=0x0001 ps=0x0010
STDCPP6 0:0001b26d
cs:eip=005b:1c94b26d      ss:esp=0053:0289fb20      ebp=0289fb38
 ds=0053      es=0053      fs=150b      gs=0000     efl=00010287
eax=0289fe2c ebx=00000000 ecx=17bc5f00 edx=17bc5f00 edi=0289feb8 esi=0289fb5c
Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it.

epm: C:\Programs\DOSBox >

Applications / Re: DOSBox Issue - STDCPP6?
« on: May 23, 2020, 10:51:35 pm »
I have probably the same problem here. I don't know, if that's caused by SMP or by the updated \usr\lib files. I guess, the first. I've changed on 2020-04-04 from an 15-years old system to a more recent AMD FM2+ system with 4 cores.

Since I've written the WarpIN macros for the next version, I had tried the installation on the newer system with the result that DOSBox isn't working. Unfortunately I haven't tried that before on that machine. It works well in my ArcaOS VirtualBox guest on a different system.

I haven't addressed Jochen so far and haven't heard from him since a long time.

Pages: [1] 2 3 ... 35