Jump to content
IGNORED

DASM On DOS


Recommended Posts

Hello everyone! I’ve been messing around with FREEDOS recently and have been loving the distraction free environment I’ve gotten setup on there. I’ve managed to find a DOS (16-bit) version of DASM (version 2.12) that works but have run into a minor issue. A source that compiles on the newest version of DASM, on my Linux PC, does not compile with DASM 2.12 as it doesn’t recognize “CLEAN_START” as a mnemonic. I’ve made sure to include macro.h, and as I d mentioned prior it does compile correctly with the newest version of DASM. My current conclusion is that version 2.12 does not recognize a few macros on macro.h. Does anyone know of a new version of DASM that will run on FREEDOS?

Link to comment
Share on other sites

You could try downloading the source code to DASM:  https://github.com/dasm-assembler/dasm...

... and compile it in your favorite 16-bit C compiler.

 

OR

 

Copy the contents of the CLEAN_START macro into your source file.

 

----

 

Feel free to share your source code.... there might just be a typo in your code.

  • Thanks 1
Link to comment
Share on other sites

19 minutes ago, splendidnut said:

You could try downloading the source code to DASM:  https://github.com/dasm-assembler/dasm...

... and compile it in your favorite 16-bit C compiler.

 

OR

 

Copy the contents of the CLEAN_START macro into your source file.

 

----

 

Feel free to share your source code.... there might just be a typo in your code.

I have no idea why I didn’t think to compile DASM’s source code! Thank you for the help!

Link to comment
Share on other sites

  • 2 weeks later...

UPDATE:

 

Just wanted to put this out there for anyone that might run into my exact situation down the line. After reading the documentation, as well as comparing my code to one written by another, I've come to realize another solution to this dilemma was merely to place 'NO_ILLEGAL_OPCODES = 1' into my code. This instantly did the trick as now the source compiles properly.

Link to comment
Share on other sites

On 12/13/2022 at 2:18 AM, pettapatta said:

UPDATE:

 

Just wanted to put this out there for anyone that might run into my exact situation down the line. After reading the documentation, as well as comparing my code to one written by another, I've come to realize another solution to this dilemma was merely to place 'NO_ILLEGAL_OPCODES = 1' into my code. This instantly did the trick as now the source compiles properly.

If you have not done so already, please join Club DASM on this site.

There is a build of DASM for DOS just released - thanks to @splendidnut

Try it out and give us some feedback if it's working for you.

 

  • Like 1
Link to comment
Share on other sites

On 12/14/2022 at 8:42 PM, Andrew Davie said:

If you have not done so already, please join Club DASM on this site.

There is a build of DASM for DOS just released - thanks to @splendidnut

Try it out and give us some feedback if it's working for you.

 

Thank you for leading me to this! I have joined and I will test out that DOS build right this instant!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...