What do you think?
Rate this book
Win32 System Programming: A Windows 2000 Application Developer's Guide
Win32 System Programming, Second Edition focuses exclusively on non-GUI Windows system programming, helping experienced system programmers make the most of Win32 fast -- whether they're migrating UNIX applications, building new server-side software, or addressing other difficult technical challenges. This new edition is fully updated to reflect Windows 2000, with valuable new coverage of network programming, threading, synchronization, the forthcoming Win64 migration, and other issues critical to high-end enterprise development. Each chapter ends with a detailed example that shows how its techniques are used in real-world systems, as well as hands-on exercises. Expert system programmer Johnson Hart assumes developers are familiar with "generic concepts" by now, and focuses instead on the specific issues they will face in maximizing the performance and reliability of their high-end Win32 server and system applications. For all developers who need to develop reliable, high-performance Win32 applications fast -- especially those familiar with UNIX, VMS, MVS, or other high-end operating systems. Previous Edition 0-201-63465-1
507 pages, Hardcover
First published September 2, 1997
10 people are currently reading
75 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 4 of 4 reviews
July 8, 2010
Solid, up-to-date (through kernel 6.0 build 6001 AKA Windows Server 2008) coverage of the Windows Base Systems API, clearly designed for the programmer who has been rocking UNIX coast-to-coast for a decade, and now finds himself required to deliver product to a Windows audience.
One might not think this a major demographic, but the path seems thus: (1) Promising computer scientists are attracted to UNIX in their youth due to its power, sanity, and elitism.
(2) Said programmers get into systems programming, because it's (a) the natural domain of badasses and (b) the dominant genre of UNIX code jobs. (3) Enabled by the power of open source and the UNIX programming environment, they become the dominant programmers of their generations. (4) PROFIT (in what other industries, save finance, can you easily make six figures at twenty?) (5) They develop social consciences, and leave the server room to code for public consumption, Vanguard accounts fattened like Arctic seals. (6) Public consumption means dealing with Redmond.
Thus, there's likely plenty of space for a serious, focused book guiding the experienced UNIX systems programmer through Windows, explaining things in idioms familiar to UNIX hackers. Frequent reference is made to Stevens+Rago's essential Second Edition of Advanced Programming in the UNIX Environment, and indeed this book might be largely unintelligible without having read that tome. One comes away with rather deep respect, I must admit, for the Win64 API and where it's come. In several areas (the fibre formalism of user-scheduled threads/coroutines, the standardized approach to arena allocators (most unfortunately named "heaps"), the promotion of PIDs within the API from numerics to capabilities, etc), it's well ahead of what's available on a standard Linux/FreeBSD deployment (Solaris hackers may feel justified in cackling at this point). For first-timers, I'd recomment APIUEe2, followed only then by this book.
---
...and a chill filled the room...
One might not think this a major demographic, but the path seems thus: (1) Promising computer scientists are attracted to UNIX in their youth due to its power, sanity, and elitism.
(2) Said programmers get into systems programming, because it's (a) the natural domain of badasses and (b) the dominant genre of UNIX code jobs. (3) Enabled by the power of open source and the UNIX programming environment, they become the dominant programmers of their generations. (4) PROFIT (in what other industries, save finance, can you easily make six figures at twenty?) (5) They develop social consciences, and leave the server room to code for public consumption, Vanguard accounts fattened like Arctic seals. (6) Public consumption means dealing with Redmond.
Thus, there's likely plenty of space for a serious, focused book guiding the experienced UNIX systems programmer through Windows, explaining things in idioms familiar to UNIX hackers. Frequent reference is made to Stevens+Rago's essential Second Edition of Advanced Programming in the UNIX Environment, and indeed this book might be largely unintelligible without having read that tome. One comes away with rather deep respect, I must admit, for the Win64 API and where it's come. In several areas (the fibre formalism of user-scheduled threads/coroutines, the standardized approach to arena allocators (most unfortunately named "heaps"), the promotion of PIDs within the API from numerics to capabilities, etc), it's well ahead of what's available on a standard Linux/FreeBSD deployment (Solaris hackers may feel justified in cackling at this point). For first-timers, I'd recomment APIUEe2, followed only then by this book.
---
...and a chill filled the room...
August 5, 2012
A good reference covering Windows systems programming constructs and mechanisms, including those newly introduced in Windows 7 and Windows Server 2008 (e.g. slim readers/writers locks, condition variables).
June 12, 2015
This book was mistitled, it should have been called How to speed up your programs and improve their communication. Those were the primary things that the author talked about and while this is suppose to be a book about Windows Programing the author mentioned UNIX and Linux so often the I wondered what system he was referring to. Also, none of the example program listing pertained to the real world and he breezed over his topics so lightly it leaves the reader scratching his/her head.
The second biggest problem with the book is that the author makes references to things in the beginning of the book that he will be covering at the middle or end. Leaving the reader confused, this also cause the reader to be flipping back and forth through the book like a chicken with its head cut off.
The second biggest problem with the book is that the author makes references to things in the beginning of the book that he will be covering at the middle or end. Leaving the reader confused, this also cause the reader to be flipping back and forth through the book like a chicken with its head cut off.
September 28, 2012
Never *actually* read the book but it was worth its weight in gold for the chart in the back that maps Unix calls to the Windows API.
Displaying 1 - 4 of 4 reviews