Setting UP KT333 Dragon+

I have built several Soyo systems with generally good luck. This is the
first KT333 Dragon+ and I can't get it going.

Everything appears OK when I don't have any HDD connected, just a floppy.
If the floppy is bootable, the system boots.

As soon as I connect a HDD things get weird. The boot process takes up to a
couple of minutes it boots at all. Sometimes it just hangs on the Dragon
logo screen.

I am building two systems so I have two sets of part to swap out. Two KT333
mobos act the same way. Three different HDDs act strange. One is fdisked,
no format, one hasn't even been fdisked yet. One has an old Win98 system
installed.

If I run DocMemory it reports that the memory is OK. Tried two different
256MB sticks, both OK.

Tried several HDD cables.

I have set the bios to very conservative settings and nothing makes any
difference.

Seeing that I'm getting the same flakey results with different combinations
of part there maybe an operator error that hopefully someone can point out
to me.

Thanks for any suggestions.

what size hard drives ? what ribbon cable 40 or 80 ? how many drives
in BIOS set to detect, ie 1, 2, 3 or all 4 ? auto or manual ? please post
system specs in detail

"Bishoop" <> wrote in message
news...
> I have built several Soyo systems with generally good luck. This is the
> first KT333 Dragon+ and I can't get it going.
>
> Everything appears OK when I don't have any HDD connected, just a floppy.
> If the floppy is bootable, the system boots.
>
> As soon as I connect a HDD things get weird. The boot process takes up to
a
> couple of minutes it boots at all. Sometimes it just hangs on the Dragon
> logo screen.
>
> I am building two systems so I have two sets of part to swap out. Two
KT333
> mobos act the same way. Three different HDDs act strange. One is
fdisked,
> no format, one hasn't even been fdisked yet. One has an old Win98 system
> installed.
>
> If I run DocMemory it reports that the memory is OK. Tried two different
> 256MB sticks, both OK.
>
> Tried several HDD cables.
>
> I have set the bios to very conservative settings and nothing makes any
> difference.
>
> Seeing that I'm getting the same flakey results with different
combinations
> of part there maybe an operator error that hopefully someone can point out
> to me.
>
> Thanks for any suggestions.
>
>

"farmuse" <> wrote in message
news:MN1Na.9839$ ...
| what size hard drives ? what ribbon cable 40 or 80 ? how many drives
| in BIOS set to detect, ie 1, 2, 3 or all 4 ? auto or manual ? please post
| system specs in detail
|
| "Bishoop" <> wrote in message
| news...
| > I have built several Soyo systems with generally good luck. This is the
| > first KT333 Dragon+ and I can't get it going.
| >
| > Everything appears OK when I don't have any HDD connected, just a
floppy.
| > If the floppy is bootable, the system boots.
| >
| > As soon as I connect a HDD things get weird. The boot process takes up
to
| a
| > couple of minutes it boots at all. Sometimes it just hangs on the
Dragon
| > logo screen.
| >
| > I am building two systems so I have two sets of part to swap out. Two
| KT333
| > mobos act the same way. Three different HDDs act strange. One is
| fdisked,
| > no format, one hasn't even been fdisked yet. One has an old Win98
system
| > installed.
| >
| > If I run DocMemory it reports that the memory is OK. Tried two
different
| > 256MB sticks, both OK.
| >
| > Tried several HDD cables.
| >
| > I have set the bios to very conservative settings and nothing makes any
| > difference.
| >
| > Seeing that I'm getting the same flakey results with different
| combinations
| > of part there maybe an operator error that hopefully someone can point
out
| > to me.
| >
| > Thanks for any suggestions.


Thanks for the reply.

A call to Soyo tech support and only about 5 minutes on hold yielded the
answer. When using only one HDD on a cable remove "all" the jumpers. DO
NOT jumper it as master.