The kernel

[techwg]

Can i use my windows version of kernel32.dll to make wine be more compatible with software? I have tested this and i dont see any difference. I also coppied a random dll and renamed it to kernel32.dll expecting programs to totally fail to work. The programs continued working as ususal, even though i added an override in the settings to use native OS dll for kernel32

Can anyone give me some input on this?

[jorl17]

Can i use my windows version of kernel32.dll to make wine be more compatible with software? I have tested this and i dont see any difference. I also coppied a random dll and renamed it to kernel32.dll expecting programs to totally fail to work. The programs continued working as ususal, even though i added an override in the settings to use native OS dll for kernel32

Can anyone give me some input on this?

(Correct me if wrong, please)

No. kernel32 is a core lib of Windows. These core functions implemented by Windows cannot be implemented in Unix-based systems/ran in Wine. Wine's kernel32 implementation is different (if you try, for instance, to run it in Windows it'll fail too).

Where did you put your kernel32.dll? What happens in terminal? I'm guessing it reports failure when loading the DLL and, thus, reverts back to the builtin.

Besides that, it probably wouldn't be helpful in compatibility (even if it made sense to replace it). You'd probably be able to bypass some game protection (but that's a very, very loooong guess).

Cheers,

Jorl17

[techwg]

terminal? its all GUI. I put the dll i the proper system32 directory where it should be. Forgive me, im a total linux noob, i know very basic terminal commands enough to navigate, edit files, maybe MAYBE compile something.

[DaVince]

Just remove the file and Wine should automatically place the original kernel32.dll back.

Wine might even just ignore or overwrite the replaced DLL since it's a core part of Wine, so you wouldn't notice if it didn't work.

[James Mckenzie]

All:

Just remove the file and Wine should automatically place the original kernel32.dll back.

Wine might even just ignore or overwrite the replaced DLL since it's a core part of Wine, so you wouldn't notice if it
didn't work.

This file cannot be overridden by just selecting the file in winecfg. The file has too many differences from the file supplied by Microsoft to even work properly.

If you are having problems running a program, tell us the program name and what the problem is. Randomly swapping out dlls may break your Wine installation and render Wine unusable.

James McKenzie

[jorl17]

terminal? its all GUI. I put the dll i the proper system32 directory where it should be. Forgive me, im a total linux noob, i know very basic terminal commands enough to navigate, edit files, maybe MAYBE compile something.

Well, GUI doesn't prohibit text-mode interfacing or output . Wine outputs quite some messages to stdout (stderr too?) and those are visible in the terminal. Try it: Open up a terminal/console and type in: winecfg. You'll see wine config.

[techwg]

I typed wincfg, it opened and everything but the console was blank, even when i deleted my dll rule and made it again.