5 comments about GPRS and 3G Wireless Applications: Professional Developer's Guide.

1. Let me confess, the author's being an Ericsson member (me, too :) further helped me to add this book to my library.
   I found this book an average book that is nothing but a good collection of information which you can find through internet.
   I expected the author to tell me from how to define effective user interfaces to how to combine servers, which directions to take about future apllications (positioning services, notification, charging etc.)
   I expected good examples from the industry, since the author was a practician, but I didn't find any concrete example from the real world that can really change the way I develop a WAP application (if I develop one).
   I didn't find these...
   Another reason for me to buy it was the CD-ROM. I thought it would be a good idea to have a collection of tools compiled in one CD for me. Let me tell you before you get frustrated like me. The whole 650 MB capacity CD contain the Nokia WAP Toolkit (an old version), and a WAP Toolkit of Ericsson plus Ericsson R380 emulator and that's it! No editors, no GPRS simulators. I still can not understand why did they stick such a content-less CD at the back of the book.
   Good luck...



2. If you're looking for a book on wireless application development from a code perspective this is the wrong book. The value of this book is it provides a solid foundation that needs to be in place before coding starts.

   It begins with basic concepts of how wireless infrastructure works. Developers can safely ignore this section of the book. I liked it because it sorted out the "moving parts" as well as the technological underpinnings. It also answered a lot of questions I had regarding where standards and the industry as a whole were headed, and the strengths and weaknesses of existing technologies and why 3G is so important. As an aside, I learned one trivial fact that had been bothering me: where did the name "Bluetooth" come from? Answer: It was named after a Danish king, Harald Blatand who brought unity among different groups of people. Blatand means Bluetooth in English. Not only does the name capture the spirit of Bluetooth as a technology, but this piece of trivia might gain you "Alpha Geek" status at a seminar or convention :-)

   From chapter 3 on, however, is of paramount interest to architects and developers because it gets into lower level details of GPRS, 3G and Bluetooth. The author provides all of the key characteristics of each technology from which a design and development strategy can be derived. Chapter 6 is where both developers and architects will gain information for performance aspects of their products. The author is meticulous in describing the issues and factors that will arise with protocols (the realities of TCP/IP over wireless in chapter 6 is priceless), and is supported with graphs and diagrams that a developer should carefully go over before writing a single line of code.

   Because of my focus in QA and SQA I thought chapter 14 on testing was particularly strong. Again, this is something that developers need to fully understand (as well as the rest of a project team), and the information provided in this chapter fills a large gap in the testing body of knowledge.

   In response to previous comments about this book: (1) Although the content on the CD ROM is out of date, the author's web site contains up-to-date artifacts and URLs. (2) I contacted the author directly (contact information is provided in the book) about the missing test documents cited on the cover of the book and found out that last minute copyright issues prevented their inclusion on the CD ROM. He sent me to where these documents could be obtained (for free) and they were well worth the effort. (3) The book is anything but basic - it gets into some low-level details such as timing and state diagrams that are essential for *properly* developing wireless applications.

   The author has a talent for packing an incredible amount of information into a paragraph and still holding your interest. He also comes across as authoritative and manages to cover a wide spectrum of issues and facts without compromising on details needed by developers and architects (or anyone who wants to update their knowledge on the latest wireless technologies).




3. I started this book with the yearning to know about all of these technologies: Bluetooth, 3G, GPRS, UMTS, CDPD, HSCSD, Location-based services, and TDMA/CDMA/etc. I really have a decent understanding after this reading this book.

   It gets to the details of how handoffs between GPRS base stations and stuff like that. Things you might not need to know, but its the details that get you places. I'd recommend this book to anyone wanting to know about the general gamut of wireless technologies.




4. As mobile internet becomes increasingly rampant and soon to be a household word, it's vital for the individuals who are on the design and sales forefront to educate themselves on this evolving technology. I recommend for all of our sales and marketing staff to familiarize themselves with Andersson's Professional Developer's Guide. Andersson's book can assist even the novice wireless hopeful with fundamental terms and concepts vital to surviving in this era of cutting edge wireless technology.



5. Emzone develops state of art mobile applications for Sales Force Automation (SFA) . The Book iscomprehensive and helps for GPRS application develoment. It isvery helpful in Emzone current development.

1 comments about C Programming for Unix.

1. Great book, if you need a good reference on C & Unix, this is it.

5 comments about Win32 API Programming with Visual Basic.

1. First, this seems like mostly a C book, not a VB book as the title implies. Sure, the C structures and function call variables are usually provided w/translations (but not always!). And there is a whole chapter on VB strings. But I got the impression the author doesn't know a ton about VB and why a VB programmer might want/need to concern himself with the API function calls. This didn't phase me a ton because I know C, but I thought a lot of the text wasn't much about VB at all.

   First-and-a-half, the author is running Windows NT, so if you're like me and on Win 95/98 you may at times feel like you're being left out. He does go to some lengths to compare and point out the differences between the two OS's, but (again) I felt like he was a C/NT programmer rather than a VB/9x programmer.

   Second, even though the intro says its for both VB5 and VB6, I use the former and couldn't get the crucial examples on the CD to run without first hunting down and finding the needed DLL's on the I-Net one-by-one. This was a tedious process because after a program would clear past one error message on startup it'd hit the next one. And so on. This was a huge hassle. It probably didn't help that the one bad spot on my CD was the dll.readme file (maybe all this was pointed out in there) -- I probably should have taken the book back, but then I would have had to wait for them to order another one and for it to come in, go back a third time to get it, etc...

   Third, the book is not any sort of complete reference to the API functions. Some of the chapters only mention a couple of the functions relevant to the topic, or at least give you the feeling there's more out there that you might want to know about. The functions that are mentioned sometimes only have one or two of their parameters explained (as if the others don't matter). So if you're looking for an API reference book, this probably isn't it.

   At least most of the typos in the book can be found at O'Reilly's website, though a careful reader can find a couple that haven't been flagged.

   I expected a better book. At least the writing is clear.




2. This is an excellent book to learn about Windows from a developer's perspective. It has the most lucid explanations I've read on the Windows operating system, covering topics such as processes, threads, synchronization, memory architecture, Windows messages, DLL injection and device contexts. There is a whole chapter dedicated to strings where the author cleary explains ALL types of strings used in Windows (there are very few books that include this important topic). For those who complain about not enough coverage of the Win32 API, *READ THE PREFACE!*. The author states very clearly that the book is "...not intended to be an encyclopedia for the Win32 API...", the goal is to present "...enough information to get an overall feel for the Windows OS and the Win32 API...". I think he went beyond the stated goal. As for the reviewers complaining about the book heavy slant towards C, it escapes me how anyone would want to read about the Win32 API without expecting to find C all over the place. This is not a book to learn VB syntax or VB tricks, it's about how to interact with the Win32 API from VB, so it's important to learn the details about the API, not about VB. Last but not least, do not expect this to be a hardcore guide to Win32 programming, that's something you just can't do with VB.

   Added Dec 12, 2001: After studying the new .NET platform I realize that this book is sadly outdated. You can still use the Win32 API in VB.NET, but there's no good reason to do that anymore because the .NET framework provides equivalents for just about every API call you can think of, and more.




3. This is a very hard book (for VB programmer with no C experience) BY NECESSITY.
   Normally, you would like the programming book to have some explanation and plenty of code examples. In the case of Win32 API
   for VB programmer, once you get all the intricacies, you just need to find the API function from API viewer applet that comes with Visual Studio.
   Why is the book hard by necessity?
   C and VB have enough differences (e.g. variable type size differences, signed and unsigned type differences etc) to make the interoperability of languages difficult. Add to this the complexity of the Windows architecture itself and C + VB + WIN32
   becomes much more complex, than just C + Win32, which makes me wonder, why use VB at all, if you are planning to make an extensive use of WIN32. Much easier to code in C or C++!
   Back to the book.
   It does excellent job explaining C + VB + Win32 API interaction
   thoroughly. He leaves no stone unturned. If you absorb the book cover to cover, you can consider yourself guru in the area.
   You want need anything else than API function declarations.
   In short, this is a book for ONLY DEDICATED, serious programmer, intending not just to spice up his code with occasional API calls, but ending up with FULL UNDERSTANDING OF ALL ISSUES.



4. This book in no way is a reference book or a how-to book. This book is designed for people who don't have previous knowledge about windows architecture and windows API.

   I find this book as a fantastic tool since it gives me initiative and direction to understand the overall picture. I can use the knowledge that I gained in this book and know what I can do with win32 API. I also purchased the dan appleman's book for win32 api which consists of more examples and it is more a reference book .

   If you have not programmed in win32 before --> this is the book for you.




5. I would beware of ordering this through Amazon. I have had to return this book after several attempts of getting the order right. They keep sending me the book without the CD-Rom.. yet the cover and their site states one is included.

2 comments about Novell Open Enterprise Server Administrator's Handbook, SUSE LINUX Edition (Novell Press).

1. I have been a Novell dealer since the 80's. I also have extensive Unix (SCO) experience, though my Linux experience is much weaker.
   
   We had already spent about six weeks with OES Linux. It was a rough ride (and still is a little bumpy at times). It could have been smoother had I had this book from the beginning.
   
   Unfortunately, we had already learned most of what this book had to tell us from the school of hard knocks.
   
   The most disappointing part was the troubleshooting section. It was limited to telling us where to find the log files--something we figured out weeks ago.
   
   What we're hoping for is a "Mastering Novell OES Linux" that goes into each component (namcd, ndsd, nss, ldap, etc.) and takes it apart, gives you all the gotchas and gives you possible causes when things don't go as planned.



2. I've been working with Novell Netware for many years and needed something to ease me into the linux side of things. It works well by taking all the services you know and love on the NW kernel and shows you how to get the equivalents running in linux.

No comments about S60 Programming: A Tutorial Guide (Symbian Press).

4 comments about Symbian OS Explained: Effective C++ Programming for Smartphones (Symbian Press).

1. This book does actually explain Symbian OS and its 'special' C++! Not every last detail, of course, but so many of the things that I never completely understood have become clear. There's loads of good stuff on active objects, client-server and cleanup.



2. This books gives as the title indicates a run down on how the Symbian OS works. The examples in the book are to complicated to be of any use with some exeptions. Many times the examples are just too long and one gets tired of starring of made up C++ code kind of quickly. The author seem to have good knowledge about the subject but I can't say I smilled many times reading this book.



3. This book is great as a reference to help understand various concepts, code constructs and conventions.
   Concise, detailed explanations...also not many screendumps which makes it more compact.



4. This book can be used as a good reference but it does not serve the basic purpose.
   This book is an introductory level book so assumption is that most of the readers will be new to Symbian Programming. There is notion in the industry that Symbian is a bit tough to follow, particularly to .NET and Java programmers. One of the main reason for that is Poor documenetation from Symbian. So only reference to learn Symbian is books like these and most of them serves the purpose.
   
   The examples used by the author are very complicated, not because of the rules of programming for symbian but because of the examples chosen by the Author. Here are some eg classes and objects
   RHerculesSession::CaptureCeryneianHind
   RHerculesSession::CleanAugeanStables
   RHerculesSession::SlayStympalianBirds
   If we can imagie how a program works, then it will be easy to implement( that is the reason why Dietel & Dietel became so famous). If I am a Mathematecian and if I am writing a book on programming doesn't mean the Class examples should be the calculations of most complex equations in Mathematics.
   
   Apart from the examples its a good reference book.

1 comments about Microsoft Windows Vista Quick Reference Card - Handy Durable Tri-Fold Windows Vista Tip & Tricks Guide. 6 Total Pages. Stores Easily. Ultimate Reference for Operating System Shortcuts, Tips & Cheats for Windows Vista OS. (Software Quick Reference Cards).

1. I love Brainstorm's cards - easy to use and high quality. I also bought their set for Office 2007.

No comments about Guide to Operating Systems Security.

5 comments about Novell's NetWare 6 Administrator's Handbook (Novell Press).

1. When using the book to set up a new NetWare6 server what the book said to do is the same as what is on the screen. this was my first time setting up a server and to have Zero back ground in netware the book was hard to use.



2. I own the previous editions of this book as well as the more comprehensive Hughes/Thomas NetWare books and could not wait to get my hands on both for NetWare 6. It's a must have for our shop - easier to get through than the online help files and also provides the tips and tricks the online docs do not. The newest edition of the Admin Handbook is useful for both the beginner and more advanced Admin. It's easy to find eveyday information fast. Excellent tool to check the syntax of commands you use infrequently. Coverage is just right, not too much to wade through for every day administration but adequately covers the ins and outs. Also addresses new features of NetWare 6 succintly. Well done again authors - thank you!



3. I've read parts of this book like a novel, and used other parts like a reference. The book works either way. Not written for the newbie, it is great for someone with some Novell experience, it is not super-geeky either -- just right.

   Depth is there when needed, enough screen-shots, drawings, and diagrams as needed for clear conveyance of the information.

   I did not detect any errors, and found it to be quite accurate regarding things I already knew.

   The physical size is handy too.

   This one will stay nearby -- I like it, and recomend it.

   Barry Betttenhausen, CNE 3/5/6




4. Excellent little book. Lots of good info packed into a conveniently sized and proportioned book. Not for newbies.



5. This book is packed with the neccessary knowledge you need to manage, set-up, and administer your Novell Netware 6 network. With extensive coverage on areas including iPrint, iFolder, eDirectory, NetStorage, Enterprise Web-Server, this book is for beginners and experts alike.

   I was a novice, never used Netware before, but now I manage a network with 4 servers and over 500 computers, and use this book daily for a reference to comply with Novell's recommendations. You can't go wrong with this book! By far the best out there!

   Thanks Novell!

   Also -

   This book can be used as a resource for the CNA 677 exam too. However don't make it your only one resource...

5 comments about Win32 System Programming: A Windows(R) 2000 Application Developer's Guide (2nd Edition) (The Addison-Wesley Microsoft Technology Series).

1. This is one of the best books I read. The description is clear. It used some UNIX commands to introduce some functions, but the reader needs not to have UNIX background, just skips those short description.
   If the author gave all system routines line by line, the book would be huge, it is not necessary ( we can tell from the title), and the price will be double. As a programmer, I like this book.



2. This book is roughly the same as Steven's "Advanced Programing in the Unix Environment". It gets you in touch with the moving pieces of the Windows operating system.

   Bring with you a strong understanding of C/C++ and some experience administrating a Windows system and you can be up and running banging against the operating system's APIs. Open network sockets, play with "Thread Local Storage", create and register your very own service, interface with the security system, whack around the registry, and a dozen other ways to shoot yourself in the foot or get some actual work done.

   This book has almost nothing about making windows, graphics, sounds, or anything else that will help you get started making yet another accounting application. If that's what you are looking for look somewhere else.

   This book also comes threateningly close to being a good beginners guide to porting *nix applications to the Windows operating system. The author draws many parallels to various *nix utilities and how to write their equivalent using Windows' APIs.

   For those that like plenty of rope to hang themselves, this is the book for you. I enjoyed learning about the various facilities Windows provides the developer, and feel that this book helped me gain a better understanding of where to look first for doing fairly common relatively low-level tasks.




3. I thought the book was well written and would be marginally useful as a basic reference book but I expected more content such at the WIN32 API and more than just a preview of WIN64 and a summary discussion of COM/DCOM and other more complex subjects.
   
   The appendix comparing Win32, Unix and the "C" Library, while making good book fodder, is relatively useless without substantive definitions and examples.
   
   All in all, not much bang for the book. I would not have purchased the book if I had reviewed a copy of the book before ordering it through Amazon.



4. The rating I give here is just based on a skim of the book. However, after visiting the author's website, I very quickly realized that there is a more recent (2004) third edition of the text. Unless you specifically want a more historical perspective, I would recommend that you get the third edition.



5. This book pretty much covers everything I needed to know about Win32 system programming. It has very good coverage of topics like threading, file handling, Memory Management, Interprocess communication, network programming, and asynchronous I/O with completion ports. Ever wonder how to share memory or access really, really huge files? Want to learn how to build more scalable servers? This book covers all that and more. I recently took a new job that uses all of this stuff and I was relieved to find a book that covered it all so well.
   
   He gives a very good generalized view of the windows programming philosophy and explains some common windows types and their uses, which helps in understanding the rest of the API. There are plenty of programming examples and he often compares Win32 programming techniques to UNIX programming techniques giving references to the Stevens book which will help put things in context for UNIX programmers.
   
   For client side programming you can get by with Petzold but for server side this book is a must. If you do system development on Win32 then this book is your weapon.