Ok, so I have masm 6.11 from winworldpc and it doesn't work. I downloaded another installation from sourceforge and masm.exe is working but ml.exe generates fatal errors involving dosxnt file.

I've noticed that second installation has dosxnt.386 file in bin folder and dosxnt.exe has smaller size (393k) than in first installation's bin folder(394k). So I copy both files and now everything works perfectly. 😀))

What sort of system do you have? It might be good to run some memory testing software as there might be an issue with the memory..

pan069 wrote on 2023-03-02, 20:52:

What sort of system do you have? It might be good to run some memory testing software as there might be an issue with the memory..

I have Dos 6.22 installed. My laptop is LG 500, 3gb ram, Intel dual core 2ghz, ATI Radeon 256 mb.

What is good app to perform memory test?

different question: why do you want to develop directly under DOS?

its much easier to use dosbox + cross-assembling with MASM or better UASM (MASM compatible but better error messages) or NASM on Win/Linux x64 - im doing all my DOS programs that way

llm wrote on 2023-03-03, 06:51:

different question: why do you want to develop directly under DOS?

its much easier to use dosbox + cross-assembling with MASM or better UASM (MASM compatible but better error messages) or NASM on Win/Linux x64 - im doing all my DOS programs that way

Well, I want to learn assembly language. I'm interested in x86 architecture and first thing that came to my brain was that dos should be good starting point. I wanted to go deeper into dos code. You know, how this system boots, works etc. So I wrote program that detects drives (fdd,hdd,cd-rom is not available yet), user can select any sector and see all opcodes.

Tbh I think sth is wrong with battery. I tried to install win 7 and Linux. During installation laptop turns off. 😒

I agree with @llm. Do your development on a modern system with DosBox. E.g. I run a Linux desktop with Sublime as my main text editor and run my MAKE command in a terminal. I mostly use OpenWatcom but any tools that run directly on your main operating system will do. Build your binaries on your main system and run in DosBox. If you need to use the debugger in in PWD then use that in DosBox. Then, every once in a while run your program on an actual target system to see if it all works correctly. Of course, for very specific types of hardware not available in DosBox or performance sensitive code you need to use a real system.

Yeah, this sounds like really good idea. 😀 I will give it a shot. Thank You for Your advise. 😀)))