Discussion about Demo of old style controls on a normal window.

[TWell]

BTW:

about linker commandline

bare /LARGEADDRESSAWARE if for win32 x86.

LARGEADDRESSAWARE is default for win64 x64, so only rare occasions /LARGEADDRESSAWARE:NO is needed.

another thing:
C isn't bloated, CRT is and in early days, lot of it was written in assembly ;)

[jj2007]

Yes or /MANIFESTFILE:filename

Dangerous option: if you specify an existing file, it gets overwritten!

The right option seems to be /manifestinput:MyFile.xml, but apparently it requires linker version 14, difficult to set up etc, and eventually it will ask you for a non-existent mt.exe :(

EDIT: Finally, I managed to convince LINK 14.0 to perform its task. It's messy, as usual
- the relevant commandline options are /verbose /manifest:embed /manifestinput:MyFile.xml
- you need at least \Masm32\bin\mspdbcore.dll
- the linker will choke unless you move MT.EXE into the bin folder
- if you are lucky, MT.EXE sits in C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin\mt.exe
- if you don't like the /verbose option, try without; on my machine, the infamous -ologo error pops up

Anyway, even for X64, polink and a standard XP manifest with processorArchitecture="*" works fine :P

[hutch--]

JJ,

Herein lies the difference, the manifest in the demo work just fine on my Win10 64 and Win7 64 just as it has for every other EXE that has been built with it and has proven to be reliable. I make no assumptions about cross OS version compatibility and don't need it as 64 bit MASM does not build 16 or 32 bit code, ML.EXE does that fine. I am pleased to hear that you have solved the problem you had with manifests and have a version that works across 32 and 64 bit code but I will make the point again that the one I am using works just fine and I have no need to change it at all.

[nidud]

deleted

[TWell]

@ninud
you are cruel
No support for windows 10

ml.exe v.14

Code: [Select]

<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"></supportedOS>
<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"></supportedOS>
<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"></supportedOS>
The following GUIDs correspond with the indicated operating systems:

Code: [Select]

{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a} -> Windows 10 and Windows Server 2016
{1f676c76-80e1-4239-95bb-83d0f6d0da78} -> Windows 8.1 and Windows Server 2012 R2
{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38} -> Windows 8 and Windows Server 2012
{35138b9a-5d96-4fbd-8e2d-a2440225f93a} -> Windows 7 and Windows Server 2008 R2
{e2011457-1546-43c5-a5fe-008deee3d3f0} -> Windows Vista and Windows Server 2008

[nidud]

deleted