News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Recent posts

#1
The Campus / Re: FillConsoleOutputCharacter...
Last post by NoCforMe - Today at 09:47:51 AM
Well, it looks to me as if you haven't figured out why it didn't work in the first place, so you've learned nothing. Poking code here and there in hopes it might work isn't the way to learn how to code.

Plus, any reason you're using 64-bit assembly? 32-bit is much easier and more straightforward, plus the MASM32 package is pretty complete and robust, unlike MASM64 which is kind of a piece of shit at this time.
#2
The Campus / Re: FillConsoleOutputCharacter...
Last post by zedd - Today at 09:38:37 AM
Quote from: sskaiser on Today at 01:36:29 AMsorry for wasting your time
Its not wasted time. As I do not know your level of experience, I must ask seemingly silly questions sometimes.

Quote from: sskaiser on Today at 01:38:34 AMAnd to answer your questions I did use the GetConsoleScreenBufferInfo and made sure it works...
:thumbsup:

Quoteand I use VS Community 2022 to watch the registers, function returns 1 so i guess no errors
Okay.  :smiley:
#3
The Campus / Re: Nested .REPEAT, .IF and .W...
Last post by NoCforMe - Today at 06:39:29 AM
Quote from: mabdelouahab on Today at 05:00:54 AM        .IF !ZERO?
                    ;GOTO found
        .ENDIF

??????
Looks like net effect is ... nothing.
#4
UASM Assembler Development / Re: Linux users, please
Last post by mabdelouahab - Today at 05:28:53 AM
hi LordAdef
I'm excited about the project, even if my time is limited. Where do you suggest we begin?
#5
The Campus / Re: Nested .REPEAT, .IF and .W...
Last post by mabdelouahab - Today at 05:00:54 AM
.IF !ZERO?
                ;GOTO found
.ENDIF
#6
Windows API / Re: How do I get access to my ...
Last post by NoCforMe - Today at 04:48:19 AM
I wrote up a tutorial on how to do recording with Windows Waveform Audio, attached here.
Wish I had a website to publish this on, but this'll have to do. I think it pretty much covers the subject. Could even be used by non-assembly-language programmers.

(This was inspired by the tutorial that Timo posted a link to earlier in this thread.)
#7
The Campus / Re: FillConsoleOutputCharacter...
Last post by sskaiser - Today at 01:38:34 AM
And to answer your questions I did use the GetConsoleScreenBufferInfo and made sure it works and I use VS Community 2022 to watch the registers, function returns 1 so i guess no errors
#8
The Campus / Re: FillConsoleOutputCharacter...
Last post by sskaiser - Today at 01:36:29 AM
Quote from: zedd on June 21, 2025, 11:16:28 PMOffhand I would say we need more information. Are you using GetConsoleScreenBufferInfo to fill the CONSOLE_SCREEN_BUFFER_INFO structure? Is the structure getting filled properly? Is the handle to stdout valid?

Perhaps post the (pertinent) code that you used prior to calling your clr procedure??
Have you stepped the code in a debugger? (While watching return values in rax and watching whether or not any exceptions are found)

It just started working after I did absolutely nothing sorry for wasting your time
#9
The Campus / Re: Nested .REPEAT, .IF and .W...
Last post by _japheth - Today at 12:37:33 AM
Quote from: Quan on Today at 12:19:25 AMBecause putting a label in a macro for the JMP instruction, and then using the macro multiple times causes the compiling to complain about label redefinition. Or is that okay and can safely be ignored?

No, since this is an error and no warning. You have to use the LOCAL directive ( inside the macro and tightly following the MACRO directive) to declare your label inside the macro as "local".
#10
The Campus / Re: Nested .REPEAT, .IF and .W...
Last post by Quan - Today at 12:19:25 AM
Ahh, right, I didn't notice that, thanks!

Quote from: _japheth on June 21, 2025, 12:14:41 AMThat's supposedly not at all what you did want to do!? A simple JMP should work better.
I don't think this works? Because putting a label in a macro for the JMP instruction, and then using the macro multiple times causes the compiling to complain about label redefinition. Or is that okay and can safely be ignored?