So one of the concerns that I have had in the past when programming in Windows 32-bit assembly is the include files. I noticed that you imported the libraries and declared the prototype in your code. I don’t know many assembly programmers ( any :-) ), but I think they typically have things in an INC file similar to a C header file. The only place I know of to get those premade is masm32 which is a package put together that includes masm without VS and GRCs SIB sample, which includes a Windows.inc. I do wonder how assembly programmers typically deal with this. I know a person can just create their own, I assume this is just typically how it is done. A few other things that I found difficult when I was first figuring out assembly on windows is how to view variables in the debugger, you showed the registers, but in assembly I know you can have global variables and I believe if I remember correctly there is no reason you can not have variables created on the stack at the beginning of a function. I assume it typically needs to be at the beginning because of something with the stack frames. So knowing how to create globals and function level variables would be useful and how to watch there values in the debugger also. I suppose knowing how to create on the heap would be useful too, but that I think requires more knowledge of the API. Also, speaking of stack frames, I’ve never really paid attention to the the stack pointer changing on function calls, I know it goes downword so the stack pointer value would be getting smaller as functions are called and variables are created, but I never really demonstrated it clearly to my self. Also I know EBP register is important when functions are called and returned from, but I obviously do not have it down cool but I ever never worked it mentally. I don’t think the concepts in their simplest essence are difficult, but as life happens and other things have to become priorities it makes learning this take more time. Thanks for the video and please please put the assembly course on your trainsec. I could type a very long list of things I hope you cover in detail but I have faith you will cover the most import first.
You can find more INC files in the masm32 project and other sources. Your other comments require more detailed responses, but they boil down to calling conventions which are different in 32-bit than 64 bit. Obviously, there is a lot to learn here, this video just scratches the surface.
Great video! Are you using an extension for syntax highlighting? If so, which one? Thanks!
I think it's what you get out of the box. But if not, there is a syntax highlight extension from Mads Kristensen
very noice assemlby program ;)
Where I can get local offline Help for Winapi, such as in your video?
Go to the Visual Studio 2022 installer, and add the Help Viewer component
So one of the concerns that I have had in the past when programming in Windows 32-bit assembly is the include files. I noticed that you imported the libraries and declared the prototype in your code. I don’t know many assembly programmers ( any :-) ), but I think they typically have things in an INC file similar to a C header file. The only place I know of to get those premade is masm32 which is a package put together that includes masm without VS and GRCs SIB sample, which includes a Windows.inc. I do wonder how assembly programmers typically deal with this. I know a person can just create their own, I assume this is just typically how it is done.
A few other things that I found difficult when I was first figuring out assembly on windows is how to view variables in the debugger, you showed the registers, but in assembly I know you can have global variables and I believe if I remember correctly there is no reason you can not have variables created on the stack at the beginning of a function. I assume it typically needs to be at the beginning because of something with the stack frames. So knowing how to create globals and function level variables would be useful and how to watch there values in the debugger also. I suppose knowing how to create on the heap would be useful too, but that I think requires more knowledge of the API.
Also, speaking of stack frames, I’ve never really paid attention to the the stack pointer changing on function calls, I know it goes downword so the stack pointer value would be getting smaller as functions are called and variables are created, but I never really demonstrated it clearly to my self. Also I know EBP register is important when functions are called and returned from, but I obviously do not have it down cool but I ever never worked it mentally.
I don’t think the concepts in their simplest essence are difficult, but as life happens and other things have to become priorities it makes learning this take more time. Thanks for the video and please please put the assembly course on your trainsec. I could type a very long list of things I hope you cover in detail but I have faith you will cover the most import first.
You can find more INC files in the masm32 project and other sources. Your other comments require more detailed responses, but they boil down to calling conventions which are different in 32-bit than 64 bit. Obviously, there is a lot to learn here, this video just scratches the surface.
Nice video :)
What do u think about making a video about using asm with x64?
Isn't this video about that? ;)