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

[Stefan Dösinger]

> 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 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.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://www.winehq.org/pipermail/wine-devel/attachments/20220705/ff595107/attachment.sig>