 |
|
 |
|
Next: Dragon Plus+WINXP crashes with RADEON 9600PRO
|
| Author |
Message |
External

Since: Jul 10, 2003 Posts: 3
|
(Msg. 1) Posted: Thu Jul 10, 2003 11:49 am
Post subject: latest BIOS was a mistake for KT333 Ultra Black Archived from groups: alt>comp>periphs>mainboard>soyo (more info?)
|
|
|
Since upgrading to the latest and greatest BIOS on my KT333 Dragon Ultra
Black mobo., I'm having some issues. At first, I was having a problem with
my FSB being set at 133. It would boot fine at 100, but when I set the FSB
to 133 and reset, the screen would stay black. All the drives and fans
would spin up, but no POST.
It seems in order for me to get it to boot at 133, I have to hold down the
reset button for about 10 seconds and usually it will POST and boot
normally. Occasionally it won't, so I'll have to hold reset again. And
while I'm in Windows, if I tell it to reboot, it will reboot but stay at a
black screen, causing me to hold down the reset button and pray it starts
up.
This is weird. I shouldn't have upgraded the BIOS, I guess. Any ideas? I
doubt it is the power supply, as it used to work great with 3 HD drives, 3
optical drives, floppy and zip. Now I'm using only 1 HD and 2 optical
drives, so the load is obviously less.
Thanks for any help. >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 09, 2003 Posts: 33
|
(Msg. 2) Posted: Thu Jul 10, 2003 12:37 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
In article <bejqsc$mf1@library1.airnews.net>,
bobby.abernathy.DeleteThis@classicnet-nospam.net says...
> Since upgrading to the latest and greatest BIOS on my KT333 Dragon Ultra
> Black mobo., I'm having some issues. At first, I was having a problem with
> my FSB being set at 133. It would boot fine at 100, but when I set the FSB
> to 133 and reset, the screen would stay black. All the drives and fans
> would spin up, but no POST.
>
> It seems in order for me to get it to boot at 133, I have to hold down the
> reset button for about 10 seconds and usually it will POST and boot
> normally. Occasionally it won't, so I'll have to hold reset again. And
> while I'm in Windows, if I tell it to reboot, it will reboot but stay at a
> black screen, causing me to hold down the reset button and pray it starts
> up.
>
> This is weird. I shouldn't have upgraded the BIOS, I guess. Any ideas? I
> doubt it is the power supply, as it used to work great with 3 HD drives, 3
> optical drives, floppy and zip. Now I'm using only 1 HD and 2 optical
> drives, so the load is obviously less.
>
> Thanks for any help.
Did you unplug the system and clear the CMOS after flashing the BIOS?
Doug<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 10, 2003 Posts: 2
|
(Msg. 3) Posted: Thu Jul 10, 2003 1:28 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Doug G." <dougng RemoveThis @newsguy.com> wrote in message
news:MPG.1977443835b324e8989d87@news.newsguy.com...
> In article <bejqsc$mf1@library1.airnews.net>,
> bobby.abernathy RemoveThis @classicnet-nospam.net says...
> > Since upgrading to the latest and greatest BIOS on my KT333 Dragon Ultra
> > Black mobo., I'm having some issues. At first, I was having a problem
with
> > my FSB being set at 133. It would boot fine at 100, but when I set the
FSB
> > to 133 and reset, the screen would stay black. All the drives and fans
> > would spin up, but no POST.
> >
> > It seems in order for me to get it to boot at 133, I have to hold down
the
> > reset button for about 10 seconds and usually it will POST and boot
> > normally. Occasionally it won't, so I'll have to hold reset again. And
> > while I'm in Windows, if I tell it to reboot, it will reboot but stay at
a
> > black screen, causing me to hold down the reset button and pray it
starts
> > up.
> >
> > This is weird. I shouldn't have upgraded the BIOS, I guess. Any ideas?
I
> > doubt it is the power supply, as it used to work great with 3 HD drives,
3
> > optical drives, floppy and zip. Now I'm using only 1 HD and 2 optical
> > drives, so the load is obviously less.
> >
> > Thanks for any help.
>
> Did you unplug the system and clear the CMOS after flashing the BIOS?
>
> Doug
Yes, many times. Sometimes, I have to clear the CMOS just to get it going.
Of course in doing this, the FSB goes down to 100. Once I change it back to
133, it can take a long time to POST. That's when I have to hold down the
reset button for several seconds to get it going again. Seems kinda flaky...<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 09, 2003 Posts: 33
|
(Msg. 4) Posted: Thu Jul 10, 2003 4:39 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
In article <bek128$f3n@library1.airnews.net>,
bobby.abernathy.TakeThisOut@verizon.net says...
> > Did you unplug the system and clear the CMOS after flashing the BIOS?
> >
> > Doug
>
> Yes, many times. Sometimes, I have to clear the CMOS just to get it going.
> Of course in doing this, the FSB goes down to 100. Once I change it back to
> 133, it can take a long time to POST. That's when I have to hold down the
> reset button for several seconds to get it going again. Seems kinda flaky...
Have you tried going back to the BIOS version you were running before?
Doug<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 02, 2003 Posts: 82
|
(Msg. 5) Posted: Thu Jul 10, 2003 4:58 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Thu, 10 Jul 2003 08:49:28 -0500, "bobby"
<bobby.abernathy.TakeThisOut@classicnet-nospam.net> wrote:
>Since upgrading to the latest and greatest BIOS on my KT333 Dragon Ultra
>Black mobo., I'm having some issues.
That's the board I have. I flashed to the 2aa7 BIOS a few days ago,
mostly to get to the most-recent version of the HighPoint RAID BIOS.
(I didn't clear CMOS with the jumper--the "/cc" switch for
AWDFLASH.EXE worked fine for me.)
No issues, no problems. So, I'd look elsewhere than the BIOS--unless
somehow your BIOS chip went flaky.
--
-denny (curmudgeon)
"I'm full of good answers--sometimes it's the question that's wrong."
Miss Behavin'<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jun 29, 2003 Posts: 45
|
(Msg. 6) Posted: Thu Jul 10, 2003 5:18 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"bobby" <bobby.abernathy RemoveThis @classicnet-nospam.net> wrote in message news:<bejqsc$mf1@library1.airnews.net>...
> It would boot fine at 100, but when I set the FSB
> to 133 and reset, the screen would stay black.
Wow. A SOYO motherboard that runs at 100 but has trouble at
133. How new and different <sarcasm mode off>
Everything old is new again, it seems.
Greg<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 09, 2003 Posts: 33
|
(Msg. 7) Posted: Thu Jul 10, 2003 9:38 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
In article <0nkrgvc0ngsshrp12ndgsapccafa8nc9nt.DeleteThis@4ax.com>,
dennyw.DeleteThis@TANSTAAFL.zipcon.net.INVALID says...
> On Thu, 10 Jul 2003 08:49:28 -0500, "bobby"
> <bobby.abernathy.DeleteThis@classicnet-nospam.net> wrote:
>
> >Since upgrading to the latest and greatest BIOS on my KT333 Dragon Ultra
> >Black mobo., I'm having some issues.
>
> That's the board I have. I flashed to the 2aa7 BIOS a few days ago,
> mostly to get to the most-recent version of the HighPoint RAID BIOS.
You do know that you can change versions of the Highpoint in the
bios.bin file to the one you want by using CBROM, right?
> (I didn't clear CMOS with the jumper--the "/cc" switch for
> AWDFLASH.EXE worked fine for me.)
>
> No issues, no problems. So, I'd look elsewhere than the BIOS--unless
> somehow your BIOS chip went flaky.
It's possible the new BIOS has caused a compatibility problem with a
card or device in his system that you may not have in yours. Remember
the video corruption problem with some ATI video cards that was
introduced with the 2aa4 BIOS for the KT333 Dragon?
Doug<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jun 27, 2003 Posts: 14
|
(Msg. 8) Posted: Thu Jul 10, 2003 11:29 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
Go F*** yourself, TROLL........
Or maybe stick that accordian up your A**.................................
"Greg B" <greg.TakeThisOut@bullough.org> wrote in message
news:63ac2e63.0307101318.770aa529@posting.google.com...
> "bobby" <bobby.abernathy.TakeThisOut@classicnet-nospam.net> wrote in message
news:<bejqsc$mf1@library1.airnews.net>...
> > It would boot fine at 100, but when I set the FSB
> > to 133 and reset, the screen would stay black.
>
> Wow. A SOYO motherboard that runs at 100 but has trouble at
> 133. How new and different <sarcasm mode off>
>
> Everything old is new again, it seems.
>
> Greg<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 02, 2003 Posts: 82
|
(Msg. 9) Posted: Fri Jul 11, 2003 4:26 am
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
On Thu, 10 Jul 2003 18:38:02 -0600, Doug G. <dougng.RemoveThis@newsguy.com>
wrote:
>In article <0nkrgvc0ngsshrp12ndgsapccafa8nc9nt.RemoveThis@4ax.com>,
>dennyw@TANSTAAFL.zipcon.net.INVALID says...
>> On Thu, 10 Jul 2003 08:49:28 -0500, "bobby"
>> <bobby.abernathy.RemoveThis@classicnet-nospam.net> wrote:
>>
>> >Since upgrading to the latest and greatest BIOS on my KT333 Dragon Ultra
>> >Black mobo., I'm having some issues.
>>
>> That's the board I have. I flashed to the 2aa7 BIOS a few days ago,
>> mostly to get to the most-recent version of the HighPoint RAID BIOS.
>
>You do know that you can change versions of the Highpoint in the
>bios.bin file to the one you want by using CBROM, right?
<Mode: Rochester>
"Who dat, boss?"
</Rochester>
Seemed a good idea to get to at least the 2aa6 BIOS anyway, though.
--
-denny (curmudgeon)
"I'm full of good answers--sometimes it's the question that's wrong."
Miss Behavin'<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Aug 02, 2003 Posts: 21
|
(Msg. 10) Posted: Fri Jul 11, 2003 5:30 am
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
another reason to avoid RAID
"Doug G." <dougng.DeleteThis@newsguy.com> wrote in message
news:MPG.1977c2e449885066989d89@news.newsguy.com...
> In article <0nkrgvc0ngsshrp12ndgsapccafa8nc9nt.DeleteThis@4ax.com>,
> dennyw.DeleteThis@TANSTAAFL.zipcon.net.INVALID says...
> > On Thu, 10 Jul 2003 08:49:28 -0500, "bobby"
> > <bobby.abernathy.DeleteThis@classicnet-nospam.net> wrote:
> >
> > >Since upgrading to the latest and greatest BIOS on my KT333 Dragon
Ultra
> > >Black mobo., I'm having some issues.
> >
> > That's the board I have. I flashed to the 2aa7 BIOS a few days ago,
> > mostly to get to the most-recent version of the HighPoint RAID BIOS.
>
> You do know that you can change versions of the Highpoint in the
> bios.bin file to the one you want by using CBROM, right?
>
> > (I didn't clear CMOS with the jumper--the "/cc" switch for
> > AWDFLASH.EXE worked fine for me.)
> >
> > No issues, no problems. So, I'd look elsewhere than the BIOS--unless
> > somehow your BIOS chip went flaky.
>
> It's possible the new BIOS has caused a compatibility problem with a
> card or device in his system that you may not have in yours. Remember
> the video corruption problem with some ATI video cards that was
> introduced with the 2aa4 BIOS for the KT333 Dragon?
>
> Doug
><!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jun 29, 2003 Posts: 45
|
(Msg. 11) Posted: Fri Jul 11, 2003 10:16 am
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Erik the Bold" <offshoreracer30 RemoveThis @nospamyahoo.com> wrote in message news:<vgs1s567er11f RemoveThis @corp.supernews.com>...
> Go F*** yourself, TROLL........
> Or maybe stick that accordian up your A**.................................
Erik, you amuse me.
Please do explain, if you consider this a 'TROLL' as opposed
to fair comment, how come you stupidly keep rising to the
supposed 'bait?'
I admit that I've on occasion caught the same trout twice
in one afternoon, but we were hoping you were smarter than
the average trout.
I guess you're just one of those guys that leaves the
starboard head through-hull open while sailing to
windward on port tack.
Greg<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 10, 2003 Posts: 3
|
(Msg. 12) Posted: Fri Jul 11, 2003 11:36 am
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Doug G." <dougng.DeleteThis@newsguy.com> wrote in message
news:MPG.19777cded556c1fc989d88@news.newsguy.com...
> In article <bek128$f3n@library1.airnews.net>,
> bobby.abernathy.DeleteThis@verizon.net says...
>
> > > Did you unplug the system and clear the CMOS after flashing the BIOS?
> > >
> > > Doug
> >
> > Yes, many times. Sometimes, I have to clear the CMOS just to get it
going.
> > Of course in doing this, the FSB goes down to 100. Once I change it back
to
> > 133, it can take a long time to POST. That's when I have to hold down
the
> > reset button for several seconds to get it going again. Seems kinda
flaky...
>
> Have you tried going back to the BIOS version you were running before?
>
> Doug
I thought about that. I need to try that and see if that makes a
difference.<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jun 27, 2003 Posts: 14
|
(Msg. 13) Posted: Fri Jul 11, 2003 4:16 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
"Greg B" <greg RemoveThis @bullough.org> wrote in message
news:63ac2e63.0307110616.62483@posting.google.com...
>
>
> Erik, you amuse me.
Must be easily amused then, huh?
> Please do explain, if you consider this a 'TROLL' as opposed
> to fair comment, how come you stupidly keep rising to the
> supposed 'bait?'
Someone has to put the trash out on garbage day..........
Occasionally, you come up with thoughtfull and helpful comments. However,
most of your time is spent negatively.
> I admit that I've on occasion caught the same trout twice
> in one afternoon, but we were hoping you were smarter than
> the average trout.
Who the hell is *we* ??
> I guess you're just one of those guys that leaves the
> starboard head through-hull open while sailing to
> windward on port tack.
>
> Greg
Sorry, I race powerboats, not blow boats. But, similarly, if you left the
*thru-hull* open, the boat would sink. Maybe you were thinking of a
ventilator. Now - go piss to windward.<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Jul 09, 2003 Posts: 33
|
(Msg. 14) Posted: Fri Jul 11, 2003 4:19 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
In article <3jpPa.11300$Hw.8586537@news2.news.adelphia.net>,
sixcatsnospam RemoveThis @adelphia.net says...
>
> "Doug G." <dougng RemoveThis @newsguy.com> wrote in message
> news:MPG.1977c2e449885066989d89@news.newsguy.com...
> > In article <0nkrgvc0ngsshrp12ndgsapccafa8nc9nt RemoveThis @4ax.com>,
> > dennyw RemoveThis @TANSTAAFL.zipcon.net.INVALID says...
> > > On Thu, 10 Jul 2003 08:49:28 -0500, "bobby"
> > > <bobby.abernathy RemoveThis @classicnet-nospam.net> wrote:
> > >
> > > >Since upgrading to the latest and greatest BIOS on my KT333 Dragon
> Ultra
> > > >Black mobo., I'm having some issues.
> > >
> > > That's the board I have. I flashed to the 2aa7 BIOS a few days ago,
> > > mostly to get to the most-recent version of the HighPoint RAID BIOS.
> >
> > You do know that you can change versions of the Highpoint in the
> > bios.bin file to the one you want by using CBROM, right?
> >
> > > (I didn't clear CMOS with the jumper--the "/cc" switch for
> > > AWDFLASH.EXE worked fine for me.)
> > >
> > > No issues, no problems. So, I'd look elsewhere than the BIOS--unless
> > > somehow your BIOS chip went flaky.
> >
> > It's possible the new BIOS has caused a compatibility problem with a
> > card or device in his system that you may not have in yours. Remember
> > the video corruption problem with some ATI video cards that was
> > introduced with the 2aa4 BIOS for the KT333 Dragon?
> >
> > Doug
>
> another reason to avoid RAID
LOL! What are you talking about?
Anyway, I have had raid 0 arrays running on at least two system, going
through several different motherboards (I upgrade often, addiction) for
at least three years with no problems. Problems with raid have more to
do with the system operator then the raid array.
Doug<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
External

Since: Aug 02, 2003 Posts: 21
|
(Msg. 15) Posted: Sun Jul 13, 2003 8:09 pm
Post subject: Re: latest BIOS was a mistake for KT333 Ultra Black [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
|
|
|
had a RAID system once, ran like sht. to each his own. wasnt operator
error. RAID just ain't natural, it's like driving two cars at the same time,
if one stops it all comes to a halt. Modern drives are plenty fast enough
IMHO. I cant imagine an OEM selling something based on RAID, they are just
asking for multiple RMA's
servers it's a completely different topic, and are useful
just my 2 cents worth
"Doug G." <dougng DeleteThis @newsguy.com> wrote in message
news:MPG.197887a9348ef36a989d8c@news.newsguy.com...
> In article <3jpPa.11300$Hw.8586537@news2.news.adelphia.net>,
> sixcatsnospam DeleteThis @adelphia.net says...
> >
> > "Doug G." <dougng DeleteThis @newsguy.com> wrote in message
> > news:MPG.1977c2e449885066989d89@news.newsguy.com...
> > > In article <0nkrgvc0ngsshrp12ndgsapccafa8nc9nt DeleteThis @4ax.com>,
> > > dennyw DeleteThis @TANSTAAFL.zipcon.net.INVALID says...
> > > > On Thu, 10 Jul 2003 08:49:28 -0500, "bobby"
> > > > <bobby.abernathy DeleteThis @classicnet-nospam.net> wrote:
> > > >
> > > > >Since upgrading to the latest and greatest BIOS on my KT333 Dragon
> > Ultra
> > > > >Black mobo., I'm having some issues.
> > > >
> > > > That's the board I have. I flashed to the 2aa7 BIOS a few days ago,
> > > > mostly to get to the most-recent version of the HighPoint RAID BIOS.
> > >
> > > You do know that you can change versions of the Highpoint in the
> > > bios.bin file to the one you want by using CBROM, right?
> > >
> > > > (I didn't clear CMOS with the jumper--the "/cc" switch for
> > > > AWDFLASH.EXE worked fine for me.)
> > > >
> > > > No issues, no problems. So, I'd look elsewhere than the
BIOS--unless
> > > > somehow your BIOS chip went flaky.
> > >
> > > It's possible the new BIOS has caused a compatibility problem with a
> > > card or device in his system that you may not have in yours. Remember
> > > the video corruption problem with some ATI video cards that was
> > > introduced with the 2aa4 BIOS for the KT333 Dragon?
> > >
> > > Doug
> >
> > another reason to avoid RAID
>
> LOL! What are you talking about?
>
> Anyway, I have had raid 0 arrays running on at least two system, going
> through several different motherboards (I upgrade often, addiction) for
> at least three years with no problems. Problems with raid have more to
> do with the system operator then the raid array.
>
> Doug<!-- ~MESSAGE_AFTER~ --> >> Stay informed about: latest BIOS was a mistake for KT333 Ultra Black |
|
| Back to top |
|
 |  |
|
You can post new topics in this forum You can reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|
 |
|
|