dodicat wrote:for the less well heeled, about 80000 dollars a head (literally).

They will probably end up less well healed.

Don't expect miracles from RtlCompressBuffer...

FB, MichaelW: NTDLL buffer compression vs ZLIB
José Roca: RtlCompressBuffer and RtlDecompressBuffer
Masm32: How difficult is it to build a shrinking/deflating routine?

Works fine, compliments! What I find slightly odd is that Acrobat reader asks me, when closing the doc, whether I want to save changes.

Glad I could help, and welcome to the forum!

It depends on what is "right" for you. Under the hood, memory is 60 4F 7D 59 你好 You are under Windows or Linux? The issue here is endianness: printf("0: %x \n", ws[0]) ' print 4f60 this is a WORD printf("%x ", (*zsp)[i]) ' this prints BYTEs

For the most curious case, it seems that "dim as integer x = x" means "dim as integer x = any" , yes? dim as integer a=a print "a=";a Gas says a= 4218880, which happens to be the entry point. Gcc loads [ebp-40], which may be 0 or -1. Not everything that looks like code...

Very cute!

If instr() takes several minutes, then you have a serious design problem. Can you post your code?

You forgot the Dodicat and Google cheatam's algorithm, now known as DaG-ca beta (an idea from badidea) Excellent! 0.106 seconds 50599 DaG-ca beta 0.096 seconds 50599 PopCount asm 0.142 seconds 50599 PopCount FB 0.097 seconds 50599 DaG-ca beta 0.093 seconds 50599 PopCount asm 0.141 seconds 50599 Pop...

A table-based solution is fastest: 31 ms for popcounting a total of 159997056 bits 31 ms for popcounting a total of 159982282 bits 31 ms for popcounting a total of 160004121 bits 30 ms for popcounting a total of 159992999 bits 31 ms for popcounting a total of 160005776 bits 31 ms for popcounting a t...

Great stuff, marpon! Here is a condensed test file using #define path and #define win10: #define PdfPath "C:\FreeBasic\Print_to_Pdf-master" #define Win10 1 ' put 0 if you run it on older Windows versions /' test example to use libPrint2Pdf32.a or libPrint2Pdf64.a version 1.0 by marpon 08 M...

To clarify one more bit: It's a constant because YOU instruct the compiler which is your target platform. So, if you are working on an application that is supposed to run on a thousand very, very old Windows XP machines, then you tell the compiler "hey, this is old stuff, please do not use func...

your code has little, if any use, in practice. I was curious if there was any difference between these two ways to open a file and get a pointer to its content: Dim as long flen=Lof(f) #define version 0 #if version Dim as ubyte ptr pContent = Allocate(Lof(f)), CurPos=pContent, CrPos Get #f, 1, *pCo...

Win7-64 should be version 6.1, build 7601 but the macro returns 1282.

Does it miss a file?