Here are a set of prototypes that will work on 64 bit capable assemblers that are compatible with the old 32 bit MASM prototype format. They should work OK with POASM. NOTE that there are no structures or equates, POASM can read C #define equates but anything else will have to find them elsewhere.
This is the format.
wvsprintfA PROTO :QWORD,:QWORD,:VARARG
INDEF __UNICODE__
wvsprintf equ wvsprintfA
ENDIF
wvsprintfW PROTO :QWORD,:QWORD,:VARARG
IFDEF __UNICODE__
wvsprintf equ wvsprintfW
ENDIF
wsprintfA PROTO :QWORD,:QWORD,:VARARG
INDEF __UNICODE__
wsprintf equ wsprintfA
ENDIF
wsprintfW PROTO :QWORD,:QWORD,:VARARG
IFDEF __UNICODE__
wsprintf equ wsprintfW
ENDIF
LoadKeyboardLayoutA PROTO :QWORD,:QWORD
INDEF __UNICODE__
LoadKeyboardLayout equ LoadKeyboardLayoutA
ENDIF
LoadKeyboardLayoutW PROTO :QWORD,:QWORD
IFDEF __UNICODE__
LoadKeyboardLayout equ LoadKeyboardLayoutW
ENDIF
ActivateKeyboardLayout PROTO :QWORD,:QWORD
ToUnicodeEx PROTO :QWORD,:QWORD,:QWORD,:QWORD,:QWORD,:QWORD,:QWORD
UnloadKeyboardLayout PROTO :QWORD
GetKeyboardLayoutNameA PROTO :QWORD
INDEF __UNICODE__
GetKeyboardLayoutName equ GetKeyboardLayoutNameA
ENDIF
GetKeyboardLayoutNameW PROTO :QWORD
IFDEF __UNICODE__
GetKeyboardLayoutName equ GetKeyboardLayoutNameW
ENDIF
See below for the corrected versions.
Thanks John.
I hope that Pelle in some day have time to develop x64 version of poasm too as recovery/WinPE environment accepts x64 binary in binary machine?
poide64 run in x64 but can't use COM.
AddIns can solve some problems as opening a file.
Anyone tested Microsoft tools in recovery environment?
Maybe time to start a new topic?
Sorry about the stuffup but as soon as I worked out a test condition, I had a typo in the conversion code and an error in the output of "PROTO" where it was adding a "," after PROTO. The attached file has been tested in ML64 which humerously still has the syntax checking for PROTO even though it does not support it.
Quote from: TWell on September 27, 2016, 11:50:07 PM
I hope that Pelle in some day have time to develop x64 version of poasm too as recovery/WinPE environment accepts x64 binary in binary machine?
Anyone tested Microsoft tools in recovery environment?
Maybe time to start a new topic?
Hi TWell,
The classical WinPE offered by MS is a simplified one and does not have a proper support of networking plus the lack of the Wow64 system does not allow you to run 32-bit executables on 64-bit WinPE systems. The right tool for the right job :
http://theoven.org/
I strongly recommend you to download the Win7PE SE and Win10 PE SE projects. They are excellent packages and have Wow64, network, .NET Framework support and many other powerful features. Please let me know if you have questions regarding Win7\10 PE SE.
Thanks.
But i think about what someone can do with just with install disk DVD.
So open a new topic in proper context for similar issues.
Just now i an a bored with this broken 8.1 :icon13:
So silly HID problem and MS can't help without install DVD?
In my case it was ATI that broke HID, but i have read how ATI & MS blames each other about that error.
Two big company can make a very big problem from such a small problem to solve.
But virus writers love that feature, OS without kb & mouse :icon_eek: