Fueling Fires

The replay shows it is clearly a fumble, there was no disputing that.  The reasoning provided was because they could not tell who had the ball at the bottom of the pile.  Garret Wolfe came up with the ball when the pile cleared, but apparently they have to tell who has it at the bottom or they give it back to the offense???  Sounds like a load of crap to me.  I was always under the impression that if you can’t see the bottom of the pile, which you usually cannot, it goes to whoever comes out with the ball. 

http://www.tracyandmatt.co.uk/blogs/index.php/2008/08/22/htc-touch-pro-review

This review has me pretty excited about the Touch Pro.  I am using the PPC 6800 (Sprint Mogul) currently and while it has been a decent phone, it is still constantly constrained by the lack of memory and unresponsive touch screen, not the mention that call quality is average at best.  It sounds as though they addressed all of this and more with this model and have even added some pretty sweet features if I say so myself.  One of the simple features they mention in this review that seemed really cool was the ability to silence your phone by simply setting down face down.  That would be handy in a lot of situations.

Also, here you can find a video of the unboxing of the Touch Pro:

http://www.tracyandmatt.co.uk/blogs/index.php/2008/08/14/htc-touch-pro-unboxed-exclusive

I am not sure if there is a coinciding issue (and there most likely is since I have not found any documented occurrences of this elsewhere), but here is what I know.  A family member mentioned that their PC out of nowhere began bringing them to the login screen instead of directly into Windows.  Then when clicking the button to login, it would appear to be working, but then immediately logoff taking them right back to the screen.  After doing some research, I found this site http://www.housing.hawaii.edu/resources/support/winlogoff.htm and quite a few others saying that the likely culprit was either this userinit.exe file was missing, or a registry entry was pointing to the wsaupdater.exe instead of the userinit.exe.  After entering the recovery console and performing the recommended actions, I unfortunately found that the issue remained.  I then realized I had simply assumed because everyone else said it would, that I could not log in using safe mode either.  This was not the case, I got in no problem.  I then remembered the owner of the PC saying that they recently installed AVG, so I removed the application while in safe mode, restarted and everything is now back to normal.  If anyone else is experiencing this problem, I hope this helps or if anyone has any insight as to why this occurred, please chime in.