> What I'm wondering is: if I don't care about being a Wine "purist", and I have a legitimate copy of Windows laying around, is there any way to dissect that co

> What I'm wondering is: if I don't care about being a Wine "purist", and I have a legitimate copy of Windows laying around, is there any way to dissect that copy of Windows for its files (drivers, helper executables, etc.) and wrap them around a Windows EXE, such that Wine will be using as few Wine implementations of DLLs as possible, rather than just the minimum required to get the individual EXE vaguely working? Is there a way to start off a Wine install with "maximum compatibility" like this? the majority of problematic DLLs are officially redistributable by MS. the vast majority of the remainder depend on undocumented kernel APIs, which are... also unimplemented in wine, and usually the reason the builtin wine DLL doesn't work properly. you'd have an easier time importing your legitimate windows drivers to Linux, through ndiswrapper!