WINE question.

Is there any way to get a program to NOT work in wine?

I maintain a program coded for Windows and am constantly being bugged to fix issues with it despite not being my fault.
How do I make it not work in wine at all? Windows Movie Maker doesn't work in it - how have they done that?

I'm thinking of just letting it search for files Windows must have that wine doesn't. Then if they don't have them it just quits. But there must be a better method.

Using C# if it matters

constantly being bugged to fix issues with it despite not being my fault.
Sounds like it doesn't work in WINE already.

_{You're a shitty coder.}

>>1
1. Look in Wine Bugzilla for a Win32 function that isn't implemented or contains bugs.
2. Use function in your application.
3. ???
4. Profit.

>>1
I maintain a program coded for Windows and am constantly being bugged to fix issues with it despite not being my fault.
Why don't you simply direct the assholes to the Wine bug tracker?

>>1
How can I detect Wine?

Unless you are Microsoft trying to prevent your application from working, you really shouldn't want to do this. If there's a quirk in Wine you need to work around, it's much better to fix it in Wine. More importantly, we might soon fix it ourselves, and then your code will be mysteriously and permanently broken.

That said, there is nothing wrong with detecting Wine for survey purposes. Many developers are surprised to learn that a substantial portion of their userbase has been running their program via Wine; sometimes developers aren't even aware that this is possible. For the best way to do this, consult the wine-devel mailing list.
http://wiki.winehq.org/DeveloperFaq#head-96551a33b168826cd805c2f62c4ea705ac02f350

I'd check for HKCU/Software/Wine.

>>1
There's a lot of ways really, but some might break compatiblity between different windows versions ( ex. XP vs Vista or 9x vs NT). Here's a few simple methods(one is enough):
1)Try resolving imports using well known(and not likely to change anytime soon in the future, but if they do, you can use GetVersionEx), but undocumented memory layouts/structures of the OS.
2)Use a driver to do things, bonus points for properly communicating with it, but if you can't properly code drivers, I would rather you not crash other people's PCs, this also forces them to run code as admin
3)Certain system information functions return information which is unusual to be returned by a real windows box(such as version info is not particularily valid)
4)Use one of the commercial DRM/protections which are known to be incompatible with WINE to wrap your application. The reason some of them don't work in WINE is usually because of 1-3 and them abusing undocumented stuff.

YOU HELPED HIM!!!

>>7
Reverse trolling.

>>7
…to shoot himelf in the foot.

Holy dix, you are bothered by lusers, and you fix that by making your product not work? What is wrong with you?

>>10
He's a Windows programmer. They do stuff like this on a regular basis.

>>10
Users must be punished for nonstandard behavior.  I'ts the only way to debug them.

>>1
Oh no, don't say it's true...

>>1
A windows programmer crippling his own app? Whodathunkit.

If you're using C# and not gratuitously P/Invoking (or using Microsoft.Win32 APIs) everywhere, it should run happily under Mono, with WINE just not being in the picture.

>>15
That would be one of the concepts of this troll, yes. Isn't there a ton of GUI stuff that's not supported, though?

>>16
Yeah. Windows Forms works, sorta, but it's kinda buggy. And slow... noticeably slower than the Windows .NET implementation.

>>1
Cut off your penis and mail it to Hillary Clinton.
That will at least get you out of your mom's basement.

>>17
I've found that well-reported WinForms bugs are usually fixed quickly. It's definitely slow, though, and will always be a misfit. If you want your CLR application to work well on Linux, you should definitely use Gtk#.

Of course, >>1-san is a faggot, so this is rather irrelevant.

You could just use windows, which has 100% compatibility and speed

use the "INT 21" dos systemcall. wine does not like that.

>>20
...windows...speed
nice try ;)

>>22
What? The OP is talking about using WINE, a windows emulator. Surely directly using the system which is being emulated will be superior to using the emulation, wouldn't you agree?

>>23
（　≖‿≖）

>>23
No, he's talking about making his program not work in WINE, not USING Wine.

IHBT

>>24
Stop posting that crap here, Cbbleh.

WINE my anus

tell them to stop the "whine"

>>23
Wine Is Not an Emulator. Wine is a reimplementation of the Windows API on top of the *NIX API. Wine can meet or even beat the speed on Windows. For example, WoW reportedly runs faster in Wine than on Windows.

>>29
*beet

>>29
beet trolled

>>29
What about ReactOS?

>>32
ReactOS is supposed to be a Windows clone. It just happens to make use of WINE software because they have intersecting scopes.