Recent posts

#1

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Kochise - Today at 04:33:21 AM

Indeed.


Total Commander does it too : select files/folders, menu Files, select Create checksum file(s). The generated file can then be checked against another set of files.

I'm not the author of this Swiss army knife, its author is Swiss though, that may explain.

#2

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by TimoVJL - Yesterday at 11:54:28 PM

Interesting tool
https://www.nirsoft.net/utils/hash_my_files.html

#3

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Kochise - Yesterday at 11:24:51 PM

Sure, but the Github repository doesn't provide the installer but the installed files. So the installer's MD5 won't help there.

#4

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Vortex - Yesterday at 10:03:26 PM

Yeah, it's not about the installer but the installed files.

There is a reason why MD5 values ared supplied with large iso files. A MD5 hash tied with the host iso file is easier to manage. No need to calculate the hashes of the individuals inside the iso.

#5

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Kochise - Yesterday at 09:33:50 PM

Thank you for the clarification.

#6

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by TimoVJL - Yesterday at 04:11:15 PM

With WinMerge, those bin files are identical with Pelles C 13.00.

#7

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Kochise - Yesterday at 01:38:09 PM

Yeah, it's not about the installer but the installed files.

#8

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Vortex - Yesterday at 10:13:19 AM

It's easy to calculate the hash of the latest installer, setup.exe v13.01 with Powershell :

D:\>Powershell -Command "(Get-FileHash "setup.exe" -Algorithm MD5).Hash"
4ABBD312312B7D2F1EDF5C0A9A2D1DC4

D:\>Powershell -Command "(Get-FileHash "setup.exe" -Algorithm SHA1).Hash"
65B178ECF29C3C59121818E794969F1E4A0987E4

D:\>Powershell -Command "(Get-FileHash "setup.exe" -Algorithm SHA512).Hash"
14E6339D5F55063E91A331201C9E20B77402941C8E157639CB9FE77FD16BD9309ABB8058CDDCC83DDA3852A51828F3E674AB47EB79B9C13A6E89F7CE7C2F5315

D:\>Powershell -Command "(Get-FileHash "setup.exe" -Algorithm SHA256).Hash"
84E586D1FCA7B9FEC55BD294A103AF16A045D1DF1BCB77A3F4FDF13D8F239141

#9

General discussions / Re: smorgasbordet.com/pellesc/...

Last post by Kochise - Yesterday at 09:35:01 AM

Since you questioned the "integrity of those file" it was only fair to check them by yourself, just to be sure.

It is nice to know that the "official current version of Pelles C" is back online.

Keep in mind the "GitHub hosted Pelles C files" can be executed online, without even having to install or clone them locally.

#10

Assembly discussions / Re: Getting memory capacity

Last post by Vortex - January 26, 2026, 06:09:10 PM

Another version based on the API function GlobalMemoryStatusEx :

Code Select Expand

include     GetMemory.inc

.data

fc1         db 'The computer %s '
            db 'has %u Gb of memory.',0

nSize       dd 32

.data?

CompName    db 32 dup(?)
MemStat     MEMORYSTATUSEX <?>

.code

start:

    invoke  GetComputerName,\
            ADDR CompName,ADDR nSize

    mov     edx,OFFSET MemStat
    mov     MEMORYSTATUSEX.dwLength[edx],SIZEOF(MEMORYSTATUSEX)

    invoke  GlobalMemoryStatusEx,\
            ADDR MemStat

    mov     edx,OFFSET MemStat

    mov     eax,DWORD PTR [edx+MEMORYSTATUSEX.ullTotalPhys]
    mov     edx,DWORD PTR [edx+MEMORYSTATUSEX.ullTotalPhys+4]

    mov     ecx,1024*1024
    div     ecx

    invoke  printf,ADDR fc1,ADDR CompName,eax
           
    invoke  ExitProcess,0

END start