![]() So we might be able to use either of those, and possible even vDos, as long as I don't use the Clarion 2.1 debugger in the emulator. I have gotten his system running and mostly tested in the Clarion 2.1 runtime under vDosPlus (which is very fast) and DOSBox-X (which is 5 to 10 times slower). ![]() If vDos will never support this feature (and vDosPlus and DOSBox-X possibly won't either), do you have any suggestions of other DOS emulators I haven't tested yet that might handle this? That emulator is very actively supported, but I don't know if or when the request will ever implemented. I have posted a request that DOSBox-X enable this Ctrl-Break. If vDos will never support this functionality, it is doubtful that vDosPlus ever will, as it is (apparently) an almost dead project. ![]() That's why I've been looking for a DOS emulator that starts up in seconds and simply runs the DOS programs. My client was hoping to migrate his software (and my CPD 2.1 development environment) to something faster. They also eat up tremendous resources and take forever to boot up. We do just fine with VMWare on my client's virtual Windows Server 2003 machine, and I support it using Oracle's VM VirtualBox, but both of these environments run slower than molasses in January. You said to him, "So sorry, but it ends for Javelin under vDos." Did you mean that function will never be implemented in vDos and that Javelin users should use a different DOS emulator? Does it also mean that the CPD 2.1 will never fully run in vDos and that I should also look elsewhere to be able to run it? I assume this is a problem similar to the one reported by the OP in this thread. When Ctrl-Break is pressed when the processor is running in either of those emulators, nothing happens. I have been trying (with no luck so far) to get the full CPD 2.1 environment (including the Ctrl-Break function in the processor that starts the debug module) in the following environments: vDosPlus and DOSBox-X. He stull uses it today and has no intentions of rewriting or switching to canned software to handle his custom needs. My client has been using this software to run his Mill for over 30 years. I wrote full industrial system in Clarion 2.1 back in those days. So I think it is inaccurate to say that "virtually no DOS program uses this." Clarion 2.1 was very popular in the 90s. ![]() Keeping this issue open until we'll have proper documentation for building with this feature enabled.The Clarion 2.1 Professional Developer (CPD 2.1, written in the late 1980s) uses Ctrl-Break when the processor is running a compiled Clarion 2.1 program (.pro) to open the Clarion debugger window. Remember about creating release build, otherwise our normal debug logs will interfere with debugger feature. ![]() Windows: install pdcurses using vcpkg, manually edit file src/platform/visualc/config.h and enable the version of debugger you want, build Release configuration.ĭon't ask me what's the difference between debugger and heavy-debugger because authors didn't bother to write documentation. Linux, macOS: install ncurses development package using your native package manager, create a release build with additional configure flag, either: -enable-debug or -enable-debug=heavy. That being said, I consider the debugger feature to be broken currently and have no real incentive to fixing it.Ĭontributions in this area are very welcome - starting with properly documenting how to build a version with Debugger feature enabled quick documentation is as follows:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |