#nasm — Public Fediverse posts

There's been some discussion recently of what motivates free software authors.

#PuTTY was originally just a Telnet client. It became really useful when I added an SSH backend, during my last year at university. I did that partly because I thought network security seemed like a good idea, but mostly because I had exams coming up, and it seemed like more fun than revising for them.

Three years earlier, #NASM started off as a long design discussion with about 17 people on an email list. Eventually the time came to write code. I volunteered to write an initial prototype for everyone to work on improving. Another member of the mailing list – also a student – suggested that he'd write one too, and then we could decide which one to use. He was at Oxford and I was at Cambridge, so naturally I went all-out to make sure mine would be better. (He never finished his, as it turned out.)

In other words, my two biggest serious free software projects were motivated significantly by Oxbridge rivalry and by revision avoidance.

I'm not quite sure that's how a university education is _supposed_ to bring benefit to the world, but I'll take it!

There's been some discussion recently of what motivates free software authors.

#PuTTY was originally just a Telnet client. It became really useful when I added an SSH backend, during my last year at university. I did that partly because I thought network security seemed like a good idea, but mostly because I had exams coming up, and it seemed like more fun than revising for them.

Three years earlier, #NASM started off as a long design discussion with about 17 people on an email list. Eventually the time came to write code. I volunteered to write an initial prototype for everyone to work on improving. Another member of the mailing list – also a student – suggested that he'd write one too, and then we could decide which one to use. He was at Oxford and I was at Cambridge, so naturally I went all-out to make sure mine would be better. (He never finished his, as it turned out.)

In other words, my two biggest serious free software projects were motivated significantly by Oxbridge rivalry and by revision avoidance.

I'm not quite sure that's how a university education is _supposed_ to bring benefit to the world, but I'll take it!

There's been some discussion recently of what motivates free software authors.

#PuTTY was originally just a Telnet client. It became really useful when I added an SSH backend, during my last year at university. I did that partly because I thought network security seemed like a good idea, but mostly because I had exams coming up, and it seemed like more fun than revising for them.

Three years earlier, #NASM started off as a long design discussion with about 17 people on an email list. Eventually the time came to write code. I volunteered to write an initial prototype for everyone to work on improving. Another member of the mailing list – also a student – suggested that he'd write one too, and then we could decide which one to use. He was at Oxford and I was at Cambridge, so naturally I went all-out to make sure mine would be better. (He never finished his, as it turned out.)

In other words, my two biggest serious free software projects were motivated significantly by Oxbridge rivalry and by revision avoidance.

I'm not quite sure that's how a university education is _supposed_ to bring benefit to the world, but I'll take it!

There's been some discussion recently of what motivates free software authors.

#PuTTY was originally just a Telnet client. It became really useful when I added an SSH backend, during my last year at university. I did that partly because I thought network security seemed like a good idea, but mostly because I had exams coming up, and it seemed like more fun than revising for them.

Three years earlier, #NASM started off as a long design discussion with about 17 people on an email list. Eventually the time came to write code. I volunteered to write an initial prototype for everyone to work on improving. Another member of the mailing list – also a student – suggested that he'd write one too, and then we could decide which one to use. He was at Oxford and I was at Cambridge, so naturally I went all-out to make sure mine would be better. (He never finished his, as it turned out.)

In other words, my two biggest serious free software projects were motivated significantly by Oxbridge rivalry and by revision avoidance.

I'm not quite sure that's how a university education is _supposed_ to bring benefit to the world, but I'll take it!

There's been some discussion recently of what motivates free software authors.

#PuTTY was originally just a Telnet client. It became really useful when I added an SSH backend, during my last year at university. I did that partly because I thought network security seemed like a good idea, but mostly because I had exams coming up, and it seemed like more fun than revising for them.

Three years earlier, #NASM started off as a long design discussion with about 17 people on an email list. Eventually the time came to write code. I volunteered to write an initial prototype for everyone to work on improving. Another member of the mailing list – also a student – suggested that he'd write one too, and then we could decide which one to use. He was at Oxford and I was at Cambridge, so naturally I went all-out to make sure mine would be better. (He never finished his, as it turned out.)

In other words, my two biggest serious free software projects were motivated significantly by Oxbridge rivalry and by revision avoidance.

I'm not quite sure that's how a university education is _supposed_ to bring benefit to the world, but I'll take it!

Spent Thursday at the National Air & Space Museum’s Udvar-Hazy Center visiting with old friends: amazing aircraft we’ve learned about and love seeing in person. Identification and links to more info in the Alt Text….

#NASM #aviation #history #WW2

Spent Thursday at the National Air & Space Museum’s Udvar-Hazy Center visiting with old friends: amazing aircraft we’ve learned about and love seeing in person. Identification and links to more info in the Alt Text….

#NASM #aviation #history #WW2

Spent Thursday at the National Air & Space Museum’s Udvar-Hazy Center visiting with old friends: amazing aircraft we’ve learned about and love seeing in person. Identification and links to more info in the Alt Text….

#NASM #aviation #history #WW2

Spent Thursday at the National Air & Space Museum’s Udvar-Hazy Center visiting with old friends: amazing aircraft we’ve learned about and love seeing in person. Identification and links to more info in the Alt Text….

#NASM #aviation #history #WW2

Spent Thursday at the National Air & Space Museum’s Udvar-Hazy Center visiting with old friends: amazing aircraft we’ve learned about and love seeing in person. Identification and links to more info in the Alt Text….

#NASM #aviation #history #WW2

It's obscurely frustrating when the same innovation both makes a job easier, _and_ makes it unnecessary. You lose the opportunity to enjoy the first of those.

When I was a student, my first free software project was #NASM. It had to support lots of x86 OSes' different object-file formats. So I had about seven OSes that I needed to test it on.

I could only afford one computer on a student budget, so I had to install them all on the same machine and do some Extreme Multiboot. No existing bootloader could handle my 7-OS setup, so I had to write my own specialist heavy-duty bootloader. (Naturally, _in_ NASM.)

Debugging code that runs at boot time, when every test requires a reboot, is a complete pain. I could test snippets of the code out of context in a DOS debugger, but sooner or later, I'd have to install the whole thing, test-boot it, and like as not, find it hung without giving me any useful feedback.

Virtual machine technology came in on x86 not long after, and made this all so much nicer. You can test your boot-time code with only a normal edit-compile-link cycle and minimal faff to install it in the VM's virtual boot media! If you're lucky you can even get per-instruction diagnostics out of the VM, or attach a debugger to it! It's all amazing! I wish I'd had a VM for debugging dboot, back in 1997 …

… Except that if I'd had VMs available, I also wouldn't have _needed_ dboot. At least five of my test OSes would have lived in dedicated VMs in the first place. (Maybe I'd still have dual-booted Linux and Windows, but that was a normal setup that any bootloader of the era could have handled.)

So I'd never have had the opportunity to enjoy the nicer debugging experience!

It's obscurely frustrating when the same innovation both makes a job easier, _and_ makes it unnecessary. You lose the opportunity to enjoy the first of those.

When I was a student, my first free software project was #NASM. It had to support lots of x86 OSes' different object-file formats. So I had about seven OSes that I needed to test it on.

I could only afford one computer on a student budget, so I had to install them all on the same machine and do some Extreme Multiboot. No existing bootloader could handle my 7-OS setup, so I had to write my own specialist heavy-duty bootloader. (Naturally, _in_ NASM.)

Debugging code that runs at boot time, when every test requires a reboot, is a complete pain. I could test snippets of the code out of context in a DOS debugger, but sooner or later, I'd have to install the whole thing, test-boot it, and like as not, find it hung without giving me any useful feedback.

Virtual machine technology came in on x86 not long after, and made this all so much nicer. You can test your boot-time code with only a normal edit-compile-link cycle and minimal faff to install it in the VM's virtual boot media! If you're lucky you can even get per-instruction diagnostics out of the VM, or attach a debugger to it! It's all amazing! I wish I'd had a VM for debugging dboot, back in 1997 …

… Except that if I'd had VMs available, I also wouldn't have _needed_ dboot. At least five of my test OSes would have lived in dedicated VMs in the first place. (Maybe I'd still have dual-booted Linux and Windows, but that was a normal setup that any bootloader of the era could have handled.)

So I'd never have had the opportunity to enjoy the nicer debugging experience!

It's obscurely frustrating when the same innovation both makes a job easier, _and_ makes it unnecessary. You lose the opportunity to enjoy the first of those.

When I was a student, my first free software project was #NASM. It had to support lots of x86 OSes' different object-file formats. So I had about seven OSes that I needed to test it on.

I could only afford one computer on a student budget, so I had to install them all on the same machine and do some Extreme Multiboot. No existing bootloader could handle my 7-OS setup, so I had to write my own specialist heavy-duty bootloader. (Naturally, _in_ NASM.)

Debugging code that runs at boot time, when every test requires a reboot, is a complete pain. I could test snippets of the code out of context in a DOS debugger, but sooner or later, I'd have to install the whole thing, test-boot it, and like as not, find it hung without giving me any useful feedback.

Virtual machine technology came in on x86 not long after, and made this all so much nicer. You can test your boot-time code with only a normal edit-compile-link cycle and minimal faff to install it in the VM's virtual boot media! If you're lucky you can even get per-instruction diagnostics out of the VM, or attach a debugger to it! It's all amazing! I wish I'd had a VM for debugging dboot, back in 1997 …

… Except that if I'd had VMs available, I also wouldn't have _needed_ dboot. At least five of my test OSes would have lived in dedicated VMs in the first place. (Maybe I'd still have dual-booted Linux and Windows, but that was a normal setup that any bootloader of the era could have handled.)

So I'd never have had the opportunity to enjoy the nicer debugging experience!

It's obscurely frustrating when the same innovation both makes a job easier, _and_ makes it unnecessary. You lose the opportunity to enjoy the first of those.

When I was a student, my first free software project was #NASM. It had to support lots of x86 OSes' different object-file formats. So I had about seven OSes that I needed to test it on.

I could only afford one computer on a student budget, so I had to install them all on the same machine and do some Extreme Multiboot. No existing bootloader could handle my 7-OS setup, so I had to write my own specialist heavy-duty bootloader. (Naturally, _in_ NASM.)

Debugging code that runs at boot time, when every test requires a reboot, is a complete pain. I could test snippets of the code out of context in a DOS debugger, but sooner or later, I'd have to install the whole thing, test-boot it, and like as not, find it hung without giving me any useful feedback.

Virtual machine technology came in on x86 not long after, and made this all so much nicer. You can test your boot-time code with only a normal edit-compile-link cycle and minimal faff to install it in the VM's virtual boot media! If you're lucky you can even get per-instruction diagnostics out of the VM, or attach a debugger to it! It's all amazing! I wish I'd had a VM for debugging dboot, back in 1997 …

… Except that if I'd had VMs available, I also wouldn't have _needed_ dboot. At least five of my test OSes would have lived in dedicated VMs in the first place. (Maybe I'd still have dual-booted Linux and Windows, but that was a normal setup that any bootloader of the era could have handled.)

So I'd never have had the opportunity to enjoy the nicer debugging experience!

It's obscurely frustrating when the same innovation both makes a job easier, _and_ makes it unnecessary. You lose the opportunity to enjoy the first of those.

When I was a student, my first free software project was #NASM. It had to support lots of x86 OSes' different object-file formats. So I had about seven OSes that I needed to test it on.

I could only afford one computer on a student budget, so I had to install them all on the same machine and do some Extreme Multiboot. No existing bootloader could handle my 7-OS setup, so I had to write my own specialist heavy-duty bootloader. (Naturally, _in_ NASM.)

Debugging code that runs at boot time, when every test requires a reboot, is a complete pain. I could test snippets of the code out of context in a DOS debugger, but sooner or later, I'd have to install the whole thing, test-boot it, and like as not, find it hung without giving me any useful feedback.

Virtual machine technology came in on x86 not long after, and made this all so much nicer. You can test your boot-time code with only a normal edit-compile-link cycle and minimal faff to install it in the VM's virtual boot media! If you're lucky you can even get per-instruction diagnostics out of the VM, or attach a debugger to it! It's all amazing! I wish I'd had a VM for debugging dboot, back in 1997 …

… Except that if I'd had VMs available, I also wouldn't have _needed_ dboot. At least five of my test OSes would have lived in dedicated VMs in the first place. (Maybe I'd still have dual-booted Linux and Windows, but that was a normal setup that any bootloader of the era could have handled.)

So I'd never have had the opportunity to enjoy the nicer debugging experience!

Как одна буква в ассемблере стоит 3× производительности

Я хочу показать вам, как одна буква в ассемблере может стоить 3× производительности. Не в теории — на живых замерах. По дороге мы заглянем внутрь процессора: Register Alias Table, partial register merge, scheduler, latency vs throughput, и даже обнаружим, что делитель выдаёт остаток раньше частного. Но начнём с основ. Приготовьтесь: кроличья нора окажется глубже, чем кажется.

https://habr.com/ru/articles/1024862/

#x86 #assembly #NASM #div #partial_register_merge #latency #throughput #микроархитектура #Skylake #оптимизация

Как одна буква в ассемблере стоит 3× производительности

Я хочу показать вам, как одна буква в ассемблере может стоить 3× производительности. Не в теории — на живых замерах. По дороге мы заглянем внутрь процессора: Register Alias Table, partial register merge, scheduler, latency vs throughput, и даже обнаружим, что делитель выдаёт остаток раньше частного. Но начнём с основ. Приготовьтесь: кроличья нора окажется глубже, чем кажется.

https://habr.com/ru/articles/1024862/

#x86 #assembly #NASM #div #partial_register_merge #latency #throughput #микроархитектура #Skylake #оптимизация

Как одна буква в ассемблере стоит 3× производительности

Я хочу показать вам, как одна буква в ассемблере может стоить 3× производительности. Не в теории — на живых замерах. По дороге мы заглянем внутрь процессора: Register Alias Table, partial register merge, scheduler, latency vs throughput, и даже обнаружим, что делитель выдаёт остаток раньше частного. Но начнём с основ. Приготовьтесь: кроличья нора окажется глубже, чем кажется.

https://habr.com/ru/articles/1024862/

#x86 #assembly #NASM #div #partial_register_merge #latency #throughput #микроархитектура #Skylake #оптимизация

From 8086 to Z80: Building a NASM-Inspired SDK for 8-Bit Retro Computing

https://fed.brid.gy/r/https://hackaday.com/2026/03/17/from-8086-to-z80-building-a-nasm-inspired-sdk-for-8-bit-retro-computing/

From 8086 to Z80: Building a NASM-Inspired SDK for 8-Bit Retro Computing

https://fed.brid.gy/r/https://hackaday.com/2026/03/17/from-8086-to-z80-building-a-nasm-inspired-sdk-for-8-bit-retro-computing/

https://www.europesays.com/es/412110/ La NASM profesionaliza el fitness clínico: el entrenamiento de fuerza como soporte imprescindible frente a los fármacos GLP-1 #Actualidad #ES #España #Fitness #Gimnasios #Health #NASM #Salud #Spain

Парсим XML и JSON на ассемблере

Отобрал для вас несколько крайне интересных, но малоизвестных проектов, реализующих работу с XML и JSON. Кроссплатформенных и без зависимостей. На чистом С и ассемблере.

https://habr.com/ru/articles/964522/

#json #xml #nasm #assembler #c_language #simd #simdjson #freebsd

Парсим XML и JSON на ассемблере

Отобрал для вас несколько крайне интересных, но малоизвестных проектов, реализующих работу с XML и JSON. Кроссплатформенных и без зависимостей. На чистом С и ассемблере.

https://habr.com/ru/articles/964522/

#json #xml #nasm #assembler #c_language #simd #simdjson #freebsd

Парсим XML и JSON на ассемблере

Отобрал для вас несколько крайне интересных, но малоизвестных проектов, реализующих работу с XML и JSON. Кроссплатформенных и без зависимостей. На чистом С и ассемблере.

https://habr.com/ru/articles/964522/

#json #xml #nasm #assembler #c_language #simd #simdjson #freebsd

Today's photo: IJplein (1894).

[EN] SS Schiedam, a ship of the Dutch-American Steamboat Company (NASM, better known as the Holland America Line), in a dock of ADM (Amsterdam Dry Dock Company). It had departed […]

[NL] Het ss Schiedam, een schip van de NASM (Holland Amerika Lijn), in een dok van de Amsterdamse Droogdok Maatschappij (ADM). Het was op 13 april uit New York vertrokken en op 5 […]

Via https://020apps.nl/olie/random/ #Amsterdam #JacobOlie #IJplein #NASM #shipyard #steamship

Today's photo: IJplein (1894).

[EN] SS Schiedam, a ship of the Dutch-American Steamboat Company (NASM, better known as the Holland America Line), in a dock of ADM (Amsterdam Dry Dock Company). It had departed […]

[NL] Het ss Schiedam, een schip van de NASM (Holland Amerika Lijn), in een dok van de Amsterdamse Droogdok Maatschappij (ADM). Het was op 13 april uit New York vertrokken en op 5 […]

Via https://020apps.nl/olie/random/ #Amsterdam #JacobOlie #IJplein #NASM #shipyard #steamship

Today's photo: IJplein (1894).

[EN] SS Schiedam, a ship of the Dutch-American Steamboat Company (NASM, better known as the Holland America Line), in a dock of ADM (Amsterdam Dry Dock Company). It had departed […]

[NL] Het ss Schiedam, een schip van de NASM (Holland Amerika Lijn), in een dok van de Amsterdamse Droogdok Maatschappij (ADM). Het was op 13 april uit New York vertrokken en op 5 […]

Via https://020apps.nl/olie/random/ #Amsterdam #JacobOlie #IJplein #NASM #shipyard #steamship

Today's photo: IJplein (1894).

[EN] SS Schiedam, a ship of the Dutch-American Steamboat Company (NASM, better known as the Holland America Line), in a dock of ADM (Amsterdam Dry Dock Company). It had departed […]

[NL] Het ss Schiedam, een schip van de NASM (Holland Amerika Lijn), in een dok van de Amsterdamse Droogdok Maatschappij (ADM). Het was op 13 april uit New York vertrokken en op 5 […]

Via https://020apps.nl/olie/random/ #Amsterdam #JacobOlie #IJplein #NASM #shipyard #steamship

A vulnerability was identified in NASM Netwide Assember 2.17rc0. This issue affects the function assemble_file of the file nasm.c. The manipulation leads to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

CVE-2025-8845 (GCVE-0-2025-8845)

#nasm #vulnerability

🔗 https://vulnerability.circl.lu/vuln/CVE-2025-8845

A vulnerability was identified in NASM Netwide Assember 2.17rc0. This issue affects the function assemble_file of the file nasm.c. The manipulation leads to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

CVE-2025-8845 (GCVE-0-2025-8845)

#nasm #vulnerability

🔗 https://vulnerability.circl.lu/vuln/CVE-2025-8845

A vulnerability was identified in NASM Netwide Assember 2.17rc0. This issue affects the function assemble_file of the file nasm.c. The manipulation leads to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

CVE-2025-8845 (GCVE-0-2025-8845)

#nasm #vulnerability

🔗 https://vulnerability.circl.lu/vuln/CVE-2025-8845

A vulnerability was identified in NASM Netwide Assember 2.17rc0. This issue affects the function assemble_file of the file nasm.c. The manipulation leads to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

CVE-2025-8845 (GCVE-0-2025-8845)

#nasm #vulnerability

🔗 https://vulnerability.circl.lu/vuln/CVE-2025-8845

A vulnerability was identified in NASM Netwide Assember 2.17rc0. This issue affects the function assemble_file of the file nasm.c. The manipulation leads to stack-based buffer overflow. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used.

CVE-2025-8845 (GCVE-0-2025-8845)

#nasm #vulnerability

🔗 https://vulnerability.circl.lu/vuln/CVE-2025-8845

This tool allows to assemble Intel 8080/8085 Assembly code with NASM and is implemented as a NASM macro package.

https://github.com/BinaryMelodies/nasm-i8080

#intel8080 #NASM #assembler

This tool allows to assemble Intel 8080/8085 Assembly code with NASM and is implemented as a NASM macro package.

https://github.com/BinaryMelodies/nasm-i8080

#intel8080 #NASM #assembler

This tool allows to assemble Intel 8080/8085 Assembly code with NASM and is implemented as a NASM macro package.

https://github.com/BinaryMelodies/nasm-i8080

#intel8080 #NASM #assembler

This tool allows to assemble Intel 8080/8085 Assembly code with NASM and is implemented as a NASM macro package.

https://github.com/BinaryMelodies/nasm-i8080

#intel8080 #NASM #assembler

This tool allows to assemble Intel 8080/8085 Assembly code with NASM and is implemented as a NASM macro package.

https://github.com/BinaryMelodies/nasm-i8080

#intel8080 #NASM #assembler

Создаем свою ОС (Часть 1)

UNIX-подобная операционная система: пишем ядро на языке C Всем привет недавно я и мой друг решили создать свою операционную систему на ассемблере и C и я решил то что будет неплохо написать об это цикл статей на Хабре! Создаем дальше...

https://habr.com/ru/articles/870000/

#os #nasm #c #linux_dev #unix_system

Создаем свою ОС (Часть 1)

UNIX-подобная операционная система: пишем ядро на языке C Всем привет недавно я и мой друг решили создать свою операционную систему на ассемблере и C и я решил то что будет неплохо написать об это цикл статей на Хабре! Создаем дальше...

https://habr.com/ru/articles/870000/

#os #nasm #c #linux_dev #unix_system

Создаем свою ОС (Часть 1)

UNIX-подобная операционная система: пишем ядро на языке C Всем привет недавно я и мой друг решили создать свою операционную систему на ассемблере и C и я решил то что будет неплохо написать об это цикл статей на Хабре! Создаем дальше...

https://habr.com/ru/articles/870000/

#os #nasm #c #linux_dev #unix_system

x64 Assembly & Shellcoding 101

Part 1: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101/

Part 2: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-2/

Part 3: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-3/

Part 4: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-4/

Part 5: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-5/

Part 6: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-6/

#assembly #shellcoding #NASM #debugging

x64 Assembly & Shellcoding 101

Part 1: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101/

Part 2: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-2/

Part 3: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-3/

Part 4: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-4/

Part 5: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-5/

Part 6: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-6/

#assembly #shellcoding #NASM #debugging

x64 Assembly & Shellcoding 101

Part 1: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101/

Part 2: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-2/

Part 3: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-3/

Part 4: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-4/

Part 5: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-5/

Part 6: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-6/

#assembly #shellcoding #NASM #debugging

x64 Assembly & Shellcoding 101

Part 1: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101/

Part 2: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-2/

Part 3: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-3/

Part 4: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-4/

Part 5: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-5/

Part 6: https://g3tsyst3m.github.io/shellcoding/assembly/debugging/x64-Assembly-&-Shellcoding-101-Part-6/

#assembly #shellcoding #NASM #debugging

Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful.

I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to remove as many proprietary tools as possible.

I guess I'm looking for some sort of Rosetta stone for 8086 Small Memory Model assembly.

Books, web pages and video suggestions welcome.

#x86 #Borland #RetroComputing

Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful.

I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to remove as many proprietary tools as possible.

I guess I'm looking for some sort of Rosetta stone for 8086 Small Memory Model assembly.

Books, web pages and video suggestions welcome.

#x86 #Borland #RetroComputing

Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful.

I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to remove as many proprietary tools as possible.

I guess I'm looking for some sort of Rosetta stone for 8086 Small Memory Model assembly.

Books, web pages and video suggestions welcome.

#x86 #Borland #RetroComputing

Has anyone got any tips on converting #TASM and #MASM code to a more modern assembler like #NASM? Even just between TASM and MASM would be helpful.

I've got a few old bits of #Psion 8086 assembly that I'd like to use with NASM. My aim is to remove as many proprietary tools as possible.

I guess I'm looking for some sort of Rosetta stone for 8086 Small Memory Model assembly.

Books, web pages and video suggestions welcome.

#x86 #Borland #RetroComputing

Última entrega del primer capítulo del #SolucionarioDelProgramador #GNU_linux . Terminamos con el lenguaje #Ensamblador para echar un ojo a lo que el #procesador realmente hace

#programming #programación #asm #nasm #HelloWorld #HolaMundo #x86_64

https://ibolcode.net/roor/2024-09-hola-mundo-en-ensamblador

Última entrega del primer capítulo del #SolucionarioDelProgramador #GNU_linux . Terminamos con el lenguaje #Ensamblador para echar un ojo a lo que el #procesador realmente hace

#programming #programación #asm #nasm #HelloWorld #HolaMundo #x86_64

https://ibolcode.net/roor/2024-09-hola-mundo-en-ensamblador

Última entrega del primer capítulo del #SolucionarioDelProgramador #GNU_linux . Terminamos con el lenguaje #Ensamblador para echar un ojo a lo que el #procesador realmente hace

#programming #programación #asm #nasm #HelloWorld #HolaMundo #x86_64

https://ibolcode.net/roor/2024-09-hola-mundo-en-ensamblador

Última entrega del primer capítulo del #SolucionarioDelProgramador #GNU_linux . Terminamos con el lenguaje #Ensamblador para echar un ojo a lo que el #procesador realmente hace

#programming #programación #asm #nasm #HelloWorld #HolaMundo #x86_64

https://ibolcode.net/roor/2024-09-hola-mundo-en-ensamblador

Installing NASM and Writing Your First Assembly Program on Linux
#Linux #NASM #C #Coding #Programming #Java #Python
https://linuxtldr.com/installing-nasm/

Installing NASM and Writing Your First Assembly Program on Linux
#Linux #NASM #C #Coding #Programming #Java #Python
https://linuxtldr.com/installing-nasm/

Installing NASM and Writing Your First Assembly Program on Linux
#Linux #NASM #C #Coding #Programming #Java #Python
https://linuxtldr.com/installing-nasm/

Installing NASM and Writing Your First Assembly Program on Linux
#Linux #NASM #C #Coding #Programming #Java #Python
https://linuxtldr.com/installing-nasm/

Installing NASM and Writing Your First Assembly Program on Linux
#Linux #NASM #C #Coding #Programming #Java #Python
https://linuxtldr.com/installing-nasm/

New #DOS fun with GNU Make, this time using #MASM (ML) 6.11.

Looks like another DPMI runtime conflict - GNU Make is 32-bit, ML is 16-bit, and their respective runtimes won't run the other one.

I can manually run ML for each .ASM file, but it defeats the point of using Make.

I could convert the .ASM files to another DOS assembler. #TASM and #NASM both work with GNU Make.

NASM would make it easy to port the toolchain to other OSes, although it doesn't understand memory models.

New #DOS fun with GNU Make, this time using #MASM (ML) 6.11.

Looks like another DPMI runtime conflict - GNU Make is 32-bit, ML is 16-bit, and their respective runtimes won't run the other one.

I can manually run ML for each .ASM file, but it defeats the point of using Make.

I could convert the .ASM files to another DOS assembler. #TASM and #NASM both work with GNU Make.

NASM would make it easy to port the toolchain to other OSes, although it doesn't understand memory models.