LOL...
Someone has just run out of patience. Lucky for you, he was kind enough to reply anyhow - unlike me.
I'll tell you straight up - as soon as I saw the code 32, I honestly stopped thinking about helping.
I'll bet most of the guys who know what they are doing didn't even make it that far - most of them didn't even click on the thread because "need some answers" isn't specific enough to let us know if the subject falls under our field of expertise, and we are busy enough that we can't answer all the questions posted anyhow, so silly titles is an easy reason to ignore a thread. By the way, codes are easy to solve, except in very rare circumstances, and are very well documented in many placed online, including here. I don't remember what the code 32 is caused by, but I could find it in seconds, so you should be able to find it in a few minutes.
There is a link in my sig that explains how to get your questions answered - the link is for computer hackers in general and linux gurus specifically, but it applies here equally as well.
I would SERIOUSLY suggest you read it, start to finish.
PS: Usually, I wouldn't even have written this up, but you caught me on a good day... and jetjock made me laugh.