D.Draker

This is good , you could use much newer onces , obviously . The thing is they want them for 1000 series and that's not possible. See my test above. Just finished it.

Suddenly had a chance to do a quick test on a GTX 1070 8GB from my neighbour. While the modded driver worked fine with a card from 2014 , it failed with this one miserably ! Awful framerates (like 10-15 or so) . Error from the log : "Dedicated video D3D11 device creation failed" So you all could just leave win32 alone because the lack of newer drivers has nothing to do with the ex-kernel and looks like no one's gonna write the new ones , sadly. So either you buy older gen cards or live with these terrible framerates . It couldn't even properly recognise the card ! See: ID=0x0 . And it tried to run on a "software adapter" at DX 10.1 (!). The only thing it got right - the amount of VRAM: 7998 MB. From the Mono engine DX11 game Log : d3d11: CreateDXGIFactory2(...) not found, fallbacking to CreateDXGIFactory1(...). d3d11: D3D_FEATURE_LEVEL_11_1 not-recognized (only 11.0 runtime installed?) d3d11: QueryInterface(IDXGIFactory5) failed (80004002). Direct3D: Version: Direct3D 11.0 [level 10.1] Renderer: Software Adapter (ID=0x0) Vendor: VRAM: 7998 MB Driver: 27.21.14.5638 Begin MonoManager ReloadAssembly - Completed reload, in 0.657 seconds WARNING: Shader Unsupported: 'Legacy Shaders/VertexLit' - All passes removed WARNING: Shader Did you use #pragma only_renderers and omit this platform? Dedicated video D3D11 device creation failed (error: 0x80004005). So here you go , did a test on a newer card for all of ya ....

The modded driver works on Vista x86 and the older gen card (900 series) without issues. My trick with packing the dll in a usual zip folder worked like a charm. But talking about x86 and the original kernel would be off-topic here, so I'm just informing of my partial success and hoping someone would continue my work. It's getting really hot here and my damaged brain is literally melting , even with AC always on , so I'm taking a break.

Dave , did you try to change the IP? All of my problems usually go away if I switch to another IP from a certain country that instagram loves. Some time ago I created a topic with the solution. https://msfn.org/board/topic/183282-instagram-communist-coutries-are-in-favour-help-to-get-clean-ranges-of-communist-ips/?do=findComment&comment=1211198

You're joking , right ? Please define "proffesional". Instagram has always had terribly compressed pictures and videos, like from the early 2000s. 156kb jpeg photo in 2022 , lol . Or 720p mp4 ? Wow . We are stunned. Even Twitter doesn't compress the media that much.

1 - Even after I switch windows to test type (I see the watermark on the screen) it still asks if I want to install the "unverified driver" crap. Is it really working ?! 2- I modded the installer of 390.67 to include the patched files . I traced what installer does . It extracts and places my patched DX9 and DX10/11 driver files , but when it comes to the kernel.sys , it extracts fine, but blocked from placing into into the system folder ! Installer failed , finita la commedia. I of course understand I could place it there myself , but I wanted the installer to do it . So what do we have ? The DSE is not really working on 64-bit systems ?! EDIT: Also , KSECDD.SYS isn't in the "right" place ? See the below.

Unfortunately we can't touch PE , like win32 said.

By any chance, you know an easy way how to redirect it from kernel to psapi in the dll itself , not in windows ? Thanks.

What can I do to entertain you ? Some funny horror stories from my childhood maybe ?

My licence doesn't say I can't modify the installed image and do its reimaging later.

It's not available ... but available . Need to exercise some cosmic connections . Be creative, I'm sure you'll get it soon.

Thank you , but the dll wants it to be in the kernel , unfortunately. Fake redirect results in weird behaviour . All I'm saying , the dll needs to get some real values. It expects them. Looks there's a chance to launch it otherwise. Also , started to dig much newer versions and they dumped idiotic Windows 7 APIs and started to use only the ones available in Vista . There are lots of negative reviews/articles 'bout those APIs. I had to read a lot ... This driver is very fast , BTW . Example : driver of the 456.xx series loads the main nvwgf2umx.dll (32 and 64 bit , both) *even without the ex-kernel* just fine ! nvwgf2um.dll - DX10/11 32-bit driver nvwgf2umx.dll - DX10/11 64-bit driver These are all I need , 'cause I don't play DX9 games.

Well , you already ordered it ... DDR4 is something I'd want in 2015 - 2016 , I remember there were tons of combo DDR3/DDR4 boards and changing the RAM type had almost zero impact on the performance. But with an Intel CPU you should be fine with that DRR4 , like I said.

@Wunderbar98 , your tag doesn't work . Perhaps it has something to do with your browser ? Oh , the game is young , thanks for reminding ... only about 19 - 20 years old. A perfect age for ones girlfriend. Why wait for winter ? Just turn your AC on , problem solved , I don't ever switch it off . Helps to keep the paste intact. EDIT: @Wunderbar98, you could also cover your windows with aluminum foil to block sun , esp. if your windows are big . Also , there should be some special coatings and foils at the stores. This will let the temps go down . Luckily I live in an old house and we have massive shields on the windows , and even so , I still use foils .

I'm pretty sure that's what I did earlier , I did not rebuild it . I removed the checkmark. Replacing K32GetModuleFileNameExA with GetModuleFileNameA was a success. Replacing K32EnumProcessModules with EnumProcessModulesEx was a failure . Found this official statement by Microsoft : "Programs that must run on earlier versions of Windows as well as Windows 7 should always call this function as EnumProcessModulesEx." https://docs.microsoft.com/en-us/windows/win32/api/psapi/nf-psapi-enumprocessmodulesex Is this a blatant lie 'cause ther's no such thing in Vista ? Perhaps you know what to insert instead ? Thank you.

I don't know about IT forums , I compared myself in games and such. Intel CPUs are usually fine with slower RAM .

Honestly , if you're that determined to buy something really new , just buy a DDR5 board 'cause they'll soon be down in price and you'll get a future proof solution . Why ? DDR5 is drastically faster, while DDR4 sucks . I didn't notice a huge difference between a good DDR3 and DDR4 . DDR4 is just basically overclocked DDR3L with insane timings (that's what make it suck). The only downside would be a problem to use 64-bit Vista with such boards. But then again , who knows ? Perhaps they change something again and it will run fine.

So you mean I need to patch the drivers and then prevent the tool to automatically rebuild the PE header while letting only the checksum to be fixed ?

A big concern is when it's too dry one could damage the GPU chip when trying to detach it. EDIT: I mean chips without metal cover plates.

I still have some leftovers of the thermal paste made in Czechoslovakia , lol. I'm afraid to use it on anything important , but is still works ! White colour , for transistors in amplifiers . EDIT: @UCyborg, yes , about 40 years old ...

1 - Absolutely ! I'd say use a good thermal compound and change it once in 2 years it is enough if you don't game every day. 2- Aren't they suppose to throttle down the speed and/or shut down ? I'm not talking about CPU from the 80's , of course. 3 - Indeed you are ! You are supposed to play Spellforce , no ? lol

First off , thanks , you are very helpful , as usual. It looks like a telemetry function , no ? Earlier drivers didn't have it and worked just fine. Anyways, the less those plonkers know about my CPU, the better ... lol. I've been (and shall be) away for some days from my testing Vista PC. Only a good one is here near me (which I don't want to mess with). So I tried to change just one bit in the sys : wcsncpy_s was changed to just wcsncpy , to be precise, and then I tried to load it on a junk win 7 PC x64 - nothing worked . It says a corrupted driver smth like that. The PC starts just fine, but with a generic driver only. Of course I disabled the driver signature and rebooted before I installed it. Looks like this procedure doesn't fully disable the checks on win 7 x64. Would it be the same with Vista ? That's why I asked about signing them . Selfsigning maybe ?

Also about 390.67 6 - No missing dependencies in nvwgf2um.dll DX10+ driver. 7 - No missing dependencies in nvcompiler32.dll, nvcuda32.dll, nvcuvid32.dll, nvd3dum.dll 8 - iCafe drivers tend to have less missing dependencies in general. 9 - Looks like the last 32bit driver. I have a couple of questions , do I need to rebuild the cheksum ,or just change the values ? Did you sign the dll after you patched? Did you pack them back with 7zip ? I mean for the installer. Do we need to remove KSECDD.SYS BCryptGenRandom ? Just in case someone wants to join: https://drivers.softpedia.com/get/GRAPHICS-BOARD/NVIDIA-GeForce-iCafe-Graphics-Driver-390-67-64-bit.shtml https://drivers.softpedia.com/get/GRAPHICS-BOARD/NVIDIA/NVIDIA-GeForce-iCafe-Graphics-Driver-390-67.shtml

Being French (like you kindly noticed), I sometimes find your American(?) sense of humour rather hard to follow and not always sure what you mean. Oh, and you forgot to include the chinese and indians to that list. Also, from I gather, one would need to purchase a licence for Windows 7 ESU updates. So looks like *for those without it* the "secure" life of windows 7 had ended 2.5 years ago.