Okay, this application - custom designed and developed cad tool originally developed in an IRAD running on dos 16-bit and runs fine native dos on Windows XP 32-bit machines either full-screen or in a window, now runs on DOSBOX .74 emulation on my HP Windows 7 Pro 64-bit quad-core notebook. Two problems: Problem 1: On my system an algorithm, call it ASAP (Airborne Sensor Avionics Program) that runs native dos on my Windows XP laptop in 29 minutes and another, for example, a C4GPU (Command,Control,Communications,Computer on Graphics Processor Unit ASIC) run native dos in ~45 minutes. On DOSBOX, on the 64-bit quad (DOSBOX options cycles=maximum, no other), no attempt (pretty useless anyway based on past experience) to boost Windows 7 DOSBOX process priority via Task Manager, requires ~12 hours to complete for ASAP and ~14 hours for C4GPU.
The emulation mode slowdown seems rather excessive, over an order of magnitude. The application, RMATE3 performs schdulability analysis of tasks (threads) and their module (methods) aggregation in mission-critical real-time embedded environments. The problem complexity, in general is combinatorial NP-Hard, e.g. an application of hundreds of tasks and thousands of modules might take ten to a hundred years to run to completion even native mode dos--the examples mentioned are low double digit data files. The fact that the application should have been re-developed to run on a super mainframe is spilt milk. Second problem: a friend on west coast with Ubuntu/Windows 7 Pro quad-core duel-boot tower PC also loaded with DOSBOX .74 is unable to read data files on the application running from DOSBOX (on either Linux or Windows) though the tool executes fine (but just as slowly as my experience, similar options) working in interactive mode -- building a threads/module software model. Don't really expect a reply, just ranting to express my frustration. -K 😒