This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DOS/16M Error: [30] Program must be built -AUTO for DPMI

I trying to re-compile a very, very, very old Project written for the Archimedes Compiler Version 4. It was created by an employee that is no longer with the company. The Target CPU is a Siemens 80535, an enhanced 8051 CPU, and a single 27C512 EPROM. When I run the MAKE File it calls C:\arch4\bin\c-51 (an .EXE file dated 11/14/1990!). I am trying to compile in a DOS window in Windows 2000. I am told that the orignal programmer used a DOS window in Windows 3.0 for compiling. Any help in how to prevent the "DOS/16M Error: [30] Program must be built -AUTO for DPMI" ERROR Message? This Embedded application has no idea what DOS/16M or DPMI is and could never use that functionality.

Parents
  • Jon,
    Yes, I did. It gives the exact same error message. Weird, Huh? I found a Manual for this product and it talks about "DXT" files for Expanded Memory Extended Memory support. I also found a C51NODXT.EXE that does not generate the DOS16M Error Message when typed at the command line. It displays all command line options when run from the command line which might indicate that it can compile under WIN2000. What an adventure this has become. I reallly didn't want to change the Make File or the Compiler or any Options since the Target system is at the Customers location in another State. So, if this creates an invalid .HEX file it will be impossible to debug. I wanted to make a "simple" software change, re-compile, burn the eprom and fed-ex to customer. "Simple" - now thats funny! :-)

    Greg

Reply
  • Jon,
    Yes, I did. It gives the exact same error message. Weird, Huh? I found a Manual for this product and it talks about "DXT" files for Expanded Memory Extended Memory support. I also found a C51NODXT.EXE that does not generate the DOS16M Error Message when typed at the command line. It displays all command line options when run from the command line which might indicate that it can compile under WIN2000. What an adventure this has become. I reallly didn't want to change the Make File or the Compiler or any Options since the Target system is at the Customers location in another State. So, if this creates an invalid .HEX file it will be impossible to debug. I wanted to make a "simple" software change, re-compile, burn the eprom and fed-ex to customer. "Simple" - now thats funny! :-)

    Greg

Children
  • OK, just one more thing. Have you created a PIF file for running the MAKE program?

    If you haven't, I'm pretty sure there is no EMS or XMS.

    In Windows 2000, click on START - HELP and select the Index Tab. Then, enter EMS or XMS. Instructions for adding EMS/XMS to a DOS program are there.

    I'd definitely try that first. Especially if things were running under Windows 3.x.

    Jon