What is the purpose of PE conversion of *.sys drivers?

[Jinoh Kang]

On 7/5/22 18:44, Stefan Dösinger wrote:
> 
> 
>> Am 04.07.2022 um 00:17 schrieb Jinoh Kang <jinoh.kang.kr at gmail.com>:
>>
>> Ideally the device driver shall be integrated with host, with Wine merely acting as a translation layer.  Not sure if it could happen, though...
> 
> Yeah we don't even do that for the limited amount of driver support we have. Transforming Wine into a super-ndiswrapper that can integrate all kinds of device drivers with Linux is a huge undertaking and I am not sure I would be a fan of it.
> 
> If necessary it could be done on a case by case basis. FUSE for file systems, iSCSI / vhba for block devices, tun/tap for network adapters, etc. I think integrating Windows printer drivers with CUPS might be an achievable and useful goal. Wine once upon a time could use Win16 printer drivers.

I didn't mean NDISwrapper.  I simply meant that the host operating system should add proper device support, barring any licensing restrictions.  Perhaps the "translation layer" part was misleading.

A more interesting endeavor would be continuing the "wineserver-inside-kernel" work.

> 
>>> I think it is the combination of those points why we want to have a windows-y kernel environment and not take the host environment 1:1.
>>>
>>
>> Thank you very much for your thoughtful response!
> 
> You seem to have better understanding of the NT kernel world than I do; Maybe someone else can contribute more than my guesswork.
> 


-- 
Sincerely,
Jinoh Kang