In this instance, if it&#39;s the program&#39;s fault, we should get them to patch their end of things.&nbsp; Just because Windows was tolerant of this specific sloppiness doesn&#39;t mean we should be.&nbsp; What app was it anyways?&nbsp; Cause if it&#39;s an older one and was written for older versions of Windows, it might be an issue that MS itself already fixed in later versions, but allowed the bad call to go through for backwards compatibility purposes.<br>
<br><div class="gmail_quote">On Sun, Dec 7, 2008 at 11:25 AM, Matthias Kupfer <span dir="ltr">&lt;<a href="mailto:mkupfer@reactos.org">mkupfer@reactos.org</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi folks,<br>
<br>
yesterday a user shows me a program what is working properly under windows,<br>
but not working under reactos. It was an open source program and it was easy<br>
to figure out the problem. It was an invalid win-api-call (wrong parameter<br>
value). Due to this situation I would like to ask one question. How<br>
compatible reactos should be? Even fault compatible?<br>
<br>
Matthias<br>
<br>
--<br>
Matthias Kupfer &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Telefon +49 (0) 371 236 46 52<br>
Wilhelm-Firl-Straße 21 &nbsp; Mobil +49 (0) 160 859 43 54<br>
09122 Chemnitz<br>
<br>
_______________________________________________<br>
Ros-dev mailing list<br>
<a href="mailto:Ros-dev@reactos.org">Ros-dev@reactos.org</a><br>
<a href="http://www.reactos.org/mailman/listinfo/ros-dev" target="_blank">http://www.reactos.org/mailman/listinfo/ros-dev</a></blockquote></div><br>