what is the exact title of the book, and author?  is it Mcgraw Hill?  If so,
I only have the one written by Stephen Hutnik.

thanks!!

"neal rauhauser" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
>  <flame>
>
>
>        It would appear that your contact with the book has so befuddled
you that
> you've forgotten what a paragraph is.
>
>        You're right that there are some problems with the CCIE Lab Study
Guide
> but its a wonderful tool to have, all in all. I imagine the second
version,
> which I see is out on the shelves at Borders, goes a long way towards
correcting
> the deficiencies.
>
>
>      I've used the book, errors and all, and I completed 70+ labs before I
went
> off and started inventing my own stuff.  I credit that book with getting
me
> through ACRC and I recommend it to anyone that is working on Cisco certs
...
> wish I'd had it when I was doing the CCNA.
>
> </flame>
>
> [EMAIL PROTECTED] wrote:
>
> > Hey Groupies,
> >     Just wanted to bring up a topic that I've been pondering. About a
month
> > ago, me and another member on the list met up and started working on his
path
> > to CCIE, starting with the "CCIE All-In-One Study Guide." Any of you who
have
> > ever used this book have all seen the massive amounts of errors in it,
from
> > picture errors, config errors, and even syntax spelling errors. We are
almost
> > through the whole book and I must say that out of the 80 labs in the
book, at
> > least 75% of them have had AT LEAST a tiny glitch on the authors part. I
have
> > hated this for the time that I've been working in the book, until last
night.
> > Me and the other member were working on one of the BGP labs. First of
all,
> > there was a config missing for one of the routers, and for router D in
the
> > config there wasn't supposed to be a serial address...but of coarse in
the
> > picture there was one. We literally spent about 2 hours on what was
supposed
> > to be a 20 minute lab. I commented this and the other member said "I
know,
> > this is great." That's when I got to thinking. What if this author made
all
> > of these mistakes to teach us troubleshooting. I must admit, I have
spent a
> > lot of time on these labs trying to figure out what's wrong with them
after
> > we use what the author wants, and I even get better from it. On the way
home
> > last night I was thinking that maybe the book was intended to be that
way and
> > all of those errata's are just ruining it because it's letting people
not use
> > their heads. If this is NOT the case and the author didn't intend in
making
> > this book a troubleshooter, then maybe he is a moron. But if he did,
indeed,
> > write this book this way intentionally, then I have to tip my hat and
say
> > that he is a genius and a great teacher. Just my thoughts guys. After
all,
> > the second half of "the lab" is fixing what was made wrong. If this book
can
> > simulate that...then it is the best CCIE study guide to a certain level.
Have
> > a good one group,
> >
> > Mark Zabludovsky ~ CCNA
> > <A HREF="mailto: [EMAIL PROTECTED]">[EMAIL PROTECTED]</A>
> >
> >     If the automobile had followed the same development as the computer,
a
> > Rolls-Royce would today cost $100, get a million miles per gallon, and
> > explode once a year killing everyone inside.
> >                                         ~Robert Cringely, InfoWorld~
> >
> > ___________________________________
> > UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> > FAQ, list archives, and subscription info: http://www.groupstudy.com
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
> ___________________________________
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> ---


___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to