Operating System / Software Installation Guide

[jukulu]

Can someone please tell me if the installation procedures on the first page of this thread are applicable to a non-Asus board. I have to assume they are (at least up until the part about loading the Asus CD).

I'm about to put together my first system; I played it safe and got an Intel 845PEBT2 -- no overclocking for me, brothers. At least not yet.

Thanks!

[AHLnut]

Yes, you can follow this guide with you Intel board Just install the devices in the same order as listed in the guide.

[jukulu]

Thanks, AHLnut!

[Mr Steveo]

Originally posted by Manfredo52
When I run the setup.exe, it does install something, but when I check back the device manager I see that still the old drivers seem to be installed.

What to do ?


regards
Manfredo

First. You wont necessariliy see new drivers or certification dates in your device manager. The INF Utulity is something all of us in the forum call "INF drivers". But in reality they arent really a full functioning driver set. The are more of a device identification and instruction set. Meaning, once you install a new set of INFs you likely wont see any change in the device maanger.

==============================================
If you are still concerned you didnt install the new INFs properly, follow either of the two methods below. The first method will work for most people. The second method will gurantee proper installation but is more complicated..

1. If you need to install new INFs over older INFs, you should boot into Safe Mode and install the new ones there. Once you are instructed to reboot, again enter safe mode. Once at the Safe Mode desktop, reboot into normal mode. All Done.


2. If you have problems installing, or if you want to do things the really technical way - heres the method thats guranteed to update even the most troublesome systems and devices.

Boot into safe mode. Go to Start button -> Run. From the browse box, navigate to the path and location of the douwloaded EXE file for the chipset INF drivers. WHen you have the path and filename in the run window, do the following

After the path and file show in the run box. put your cursor at the end where it says ".exe" Then add the following:

(space)- OVER ALL

That means you type a space, then a dash, and then a space, then the word "OVER", then a space, then the word "ALL", with no quotations.

Let the program run.

When its done reboot back into safe mode NOT The normal desktop. Once everything has laoded normally into safe mode, reboot and enter normal mode.
============================================

If you have any other questions, let me know.

[Mr Steveo]

Originally posted by fvlmasl2
Very helpful...but for this step here----Installation Order for Software on an Asus Motherboard with Intel Chipset---- what steps would be different if any for VIA?

Thanks
-fvlmasl2

Wherever you see Intel INF driver Utility - change that to VIA 4 in 1 drvier set. Other than that you can follow the Guide for your P4 VIA rig.

[Mr Steveo]

Originally posted by YoBoGo
So what is the recommendation? If doing a new install should we go with SP1 (assuming it was saved to disk) or with the new SP1a?

Since I still ahvent ehard if MS is definitely going to keep offering security patches for their now discontinued MS JVM; I dont know what to recommend. Im as lost as you are on this one.

Flip a coin maybe?

Whatever you decide, remeber we will have Service Pack 1b rolled out within 30 days and it will include Sun Java included.

[Mr Steveo]

AHLNut

Thanks for helping out.

[YoBoGo]

Originally posted by Mr Steveo
Since I still ahvent ehard if MS is definitely going to keep offering security patches for their now discontinued MS JVM; I dont know what to recommend. Im as lost as you are on this one.

Flip a coin maybe?

Whatever you decide, remeber we will have Service Pack 1b rolled out within 30 days and it will include Sun Java included.

That makes sense, thanks. Guess I will wait for 1b...

[AHLnut]

NP Steveo, BTW, I now have the $$ for my new stuff, but after the announcement about an Intel price drop Feb. 23, why not wait another 2 + weeks Time will tell if I can wait or not

[+ve psi]

Hey, thanks gorg and steveo for ur help on finding that bios setting for pci latency. I had no problems finding it after ur advice however, since i have set it to 64 i have noticed a considerable increase in boot time. I recall reading that this shoud DECREASE the boot time. Have i done something wrong?


Thanks

[mrksha]

Well,this guy have a couple of wrong advices in his globally good guide for noobs.
"5. Set your “PCI Latency Timer” to 64"

This is just one of them.Return it yo default value 32.Only via users can benefit from pci latency change.

Another one,also questionable:
"8. For Windows NT/2000/XP be sure “Plug and Play OS” is set to “disabled/No” in BIOS"

I like to ask the author to go over his guide nad somehow mark potentionally dangerous or non benefitial settings.

[FB]

hey i am a non-VIA user and changing from 32-->64 on the PCI decressed my boot time by 10-12 seconds

also a lot of us have followed this guide almost to a "T" and have experienced no problems.

[YoBoGo]

I also have had no problems with the PCI Latency Timer. I believe that some had found a problem with sound cards working with the P4PE board and Mr Steveo had suggested setting PCI latency to 64 to help correct this.

As far as #8, I remember reading when you inable Universal Plug and Play in Windows NT/2000/XP, it overrides the BIOS setting Plug and Play OS anyway. I think the idea here is to disable anyway to be sure of no conflict. Correct me if I am wrong someone?

[Mr Steveo]

Mrkska,

Thank you for expressing your concerns. As you ahve seen if you read this thread, I have made corrections and improvements to the Guide when a member pointed out an error or better suggestion. And I continue to remain open to making changes and corrections when warranted. However, per the two BIOS settings you mention, I stand by what I wrote based on a great deal of trial and research.

PCI Latency Timer:
There is absolutely nothing wrong or harmful about a PCI Latency setting of 64. In fact, Asus is one of the few brands that defaults at 32, most default at 64.

Per the utility of this setting: You are correct that VIA users benefit from tweaking PCI Latency settings or using my good friend George Breese's patch. But is incorrect to say an adjusted PCI Latency setting will have no benefit to Intel based system. Please read eaerlier posts in this thread and forum for details.

So WADR, at this time I do not feel the recommended setting needs to be changed. For a further discussion on PCI Latency, what the setting does, and in what areas benefits can be found; I encourage you to read back a few pages in this thread. This settign has already been discussed at length.

Plug and Play OS / Plug and Play Aware OS:
This setting is widely misunderstood. Many people feel that if you want plug and play abilities such as for USB devices, you need to set this to Enabled in the BIOS. That is incorrect.
It is also incorrect to assume that you need to set it to enabled because Windows XP is a Plug and Play OS.

The only times you would need to choose enabled for PnP OS would be:
- For some analog modem PCI cards
- For systems that include poorly designed PCI cards, or pre PCI2.1 standard PCI cards.
- For some early BIOS versions of the Asus A7V333 (not an Intel board addressed in this Guide). Early revisions with early BIOS's sometimes needed the PnP OS set to enabled to work around a bug in the boards handling of system resources.

In every other instance almost without expcetion you will have a faster boot up, less resource problems, less shut down problems, and less chance of random reboots by setting PnP OS to disabled. Furthermore, if you are to beleive Microsoft, any OS newer than Win98 will in most operations ignore the PnP OS BIOS setting anyway.

Because this setting has been discussed numerous times already in this forum, I will not expend the time to repeat the definitions of its functions again here. You are welcome to use the forum search button to learn more. Also since this settings function is widely misunderstood, I might suggest you research it online at both Microsofts website, and Adrian Wongs Difinitive BIOS Guide.


============================================
Again, thank you for taking the time to express your concerns for the accuracy of the Guide. At this juncture, neither setting you mention is either "dangerous" or "non beneficial." If you have some empirical evidience that contradicts anything in the Guide, please feel free to send it to me and I will make any necessary changes. But at this point, and in the absence of any contradicting data, I see no reason to make such changes

Best regards,
- "The Author" LOL

[Mr Steveo]

Originally posted by YoBoGo


As far as #8, I remember reading when you inable Universal Plug and Play in Windows NT/2000/XP, it overrides the BIOS setting Plug and Play OS anyway. I think the idea here is to disable anyway to be sure of no conflict. Correct me if I am wrong someone?

Actually Universal Plug and play is destinctly different from the Plug and Play abilities of your OS; which is distinctly different from the PnP OS setting in the BIOS. All of them are called "plug and play" but none of them have functions that overlap. LOL Someone needs to change their names IMHO

FWIW, Universal Plug and play is a purely network and DirecX based function as of today. In short, Universal Plug and Play would be better named, "Network Plug and Play" The general idea is that your OS will recognize UPnP capable network devices and automatically configure their ports for best operation. Currently Universal Plug and Play is used by Windows and MSN Messenger to automatically configure the ports on a UPnP capable router such as dLink or Linksys. By enabing UPnP in the OS and using a UPnP router, you can finally use all of Messengers voice, video, and application sharing abilities. In the background the UPnP function is dynamically managing your routers ports so you do not have to.

Univcersal Plug and Play is also used in Direct Play gaming through Microsoft for auto configuration of ports. As time passes you will see more and more network devices become UPnP capable as we move into the years ahead. To learn more about UPnP networking, feel free to visit www.upnp.org

HTH