Already used by 600,000 programmers in its previous editions, this encyclopedia presents up-to-date technical information on virtually every aspect of the PC--from its architecture and make-up to its built-in components and add-on peripherals. The authors clearly explain system level programming, illustrating their solutions in C++, assembly language, Pascal, and Visual Basic. The CD-ROM includes every program from the book.
Book Description
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
Discover books, learn about writers, read author blogs, and more.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
11 of 11 people found the following review helpful:
3.0 out of 5 stars
Caution: Proceed with care!,
By A Customer
This review is from: PC Intern: The Encyclopedia of System Programming (Developers Series) (Paperback)
Even though this book contains a lot of information about low-level programming, you should read it very, very carefully. The book would have received a rating of 10 were it not for the fact that there are several errors across various chapters. Some of the book's explanations can also be a bit misleading at times.
Here are some examples of the errors you'll find: "However, the joysticks can be monitored only with the polling method because a special hardware interrupt, which executes when the user moves the joystick or presses a button, is assigned to joystick cards" - page 289. The above is not true: a game card does not generate any hardware interrupts. In other words, no hardware interrupts are "assigned to joystick cards". "If you want to access the keyboard at its lowest level, you must capture and redirect keyboard hardware interrupt 90H." - page 283 Actually, the right answer to the above would be would be interrupt 09H. The digits are reversed. "One of the special features of the PIC is to 'cascade' interrupts [...] this method has been used so 16 different hardware interrupt devices can be handled" - page 207 No. Today's IBM-PCs can service the interrupt requests of up to 15 hardware devices. This is due to the fact that one of the interrupt request lines, which would otherwise be used for this purpose, is needed by the system to cascade (connect together) its two interrupt controllers (PICs). This leaves only 15 lines available for use by hardware devices. There is also another problem with this book. While in some cases it explains how gain direct access to certain devices (like the keyboard controller), in other cases it simply talks about the BIOS functions which allow access to devices (such as game cards). Despite all of the above, there IS a lot of information in this book, and it could actually prove useful if read with a bit of skepticism.
6 of 6 people found the following review helpful:
4.0 out of 5 stars
A very in-depth reference book on hard to find PC info.,
By A Customer
This review is from: PC Intern: The Encyclopedia of System Programming (Developers Series) (Paperback)
We used this book in a systems programming class I had at IIT in Chicago. It is not the end all "bible of PC", but it is certainly a very, very good book. Much of the information you will never use, but there will come a time when you will need that one sub-routine that no one else can find or understands, and you pull a code snippet out of this book, apply it to your code, and appear "god-like" to your colleagues. This has happend at least five times since I've owned both editions, and for that, the book has paid for itself. If you write code that goes beyond what the component libraries in your prgramming environment can provide, such as multimedia, games, or networking, it would be a wise investment to have this book in your arsenal. David C. Freeman
1 of 1 people found the following review helpful:
4.0 out of 5 stars
Useful or not...?,
By A Customer
This review is from: PC Intern: The Encyclopedia of System Programming (Developers Series) (Paperback)
Well, what to say about this book ? On one hand, it has really good examples for system programming. On the other hand, you sometimes should ask yourself: "Man, this is a good code and it works well...but, what is the use for myself?" What I want to say, is that you often learn good tricks but you will never need them. Sometimes there are also things, which are very difficult, but not very well explained and you need another book to understand it completely. But at least the biggest part of this book is very useful, and every ambitious DOS coder should own it...unfortunately, the later books of this series also contain Windows-programming...Windows and System-programming....hmmm. (Sorry for my bad English, I'm from Germany)
Share your thoughts with other customers: Create your own review
|
|
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items. |
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
