Hoster 3318, early chipset initialization

[laddie]

Originally Posted by Skybird74

First of all, "files disappearing" was only an issue with Vista (not XP) because Vista required that Hoster be installed in C:\MTU and not in \ProgramFiles and Vista wanted to move all the kmas.

Also, SP3 was only required for 4.0. So it is possible that Windows SP3 is causing the problems with 3.318. I suggest either Restoring back to SP2 to use with 3.318 or Upgrade to 4.06.

I ran xp with 3.318 and had all my . kma files disappear. I am pretty sure the the problem was not isolated to Vista. MTU released V3.321A because of the problem. MTU does not recommend running 3.318 at all.
This problem may be associated with sp3, but it is more than likely hardware related.

[madjim- with the Lord]

Originally Posted by laddie

I ran xp with 3.318 and had all my . kma files disappear. I am pretty sure the the problem was not isolated to Vista. MTU released V3.321A because of the problem. MTU does not recommend running 3.318 at all.
This problem may be associated with sp3, but it is more than likely hardware related.

Doransdome,
Laddie is correct, the problem is in 3.318 and MTU advises we do not use 3.318, upagrade to Hoster 3.321a, it's free.

I would try a system restore to the point before you installed SP3 then upgrade to 3.321a. If this does not clear the problem, it's like Mark said:

Early chipset initialization can be very hard to pin down.

I wish I could be more help.

Jim

[capnvic]

Did you check with MSI's website to see if flashing the system bios may correct compatibility issues with the CD ROM drive?

[Metalgodz]

I lost all my files and I was running xp. 3.318 was the culprit that spawned the devils child that was the end of MTU perfect record. Only a perfect 4.10 can erase the nightmares that were 3.318. God speed MTU God speed

[doransdome]

Marklwood and Laddie - You are so right, early chipset initialization is a bear to pin down. I have been to bare bones and tried every combination of new and old parts as well as removing the motherboard and reseating. I see no reason for this error to have come at this time, after running the same components for several years which is why I tried some new parts. Alas, I have given up and have ordered a new board and will be posting with support for permission to reload on new board next week.

Jim - I would love to use system restore to roll back, but since I can't boot at all, this is not possible.

Capnvic - Yes, I did contact MSI but can't flash a board that won't boot. I also checked about replacing the whole bios chip but didn't get much hope for that process. And, MSI will not repair the board, even at my cost, because of its age. Another reason to give up and get a new board.

Meanwhile, I thank all of you for your thoughts and ideas. I thought I had covered all the bases, but getting input from others is always helpful cause when your mind is boggled you can miss the obvious. Or at least I can. I'll post again and let you know how the new build goes.