Great Program, But

[MEESTER HAM]

Bryan, Thanks For Your Post
Maybe I Should Have Rephrase My Post. I Wasn't Saying That Mtu Would Do Anything To Corrupt Hal.dll File. I Was Saying That After Installing The Hoster Program Is When I Have My Problem. I Just Thought That Maybe There Was Something On My Computer Was Conflicting With The Hoster. I Have Never Had This Problem Before With Any Of Your Programs. I Am Going To Reinstall My Xp Pro Windows Again And Not Install Hoster Right Now. The Problem Might In The Computer Itself. I Will Give It Time To See If This Happens Again. This Is A New Unit That I Might Not Have Set Up Correctly. I Built This Computer Myself.
Flipeoke,
Thanks For You Post. I Tried What You Reccomended, But Still No Results. I Will Stay In Contact With The Forum And Maybe Someone Will Will Have Some Ideas Of What I Am Doing Wrong Or What The Problem Is, But I Must Go On.i Am Really Getting Behind.
Thanks
Have A Wonderful Day

[Beavis]

why dont you try and do a repair of windows ? or restore to an earlier date.

[nreel]

Not with Hoster, but, I have had a HAL.DLL problem before.

I, like you, build my own Computers.

I, too, tried everything, which included reinstalling the operating system...several times, researching the HAL.DLL problem via the Internet, changing the Memory, and changing the Video Card. If you ask me, I think the BIOS got hosed, but I had no way to verify that.

Strange thing about the HAL.DLL problem, it didn't manifest itself all at once. Many times, the Computer would Boot to Windows OK and, likewise, would Lockup, just as many times, during Boot, in which, the problem would go away upon Power Down and UP. Then, one day, the Computer wouldn't Boot any further than the HAL.DLL problem.

I state this because you stated that you never got the HAL.DLL malfunction until you Installed Hoster. If your Computer emulates mine, the HAL.DLL problem will eventually keep your Computer form Booting to Windows, no matter what Programs you have installed.

The ONLY thing that fixed this problem, for me, was installing a NEW Motherboard. I, also, put in NEW Memory as I didn't know the condition of the Memory in the old Motherboard and didn't want to take a chance of installing BAD Memory in a NEW Motherboard. Bad Memory can Damage any Motherboard, NEW or OLD. Even though I didn't know the condition of my OLD Video Card, I took a chance on installing it in the NEW Motherboard, but everything worked OK.

Let me tell you, I have been building my own Computers since 1984 and I have NEVER been more frustrated than I was when trying to resolve that HAL.DLL malfunction. If this ever happens to me again, a NEW Motherboard and Memory is my first action!

Norm