Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The thing that always floors me about Wine is how unbelievably huge it is. It makes me rather cringe at the thought of having to be a programmer on the Windows team in Redmond. (Of course, it also gives me a healthy respect for their skill and abilities.)
Don't we have a copy of the win API (#include <windows.h>)?
The header files only give the interface to the functions, they don't say how they work. For the Unix API there are multiple open source implementations. Having more than one implementation is important because it helps demonstrate what is specified by the API and what is just a quirk of the implementation. For Windows there is only one closed-source implementation so it's hard to see what's a bug and what's a feature.
I know there's more in it that just that (wincon.h).
Understatement of the year
Don't most major applications also ship with their own libraries?
Windows applications rely a lot more on the stuff that ships with windows, because there is so much more installed by default.
And what about MSDN isn't that a mildly good piece of documentation on the WINAPI?
Not good enough, obviously.
Originally Posted by wikipedia
incomplete and incorrect documentation of the Windows API. While Microsoft extensively documents most Win32 functions, some areas such as file formats and protocols have no official Microsoft specification. Microsoft Windows also includes undocumented low-level functions and obscure bugs that Wine must duplicate precisely in order to allow some applications to work properly.