Hoster 3318, early chipset initialization
 

Have been running 3318 since first available. Did NOT have problems other mentioned with files disappearing. In fact it has run remarkablable well....until recently. I am running MSI-6728 motherboard for years, with same memory and other components and have had have no problems until recently. Prepared to burn some some disks and the system locked up. Rebooted and found unbootable due to "early chipset initialization" for which there is no cure. Thought it to be an unusual quirk of windows. Bought a new MSI 6728 board so I didn't have to reload Hoster and other MTU programs. After running for about 3 months it happened again, also while trying to burn a disk. Mind you I burned disks in between this time without problem.

Anyone have an idea as to what the problem might be??? I know, everyone said update Hoster, but I wasn't having any problems until recently....after updating to SP3.

If anyone has an idea as to how to salvage these boards I would love to hear it. Meanwhile, I guess I will select another board and reload everything for my backup/work system. Interestingly, the system on my laptop that I use for show is still working perfectly. I just don't understand. Any ideas will be greatly appreciated.

PS: Still running XP, 3 gig processor, 1 gig ram

Early chipset initialization can be very hard to pin down. It can be anything from a simple spacer under the mobo shorting it out, to a power supply, to a bad drive or ram. Because of the timing, I would start by disconnecting the cdrom drive(s) at the mobo connection and try to boot. Then, if you have any spares, replace the memory. If you have 2, try one chip at a time. It is a process of elimination. It could just be a failed mobo, but unlikely coincidence.

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.

I agree with mark and this could be a bear to solve.

Early chipset initialization means that either it's not initializing the chipset or some device that is connected through the chipset. In addition to the things Mark ask you to check. You may have to pull all cards and disconnect any drives not used. Once you have it down to bare bones, check to see if you still have the problem. If so then you know that its either the mobo, CPU ,RAM or the PS. If the bare bones setup does boot, then make sure that you add things back one item at a time, till you find the problem. Hope this helps

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:

I wish I could be more help.

Jim :g

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

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

Hoster 3318, Early Chipset Initialization
 

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.