Recent posts

#11

Bug reports / Re: Creating resource with man...

Last post by PaoloC13 - March 19, 2026, 12:14:37 PM

Thanks Timo and John,
I've worked on the original version of the manifest automatically generated by version 13.00.9:

Code Select Expand

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<assemblyIdentity
    type="win32"
    name="MyOrganization.MyDivision.MyApp"
    version="1.0.0.0"
    <!-- processorArchitecture="amd64" -->
    processorArchitecture="X86"
/>

<description>Verbal description of MyApp.</description>

<dependency>
  <dependentAssembly>
    <assemblyIdentity
        type="win32"
        name="Microsoft.Windows.Common-Controls"
        version="6.0.0.0"
        processorArchitecture="X86"
        publicKeyToken="6595b64144ccf1df"
        language="*"
    />
  </dependentAssembly>
</dependency>

<!--
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
        <requestedPrivileges>
            <requestedExecutionLevel
                level="asInvoker"
                uiAccess="false"
            />
        </requestedPrivileges>
    </security>
</trustInfo>
-->

<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
  <application>
     <!-- Application supports Windows 10-->
     <supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}"/>
     <!-- Application supports Windows 8.1 -->
     <supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}"/>
     <!-- Application supports Windows 8 -->
     <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
     <!-- Application supports Windows 7 -->
     <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
     <!-- Application supports Windows Vista -->
     <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
  </application>
</compatibility>

</assembly>
Proceeding step by step, I've identified three problems, each of which alone causes the .exe to break in my sysem (now I tested also in Windows 10).

1) Line 8 - XML comment inside an opening tag.
   <!-- processorArchitecture="amd64" -->

2) Line 9
   processorArchitecture="X86"

3) Line 20
   processorArchitecture="X86"


Fixes:

1) comment outside <assemblyIdentity ... />

2 & 3) processorArchitecture="*" (processorArchitecture="X64" don't work)

#12

Bug reports / Re: Creating resource with man...

Last post by John Z - March 19, 2026, 10:06:02 AM

Hi PaoloC13,

I can't replicate the same problem because I uninstalled and reinstalled. It now compiles, but the .exe is broken. I suspect a file encoding issue (or some flag I haven't set?). You cannot view this attachment.

Attached a new version which compiles and runs with a simplified manifest.  If you add to it, do it step by step testing each addition

John Z

#13

Assembly discussions / Re: Verifying the support of t...

Last post by Vortex - March 19, 2026, 10:03:41 AM

Shorter 32-bit version and new upload above.

#14

Beginner questions / Re: same code pelles c and gcc...

Last post by ander_cc - March 19, 2026, 09:20:27 AM

Thank you, rweidner and John Z!

#15

Bug reports / Re: stdckdint.h bug report

Last post by ander_cc - March 19, 2026, 09:19:51 AM

I think ckd_<op>() came more or less straight from GCC to the C23 standard, and like some other GCC "innovations" it's a bit over-worked / under-thinked.

I will revise my initial implementation slightly, mostly just to reject more bogus cases -- like the original bug report.

Thank you, Pelle!

[_write()]

#16

Bug reports / Re: bug report. setvbuf() func...

Last post by ander_cc - March 19, 2026, 09:19:30 AM

In the low-I/O C runtime function _write(), when operating in text mode (ANSI/UTF-16LE/UTF-8/...), there is a ~2kB buffer for LF to CRLF translation. When this buffer is full, the content is sent to the destination (console/file/...), the buffer cleared, and the translation resumed. When resuming the translation the first character was lost (in translation).

( The printf family is one path to the _write() function )

Thank you, Pelle!

#17

Bug reports / Re: Creating resource with man...

Last post by TimoVJL - March 18, 2026, 11:39:45 PM

Just remove comments from xml file
like

Code Select Expand

    <!-- processorArchitecture="amd64" -->and use this line if it is common to X86 and X64

Code Select Expand

    processorArchitecture="*"

#18

Bug reports / Re: Creating resource with man...

Last post by PaoloC13 - March 18, 2026, 10:48:12 PM

I can't replicate the same problem because I uninstalled and reinstalled. It now compiles, but the .exe is broken. I suspect a file encoding issue (or some flag I haven't set?). You cannot view this attachment.

#19

General discussion / Re: Compiling using pomake

Last post by John Z - March 18, 2026, 08:57:56 PM

Yes, the povarsxx.bat files are generated at install time and are based on the directory (default, or user entered) during the install dialog.

To successfully run multiple versions is a bit more complicated however, thus the use of an xml file(s) as Timo mentioned.

John Z

#20

Announcements / Re: Release Candidate #1 for v...

Last post by Vortex - March 18, 2026, 07:05:24 PM

Hi Timo,

Thanks for the new tool. My result :

Code Select Expand

MOVBE not supported