P4P800 1016 BIOS

Toggle sidebar Toggle sidebar
P

Paul

Splendid
Mar 30, 2004
5,267
0
25,780
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Hey all, if you have probs with this BIOS. revert
back to the old one (1015). There is definitely
something wrong with this 1016 BIOS. Well with XP
there is. I had constant crashing, BSOD's/random
reboots (Even when I unticked Automatically reboot it
rebooted constantly/often).

I also use Publisher 2002, and an HP Photosmart 145 printer. Before, when I
had 1016 of this BIOS,
and this printer was set as default, Publisher
would crash. You COULDN'T do anything in it.

Now that I have gone back to 1015, Publisher works
with this printer as default. NO probs at all.

It stuffs up your system fullstop!

Wait for 1017 if it ever comes out.
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Pail,

Did you load setup defaults after you flashed the bios then re-set the
specific settings you need for your system to run?
If you didn't then there may be nothing wrong at all with the bios.

Yesterday for example, I had a printer refuse to work (I hadn't used it for
months) and found that in the bios it had become set to EPP mode only. Not
surprisingly this screwed up the driver operation. I have no idea how this
happened as I always load defaults and never touch the printer settings.

If you get a BSOD, then - even in what seems like such a clear cut
situation - I would look into the BSOD error, driver mentioned if any (no
doubt the HP driver) and follow through on this, because you did have a
solid reason for upgrading the BIOS didn't you?

It *may* be exactly as you say but... it may not.

- Tim



"Paul" <noone@home.com> wrote in message
news:cabnkv$b66$1@lust.ihug.co.nz...
> Hey all, if you have probs with this BIOS. revert
> back to the old one (1015). There is definitely
> something wrong with this 1016 BIOS. Well with XP
> there is. I had constant crashing, BSOD's/random
> reboots (Even when I unticked Automatically reboot it
> rebooted constantly/often).
>
> I also use Publisher 2002, and an HP Photosmart 145 printer. Before, when
> I
> had 1016 of this BIOS,
> and this printer was set as default, Publisher
> would crash. You COULDN'T do anything in it.
>
> Now that I have gone back to 1015, Publisher works
> with this printer as default. NO probs at all.
>
> It stuffs up your system fullstop!
>
> Wait for 1017 if it ever comes out.
>
>
>
>
>
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Same problems occured on a friends machine I setup.
Random BSOD's and program glitches. I thought it
might have been the raid setup, are you using raid Paul?
The machine I had trouble with started having trouble
when I upgraded him from 2.8 P4 to a 3.0 HT P4.
They sent the wrong chip so now I put in the correct one he ordered
a P4 Prescott 3.0 GHz. I am still concerned about his memory
because the FSB went from 533-800.

Last thing I did was update to 1017beta bios couldn't go back to 1015
cause 1016 is required for Prescott according to Asus. No BSOD's
for 2 days and it screams !!! If BSOD's come back I'll float him
512 of my Corsair DDR400 and see if that resolves it.

"Tim" <Tim@NoSpam.com> wrote in message news:cabs8k$elm$1@lust.ihug.co.nz...
> Pail,
>
> Did you load setup defaults after you flashed the bios then re-set the
> specific settings you need for your system to run?
> If you didn't then there may be nothing wrong at all with the bios.
>
> Yesterday for example, I had a printer refuse to work (I hadn't used it
> for months) and found that in the bios it had become set to EPP mode only.
> Not surprisingly this screwed up the driver operation. I have no idea how
> this happened as I always load defaults and never touch the printer
> settings.
>
> If you get a BSOD, then - even in what seems like such a clear cut
> situation - I would look into the BSOD error, driver mentioned if any (no
> doubt the HP driver) and follow through on this, because you did have a
> solid reason for upgrading the BIOS didn't you?
>
> It *may* be exactly as you say but... it may not.
>
> - Tim
>
>
>
> "Paul" <noone@home.com> wrote in message
> news:cabnkv$b66$1@lust.ihug.co.nz...
>> Hey all, if you have probs with this BIOS. revert
>> back to the old one (1015). There is definitely
>> something wrong with this 1016 BIOS. Well with XP
>> there is. I had constant crashing, BSOD's/random
>> reboots (Even when I unticked Automatically reboot it
>> rebooted constantly/often).
>>
>> I also use Publisher 2002, and an HP Photosmart 145 printer. Before, when
>> I
>> had 1016 of this BIOS,
>> and this printer was set as default, Publisher
>> would crash. You COULDN'T do anything in it.
>>
>> Now that I have gone back to 1015, Publisher works
>> with this printer as default. NO probs at all.
>>
>> It stuffs up your system fullstop!
>>
>> Wait for 1017 if it ever comes out.
>>
>>
>>
>>
>>
>
>




----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

"tk" <tk@home.com> wrote in message news:40c9b9b0$1_1@127.0.0.1...
> Last thing I did was update to 1017beta bios couldn't go back to 1015
> cause 1016 is required for Prescott according to Asus.
>

Not true, you need 1014 for Prescott, I am currently running 1014 with a 2.8
(hotter than hell) Prescott.
When I recieved the board from Overclockers UK it had 1003 installed so I
had to borrow a 2.4 celeraon from my next door neighbour (nice guy, he had
to rip it out of his running system) to flash the Bios up. I chose 1014
because of a few posts I had seen on 1016 problems. Still running 1014 and
everything stable.

regards
Freddie
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Fri, 11 Jun 2004 19:40:15 +1200, "Paul" <noone@home.com> wrote:

> Hey all, if you have probs with this BIOS. revert
> back to the old one (1015). There is definitely
> something wrong with this 1016 BIOS. Well with XP
> there is. I had constant crashing, BSOD's/random
> reboots (Even when I unticked Automatically reboot it
> rebooted constantly/often).

I have had no problems whatsoever with 1016 under XP.
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Yup I set the default settings everytime I
flash the BIOS Tim. The P4P800 BIOS doesnt
have a EPP mode from what I can
see. Well I usually flash an update, if one comes
out.

I don;'t really have any particular reason tho. I just updated it.



"Tim" <Tim@NoSpam.com> wrote in message news:cabs8k$elm$1@lust.ihug.co.nz...
> Pail,
>
> Did you load setup defaults after you flashed the bios then re-set the
> specific settings you need for your system to run?
> If you didn't then there may be nothing wrong at all with the bios.
>
> Yesterday for example, I had a printer refuse to work (I hadn't used it
for
> months) and found that in the bios it had become set to EPP mode only. Not
> surprisingly this screwed up the driver operation. I have no idea how this
> happened as I always load defaults and never touch the printer settings.
>
> If you get a BSOD, then - even in what seems like such a clear cut
> situation - I would look into the BSOD error, driver mentioned if any (no
> doubt the HP driver) and follow through on this, because you did have a
> solid reason for upgrading the BIOS didn't you?
>
> It *may* be exactly as you say but... it may not.
>
> - Tim
>
>
>
> "Paul" <noone@home.com> wrote in message
> news:cabnkv$b66$1@lust.ihug.co.nz...
> > Hey all, if you have probs with this BIOS. revert
> > back to the old one (1015). There is definitely
> > something wrong with this 1016 BIOS. Well with XP
> > there is. I had constant crashing, BSOD's/random
> > reboots (Even when I unticked Automatically reboot it
> > rebooted constantly/often).
> >
> > I also use Publisher 2002, and an HP Photosmart 145 printer. Before,
when
> > I
> > had 1016 of this BIOS,
> > and this printer was set as default, Publisher
> > would crash. You COULDN'T do anything in it.
> >
> > Now that I have gone back to 1015, Publisher works
> > with this printer as default. NO probs at all.
> >
> > It stuffs up your system fullstop!
> >
> > Wait for 1017 if it ever comes out.
> >
> >
> >
> >
> >
>
>
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Hey TK. Umm, nope not using Raid.

But do use 1 SATA 120GB hdd. XP detects
it OK (the sata). I think whatever 1016 has in it
it buggers up systems, which use P4's and when HT
is enabled. (I use a P4 2.4 here, with HT enabled).

What I had installed already has worked fine
for the last 2-3 years! This includes a firewire card
a TV tuner, 1GB ram, the sata and a 80 GB hdd.

It wasn't until I flashed 1016 that I starting having
major reboots/probs. I use the non-deluxe P4P800
btw.


"tk" <tk@home.com> wrote in message news:40c9b9b0$1_1@127.0.0.1...
> Same problems occured on a friends machine I setup.
> Random BSOD's and program glitches. I thought it
> might have been the raid setup, are you using raid Paul?
> The machine I had trouble with started having trouble
> when I upgraded him from 2.8 P4 to a 3.0 HT P4.
> They sent the wrong chip so now I put in the correct one he ordered
> a P4 Prescott 3.0 GHz. I am still concerned about his memory
> because the FSB went from 533-800.
>
> Last thing I did was update to 1017beta bios couldn't go back to 1015
> cause 1016 is required for Prescott according to Asus. No BSOD's
> for 2 days and it screams !!! If BSOD's come back I'll float him
> 512 of my Corsair DDR400 and see if that resolves it.
>
> "Tim" <Tim@NoSpam.com> wrote in message
news:cabs8k$elm$1@lust.ihug.co.nz...
> > Pail,
> >
> > Did you load setup defaults after you flashed the bios then re-set the
> > specific settings you need for your system to run?
> > If you didn't then there may be nothing wrong at all with the bios.
> >
> > Yesterday for example, I had a printer refuse to work (I hadn't used it
> > for months) and found that in the bios it had become set to EPP mode
only.
> > Not surprisingly this screwed up the driver operation. I have no idea
how
> > this happened as I always load defaults and never touch the printer
> > settings.
> >
> > If you get a BSOD, then - even in what seems like such a clear cut
> > situation - I would look into the BSOD error, driver mentioned if any
(no
> > doubt the HP driver) and follow through on this, because you did have a
> > solid reason for upgrading the BIOS didn't you?
> >
> > It *may* be exactly as you say but... it may not.
> >
> > - Tim
> >
> >
> >
> > "Paul" <noone@home.com> wrote in message
> > news:cabnkv$b66$1@lust.ihug.co.nz...
> >> Hey all, if you have probs with this BIOS. revert
> >> back to the old one (1015). There is definitely
> >> something wrong with this 1016 BIOS. Well with XP
> >> there is. I had constant crashing, BSOD's/random
> >> reboots (Even when I unticked Automatically reboot it
> >> rebooted constantly/often).
> >>
> >> I also use Publisher 2002, and an HP Photosmart 145 printer. Before,
when
> >> I
> >> had 1016 of this BIOS,
> >> and this printer was set as default, Publisher
> >> would crash. You COULDN'T do anything in it.
> >>
> >> Now that I have gone back to 1015, Publisher works
> >> with this printer as default. NO probs at all.
> >>
> >> It stuffs up your system fullstop!
> >>
> >> Wait for 1017 if it ever comes out.
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>
>
>
> ----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
> http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
> ---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption
=---
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

What about HT?? Is Hyperthreading enabled?

If you use a P4 Ken?

"Ken Oaf" <tipsy@beerlover.com.au> wrote in message
news:747kc0hs7ugj5d86b2ipgcn8gr8hgrjk8t@4ax.com...
> On Fri, 11 Jun 2004 19:40:15 +1200, "Paul" <noone@home.com> wrote:
>
> > Hey all, if you have probs with this BIOS. revert
> > back to the old one (1015). There is definitely
> > something wrong with this 1016 BIOS. Well with XP
> > there is. I had constant crashing, BSOD's/random
> > reboots (Even when I unticked Automatically reboot it
> > rebooted constantly/often).
>
> I have had no problems whatsoever with 1016 under XP.
>
>
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Umm the P4P800 is an 800 FSB board TK

It may have been the previous CPU u had installed
was a 533 CPU? And the newer one was a 800 one?

That maybe why, it went from 533 to 800? That'll
be the CPU that changed the FSB? Not the memory?


"tk" <tk@home.com> wrote in message news:40c9b9b0$1_1@127.0.0.1...
> Same problems occured on a friends machine I setup.
> Random BSOD's and program glitches. I thought it
> might have been the raid setup, are you using raid Paul?
> The machine I had trouble with started having trouble
> when I upgraded him from 2.8 P4 to a 3.0 HT P4.
> They sent the wrong chip so now I put in the correct one he ordered
> a P4 Prescott 3.0 GHz. I am still concerned about his memory
> because the FSB went from 533-800.
>
> Last thing I did was update to 1017beta bios couldn't go back to 1015
> cause 1016 is required for Prescott according to Asus. No BSOD's
> for 2 days and it screams !!! If BSOD's come back I'll float him
> 512 of my Corsair DDR400 and see if that resolves it.
>
> "Tim" <Tim@NoSpam.com> wrote in message
news:cabs8k$elm$1@lust.ihug.co.nz...
> > Pail,
> >
> > Did you load setup defaults after you flashed the bios then re-set the
> > specific settings you need for your system to run?
> > If you didn't then there may be nothing wrong at all with the bios.
> >
> > Yesterday for example, I had a printer refuse to work (I hadn't used it
> > for months) and found that in the bios it had become set to EPP mode
only.
> > Not surprisingly this screwed up the driver operation. I have no idea
how
> > this happened as I always load defaults and never touch the printer
> > settings.
> >
> > If you get a BSOD, then - even in what seems like such a clear cut
> > situation - I would look into the BSOD error, driver mentioned if any
(no
> > doubt the HP driver) and follow through on this, because you did have a
> > solid reason for upgrading the BIOS didn't you?
> >
> > It *may* be exactly as you say but... it may not.
> >
> > - Tim
> >
> >
> >
> > "Paul" <noone@home.com> wrote in message
> > news:cabnkv$b66$1@lust.ihug.co.nz...
> >> Hey all, if you have probs with this BIOS. revert
> >> back to the old one (1015). There is definitely
> >> something wrong with this 1016 BIOS. Well with XP
> >> there is. I had constant crashing, BSOD's/random
> >> reboots (Even when I unticked Automatically reboot it
> >> rebooted constantly/often).
> >>
> >> I also use Publisher 2002, and an HP Photosmart 145 printer. Before,
when
> >> I
> >> had 1016 of this BIOS,
> >> and this printer was set as default, Publisher
> >> would crash. You COULDN'T do anything in it.
> >>
> >> Now that I have gone back to 1015, Publisher works
> >> with this printer as default. NO probs at all.
> >>
> >> It stuffs up your system fullstop!
> >>
> >> Wait for 1017 if it ever comes out.
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>
>
>
> ----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
News==----
> http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
Newsgroups
> ---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption
=---
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

"Freddie Clark" <fredclark@SPAM@loxinfo.co.th> wrote in message
news:cacri8$9bm$1@news.loxinfo.co.th...
>
> "tk" <tk@home.com> wrote in message news:40c9b9b0$1_1@127.0.0.1...
>> Last thing I did was update to 1017beta bios couldn't go back to 1015
>> cause 1016 is required for Prescott according to Asus.
>>
>
> Not true, you need 1014 for Prescott, I am currently running 1014 with a
> 2.8
> (hotter than hell) Prescott.
> When I recieved the board from Overclockers UK it had 1003 installed so I
> had to borrow a 2.4 celeraon from my next door neighbour (nice guy, he had
> to rip it out of his running system) to flash the Bios up. I chose 1014
> because of a few posts I had seen on 1016 problems. Still running 1014 and
> everything stable.
>
> regards
> Freddie
>
Thanks for the heads up, I got the 1016 info from Asus and as usual
their website was worthless.




----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

"Paul" <noone@home.com> wrote in message
news:cadcu2$h7i$1@lust.ihug.co.nz...
> Umm the P4P800 is an 800 FSB board TK
>
> It may have been the previous CPU u had installed
> was a 533 CPU? And the newer one was a 800 one?
>
> That maybe why, it went from 533 to 800? That'll
> be the CPU that changed the FSB? Not the memory?
>
Yes exactly, I was concerned that the memory could run fine at 533 but
have problems at 800 but that was not the case. The system is fine now , not
1 BSOD
yet running Bios 1017 Beta.

>
> "tk" <tk@home.com> wrote in message news:40c9b9b0$1_1@127.0.0.1...
>> Same problems occured on a friends machine I setup.
>> Random BSOD's and program glitches. I thought it
>> might have been the raid setup, are you using raid Paul?
>> The machine I had trouble with started having trouble
>> when I upgraded him from 2.8 P4 to a 3.0 HT P4.
>> They sent the wrong chip so now I put in the correct one he ordered
>> a P4 Prescott 3.0 GHz. I am still concerned about his memory
>> because the FSB went from 533-800.
>>
>> Last thing I did was update to 1017beta bios couldn't go back to 1015
>> cause 1016 is required for Prescott according to Asus. No BSOD's
>> for 2 days and it screams !!! If BSOD's come back I'll float him
>> 512 of my Corsair DDR400 and see if that resolves it.
>>
>> "Tim" <Tim@NoSpam.com> wrote in message
> news:cabs8k$elm$1@lust.ihug.co.nz...
>> > Pail,
>> >
>> > Did you load setup defaults after you flashed the bios then re-set the
>> > specific settings you need for your system to run?
>> > If you didn't then there may be nothing wrong at all with the bios.
>> >
>> > Yesterday for example, I had a printer refuse to work (I hadn't used it
>> > for months) and found that in the bios it had become set to EPP mode
> only.
>> > Not surprisingly this screwed up the driver operation. I have no idea
> how
>> > this happened as I always load defaults and never touch the printer
>> > settings.
>> >
>> > If you get a BSOD, then - even in what seems like such a clear cut
>> > situation - I would look into the BSOD error, driver mentioned if any
> (no
>> > doubt the HP driver) and follow through on this, because you did have a
>> > solid reason for upgrading the BIOS didn't you?
>> >
>> > It *may* be exactly as you say but... it may not.
>> >
>> > - Tim
>> >
>> >
>> >
>> > "Paul" <noone@home.com> wrote in message
>> > news:cabnkv$b66$1@lust.ihug.co.nz...
>> >> Hey all, if you have probs with this BIOS. revert
>> >> back to the old one (1015). There is definitely
>> >> something wrong with this 1016 BIOS. Well with XP
>> >> there is. I had constant crashing, BSOD's/random
>> >> reboots (Even when I unticked Automatically reboot it
>> >> rebooted constantly/often).
>> >>
>> >> I also use Publisher 2002, and an HP Photosmart 145 printer. Before,
> when
>> >> I
>> >> had 1016 of this BIOS,
>> >> and this printer was set as default, Publisher
>> >> would crash. You COULDN'T do anything in it.
>> >>
>> >> Now that I have gone back to 1015, Publisher works
>> >> with this printer as default. NO probs at all.
>> >>
>> >> It stuffs up your system fullstop!
>> >>
>> >> Wait for 1017 if it ever comes out.
>> >>
>> >>
>> >>
>> >>
>> >>
>> >
>> >
>>
>>
>>
>>
>> ----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet
> News==----
>> http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000
> Newsgroups
>> ---= 19 East/West-Coast Specialized Servers - Total Privacy via
>> Encryption
> =---
>
>




----== Posted via Newsfeed.Com - Unlimited-Uncensored-Secure Usenet News==----
http://www.newsfeed.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
---= 19 East/West-Coast Specialized Servers - Total Privacy via Encryption =---
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Sat, 12 Jun 2004 09:43:51 +1200, "Paul" <noone@home.com> wrote:

> What about HT?? Is Hyperthreading enabled?

Yes, it is enabled.

> If you use a P4 Ken?

A P4 2.8 800 FSB

> "Ken Oaf" <tipsy@beerlover.com.au> wrote in message
> news:747kc0hs7ugj5d86b2ipgcn8gr8hgrjk8t@4ax.com...
> > On Fri, 11 Jun 2004 19:40:15 +1200, "Paul" <noone@home.com> wrote:
> >
> > > Hey all, if you have probs with this BIOS. revert
> > > back to the old one (1015). There is definitely
> > > something wrong with this 1016 BIOS. Well with XP
> > > there is. I had constant crashing, BSOD's/random
> > > reboots (Even when I unticked Automatically reboot it
> > > rebooted constantly/often).
> >
> > I have had no problems whatsoever with 1016 under XP.
> >
> >
>
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Another thing I forgot to mention is Norton
Internet Security 2003.

If you use this, I dont know how, BUT it seems to crash/make your system
reboot too. I tried the Kstack reg fix, which is on the Symantec site. And
so far so
good (It has something to do with using 2000/XP
and also, if you have a NTFS formatted hdd).

It fixes some stack prob, so you dont get the
Kernal overstack error/BSOD, or something, whilst
using NIS 2003. BUT the system hasn't rebooted
since reverting back to 1015 of the BIOS and using this
Kstack registry fix for 2000/XP.


"Ken Oaf" <tipsy@beerlover.com.au> wrote in message
news:0dalc0ps3nqob9b9femqcs058pd35o54jq@4ax.com...
> On Sat, 12 Jun 2004 09:43:51 +1200, "Paul" <noone@home.com> wrote:
>
> > What about HT?? Is Hyperthreading enabled?
>
> Yes, it is enabled.
>
> > If you use a P4 Ken?
>
> A P4 2.8 800 FSB
>
> > "Ken Oaf" <tipsy@beerlover.com.au> wrote in message
> > news:747kc0hs7ugj5d86b2ipgcn8gr8hgrjk8t@4ax.com...
> > > On Fri, 11 Jun 2004 19:40:15 +1200, "Paul" <noone@home.com> wrote:
> > >
> > > > Hey all, if you have probs with this BIOS. revert
> > > > back to the old one (1015). There is definitely
> > > > something wrong with this 1016 BIOS. Well with XP
> > > > there is. I had constant crashing, BSOD's/random
> > > > reboots (Even when I unticked Automatically reboot it
> > > > rebooted constantly/often).
> > >
> > > I have had no problems whatsoever with 1016 under XP.
> > >
> > >
> >
>
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

On Sat, 12 Jun 2004 19:11:14 +1200, "Paul" <noone@home.com> wrote:

> Another thing I forgot to mention is Norton
> Internet Security 2003.
>
> If you use this, I dont know how, BUT it seems to crash/make your system
> reboot too. I tried the Kstack reg fix, which is on the Symantec site. And
> so far so

Yes, I found the same with NIS. I find Sygate Personal Firewall to be better.
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Yup the funny thing it was going OK (NIS)
before the 1016 update. BUT still so far so good
no reboots. And I run NIS 2003 on another PC
here. No reboots/crashes at all. That's the strange
thing. BUT the other PC here isn't a P4P800 and
it doesnt have HT either (but it is a 2.4 with an Asus
mobo). Good to hear things are OK now TK!

Nah the P4P800 can go to 400 DDR (or maybe even higher), it's pretty good
with handling ram up to this speed. And the mobo can handle between 400-800
FSB, so any CPU would, or should work OK with the P4P800
(between 400-800 FSB). I'll wait for the release version
of 1017 (if and when it ever comes out), before I flash
again.




"Ken Oaf" <tipsy@beerlover.com.au> wrote in message
news:0b1nc090ldobq9gstiisv3d5kq3oditrkl@4ax.com...
> On Sat, 12 Jun 2004 19:11:14 +1200, "Paul" <noone@home.com> wrote:
>
> > Another thing I forgot to mention is Norton
> > Internet Security 2003.
> >
> > If you use this, I dont know how, BUT it seems to crash/make your system
> > reboot too. I tried the Kstack reg fix, which is on the Symantec site.
And
> > so far so
>
> Yes, I found the same with NIS. I find Sygate Personal Firewall to be
better.
>
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

"Ken Oaf" <tipsy@beerlover.com.au> wrote in message
news:0b1nc090ldobq9gstiisv3d5kq3oditrkl@4ax.com...
> On Sat, 12 Jun 2004 19:11:14 +1200, "Paul" <noone@home.com> wrote:
>
> > Another thing I forgot to mention is Norton
> > Internet Security 2003.
> >
> > If you use this, I dont know how, BUT it seems to crash/make your system
> > reboot too. I tried the Kstack reg fix, which is on the Symantec site.
And
> > so far so
>
> Yes, I found the same with NIS. I find Sygate Personal Firewall to be
better.
>
I have been running Sygate for a few years now. Never any problems. I
recommend it to anyone.

regards
Freddie
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

"Paul" <noone@home.com> wrote in message news:<cabnkv$b66$1@lust.ihug.co.nz>...
> Hey all, if you have probs with this BIOS. revert
> back to the old one (1015). There is definitely
> something wrong with this 1016 BIOS. Well with XP
> there is. I had constant crashing, BSOD's/random
> reboots (Even when I unticked Automatically reboot it
> rebooted constantly/often).
>
> I also use Publisher 2002, and an HP Photosmart 145 printer. Before, when I
> had 1016 of this BIOS,
> and this printer was set as default, Publisher
> would crash. You COULDN'T do anything in it.
>
> Now that I have gone back to 1015, Publisher works
> with this printer as default. NO probs at all.
>
> It stuffs up your system fullstop!
>
> Wait for 1017 if it ever comes out.

Paul, I think you are right. Please read my older posting in the
subject:
http://tinyurl.com/2efcg

I eventually solved my particular problem (IEEE1394 port) by disabling
the port and installing an add-on IEEE1394 PCI card that is based on
TI chipset, not VIA.

So, the system now does all what I need but it make me cringe whenever
I think about the fact that I paid for certain functions that are
completely useless because they simply do not work.

BTW, there is already a 1017 BIOS, but it is beta. I never use a beta
BIOS on my main system.

HTH,
Lynn
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Hey Lynn. Yup Firewire works OK on this.

That wasn't the prob. It is a PCI firewire card.
(Dolphin, if I remember).

I use the non-deluxe P4P800, which doesn't have
firewire as standard. It was only this stupid 1016
BIOS that buggered this thing up. I've just removed
Norton Internet Security 2003 as well. As this for
some reason, USED to work, BUT now it constantly
crashes the system too. This Norton's prob seems to
be a major prob, with some people. Something to
do with SYMTDI.sys (or similar), which is part of Symantec Redirector which
is part of this firewall.

I can't say I've tried recording back to a DV cam (I use a Panasonic DV-30
digital cam with firewire connection). It works transferring to the PC tho..
NP at all.

Yup I note the beta BIOS 1017 b2. BUT yup, I'll
wait for the release version to come out too.

Some people (you may or may not know), do have
probs with Firewire, and built-in NICS (With Windows
XP, (what I use), it thinks the firewire is also a network card), and this
can ah heck things up a bit....BUT this
can be fixed.


Cheers!

"Linux Lover" <linuxlover992000@yahoo.com> wrote in message
news:7687bfbd.0406141130.5ad4698f@posting.google.com...
> "Paul" <noone@home.com> wrote in message
news:<cabnkv$b66$1@lust.ihug.co.nz>...
> > Hey all, if you have probs with this BIOS. revert
> > back to the old one (1015). There is definitely
> > something wrong with this 1016 BIOS. Well with XP
> > there is. I had constant crashing, BSOD's/random
> > reboots (Even when I unticked Automatically reboot it
> > rebooted constantly/often).
> >
> > I also use Publisher 2002, and an HP Photosmart 145 printer. Before,
when I
> > had 1016 of this BIOS,
> > and this printer was set as default, Publisher
> > would crash. You COULDN'T do anything in it.
> >
> > Now that I have gone back to 1015, Publisher works
> > with this printer as default. NO probs at all.
> >
> > It stuffs up your system fullstop!
> >
> > Wait for 1017 if it ever comes out.
>
> Paul, I think you are right. Please read my older posting in the
> subject:
> http://tinyurl.com/2efcg
>
> I eventually solved my particular problem (IEEE1394 port) by disabling
> the port and installing an add-on IEEE1394 PCI card that is based on
> TI chipset, not VIA.
>
> So, the system now does all what I need but it make me cringe whenever
> I think about the fact that I paid for certain functions that are
> completely useless because they simply do not work.
>
> BTW, there is already a 1017 BIOS, but it is beta. I never use a beta
> BIOS on my main system.
>
> HTH,
> Lynn
 
Archived from groups: alt.comp.periphs.mainboard.asus (More info?)

Umm, how did you manage to get the cam going
in 2000?? I had 2000 installed last week, but it
didn't install a driver for it. So, I reinstalled XP again
which detects the digital video cam automatically.

XP detects it as a Panasonic DV camera, whereas
2000 didn't or couldn't find a decent driver for it.


"Linux Lover" <linuxlover992000@yahoo.com> wrote in message
news:7687bfbd.0406141130.5ad4698f@posting.google.com...
> "Paul" <noone@home.com> wrote in message
news:<cabnkv$b66$1@lust.ihug.co.nz>...
> > Hey all, if you have probs with this BIOS. revert
> > back to the old one (1015). There is definitely
> > something wrong with this 1016 BIOS. Well with XP
> > there is. I had constant crashing, BSOD's/random
> > reboots (Even when I unticked Automatically reboot it
> > rebooted constantly/often).
> >
> > I also use Publisher 2002, and an HP Photosmart 145 printer. Before,
when I
> > had 1016 of this BIOS,
> > and this printer was set as default, Publisher
> > would crash. You COULDN'T do anything in it.
> >
> > Now that I have gone back to 1015, Publisher works
> > with this printer as default. NO probs at all.
> >
> > It stuffs up your system fullstop!
> >
> > Wait for 1017 if it ever comes out.
>
> Paul, I think you are right. Please read my older posting in the
> subject:
> http://tinyurl.com/2efcg
>
> I eventually solved my particular problem (IEEE1394 port) by disabling
> the port and installing an add-on IEEE1394 PCI card that is based on
> TI chipset, not VIA.
>
> So, the system now does all what I need but it make me cringe whenever
> I think about the fact that I paid for certain functions that are
> completely useless because they simply do not work.
>
> BTW, there is already a 1017 BIOS, but it is beta. I never use a beta
> BIOS on my main system.
>
> HTH,
> Lynn
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom