Author Topic: Discussion about Demo of old style controls on a normal window.  (Read 4850 times)

TWell

  • Member
  • ****
  • Posts: 748
Re: Discussion about Demo of old style controls on a normal window.
« Reply #30 on: March 03, 2017, 09:20:18 PM »
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

  • Member
  • *****
  • Posts: 8510
  • Assembler is fun ;-)
    • MasmBasic
Re: Discussion about Demo of old style controls on a normal window.
« Reply #31 on: March 03, 2017, 11:15:06 PM »
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 :badgrin:
- 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
« Last Edit: March 04, 2017, 03:59:17 AM by jj2007 »

hutch--

  • Administrator
  • Member
  • ******
  • Posts: 5486
  • Mnemonic Driven API Grinder
    • The MASM32 SDK
Re: Discussion about Demo of old style controls on a normal window.
« Reply #32 on: March 04, 2017, 05:25:44 AM »
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.
hutch at movsd dot com
http://www.masm32.com    :biggrin:  :biggrin:

nidud

  • Member
  • *****
  • Posts: 1528
    • https://github.com/nidud/asmc
Re: Discussion about Demo of old style controls on a normal window.
« Reply #33 on: March 04, 2017, 06:40:24 AM »
Is there a manifest added to ML.EXE?

TWell

  • Member
  • ****
  • Posts: 748
Re: Discussion about Demo of old style controls on a normal window.
« Reply #34 on: March 04, 2017, 07:21:05 AM »
@ninud
you are cruel :biggrin:
No support for windows 10 :biggrin:

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
« Last Edit: March 04, 2017, 08:00:31 PM by TWell »

nidud

  • Member
  • *****
  • Posts: 1528
    • https://github.com/nidud/asmc
Re: Discussion about Demo of old style controls on a normal window.
« Reply #35 on: March 04, 2017, 08:41:19 AM »
 :biggrin:

Had a little run-day view with windows 10 some time back. A family member finally cave in to the update lure and installed it: mouse didn't work, printer didn't work, and the internet connection only worked in "mobile mode" so I'm not that "supportive" of windows 10 to put it mildly.

As for the lack of manifest in various binaries that doesn't seem to be a problem thought.