Close Topic Options

Hmm...

Last I knew "Console Apps" are Win32 Only!

yes all console apps are win32 but the ntvdm emulates dos...chasm knows the right compile/link options because the program runs successfully in the ntvdm (console window)....

i believe that i am getting closer to a solution....i believe that i need /omf switch on linker and need 16 bit linker which i just downloaded....not sure where to tell winasm or vs2008 use link.exe instead of the default which i guess is ml.exe

when the program is set as .80386 i believe the program is trying to run in the privilege 386 space but the os prevents access to dos interrupts...but i am now attempting to define as .8086 which i believe will cause it to run in a protected space from which it is allowed to issue dos interrupts....

chasm can do it so i know there is a way....

If your Studio is setup correctly...

For new projects...

Simply choose Standard .exe for GUI app or Console App for Win32.

or

Choose DOS project for Dos16 .exe's

Then the studio knows what type of project you are doing.

problem is now solved.

for folks who may find themselves in a similar situation i refer them to http://webster.cs.ucr.edu/Page_TechDocs/MASMDoc/ProgrammersGuide/Chap_02.htm

i thought i had followed all of these steps before posting but apparently not.

i did select dos project and this code structure
i also omitted a dos 20h call as i believe the .exit code is handling that....

i did not need the 16 bit linker or the /omf switch....the settings in winasm worked as is...

so now the program builds with both chasm and masm but the two code sets are
not the same.....it's an interesting problem - very arcane which no one doing real work should encounter....

one last note - the code did not compile in vs2008 - gave error
1>.\addexamp.asm(35) : error A2006:undefined symbol : DGROUP

obviously there is a need to reconcile environments but i have no idea where dgroup is defined such that winasm compiles but vs does not....