First your PC must be able to boot to MS-DOS or Windows 95/98 DOS. This excludes all UEFI-Only systems such as Microsoft Surface Pro (Not sure about Intel Macs, as one of my Macbook Pro could boot to DOS from CD-ROM but not USB).
Second, your PC must have a whole continuous page (64KB) free in the High Memory Area for use with an EMS emulator. I used JEMMEX as the EMS emulator as it only use few KBs of conventional memory, compatible with modern motherboards and also provides XMS service.
Use UMBCHK in UMBPCI package without any memory manager loaded to see the free parts of High Memory Area.
If there are 4 or more continuous blocks, the EMS emulator will work. Take note of the start and the end address.
Write the config.sys using the addresses.
If Mem.exe reported more than 614K conventional memory and 32M EMS is available, the environment should be OK to build non-Debug builds of Word 1.1A.
Microsoft kindly provided the complete toolchain for building the source code with the archive. Most of those tools lay in /Opus/tools directory of the source archive.
Edit your INI file for makeopus.exe.
The "BUILD=" is the directory for storing intermediate files.
Use "+s" option for a Ship (release) build.
Use "NOAPPLOADER=" to disable the Word's own NE loader, thus the output EXE file could be used in Borland Resource Workshop, or potentially run under NTVDM.
Don't forget to check your TEMP environment variable, it must be pointed to a writable directory for some tools used in build progress.
Assume that your INI file name is fast.ini. under Opus directory, run this command
Code: Select all
tools\makeopus @fast.ini
If you see this, the build is succeeded.
If your DOS is booted from a slow media such a USB Flash drive, you could load XMSDSK or other DOS Ramdisk driver that don't use much conventional memory, copy everything to Ramdisk and build Opus from there to save time. However, makeopus.exe will fail if the BUILD directory is outside of boot drive so use mo1.bat in this situation.
