Assembler problems

[C3]

It's not that hard to check whats in the VS Debugger(?)

Be sure to read the original post and the last line of the first post in this thread. I would be fine with the assembler that comes with VS if it worked.

I know that thing, Hutch designed that the SDK will work on drive C:\ what if you move your folder from D:\ to C:\

[jj2007]

Integration with MS other tools, C/C++,VB,.NET

Ok, thanks, so I won't need it

Hutch designed that the SDK will work on drive C:\ what if you move your folder from D:\ to C:\

Actually, Hutch designed it so that there is a root folder \Masm32. That can be C:\Masm32, D:\Masm32, X:\Masm32, whatever. That's why I get the creeps when n00bs start their code with include C:\Masm32\... that's just plain wrong.

[C3]

Integration with MS other tools, C/C++,VB,.NET

Ok, thanks, so I won't need it

I need only C/C++ because Microsoft Learning (MSDN) is presented in C or C++ and I need it to translate that to MASM. I cant do properly neither VB or .NET. But C and C++ is easier if you know already MASM.

[C3]

Integration with MS other tools, C/C++,VB,.NET

Ok, thanks, so I won't need it

Hutch designed that the SDK will work on drive C:\ what if you move your folder from D:\ to C:\

Actually, Hutch designed it so that there is a root folder \Masm32. That can be C:\Masm32, D:\Masm32, X:\Masm32, whatever. That's why I get the creeps when n00bs start their code with include C:\Masm32\... that's just plain wrong.

I had problem with this concept with setup of 64bit environment. It works better if you keep the folder on drive C:\
I may be a noob, and I use this as include:

INCLUDE <c:\masm64\include64\masm64rt.inc>

[jj2007]

I use this as include:

INCLUDE <c:\masm64\include64\masm64rt.inc>

Try \masm64\...

(the <quotes> are not needed, either)

[C3]

I use this as include:

INCLUDE <c:\masm64\include64\masm64rt.inc>

Try \masm64\...

(the <quotes> are not needed, either)

I had problems with the includes if its that way. Got things to work in Visual Studio after that what I posted.

[jj2007]

I had problems with the includes if its that way.

Only if your Masm32 installation is on a different drive than VS, and if VS doesn't allow to specify a drive for building assembly projects. Which would be dumb, of course.

[C3]

I had problems with the includes if its that way.

Only if your Masm32 installation is on a different drive than VS, and if VS doesn't allow to specify a drive for building assembly projects. Which would be dumb, of course.

You should try Visual Studio to verify this 

Ok I tried to remove angle brackets and drive letter. It works. But there WERE a problem with this on some version.

Ok, one edit more. This will work on Visual Studio 2022 but not on Visual Studio 2019.

[ahsat]

what if you move your folder from D:\ to C:\

I don't put anything on drive C: that I don't have to. Since the 80s Microsoft has, one way or another, destroyed drive C: too many times. It is easier, today, just to give drive C: to Microsoft, like the want you to, and put my stuff on another drive. It is much easier to restore Windows than it is to restore all of my stuff along with it.

[NoCforMe]

How does the VS debugger compare to Olly? Any features that Olly doesn't have?

It's not that hard to check whats in the VS Debugger(?).

It certainly is that hard if you don't have Visual Studio, and moreover have no intention of ever installing it. Can you give us at least one or two features of it?

[C3]

How does the VS debugger compare to Olly? Any features that Olly doesn't have?

It's not that hard to check whats in the VS Debugger(?).

It certainly is that hard if you don't have Visual Studio, and moreover have no intention of ever installing it. Can you give us at least one or two features of it?

Sorry! My memories are so faint as I have used it more than 5 years ago. But I'd like to emphasize that VS Debugger works extremely fine under all MS developement tools/languages.

[daydreamer]

what if you move your folder from D:\ to C:\

I don't put anything on drive C: that I don't have to. Since the 80s Microsoft has, one way or another, destroyed drive C: too many times. It is easier, today, just to give drive C: to Microsoft, like the want you to, and put my stuff on another drive. It is much easier to restore Windows than it is to restore all of my stuff along with it.

I agree,could even use external drive which can be moved between my different computers so i can testrun on different cpus + use different graphics programs for make nice icons in my programs
One thing i dont know if possible is run ml and linker in usb connected android tablet internal/external sd card ? With pc

[kkurkiewicz]

Do you possibly know how to configure Visual Studio to use a different assembler?

If you're using Visual Studio 2019 or 2022, try reading this.

[ahsat]

If you're using Visual Studio 2019 or 2022

Thank you very much.