user57

Zalmann copper coolers they are pretty good "CNPS9000" "CNPS9500" "CNPS9700" "ZF1125BTH" "CNPS10X" maybe the "zalman ZM-CS1" but for this one you may look if that one fits to the MB others: "ACV Napoleon Socket 775" "Deepcool LGA 775" "Arctic Freezer 13 Co - socket 775" "Sunbeam Core-Contact Freezer LGA 775" " COOLER MASTER Hyper TX2 LGA 775" "Arctic Cooling AC Freezer 7 LGA 775" the "Zalman CNPS9900" i do not recommend, the 9900 is not copper

looks actually very good on reddit they say sometimes it can get laggy - maybe also the reason for this is that xp users useally dont have a fast cpu anymore youtube has changed their codec a bit too, the code got bigger, probaly less efficient too the hardware acceleration might plays a role that screenshot is from a dual core ? we might give xp a chance with similiar hardware a problem of high languages is that they trigger a "common code" such as the SDT too what result in more and more code - that then results in needed more cpu power the SDT is for example only there to provide an easier way to solve programming but that being said - that always leaded to "script like code" and as we know script languages are useally not very fast the more it goes at that direction of a script the less efficient the code get

most things have been said maybe search words "socket 775" and "sata" on an shop your cpu might be underclocked the term "DDR2-800" means 800 mhz FSB FSB is the speed to the RAM your CPU says it works with 1066 mhz (your ram use only 800 mhz of this) there are also DDR2 rams with 1066 mhz, useing DDR2-1066 mhz might be a idea as said DDR3 ram is useally cheaper now then DDR2 since socket 775 is kinda old i think all of that motherboards actually work with xp just look the motherboard description / or look what the driver(s) that are given support as motherboard drivers they useally have a list "win10/winxp/win7/winvista socket 775 is a intel cpu socket there like many cheap 4core/4 thread cpus for cheap prices (your cpu is a 2 core/2 thread) just to make an example here is a Intel Core 2 Quad - v Q6700 for only 6 € https://www.ebay.de/itm/276146665900?hash=item404b9fb9ac:g:7XYAAOSwUQllRsuk&amdata=enc%3AAQAIAAAA8D4emZzQFyg7ESoT4jkFIfMFtXZJBVQIXhF%2BXWjHPjTYD1TCBn4JwKfLg1usJAvF3JYsFSy7wyt1LECip2qzdRsi8gxtCk10q50KZKs%2Fx%2BcZPYgxNEKB39MDQUnZfGkr7LQCaey2c95xTgAWPuVEzIO0Itxx4Sb54760rxHFogZHjUU56mh4iZA0W98dY3PTOBFn5kOe219DLz32FZFdE46hzh8eVcpl0wXWPUQt4j1R8s3m6L38PxRWiA49IBkg1ok%2BOJAfTWk17IhzxUu%2F5wE77Tozlgybvwr5XB%2BT9zx0RdVq4uLTPTxCwA9imwczxA%3D%3D|tkp%3ABk9SR-KBt5SKYw list with 4 core - socket 775 cpu´s: https://de.wikipedia.org/wiki/Liste_der_Intel-Core-Prozessoren#Core_2_Quad RAM: "DDR2-1066 PC2-8500" 20 € for 4 GB RAM https://www.ebay.de/itm/116000436163?epid=113317048&hash=item1b022a2fc3:g:Z~oAAOSwIF9lbllM&amdata=enc%3AAQAIAAAAwIfSpqcPpBK2Nx4X9I5rtBqAjHL6guqCKQ8LuyWVdJWm43SnYoiYNpMtYUzIyM%2BIbboikCtj2rEvjYee4%2FWR6qLxLRStIaig2dhaFAN7ML7p0MJcGKkJYh7q7lTSJSsNWFeiK8g95etTe5tfrpc%2B%2BURK8XJBmEqI2NcEV1Ekrp9PbF7I6hFV2sLj5ygWz29i8zr%2FR%2F91z7pz%2BqDim0EatMh34FmfujqyRh9sRe9STrjooVYrEh0geGUfkwa8k09Jdg%3D%3D%7Ctkp%3ABk9SR_Tn65SKYw 7 € (but need 4 slots - some boards only have 2) https://www.ebay.de/itm/115984941065?hash=item1b013dc009:g:LtEAAOSwxI1lXM10&amdata=enc%3AAQAIAAAA4HZKG2TS64bjlKH0w8RMhWA1AXE5iqSLmHZmpWoYC82D%2B288ObEDsvNzEI0DJ%2F6kwECccmjiljypvy0lY5xde%2F6bfrxEodV0mS7xUPz8LRSWaVZt6gwTUZf7GstpF9qWlBR4Fn%2B8QP9ZXsY%2FvdTRk3hGb4%2FE4GX48Ct1kKRj8QMjxt8P7LV6ZgBTh2hca44Zpjx4oXTlyzeyf8EEjvM517rvvXpQz9AL4JvMFxhRvlRm6Jm5KZXdNgDBWv3VeIusVa5pBTilfGaG0NFUZxJR%2BstrvEz01uC6mRWkgGbMTqhF%7Ctkp%3ABk9SR7jKu5WKYw DDR3 is 9 € for 4 GB ram https://www.ebay.de/itm/362559898619?hash=item546a4103fb%3Ag%3AoBMAAOSwby9gC15q&amdata=enc%3AAQAIAAAA4LY3lKP0w0WooietvXE%2BOht58Xt0DNnW9GkZvNS0e2WUfOEL6kDGUQftKOholDnoiqKkrWwZw0OnZkY523mWXLS3gmfru6J%2F%2BfimURg0lvormJuPEHx55R4zQ8rV%2FKZs0plJ69BKhTsommBD7%2BHq3Dv0gK8plTjB0IdaWaPDRa9R7dCACSDByiyfb6nEtUEJLUO%2Fx0KkvvLyegpYrHkfi0%2B8mCIkRy8NkfMLMKe5tWA4cD2Dg5tWgViZ2e%2Fko7ovC%2BHiE9VPtaCY86KPQ5to%2BxROaFVKxE8bbLlnZlghB5nI%7Ctkp%3ABFBMwK2RlYpj&LH_BIN=1 useally it is also possible to underclock the RAM like 1333 mhz ram useally can run at 1066 mhz (that sometimes can have problems but you better be certain to get the intel before) grafic card: nvidia grafic card hard to say but look that a driver for windows xp is available that is done here: https://www.nvidia.com/download/index.aspx the second thing you have to look at is what slot your motherboard has (AGP/PCIE - some have only AGP some only PCIe , some even have AGP and PCIe)

well i was trying those who actually say they work in windows xp i tryed (chasys draw ies converter) 1: checking dependencies (heif/avif/avci) 2: video codec not found HEIC, common (avif, and av1) when doing the convert it dont create the file (it created an empty folder) prgramm (pixillion) calls up http://www.nch.com.au/components/libheif.exe i had to download that one, because IE6 in xp cant download that file but after that i installed libheif.exe but the converter just hangs up do i make something wrong ? both of these opened in windows xp but and installed

Intellectual Property Rights: A granted patent is valid for a maximum of 20 years, starting on the day after registration.

the EIP is for instructions (instrution pointer) (and useally is connected to a segment called the CS segment (or Code Segment) but a executable is not only made of instructions (buffers for example or just "data", some can see this with a PE editor the .text section is for code) using just 2 segments would already double the amount of memory (the segments in 32 bit proctected mode are 16 bit of in hex FFFF) the other segment is called the DS (or Data Segment) 16 bit means 65536 possible segments (this time including segment 0 or the 0) CS segment + eip = 16 bit * 32 bit = 65536 GB of ram (4 GB * 65536) (4 gb = 4´294´967´295) (4 gb * 65536 = 262144) DS segment + eip = 16 bit * 32 bit = 65536 GB of ram (4 GB * 65536) ES, GS could also be of interests FS is used by MS (but only 2 numbers/vars) (different approach : 4294967296 (32 bit size limit) * 65536 / 8 / 1024 (kb) / 1024 (mb) / 1024 (gb) = gb) 4294967296 * 65536 = 281470681743360 (again thats 1 segment only) 281470681743360 / 8 (byte) / 1024 (kb) / 1024 (mb) / 1024 (gb) = 32767 gb (this one is precise, not skipping some parts of the calculation or bits nor the 0) depending on how we calculate we either can use the / 8 for byte or / 1024 ( next kbit skip) or even the the classical / 1000 steps ------------------------------------------------------------------ an example for 16 bit (segments) that was a common trick in 16 bit 16 bits are FFFF and FFFF is 65535 (without the 0, aka you have to +1 that for the 0) what people might have heared 16 bit can use 1 megabyte of ram instead of 64k/65k ram (speacing k not kbit) thats because in 16 bit segments are used 16 bit have a segment register of 4 bits that makes 20 bit and 20 bit are ? we know 1048575 aka 1 MB (if we include the 0 then +1 = 1048576) thats also why they say "k not kbit" 1 M would be the right term (or it would be / 8 (byte) / 1024 (kb) / 1024 (mb)) https://en.wikipedia.org/wiki/Megabyte -------------------------------------------- here comes the trick point now we have PDE´s and PTE´s to simplify i will discuss that a bit easier the PTE is a relation to the direct physical memory as you guys might know we have severial executables (or processes running) in windows / in an operating system those used to start at 00400000 (for all processes) but how can it be that the same EIP for every process is 00400000 would that not just execute always the same programm or all at once ? right that dont make sence (if you said has a own address space yes but how can it lead to same memory address?) the reason is the PTE, that PTE holds the relation to a physical page thats why on every process change (the PDBR page directory base register) that PTE´s can address/point to a different memory (also the ones above 4 gb) and haveing all the time the same EIP at 00400000 /start of program https://en.wikipedia.org/wiki/Page_table the combination of 2 times 10 bits make only 20 bit (PDE and PTE) however here pages are the size of 4096 bit / 1 page (you are right this is 4 GB again (20 bits * 4096 = FFFFF(1048576) * 4096 = 4 GB) but here is the tricky part now the /PSE makes this 4 k (4096 bit) page to a 4 MB page (2 MB for /PAE) t g m k b taking that route for 2 mb (2097150) * FFFFF (20 bit possibilies (1048576) ) = 2´199´019´061´250 and that can be done just by turning the PSE flag on (and therefore point to higher memory then 4 gb) therefore XP / 32 bit can address with simple calculation / 1000 (kb) / 1000 (mb) / 1000 (gb) (often done with harddrives) = 2199 GB the real one however is / 8 / 1024 / 1024 / 1024 = 255 GByte (the non bit calculation or however i should call that) and that´s only per 1 process/executable, and even only 1 segment ! - because again the PDBR can be changed by process/executable using 1 segment already gives 65536 times that 2199 / 255 GB and each process can be addressed with different PTE´s (also the physical pages above 4 gb) thats a win win situation ------------------------------ Chappells reasoning is good in sence of that license detection, we cant see what windows really do here ... he later then explains that the license sets the PAE flag (but here i saw that with that 2 times 9 bit limit on the os wikipedia website) in sence of "hdd" (today ssd)) as ram im chappels meaning , you actually can use a SSD or HDD as memory and thats nothing new even (if memory is not needed unchange that (for example a level of a game)) and just use that ram again .... or store it in the harddrive - also possible in sence of DMA i dont know what chappels know here i cant talk about that i just dont know in sence of MMPFN i also dont know about this, it sounds interesting what chappell write here but maybe that MMPFN (from microsoft) always had the possibility - or maybe just it dont - i really cant tell one more word about /PAE the wiki page says for PAE its 2 times 9 bits that makes 18 bits and having only 2 mb page (that results in less ram what is possible with the normal paging, but more then 4gb still (around 137 gb thats near to chappels 128 gb) /PAE was rather of the NX flag nature (what is a data protection mechanism) if im wrong im happly being corrected https://msfn.org/board/topic/130001-32bit-windows-not-usingseeing-all-4gb-ram/

j7n is absolutly right that it also degraded actually the orginal file with same size isnt provided by wikipedia but what i still can tell is that even then it degraded a lot lower then the other heic file (even double compressed) because i didnt even have the orginal file, and compressed the entire image to around the same filesize then the image still had more pixels preserved even when 2 compressions happend, even then we can see the improvment and even when put to a higher compression the encoder from msfn still passed the other heic file (for this i actually made a even smaller filesize, what is around compared to the target filesize) the places are: 1 heic from msfn 2 heic from wikipedia heic 3 jxr - preserved the image better then the others 4 jpeg 2000 - yes preserved more pixels then normal jpeg 5 normal jpg - huge losses nowhere near the other compressions it can be seen on the lamp, that window, or from the "tree top left to the white car" the heic from wikipedia has lost that window split, jxr also lost that texture that can be tested by somebody just looking the lamp/or that window at the wikipedia file then testing if that texture was preserved with the msfn heic file (also trying different filesizes can be tryed) many image encoders actually have that "recompression problem", that they transfer to a RGB image and then recompress the image again. sometimes the differens ist not well seen but actually the image itself is not changed like in a RGB image for compression often a other approach is done: it just call the encoder (with the same settings) again ... what useally means again a few losses i wonder why Francebb hasnt answered yet he might actually have a h.266 image

well there are some websites that offer a decoder for that heif format https://strukturag.github.io/libheif/ is that one working for you ? but encoders are rare for now, special a encoder for winxp dont exits, and having hardware acceleration and this encoder use the best settings, best code, and dont go down the road any time to create a .heic file as everybody can see normal jpg, jpeg 2000 and jpeg jxr are beaten up even the heif file from wiki is beaten up

a dark background could actually be for energy saveing, aka it opens the question again if win10/11 is a smartphone software screensavers do use dark parts, because dark parts dont consume power, they simple not emmiting light an exception would be just to block the emmiting light, but that is normally not done lots of dark parts = less emmiting lights lot of bright parts = more emmiting lights actually a grafic interface that is dark could be remade for xp or even back to win95 here is a example of how a different gui style looked in windows 95

well it interhents from hevc (h.265) then the idea seems to be .HEIF (High Efficiency Image File Format) what can store multiple formats (such as jpg2000) but jpg2000 is not a new file format so the new files that are actually encoded with the new encoder are called .heic so .heic is what we want (High Efficiency Image Coding)

as promised .heic is brought to windows xp closing the gap for xp having a very new image encoder and decoder (and nothing using any other modules, engines or weird operating system dependencys) the resulting image is even better then the one on wikipedia https://en.wikipedia.org/wiki/High_Efficiency_Image_File_Format reason behind this i only choosed the best options, better internal code, better decisions, and disregarded code that decreases image quality ----- APP "WinXP HEVC/HEIF/H265 Image En/Decoder explained" The Encoder: Encode By Filename: allow you to select a file this heic encoder supports : .jpg, .png, .tif and .y4m (raw YUV format) the encoder make a .heic file from the choosen file Encoder By Folder: this read "Encode By Folder Searched Format Ending" if you have choosen jpg then it will search all .jpg files in the choosen folder actual chooses: png, jpg, tif or y4m if the entry was jpg then the encoder will encode all .jpg files in that folder to .heic this by folder was made so you can encode many files instead of always 1 file, while going to drink some coffee Encoder Complexity: "placebo" is the best setting here i actually dont see any reason to choose a different setting that actually only results in less image quality (best: 1: placebo, 2: veryslow, 3: slower, 4: slow, 5: medium, 6: fast , 7: faster, 8: veryfast, 9: superfast, 10 ultrafast) why we should we set a setting that decreases image quality? (basicly i not even wanted to have this box) (1 word about this, placebo use the best compressions tricks therefore the time is longer(more code = more time), the others try to speed up this (and leave out some functions, tricks, try to end the encoder before it really was done), it might not always increase the image - but you can be certain you got the best option (and the highest amount of pixels possible) also it can happen that that your image might not challenged the encoder for its maximum, then a "faster" setting dont have that much difference, still it can result in less amount of pixels, with placebo you are certain to get the maximum it really raise questions to use the others, you can make a big jpg file and you may dont see the image difference that much - but why ? are we making a jpg or are we making a high efficienty image encoder ?) Hardware Acceleration: makes use of hardware registers such as MMX, SSE and AVX this speed up encoding time a lot since the encoder is very complex image encoding can take time hardware acceleration makes encoding a lot faster notice: depending on your cpu power since the encoder is complex can take some time (if so keep a look "Encoded Image Files") (MMX, SSE and AVX are speed hardware registers they are between 64 and 512 bits wide, depending what one is available (yes in 32 bit)) Quality: controls the filesize of your .heic file, the lower this number the smaller your .heic file lossless: that option is not very useful as the real question is how well the pixels was preserved making a compression (we actually dont make a raw format - we make a compression) so better set this option to 0 (it dont make a real compression) Tuner: this increases the image quality even further good settings are psnr and ssim - the other settings only decrease image quality the tuner increased the amount of pixels, as said before its a extra function to improve more pixels more code = more time - this makes a good example - if you leave out many of good possible tricks you might end up in a less fancy picture ----- The Decoder: you have to choose a output image format for your .heic file (we have png, tif, jpg, and y4m) png compression level (0-9): png compression level -1 actually represents png compression 6 i actually dont see a well reason to have -1 as option, since -1 just represent compression 6 (you can try this out by looking at the filesize of the resulting .png file (try -1 and 6 they are the same) -1 actually is called png_default_compression what then is defined as 6 0 means no compression (this is good to make a compare how well your .heic file was preserved) increasing values make higher compressions losing more pixels (again 6 is equal to -1) 0 is the best png compression regarding pixels going from 0 to higher numbers decreasing image quality (higher numbers create smaller file sizes) (and make a compromise about pixels and compression) png is said to be lossless, but i only know for certain if option 0 is selected that it is a lossless copy. (what makes a 1:1 copy of the .heic file as it exits) jpg compression (1-100): nothing much to say here the higher this value the better the resulting jpg image notice higher values also cause bigger filze sizes 90 seems to be a good choice Decode By Filename: this button actually reads out "Decode In Format" why ? because if you select a .heic file the decoder has to know the decompression format valid formats are: png , jpg , y4m, tif Decode By Folder: reads out "Decode In Format" then the selected folder is searched for .heic files and then the decoder decodes all .heic files into the image format you set in "Decode In Format" Multi-pass: this makes a second image and compare the result with the first image - according to information this also improves image quality a bit (the h.266 says for example 1-3 % in average, then something about maybe sometimes more) Create A Subfolder: this allow you to put a folder where the WinXP HEIC en/decoder put its files it trys to create that folder, but you also can create that folder yourself this also avoid the name problem when controlling with "By Folder" ------ rumors say .heic is the best image encoder at the moment as we know .heic passes jpg, jpg2000 and jxr (jpeg xr) what we can see in the wikipedia site for heic maybe .heic also other jpg formats like the jxs format (what is rather speed orientated then quality orientated) there are some (jpeg xt, jpeg xs, jpeg ls, jpeg xe, jpeg xl) (https://jpeg.org) if someone wants to makes the compares the h.266 by frauenhofer or jxl would be candidates to try or even the others ... i actually never seen a h.266 frauenhofer image yet (updated the links): https://www.file-upload.net/download-15405155/WinXP_HEIC.zip.html https://www.mediafire.com/file/g9t94vi3dr4gycl/WinXP_HEIC.zip/file

when vc++ 2022 and windows 11 SDK is reached, and even win10 stuff isnt working anymore that means windtows xp passed to that win11 time in sence of compiler however why i have doubts if it was worth to spend the time for this project according to dibya no one actually used it it took many time to fix all of the problems and also i lost many time related to the hevc encoder, by now (everybody wants something from me, however there is not that much space for a different code on such very big projects) i really hope it was worth that dibya had a different idea how this work, something "super simple" "something super fast", i always told him no it is not that simple to add all these codes, it are 173 projects and such, and we need more of compiles ect. still however i fully explainded how to add the code now, i think he should be able to add the code by himself now at least he brought the requied patience once he realized what has to be done

francebb is back ? i thought last time he left us and said he should not look back anymore well if there is a limit set that should be able to be changed by the way we recently talked about francebb and that this might solve his problem, he wasnt there to see whats going on: https://github.com/reactos/reactos/commit/66dead68ec780a4a40c5b7d31f57e3646979a402 its from reactos just look this line: /* The forced speed, 10Mb, 100Mb, gigabit, 2.5Gb, 10GbE. */

i can not join the project fully yet - i have a long route to go still in the past i set the .heic picture encoder as main next needed target according to information around its probaly the best image encoder available at the moment, only other candidates are the frauenhofer h266 and jxl (the other jpg like JPEG XT, JPEG XS), dont have maximum image quality as their target goal but belive me the settings and how i made the code should be very competitiv even with those (edit deleting old links) this a pre type not released but it can convert a jpg or png to .heic (dont use other formats for now) the best is to use a lossless .png file (made from a raw file or lossless bitmap) .png is said to compress an image lossless (without losing any pixels) when compression level is set to lossless (aka 0 ) compression_level = -1 means default_png_compression level (PNG_Z_DEFAULT_COMPRESSION) what is the same as png_compression_level 6 so the compression levels go from 0-9 (0 is lossless) increasing that value set higher compressions (aka more losses in pixels) -1 actually dont exits it is just equal to 6, -1 dont mean a better compression then 0 would be the first choose if no pixel losses are wanted https://refspecs.linuxbase.org/LSB_3.1.0/LSB-Desktop-generic/LSB-Desktop-generic/libpng12.png.set.compression.level.1.html 1 picture of setting png compression levels in other programms (here 9): https://i.stack.imgur.com/NLfvP.png 0 being lossless for png and 9 being png highest compression aka smallest filesize the heic encoder settings : placebo = for best image quality (faster settings mean less image quality) tuner = something to tune quality even more PSNR and SSIM are good quality = control filesize of your .heic file lossless = lossless but not very useful - dont use this one (actually we want a good compression for a raw file, not a raw file itself - and its about how many pixels remained in the compression) hardware acceleration = make use of hardware registers such as mmx, sse, and avx (choose by filename) select a .jpg or .png file and the encoder encodes a single file to .heic (choose by folder) checks the ending in (format ending) in the selected folder and compress all files that have that ending for .jpg it is a good idea to make a big jpg file , big file size jpg means more pixels we like that

oh yes the idea of removing the SSE instructions by intel is a such thing intel probaly knows that SSE is a good competitor that actally can solve the compressions fast to get rid of those and programming their AVX512 they can force you to a new computer/cpu and those intel 12 gen + are spywares - and benefits systems or mechnism that support such idea´s they just make certain the computer is safe against you - for microsoft thats the idea - intel and microsoft seems to be brothers in arms in this question if SSE would stay there would be a valid good solution for intense compression it it also backwards compatible what avx512 is not microsoft creating a new monopoly ? microsoft is well known for lawsuits in that direction only one of many many many cases: https://www.jurist.org/news/2022/12/microsoft-faces-private-antitrust-lawsuit-over-68-7b-purchase-of-activision-blizzard/ there had to be something wrong with the "deal"

exactly and people always said: that will not happen intel will never support a such mechanism they dont just change their policies / terms of use to something more bad -> even more is possible now intel even removes SSE commands they removed the 16 and 32 bit modes too - what is wrong using a old hardware with a new cpu ? or also "security is always good" yes against yourself - and making the software secure against you for microsoft - security against you - security for microsoft and thats also why they stopped the support for this version there was nothing wrong with it

well here is the v16.0.5 https://www.file-upload.net/download-15158304/LLVM_XP_v16.zip.html it contains also some screenshots

deleted

there is often a missconseption 32 bit means 4 gb ram limit thats not directly right first there is a second register (segment registers) that can take another *FFFF (16 bit)= 65535 * 32 bit (aka FFFFFFFF = 4gb) offset register = 281470 GB address room (and thats only https://wiki.osdev.org/Segmentation (gs would be a good candidate) but windows isnt doing that at least for windows xp i told them to make a virtualalloc2 functions what also returns the segment register that then could pass the 4 gb limit a second way is that when a process is switching the PDBR page directory base register changes that means it can address 4 gb each process thats because the memory is addressed by entrys if the entrys point to a different ram it could use the other ram a other problem is that usermode limit 7FFFFFFF (2gb) and the rest is kernel mode both make 4 gb (2 * 2gb) 80000000-FFFFFFFF is used by kernel (aka 2 gb) there was a time the usermode was extended to like EFFFFFFF (because the kernel mode do not need that much ram) the next problem is that windows useally maps those entrys for a maximum of 4 gb size that means going beyond without changing that system overwrite the PDE´s what cause a os crash

not having knowlegue about this but structure si->si_band it is saying it has no such "si_band" member was it renamed or deleted ?

greetings all, we found the related information that caused that problem even tho we have no inside information, the information i posted is incredible accurate so here is what microsoft did, it probaly is useful information to know https://github.com/microsoft/STL/pull/1194/commits/faa3434d7e748fcfdc253ad2788a0e4fddfea105 explain that __crtInitializeCriticalSectionEx(&_M_critical_section, 4000, 0); // to InitializeCriticalSectionEx(&_M_critical_section, 4000, 0); it also explains why the dependency walker for versions up to 16.7 show a try to search for that functions (meant is that there these functions where found on dependency walker but not in the import list)

well i gone after that annotions message here is a next test: https://www.file-upload.net/download-14953656/SumatraPDF3.4.6.zip.html (edit now has a own jxr decoder) the dialog should apear now and ask "save to existing pdf, ect." well with the JXL file i think you got a version problem JXL should open on a new version of windowscodecs.dll a programmer has the choose to let a engine do the encode/decode, or manual this time windows is choosen to do so, if it cant find the the decode routine, it wont work here is a list that seems to be involved (from a programming standpoint it is just windowscodec.dll (that is the one we give the jxl file) WINDOWSCODECS.DLL loadlist: WINTRUST.dll IMAGEHLP.DLL WINTRUST.dll - loads and connections : RSAENH.DLL CRYPT32.DLL ADVAPI32.DLL xpsp2res.dll crypt32.dll - loads and connections : userenv.dll VERSION.dll CRYPTNET.DLL userenv.dll - loads and connections : SECUR32.DLL netapi32.dll CRYPTNET.DLL - loads and connections : PSAPI.DLL SENSAPI.DLL WINHTTP.DLL WLDAP32.DLL OLE32.DLL - loads and connections : wmphoto.dll sendmail.dll maybe not all are requied

well i have made a test version but notice this one is only experimental del

i readed it today, the first time it still had the 3.3.3 version also working on other project but whats new with it ? it might be of use

there is already a problem 1 function isnt found by visual studio RtlRaiseStatus so i looked the ntdll.lib and the lib file has got the function RtlRaiseStatus is present in ntdll.dll in windows xp ntdll.lib is added in the linker list so i added the function to at first my cpp file then on winnt.h NTSYSAPI VOID NTAPI RtlRaiseStatus( DWORD Status ); but the visual studio compiler keeps telling me that it dont find that i also tryed with NTSTATUS instead of DWORD but that doesnt change anything what is causeing that problem? i know i could go for a loadlibrary and getprocaddress or maybe the definition from reactos well i choosed a solution just by doing the same thing windows is doing VOID NTAPI RtlRaiseStatus(IN NTSTATUS Status) { EXCEPTION_RECORD ExceptionRecord; ExceptionRecord.ExceptionAddress = _ReturnAddress(); ExceptionRecord.ExceptionCode = Status; ExceptionRecord.ExceptionRecord = NULL; ExceptionRecord.NumberParameters = 0; ExceptionRecord.ExceptionFlags = EXCEPTION_NONCONTINUABLE; RtlRaiseException(&ExceptionRecord); }