![]() When creating the PCODEMAP.* files, makeopus fails invoking the egrep utility. In your CONFIG.SYS file, add a "IOPL=YES" line, as the dialog editor/compiler (DE) and possibly some other tools as well appear to use operations that are only available at ring 2. Add your OPUS\TOOLS directory to the path not only in AUTOEXEC.BAT, but also in CONFIG.SYS If you try compiling Winword in OS/2, remember to perform the following additional steps, compared to DOS: The attempt hasn't been entirely successful yet, although nearly all of the compilation steps go through without problems. 1.3.1, as that seems to be the most suitable choice. I'm trying to set up a build environment for Winword in MS OS/2 v. ini files? If so, then I changed fast.ini strings to something like that:Ī small update. #define szVerDateDef "Winword 1.0A Development Team"ġ) It seems to me that you have to edit autoexec.bat to add that path, as stated in $readme.ini, or you are talking about editing. Post your %PATH%, your makeopus.exe command line, your ini file used, the screen when the last error happened (don't use the +k switch in the default ini files as it will make the build progress continues even after an error occurred).Īnd the verdate.h generated in DOSBox will have errors in the last line. I checked everything you told about, and I still can't compile the exes, and I get some errors, but mostly they seem to be code-related. Did you carefully read the "makeopus.exe -?" ? Don't try to convert the resources files, as the make process presumes them to be in original format.Ĥ. 0.74 had a serious memory leak in its batch file interpreter.ģ. A system capable to run 386MAX 4.03, or compiling under OS/2 1.x might be the only solution to compile the debug build. According to my test the debug code won't even compile with 620K+ conventional memory. This was very redundant I had to do each file individuallyĪnd I have "NOAPPLOADER=" in the makeopus.cm fileġ. TheWaffle wrote:So I too am having troubles compiling.Īnd I get an out of memory error when compiling debug\debugcmd.c on line 596Īlso I converted all the bmp files to the windows 3 format using borlands resource workshop What's worse as Win16 API for Windows 3.0 lacks support for many essential features such as advanced file operation, applications rely on MS-DOS API via calling INT 21H directly or call DOS3Call, which are prohibited under Win32, for these features. The Word's p-code interpreter is written in assembly, so it needs a rewrite for porting to Protected mode 32-bit Windows. Or is it?Ĭompared to X86 Protected mode, X86 Real mode uses a different memory model so all assembly source code written for Real mode must be rewritten when porting to Protected mode. In which case, compiling to a physical machine wouldn't just be possible (but another question would arise: how are the capabilities of such a rich VM accessed within regular C code?)įinally: I assume the source code to the p-code machine is not provided. Unless the p-code machine doesn't abstract only over the physical processor, but also over the Windows API. What is it that would prevent us from targeting a concrete platform rather than the p-code machine? At which point the compilation of the C and assembly code that makes up winword 1.1 would break? Thus, it's basically a packed form of bytecode + its interpreter. the p-code) and linked against the virtual machine itself. P-code is generally an alternative target to a given language: rather than targeting a concrete platform (x86 and such), the source is compiled to the machine code of a certain virtual machine (i.e. What I still do not understand (but I haven't really inspected the code yet) is the following: Information about your computer ports is displayed.TheWaffle wrote:Is it be possible to compile dos or word as 64 bit?Ī major rewrite of the p-code system is required and if so it will not be the same application at all. To execute the debug routine, you need to type "G" and press Enter. To get out of debugging mode, you need to type "Q" and press Enter. Specifies command line information required by the file you want to test.Īfter debug starts, type "?" to display a list of debugging commands. MS-DOS 5.x and later and all versions of Windows that support this command above uses debug.exe as the external file.ĭebug syntax DEBUG filename ] filename MS-DOS 2.x - 4.x use as the external file. Debug is an external command and is available for the following Microsoft operating systems.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |