Comments by Member 15439227 (Top 2 by date)

Member 15439227 27-Mar-22 13:02pm View

ok what i mean is this. when i compile with nasm -f win64, i use link or golink.exe to link it together. this exe that is produced works fine. however, if i convert it to shellcode using nasm -f bin sw64.s -o sw64.sc and then use this shellcode in a dropper, meaning i am basically allocating a region of memory and copying this string into that buffer and calling virtualprotect and waitforsingleobject, etc i am not able to get a 64-bit program to execute that way. i can for 32-bit. i am aware of x86 and x64 cl.exe

Member 15439227 27-Mar-22 12:04pm View

it is. it is being compiled with cl.exe. the code produced from nasm -f bin is basically not working and it should. it works for other programs that i have not written though such as calc 64 bit and notepad 64 bit. it seems that the programs i write in 64-bit are not able to be used. is there something else i am not aware of? the 32-bit works fine.