(Greg B) wrote in message news:<. com>...
> "thomas k." <> wrote in message news:<7RX3d.24$gu5.1@trnddc09>...
> > Thanks for the responses, guys.
> >
> > I forwarded this to Soyo tech and their suggestion was to try a different
> > PS.
>
> Ah, yes. The SOYO equivalent to 'have you re-booted Windows?'
>
> Send the round-eye out to drop a hundred bucks on a power supply. Maybe
> he'll be so ****ed off by the time he comes back with the same symptom
> he'll by ASUS or GigaBit or MSI. Either way, we got him off the call and
> we still have his money.
>
> I think it was the KT-400DUP that led Soyo to un-link this group from
> their support site...too much traffic with silly problems. RAID no work,
> sound no work, sound no work with NIC enabled, you name it. BIOS updates
> from hell (leading them to the disclaimer, 'Don't update your SOYO BIOS
> except to fix a bug' [since you'll acquire twice as many in the update,
> until we just give up and stop doing updates altogether].
>
> Maybe they'll get serious and ask you to send all your components to them
> for weeks at a time. After all, you're just a hobbyist, you didn't actually
> intend to *use* this computer did you?
>
> Not a bad business model. You can make a pretty good living selling
> everybody one really pretty motherboard.
> Greg
Anyone who is running a Barton core chip in a KT400 board with a "no boot"
condition should contact Soyo about ECN-E000-K7VX4L-001. It is a component
change that should fix the problem once and for all. Newer Rev 7 boards don't
have this problem.
Andy