Hard coding the defect handling should be last option because who to say in every case the correction you do in your code will not be cased by something you overlooked your end?
Wine emulator virus driver#
With wine where defects can disappear or be dependent on a particular video card driver or bit of software.
To us we have provided enough paths detection reduces the usefulness of your program to us for bug testing. Using a controllable defect correction system would be the preferred method since wine developers still could use your program in bug testing by not enabling the work around and gets the most usage out the defect correction code. Thinking defect work around might have usage on future version of windows, cedega or clones like reactos. A path was already provided basically just required binary for windows and binaries for different platforms.Ģ) What would be wrong asking user if they are running in wine in the installer or providing a option in application to enable defective work rounds megapup.
Wine emulator virus mac os#
Making like binaries allows you the detection you are talking about since does not work with windows but works with wine also these files are platform Dependant ie Linux Mac OS BSD. Secondary advantage is that you can take advantage of native paths for load heavy parts. So if your program is compatible with winegcc and other tools when in build due to header flags wine is detectable. There are two major solutions to your problems megapup.ġ) Wine is designed to assist in cross porting of applications to build native programs as well. If you are looking at wine as a free path out of having to develop natively for other platforms it is not megapup. Giving developers a free pass does not help wine develop.Īpplications builder are free to ship custom versions of wine if required. You would have to give a really good reason why we have to. Downside of giving it up is cross platform viruses become simpler.ĭownside out weights the good. Once you know the host OS you can code to syscall the hosting OS and attack it. Problem is for support wine would have to expose wine version and host OS reason some bugs are particular to like Mac OS or Linux or BSD. If wine is reliability detectable this can be used by virus writers to attack host OS.
Reason why we have to reserve the right to move any internal part as we see fit so in case of someone excluding wine we can counter. If wine is reliability detectable applications developers have a simple path to exclude wine. Its a double sided sword if wine is detectable why bother fixing wine bugs.