The HUGE BIG-BIG Windows Vista Thread

[ReelFiles]

I used the 88.61 graphics drivers and the latest Sil3114 Non-Raid drivers for XP. You didn't instal the Sil3114 drivers? Or do you mean the nVraid drivers? Are you planning on using Raid-0? It seem to be a hit or miss getting it to work optimal.

 

Beta Driver - nForce – Windows Vista x86 Beta 2

 

http://www.nzone.com/object/nzone_download..._x86_beta2.html

 

Sil Download Center

 

http://www.siliconimage.com/support/downlo...rs=1&sataraid=0

[dr_bowtie]

I am using a GeForce fx5700ultra and the Vista drivers installed say they are causing slow start-ups but the games played fine....

 

I went to the nVIdia website and downloaded and installed the latest Vista card drivers...Still get the error pointing to the old drivers but the games play better yet...

[ReelFiles]

I haven't had that issue since I switched to the x86 version.

[dr_bowtie]

I think I may wipe it and try again...

 

I cant get it to load above 210x9...220x9 is a no go for sure...

 

I am testing it on:

Abit AV8/3000venice/939 1.45vcore

PDP patriot-XBLK [email protected]

fx5700ultra

passes memtest fine at 220x9 hits the boot screen and blue screens.... I may try more vcore but I think 1.45vcore would be fine

 

so maybe I'll slacken the ram timmings (it's rated 2.5-3-3-7@ddr500)

[ReelFiles]

I had 2 BSODs when I was runnign 275x10, lowered it to 270x10 @1.45v and it's all good since. Memory is 1:1 (270MHz) 1T-2.5-4-4-8 undervolted @ 2.59v. That Venice can handle a bit more voltage as long as your cooling is good, had mine up to 1.72v on liquid 1.65v on air.

[ReelFiles]

View system stability with Reliability Monitor

 

http://www.microsoft.com/technet/windowsvi...mspx#BKMK_Scen6

 

Overview: View system stability with Reliability Monitor

Reliability Monitor is a snap-in for the Microsoft Management Console (MMC) that provides a system stability overview and trend analysis with detailed information about individual events that may affect the overall stability of the system. It will begin to collect data at the time of system installation.

 

In this task you will review the System Stability Chart and become familiar with the detailed event information Reliability Monitor uses to calculate the stability index.

 

Prerequisites for viewing system stability with Reliability Monitor

To complete this task, ensure that you meet the following requirements:

 

• Windows Vista Beta 2 is installed.

 

• There has been a minimum system running time of 24 hours since installation.

 

If you perform this task on a new system, you may see only minimal data regarding reliability events. Repeat the task after installing applications and adding hardware to learn more.

 

• You are logged on with administrative credentials.

 

The requirement for administrative credentials is related to a known issue in Windows Vista Beta 2. See the "Known Issues" section for more information.

 

 

Known issues for viewing system stability with Reliability Monitor

The following known issues may affect your ability to complete this task:

 

• Data used by Reliability Monitor is only accessible to accounts with administrative credentials. In order to see the System Stability Chart, you must be logged on as the local administrator, or have launched MMC with elevated privileges.

 

• Your Windows installation must run for at least 24 hours before data will be displayed in the System Stability Chart.

 

• Until Reliability Monitor has 28 days of data, the stability index will be displayed as a dotted line on the graph, indicating it has not yet established a valid baseline for the measurement.

 

 

Steps for viewing system stability with Reliability Monitor

Start Reliability Monitor from Windows Performance Diagnostic Console

1.

Log on to the computer using an account that is a member of the Administrators group.

 

2.

Click Start, click All Programs, click Accessories, right-click Command Prompt, and click "Run Elevated…" in the context menu.

 

3.

At the command prompt, type mmc.exe and press ENTER. MMC will start.

 

4.

In the File menu, click Add/Remove Snap-in…, select Reliability Monitor from the list of available snap-ins, click Add, and then click OK.

 

5.

In the navigation tree, click Reliability Monitor.

 

If your system has been running for less than 24 hours, you will see this error message:

 

Reliability Monitor cannot provide data because the Reliability Analysis Component (RAC) task has been disabled or because RAC has not calculated a session yet. Either enable the RAC task, or if the RAC task is running, please wait 24 hours and check for data again.

 

 

The top half of the Reliability Monitor window contains the System Stability Chart and a calendar for selecting a single date or a range of dates to display. To view a graph of all available data, click Select All Dates. To view data for a single date, click that date on the calendar.

 

Reliability monitor maintains a year of history for system stability and reliability events. The System Stability Chart displays a rolling stability index for the operating system. In Windows Vista, it shows one month of data.

 

At the bottom of the System Stability Chart, five bands track Reliability Events that contribute to the stability measurement for the system. Below the System Stability Chart, you can expand each Reliability Event category by clicking the plus sign (+) to view events for the date or range of dates selected. The data for each event type is as follows:

 

Software (Un)Installs

This category tracks software installations and removals including the operating system, Windows updates, drivers, and applications.

 

Software: Operating system, name of application, Windows update name, or driver name.

 

Version: Version of the operating system, application, or driver (this field is not available for Windows updates).

 

Activity: Indicates whether the event is an install or uninstall.

 

Activity Status: Indicates success or failure for the action.

 

Date: The date of the action.

 

Application Failures

This category tracks application hangs (including the termination of a non-responding application) and crashes.

 

Application: Executable program name of the application that hung or crashed.

 

Version: Version number of the application.

 

Failure Type: Indicates whether the application failed due to hang or crash.

 

Date: The date of the application failure.

 

Driver Failures

Drivers that failed to load or unload correctly are tracked in this category.

 

Driver Name: File name of the driver that failed to load or unload.

 

Version: Version number of the driver.

 

Failure Type: Indicates whether the driver failed to load or unload.

 

Date: The date of the driver failure.

 

Hardware Failures

Disk (DFD) and Memory (WMD) failures are tracked in this category.

 

Component Type: Indicates whether the failure occurred in hard drive or memory.

 

Device: Identifies the device that is failing.

 

Failure Type: Indicates whether a hard drive failure resulted from a bad disk or a bad block, or indicates that a memory failure resulted from bad memory.

 

Date: The date of the hardware failure.

 

Windows Failures

Operating system crashes, boot failures, and sleep failures are tracked in this category.

 

Failure: Indicates whether the event is a Boot Failure, OS Crash, or Sleep Failure.

 

Version: Versions of the operating system and service pack.

 

Failure Type:

 

• OS Crash: Indicates the Stop code.

 

• Boot Failure: Indicates the detected problem.

 

• Sleep Failure: Indicates the component veto or failure to enter hibernation.

 

 

Date: The date of the Windows failure.

[eelemus]

hrmm....okay...up and running vista 32 bit...gonna check out to see if it oc's the same....the only driver i cant get is for my wireless card..havent had much time to play around yet...some things i like...some i dont.well just have to see how it all works out...

[ReelFiles]

Windows Vista Beta 2 Windows System Resource Manager Step by Step Guide

 

http://www.microsoft.com/technet/WindowsVi...d.mspx?mfr=true

 

Just way too much info and links to cut and paste on that page, but might be useful to some hardcore tweakers.

[ReelFiles]

http://www.microsoft.com/technet/windowsvi...ipv6wv.mspx#ESD

 

New Features/Functionality of IPv6

Expanding the available IP address space was critical, but was not the only driver in developing IPv6. Many new requirements were taken into account, based on the limitations of IPv4 and how the future of packet networking was perceived to be progressing. IPv6 was created with the goal of supporting convergence, which will provide ubiquitous support for voice, video and data services over a single IP infrastructure. In order to achieve this goal, many new or advanced features and functions were incorporated into IPv6, including:

 

• Increased Address Space: One of the major advantages of IPv6 is the massive increase in address space. The address space available in IPv6 is so great it is difficult to even provide a comparison on how much more address space there is in IPv6 versus IPv4. IPv4 has 4,294,967,296 IP addresses where IPv6 has 340,282,366,920,938,463,463,374,607,431,768,211,456 (or 3.4x1038) IP addresses. The increase in the globally routable address space will allow organizations to move away from using non-routable IP addresses with Network Address Translation (NAT) and start again utilizing applications in a true end-to-end environment. It will also allow the explosion of IP-enabled wireless devices to continue, where every user will have multiple IP addresses, and will increase the flexibility businesses and service providers have with developing and rolling out new services and applications.

 

• Stateless Autoconfiguration: Automatic IP configuration has been available in IPv4 in the form of DHCP and is also available in IPv6 in DHCPv6. However, the real step forward in IPv6 is with stateless autoconfiguration. Stateless autoconfiguration allows the devices to configure their own IPv6 addresses by communicating with a neighboring router. While stateless autoconfiguration will be beneficial for most environments, the concept is critical in networks that are mobile, ad-hoc and/or have a significant number of devices with limited management capability. An example is sensor-based networks that could include millions of remote, wireless devices that are accessible only on the network. Autoconfiguration will help companies lower their network administration costs and the resources required to maintain and move network devices. Although Automatic Private IP Addressing (APIPA) has some similar characteristics to autoconfiguration, it is very different. APIPA allocates an address from a specific range of IPv4 address space (169.254.0.1–169.254.255.254) when a DHCP server is not available. Address Resolution Protocol (ARP) is used to verify IP addresses are unique on the Local Area Network (LAN). Once a DHCP server is available, the IP addresses of the clients are updated automatically. APIPA addresses are only usable for the local subnet. Routing information is not provided to the host and APIPA addresses are not routed off the local subnet.

 

• Extension Headers: While the IPv6 header has been greatly simplified when compared to IPv4, extension headers are used to provide advanced functionality required at the header level in the IP packet. As the name suggests, they are simply incremental headers added to the base IPv6 header that provides tremendous flexibility for future capabilities. This method for adding functionality at the header level allows the base header to remain constant and deterministic, while allowing new capabilities to be phased in over time. These "extensions" to the protocol can determine behavioral characteristics at the infrastructure and routing level, or at the application level, providing dynamic, policy-based networking and user-defined end-to-end services. Extension headers provide enormous flexibility in the future development of services and applications by providing a standard framework to add new capabilities into IPv6. Business and service providers will be able to utilize extension headers in the future to leverage capabilities not already existing in IPv6.

 

• Mandatory Security: Although Internet Protocol security (IPsec) is available for IPv4, it is an add-on that has been primarily used for tunneling and network encryption for remote access Virtual Private Networks (VPNs) and connecting sites. Many organizations have begun exploring the use of IPsec on a wider basis, but obstacles, such as NAT, can make IPsec hard to deploy. With IPv6, IPsec is a mandatory part of the implementation and will provide for a common network layer security infrastructure as well as security services such as authentication, integrity, and confidentiality to be used as needed. The inclusion of IPsec will allow businesses to improve their security model and extend their security policies down to the host level and not just maintain an enclave mentality.

 

 

IPv6 Addressing

Significant work and diligence has extended the IPv4 address life through various policies and the use of NATs; however, recent reports show that IPv4 address exhaustion is imminent. A report prepared by the NRO2 in conjunction with the regional Internet registries including African Network Information Center (AFRINIC), Asia Pacific Network Information Centre (APNIC), American Registry for Internet Numbers (ARIN), Latin American and Caribbean Internet Address Registry (LACNIC) and RIPE Network Coordination Centre (RIPE NCC) shows approximately 25% of IPv4 addresses remain for allocation. Although many organizations and carriers within the US and Europe may not have a short-term concern based on their current IPv4 address allocation pool, the exponential growth of IP-enabled devices coupled with the lack of available IPv4 address space will drive the migration to IPv6.

 

The way that IP addresses are represented has also changed. Under IPv4, IP addresses were represented by four octets or 8 bit fields (0–255 for each field written in standard decimal notation) separated by decimal points. Examples of IPv4 addresses include:

 

• 131.107.20.60

 

• 192.168.118.183

 

 

With IPv6, IP addresses are typically represented by 16-bit fields (0–FFFF for each field written in hexadecimal notation) separated by colons. Examples of IPv6 addresses include:

 

• 3ffe:2900:d005:4:104a:2a61:0:0

 

• 3ffe:ffff:4004:1952:0:7251:bc9b:a73f

 

 

In cases where multiple 0 blocks are part of the IPv6 address, "::" can be used once in an IPv6 address to shorten the notation. For example, fe80:0:0:0:0:70:77:26 is shortened as fe80::70:77:26.

 

The primary driver behind IP address allocation policies in IPv6 is not conservation of IP addresses, but more hierarchical and efficient routing. Internet routing tables are exceedingly large today under IPv4 and they could become excessively large if not tightly managed under IPv6. Using the concept of aggregation, the IPv6 address is thought of as two separate pieces brought together. The first 64 bits of the IPv6 address typically identifies your network or "where you are" and the second 64 bits identifies the device or "who you are." This not only supports the concept of hierarchical routing, but also plays a very large role in the ability for IPv6 devices to use autoconfiguration. But the implications of this type of allocation are enormous. This means that every LAN segment could potentially have 264 devices saying "who they are." Remember, the current Internet has a total of 232 addresses, so each subnet on the "New Internet of IPv6" would have several orders of magnitude more IP addresses available than the current Internet has today.

 

In addition to the technical changes in addressing, major IP allocation policy changes have occurred as well. Under IPv4, the RIRs, such ARIN, have many policies in place to strictly limit and conserve the IPv4 address space. Under IPv6, the story is different. While the registries will manage the IPv6 address space efficiently, current guidelines from ARIN recommend Internet Service Providers (ISP) allocate 48-bit public address prefixes (with 216 subnets) for every site (home and business users) as the standard initial allocation. This would mean that every home user would be able to establish 65,536 subnets each with the potential for 264 devices on each subnet.

 

Implementing and Using IPv6 in Windows Vista

One of the major issues with transitioning is that IPv6 is not backwards compatible with IPv4. Thus, a computer on the network operating with only IPv6 addresses can not directly communicate with a computer on the network operating in IPv4 mode only; however, Microsoft's implementation of Windows Vista will solve a significant problem for agencies, businesses, educational institutions, ISPs, and consumers that want to transition to IPv6. Windows will be both IPv4- and IPv6-capable out of the box. This means that every computer running Windows Vista will be able to communicate across IPv4 and IPv6 networks at the same time. Windows Vista runs a single-stack, dual-IP layer architecture for easier deployment and manageability. This dual-IP layer approach will allow organizations to save money and resources by transitioning their organization's infrastructure to IPv6 over time without worrying about interoperability issues with their workstations.

 

If you want to access IPv6 resources and your network infrastructure does not support IPv6, don't worry, Windows Vista also builds in support for automated tunnels such as ISATAP and Teredo. If Windows Vista does not detect IPv6 within the network it will try well known IPv6 tunneling mechanisms. This means that anyone who installs Windows Vista or turns on a new computer with Windows Vista could have automatic access to IPv6-based Web sites and resources over an existing Internet or intranet connection, if their network administrators allow it—even if the enterprise's ISP does not support IPv6.

 

IPv6 will be dominant in Windows Vista. What does this mean? If you have the option of using either IPv4 or IPv6 for a particular application, then Windows Vista will default to using IPv6. Again, this allows organizations to transition to IPv6 at their own pace, without costly reconfiguration of every workstation. When applications are upgraded to IPv6, users will be able to automatically access those new features with IPv6 without having to do anything, since Windows Vista will utilize IPv6 by default. Of course, this can be configured by the administrator.

 

Microsoft has a strong focus on security, too. Windows Vista includes IPsec and a built-in host-based firewall that works for both IPv4 and IPv6. IPsec can be used to protect traffic sent over the network as well as to authenticate connections coming into the workstation. Microsoft has introduced a concept called Domain Isolation, which will allow organizations to develop “zones of trust,” where only trusted computers can communicate with each other. All other connections attempted will be dropped and will not be visible to un-trusted users. Microsoft has also introduced the concept of Server Isolation that allows only trusted domains or subsets of domains to connect to specific servers.

[soundx98]

The download section at www.planetamd64.com should be back up in a day or two.

(Some dirtballs hacked the site over the weekend).

It's got large amount of drivers for most devices and the members are extremely friendly and helpful like the "street".

 

How about giving us some detailed information on what wireless device you are using?

Later models may or may not work in x64.

DON'T expect 32-bit wireless drivers to work in x64. $34.95 at Wal-Mart.

 

Have you had a chance to check your wireless manufacturer's site?

 

I'm using a early Belkin USB wireless (F5D7050) will Ralink modded drivers.

It connects and stays connected but I have to manually enable it after every reboot in Vista x64.

I have no issues with it in XP x64 Edition. The 7051 new model I have no idea on.

 

Getting any Videocam to work in x64 is a nightmare.

Hopefully with the reception Vista Beta 2 is getting more manufacturer's will be releasing updated drivers shortly.

[Spyvie]

• IPv4 has 4,294,967,296 IP addresses where IPv6 has...

 

This explains all the trouble I had configuring my network adapter in XP64 a few months ago, I must have been the four billion two hundred ninety four million nine hundred sixty seven thousand two hundred and ninety seventh node.

[ReelFiles]

Hehe funny. I like that embossed effect of your sig, very cool.

 

I like the new nVidia control panel