This book, being a memoir, barely begins to tell the story of Robert Frost in Florida. His time in Key West is given extremely short shrift, and no mention at all is made of his important friendship with Florida's own Marjorie Kinnan Rawlings. The Frosts were treasured dinner guests at Cross Creek before Mrs. Frost's death; Mr. Frost alone visited Marjorie in St. Augustine and Van Hornesville, NY. I don't know how Muir missed this connection except that she was focused on his Miami ties. But in that case, the book should be called "Frost in Miami."

Still, for Frost afficianados, this book is a fix. Contains much personal information about his rotten personality, but most of us have heard that before. If you had written "Stopping by Woods," you would have a right to be a so-and-so sometimes.

Okay, I bought this book because I'm a punk and I thought that this would be highly entertaining to me...wrong. The only story I even like din here was the one by Poppy Z. Brite and it's a gothic story. The stories aren't bad at all they're just not what they say they are. xXx

this book opens with blackwood's great story: the wendigo. B is the master of the setting, noone can create the background and atmosphere like him. a very well written story from Brennan here. and Meloff's story is also an interesting read. derleth is at his best here. i don''t care that much for the guy, have never considered him to be HPL's great successor or anything, but he knows how to write, and i have always considered his story about Ithaqua to be his best contribution. the rest of the stories are well written. i don't think any of chaosium's anthologies contains of so much good writing than this. but good is not great. and the rest of the stories never turns out to be really good. the suspence killed by irrelevant writing going on for too long, mostly. sad. but the book is still wort reading

There is an over reliance on academic insights. The Christian scriptures are explicit concerning the limitations of rational thought. Rational inquiry into the ways of the Almighty always ends with a gaping question mark! This open question can only be bridged by personal experience which produces a personal knowing without the need to comprehend. This quote from Carl Jung makes my point : "I cound not say I believe. I know! I had the experience of being gripped by something that is stronger than myself, something, that people call God." While calling upon the sights of a multiplicity of sources, why did the authors neglect insights from two very well known Christian psychologists/priests: Morton Kelsey and John A. Sanford?

'Point Man' writes from experience. Although this is 'fiction', he has 'been there, done that' and knows what he's talking about. Might be a little confusing, but so is combat, esp. close quarters combat! There are many authors who claim to write 'true' books, but how many do you know who write 'fiction' that's from REAL EXPERIENCE? Good reading...ENJOY! Also, check out his Non-Fiction books! "Point Man" & "Walking Point" to read the true stories!

This is an excellent starter book for stargazers, and fits into your pocket.

I bought this book mainly for it's 3D section, but also to learn about DirectX in general. I had hopes of writing a simple 3D game (maybe even a 2D one), however it quickly became apparent that the Author has probably never used DirectX for that purpose!! I honestly found myself wondering, "Why else would you use DirectX if not for programming games?"

I worked through a few of the lessons (attempting the 24 hour goal), however after the first few lessons, I just couldn't continue. The lessons were so damm boring. I mean - the whole point of DirectX is to bring games to life, if not games, then at least bring the screen to life! This Author killed any spirit I had to create a "laser gun battle while driving to a fight scene in my Hover-Ferrari dodging laser fire from monsters with laser-cannons grafted to their chests!"

Instead we get a [bad] picture of a two dimensional, badly drawn taxi, moving to the left of the screen slowly (but smoothly), while the background moved a little bit and a sound moved from one speaker to the other. I mean really!!!! I have not seen a game like that EVER in my life - except for something designed for toddlers whilst learning to tell the difference between a horsy and a cow! Granted, this particular topic was only a demonstration of some DirectX techniques, but I had to wonder in what kind of game I would use these techniques? It just wasn't interesting at all - completely boring beyond belief!

The most complex example in the book involved several textured buildings, with a single stationary car and a moving helicopter that you got to fly, except fly is the wrong word! It quickly became apparent that the Author doesn't know how to program the DirectX 3D stuff. When the helicopter rotated, the buildings changed shape! I was absolutely dumbfounded!

SAMS put their name to this book, but instead of that being a good thing, it's now a warning label when I go shopping. Obviously SAMS do not require a high standard for their books, or their Authors.

This book, gives me many many mixed feelings. I've read through hour 13, and almost dread to go forward. I've learned alot though, debugging the horrid spaghetti code, getting this stuff to compile (MSVC++ 6.0). Chapter 1-6 was great. All the code compiled and all. though the author tends to all the sudden drop a code snippet in with no mention that it should go into your program, and no mention as to where to put it. You kind of need to figure that out. I almost get a sense of schitzophrenia and a lack of focus in my readings of this book. I can't go on without sayinh I've actually learned from this book, and possibly the authors "run as fast as you can and don't look back" attitude of dropping in code with no explanation and moving forward has got me by surprise but I've managed to catch it as I type in my programm with his in the next window so I can follow without getting to lost. His coding style is a bit hectic as the earlier chapters used an ancient directX interface then switched over to the current one, then he looped function one way and another in a different chapter and created projects by telling us you need to link in "X.lib" and never making a mention of what is needed for linkage.

If this review confused you but made sense all at once that is how I felt reading the book to the point i am at.

i borrowed this book from a friend, and must note that there are SEVERAL SEVERE errors in Hour 5 (i havent got past it now)

for instance, they modify the bitmap_surface function, yet do not disclose the new one, or how to modify the existing one to handle the RECT they've added... im not a new programmer, and i STILL cant get this working via the book...

I have used other books in this series and was quite happy with them. But after reading the first few pages in this poorly constructed book, I could see it was only going to frustrate me with it's blatant and carelees errors. Some of the questions were appreciated, but over all it was not worth the time to even scan over it. Too many errors for my liking...Here is a simple explaination found before the 1st chapter.....We all know that the minimum RAM required to install Sever 4.0 is 16MB...right? According to this book..both Workstation and Server require 32MB!!!! DAHHHH

If you can figure out all the errors, then you will probably pass the (70-58) exam. This book was very poorly edited. The concept and design is good, and would be a great help to anyone wanting to pass the (70-58) exam, if it did not have so many errors.

In comparison to the Exam Cram Networking Essentials I found this publication to be more than adequate. In fact I managed to pass the exam mainly through the questions in the book. Yes, there are errors, but if you know your basics you will pick them out. Yes, the publisher should have proofed it better. But on the whole I found that many of my exam questions had something in common with those in the book. This was a second purchase from this series and it's a cheaper method than Transcender

I am not familiar with the particular family that is the focus of the book and documentary, but having lived in Eastern Kentucky all my life, I can attest to the fact that this family represents the exception and not the rule. It is quite dangerous to generalize that the entire region is full of families living in such conditions. There are poverty-stricken people in every region, even in inner-cities. Documentaries like this serve to perpetuate the "hillbilly" stereotype that is so demeaning and destructive to the proud people of Appalachia. Most of us are not living without modern conveniences, technological advances, or even advanced education. I would have appreciated the spirit of this effort if there had been any attempt to distinguish the experiences of this family from the majority of the population of Eastern Kentucky. Instead, they are presented as a typical example of the "modern" Appalachian family. That is a shamefully deceptive myth.

I am not from Kentucky but I personally know relatives of this family and I have visited this mountain area with them. This is really how this family lives and I find the documentory and the book to be actual fact regarding this situation. Many of the relatives have left the area over the years and do lead fine lives in other states. This would represent the remainder of the family that chose to stay with their roots.

In my opinion, the American Hollow is not the author's literary and photographic perception of life in Appalachia. It is an unbiased view of life in the hollow as seen by one family. The author did not attempt to label the family as being representative of the population in general. Whether the family is atypical of the average Appalachian family is irrelevant. The determination of authenticity can be more appropriately evaluated by the participants, the actual family members depicted in the book and film. If the family and neighbors recognize the depictions as creditable, then the author has done a good job of telling it like it is, without approval or disapproval, but merely acceptance that this is one Appalachian family. I missed the documentary on HBO and have searched high and low for it without success. Would be interested to know where I might obtain a copy...all comments welcomed.

Even a beginner should avoid this book. To begin with, the book is littered with grammatical and graphical errors, as well as poor explanations for configuring sites. Secondly, the author spends more time trying to SELL MS Exchange rather than showing you how to CONFIGURE it; I mean really, there should be a law against abusing the word "robust". I was warned about books like this one waaaay back in school (something about a 10-foot pole).

I bought this book in a bit of rush about a year ago because I was starting a new contract with a company upgrading to 5.5, and my experience was with 4.0 and 5.0. For me this book told me nothing I could not find out for myself by a couple of hours playing with V5.5 or just reading the release notes. However a beginner may find it a reasonable introduction, but it isn't post MCSE material.

This book provides excellent summary of the networking aspects of exchange server and an introduction to its application-development capabilities. However, specific programming procedures are not covered.