Hi everyone,

I'd like to share my tutorial on 32bit Assembly with FASM.

Part 1: http://blog.brakmic.com/intro-to-x86-assembly-with-fasm
Part 2: http://blog.brakmic.com/intro-to-x86-assembly-with-fasm-part-2/

PDF Versions:

Part 1: http://blog.brakmic.com/wp-content/uploads/2016/09/Intro_to_x86_Assembly_with_FASM_Part_1.pdf
Part 2: http://blog.brakmic.com/wp-content/uploads/2016/09/Intro_to_x86_Assembly_with_FASM_Part_2.pdf

I consider myself a beginner and I'm writing these tutorials to expand my knowledge about FASM/Assembly.

Your Comments/Criticism are very welcome.

Regards,

Do your images require JS or something? Because I see only blank spaces where images presumably should be.

I feel like you should have mentioned the term "calling conventions" when you explained the stack setup and teardown procedures. Are you planning on expanding this tutorial into a series that makes Win32 calls and other goodies?

I'm using Wordpress as my blogging engine so you'd have to enable JS. However, my blog contains no advertisements or any malicious scripts. I do not use my blog for any commercial activities. All my articles are BSD-licensed and completely free.

Yes, I'm planning to write several follow-up articles. I think its best to explain "calling conventions" within an article dedicated to functions/stack frames/call/ret/EIP.

Well structured and read on one breath, nice!

Nice article brakmic. I read it easily with the moderate English i know.

Hi everyone,

Thanks for the kind words! Much appreciated.

Here's the second part:

http://blog.brakmic.com/intro-to-x86-assembly-with-fasm-part-2/

Best regards,

Still a lot of blank spaces where images are intended. Perhaps you can eliminate the JS there. HTML since the very beginning supports images without needing JS.

No blanks for me. Images are displayed fine in Chrome and IE 11.

Do you have JS enabled?

Yes, everything's enabled. Images are JS, indeed. They kinda fade in smoothly when scrolling

So there is the problem: images require JS. This is not within the spirit of the WWW or HTML. Images are a basic element of the web and now many sites are breaking it just to have fancy fade-in effects, and other flashy whatnot, that is not really necessary, and can actually be annoying for many users.

Anyhow, it is just what I see. If the author is okay with it then that is fine.

I've exported the articles to PDF. The links are in the documents.
I'll also update the original posting and put the PDF-Links there.

Part 1 http://blog.brakmic.com/wp-content/uploads/2016/09/Intro_to_x86_Assembly_with_FASM_Part_1.pdf

Part 2 http://blog.brakmic.com/wp-content/uploads/2016/09/Intro_to_x86_Assembly_with_FASM_Part_2.pdf

Kind regards,

brakmic: Can you place an <img> tag in your HTML source without all the extras? If not then Wordpress has a bad setup IMO (and creates yet another broken non-conforming website in the process).

I'm not writing HTML manually but via Wordpress Tools. Writing HTML structure is very error prone (and boring).

And the current IMG-Tags are pretty standard...there's nothing special in them, so I see no reason to remove, let's say, the "class" attribute from them.

But, there's now the PDF-Export of these articles so I hope this would be sufficient to readers who have problems with JavaScript (or have not activated it).

Regards,

Thanks for the PDF pointer.

As for the IMG tags, the "src" attribute gives a blank image, this is what all browsers know about and can display without and special steps. It is the "data-src" attribute that the JS reads to determine the actual image. But "data-src" is not a standard anywhere, its contents is purely defined by whatever JS code has been included.

Anyhow, if this is a limitation of Wordpress then ... umm, okay. All I can think of is "What were they thinking?".

There's no "data-src" in my HTML code. But this is actually allowed as per HTML standard:

https://developer.mozilla.org/de/docs/Web/Guide/HTML/Using_data_attributes

Any data-* attribute is valid.

However, I see no "data-src" but only "src" attributes in my original HTML.

[UPDATE]
Wordpress (or some of its plugins) change the original "src" attributes into a pair of "src" & "data-src". This is, however, allowed by HTML5 standard which is JavaScript-inclusive.
[UPDATE]

Yeah, data-* is valid but the content are not defined. It requires JS to figure it out, and there are no standard defined values for the * portion.

But anyhow, from what you say above, it appears as though the webserver is rewriting the standard input into the non-standard output form that is delivered to the clients.

I updated my last post. Well, it's because of HTML5 standard that treats JavaScript as an integral part of the overall "web experience"