Category Archives: Windows 2000

Realtek HD Audio Driver Revision History – Windows 2000 x86 and Windows XP x86 – x64

Leave a reply

Realtek HD Audio Driver Revision History – Windows 2000 x86 and Windows XP x86/x64

 

R2.71 – 5.10.0.6873 -

R2.70 – 5.10.0.6662 -

R2.69 – 5.10.0.6649 -

R2.68 – 5.10.0.6602 -

R2.67 – 5.10.0.6526 -

R2.66 – 5.10.0.6482 -

R2.65 – 5.10.0.6449 -

R2.64 – 5.10.0.6438 -

R2.63 – 5.10.0.6410 -

R2.62 – 5.10.0.6392 -

R2.61 – 5.10.0.6383 -

R2.60 – 5.10.0.6363 -

R2.59 – 5.10.0.6343 -

R2.58 – 5.10.0.6316 -

R2.57 – 5.10.0.6299 -

R2.56 – 5.10.0.6278 -

R2.55 – 5.10.0.6257 -

R2.54 – 5.10.0.6235 -

R2.53 – 5.10.0.6215 -

R2.52 – 5.10.0.6194 -

R2.51 – 5.10.0.6167 -

R2.50 – 5.10.0.6151

R2.49 – 5.10.0.6132

R2.48 – 5.10.0.6101

R2.47 – 5.10.0.6083

R2.46 – 5.10.0.6077

R2.45 – 5.10.0.6069

R2.44 – 5.10.0.6066

R2.43 – 5.10.0.6050

R2.42 – 5.10.0.6043

R2.41 – 5.10.0.6029

R2.40 – 5.10.0.6013

R2.39 – 5.10.0.6000

R2.38 – 5.10.0.5995

R2.37 – 5.10.0.5983

R2.36 – 5.10.0.5969

R2.35 – 5.10.0.5953

R2.34 – 5.10.0.5943

R2.33 – 5.10.0.5936

R2.32 – 5.10.0.5928

R2.31 – 5.10.0.5919

R2.30 – 5.10.0.5911

R2.29 – 5.10.0.5898

R2.28 – 5.10.0.5888

R2.27 – 5.10.0.5874

R2.26 – 5.10.0.5864

R2.25 – 5.10.0.5859

R2.24 – 5.10.0.5854

R2.23 – 5.10.0.5845

R2.22 – 5.10.0.5832

R2.21 – 5.10.0.5821

R2.20 – 5.10.0.5817

R2.19 – 5.10.0.5809

R2.18 – 5.10.0.5804

R2.17 – 5.10.0.5794

R2.16 – 5.10.0.5791

R2.15 – 5.10.0.5783

R2.14 – 5.10.0.5772

R2.13 – 5.10.0.5767

R2.12 – 5.10.0.5764

R2.11 – 5.10.0.5755

R2.10 – 5.10.0.5745

R2.09 – 5.10.0.5735

R2.08 – 5.10.0.5730

R2.07 – 5.10.0.5717

R2.06 – 5.10.0.5713

R2.05 – 5.10.0.5708

R2.04 – 5.10.0.5700

R2.03 – 5.10.0.5694

R2.02 – 5.10.0.5683

R2.01 – 5.10.0.5680

R2.00 – 5.10.0.5672

R1.99 – 5.10.0.5667

R1.98 – 5.10.0.5657

R1.97 – 5.10.0.5653

R1.96 – 5.10.0.5643

R1.95 – 5.10.0.5636

R1.94 – 5.10.0.5628

R1.93 – 5.10.0.5624

R1.92 – 5.10.0.5618

R1.91 – 5.10.0.5605

R1.90 – 5.10.0.5591

R1.89 – 5.10.0.5582

R1.88 – 5.10.0.5574

R1.87 – 5.10.0.5567

R1.86 – 5.10.0.5559

R1.85 – 5.10.0.5548

R1.84 – 5.10.0.5532

R1.83 – 5.10.0.5523

R1.82 – 5.10.0.5512

R1.81 – 5.10.0.5506

R1.80 – 5.10.0.5497

R1.79 – 5.10.0.5490

R1.78 – 5.10.0.5485

R1.77 – 5.10.0.5480

R1.76 – 5.10.0.5477

R1.75 – 5.10.0.5473

R1.74 – 5.10.0.5470

R1.73 – 5.10.0.5464

R1.72 – 5.10.0.5449

R1.71 – 5.10.0.5443

R1.70 – 5.10.0.5436

R1.69 – 5.10.0.5433

R1.68 – 5.10.0.5413

R1.67 – 5.10.0.5413

R1.66 – 5.10.0.5404

R1.65 – 5.10.0.5397

R1.64 – 5.10.0.5391

R1.63 – 5.10.0.5377

R1.62 – 5.10.0.5377

R1.61 – 5.10.0.5377

R1.60 – 5.10.0.5366

R1.59 – 5.10.0.5366

R1.58 – 5.10.0.5366

R1.57 – 5.10.0.5366

R1.56 – 5.10.0.5345

R1.55 – 5.10.0.5345

R1.54 – 5.10.0.5345

R1.53 – 5.10.0.5324

R1.52 – 5.10.0.5324

R1.51 – 5.10.0.5324

R1.50 – 5.10.0.5319

R1.49 – 5.10.0.5319

R1.48 – 5.10.0.5317

R1.47 – 5.10.0.5296

R1.46 – 5.10.0.5294

R1.45 – 5.10.0.5288

R1.44 – 5.10.0.5286

R1.43 – 5.10.0.5283

R1.42 – 5.10.0.5282

R1.41 – 5.10.0.5273

R1.40 – 5.10.0.5268

R1.39 – 5.10.0.5265

R1.38 – 5.10.0.5257

R1.37 – 5.10.0.5253

R1.36 – 5.10.0.5247

R1.35 – 5.10.0.5242

R1.34 – 5.10.0.5233

R1.33 – 5.10.0.5229

R1.32 – 5.10.0.5224

R1.31 – 5.10.0.5221

R1.30 – 5.10.0.5211

R1.29 – 5.10.0.5202

R1.28 – 5.10.0.5200

R1.27 – 5.10.0.5188

R1.26 – 5.10.0.5178

R1.25 – 5.10.0.5172

R1.24 – 5.10.0.5152

R1.23 – 5.10.0.5136

R1.22 – 5.10.0.5128

R1.21 – 5.10.0.5127

R1.20 – 5.10.0.5125

R1.19 – 5.10.0.5123

R1.18 – 5.10.0.5122

R1.17 – 5.10.0.5120

R1.16 – 5.10.0.5119

R1.15 – 5.10.0.5116

R1.14 – 5.10.0.5109

R1.13 – 5.10.0.5038

R1.12 – 5.10.0.5037

R1.11 – 5.10.0.5036

R1.10 – 5.10.0.5034

R1.09 – 5.10.0.5033

R1.08 – 5.10.0.5032

R1.07 – 5.10.0.5031

R1.06 – 5.10.0.5030

R1.05 – 5.10.0.5029

R1.04 – 5.10.0.5028

R1.03 – 5.10.0.5027

R1.02 – 5.10.0.5022

R1.01 – 5.10.0.5022

R1.00 – 5.10.0.5017

Windows 2000 and Windows XP – Realtek HD Audio Device Driver Support is available for the following Devices and HD Audio Chipsets:

ALC880

ALC882

ALC883

ALC885

ALC886

ALC887

ALC888

ALC889

ALC892

ALC899

ALC861VC

ALC861VD

ALC660

ALC662

ALC663

ALC665

ALC670

ALC671

ALC672

ALC676

ALC680

ALC221

ALC231

ALC260

ALC262

ALC267

ALC268

ALC269

ALC270

ALC272

ALC273

ALC275

ALC276

ALC280

ALC282

ALC290

Watchguard XTM Firewall and UTM Appliance – High CPU Usage in the GAV (gateway anti-virus) scand process causes lag and typing delay in Remote Desktop Sessions (RDP) and SIP or VoIP latency issues

Watchguard XTM Firewall and UTM Appliance – High CPU Usage in scand process causes lag and typing delay in Remote Desktop Sessions (RDP).  You may find that remote users report a lag with Remote Desktop Sessions, freezing sessions, black screen and random disconnections.  At around the same time users report these issues you may find that the CPU usage of the scand process on your Watchguard has increased to 100% and the majority of the activity is attributed to the scand process.  You may be able to recreate this issue by browsing websites that utilise lots of Adobe Flash or Media Content as GAV will need to scan all these elements of the web page.  Login to the Watchguard System Manager and then open Firebox System Manager click on Status Report and scroll down the report until you find the Process List (Screenshot Below).  This information will automatically update every 30 seconds so you can see the %CPU column will change and update every 30 seconds.  The top value system shows the overall CPU utilisation and if you look further down you can see which sub processes are actually occupying the CPU time and making up the overall system usage.  In the screenshot below we can see that system is showing 100 % CPU Usage and then further down we can see that the scand process is accounting for 90.99% of this.  When the CPU Usage reaches 100% on the Watchguard unit it may stop forwarding other traffic and this accounts for the lag and jitter we see within the Remote Desktop Session.  Other time sensitive traffic such as VoIP or SIP traffic may also be affected by this issue as the packets are delayed whilst the Firewall recovers from the resource exhaustion.  Users may also report that web pages are slow to load at the time these issues occur where the GAV process is still dealing with the other requests.

Resolution/Workaround:

You can try disabling the GAV (gateway antivirus) for the HTTP and FTP Proxy to ensure that this is the actual cause of your issues, if the problem subsides then you may need to consider updating the XTM OS to the latest release i.e. 11.5.2 and/or adjusting the GAV policy so that it does not scan some content i.e. Images/Text within websites.  You may also need to consider opening a support case with Watchguard to make them aware of this issue, if you have a large number of users then you may even need to consider upgrading your XTM appliance to a larger unit i.e. XTM 23 to XTM 505 or XTM 22 to XTM330 to provide additional processing power (CPU) and system resources to cope with the additional anti-virus scanning requirements.

Watchguard XTM High CPU Usage scand

Watchguard XTM High CPU Usage scand

Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 DNS Server may stop responding to DNS queries and requests from client computers

Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 DNS Server may stop responding to DNS queries and requests from client computers, this issue may occur randomly and when it is occuring the DNS Server stops responding.

This issue occurs because the DNS Server goes into an infinite loop, more information about this issue and a hotfix to address the issue is provided in Microsoft KB 2655960 http://support.microsoft.com/kb/2655960

Troubleshoot a Blue Screen of Death BSOD or Crash Dump on a Microsoft Windows Operating System

It’s probably the thing we all dread most, evereything has been working great for weeks/months/years and then suddenly your machine starts randomly crashing to a Blue Screen of Death or BSOD

All is not lost though as Windows will often generate its own crash dump a report of what happened to cause the crash, this is often invaluable when it comes to finding the cause and fixing it.

A company called Nirsoft offer a great little utility called Blue Screen View, you can download it from here ttp://www.nirsoft.net/utils/blue_screen_view.html

This program will automatically analyse the default Mini Dump and Crash Dump locations and then pull back a summary of the driver or system file that was most likley the cause of your crash.  In many cases it’s then just a simple case of removing the offending software, updating/downgrading the device driver or installing a software patch/hotfix.

Microsoft Windows – Network Printer/s Unexpectedly Show Offline

When using Microsoft Windows (various editions and versions) you may find that your Network Printer Unexpectedly Shows Offline.  This can occur for a number of reasons and todays blog will try and help get you printing again.

First you should verify that you can ping the printer you are trying to print to, you can usually find the hostname or the IP address of the printer from the “Ports” tab of the printers “properties” page.

It should look something like this:

Printer Name or IP Address is where we can see which port the printer is trying to print to, we can then enter a “command prompt” by typing “cmd” into the “run” box and then type the ping command and the ip address or hostname of our printer.  Example is “ping 192.168.1.230″ or “ping hpinkjetprinter”

If we do not get a response from the address or hostname then it could indicate that the printer has been assigned a different IP address (DHCP) by the server or your Router.  It could also indicate that the printer is turned off, the network cable is unplugged or damaged, if the printer is wireless it may be that the signal is no longer in range or that the wireless credentials it was setup with have been changed (WEP or WPA Key, SSID).  Many Servers or Routers support reservations so that you can ensure your printer always gets the same ip address, alternatively you can find the hostname of your printer and set the printer port to the hostname, if the ip address changes the computer should then still be able to resolve the hostname to the current and valid ip address of the device.

If your printer is responding to a ping command but you still cannot print then it may be an issue with the configuration of the printers “Standard TCP/IP Port” you will several options on the port configuration page that can effect your ability to submit a print job to the network printer, it may also cause the printer to incorrectly report that it is offline.

One particular issues that I have witnessed first hand is an HP OfficeJet Printer showing offline when the “SNMP Status Enabled” is ticked under the  ”Standard TCP/IP Port” printer port configuration tab.  You may be able to ping the printer and access its web configuration but the printer will continue to show offline in Windows and print jobs will remian in the print queue.  Once the “SNMP Status Enabled” is unchecked the printer will appear online again and print correctly.

You amy also find that your printer only supports RAW or LPR mode, you can usually find further information on the “Protocol” that your printer supports via the technical manual or sometimes via the printers web configuration page.

Last but not least please remeber to check that you have the latest printer drivers from the manufacturers website, any firmware updates or software updates should also be installed to ensure the optimum performance and reliability of your product.  It is also important to remember that you should ensure the printer you are accessing is compatbile with your operating system and that driver support is either providd natively within Windows or the manufcaturer supply drivers via their website.

Windows will not boot with a Stop Error 0x0000007B

A very common BSOD (Blue Screen of Death) is a STOP error 0x0000007B and may indicate either a hardware, software or driver issue.

Please see the great troubleshooting guide put together by Tim Fisher on about.com

http://pcsupport.about.com/od/findbyerrormessage/a/stop0x0000007b.htm

One thing that Tim does not mention is that sometimes it is necessary to slipstream the AHCI SATA Controller Drivers into your Windows XP or Windows Server 2003 installation media.  This can easily be done by downloading and using nLite to slipstream drivers and updates into your Windows XP or Windows Server 2003 CD Media, you can get the application from http://www.nliteos.com/

Common AHCI Sata Drivers include:

Intel – http://downloadcenter.intel.com (Look under Chipset, Chipset Software and then Intel Rapid Storage Technology.  You will need the F6 Drivers for either x86 or x64 depending on you using 32bit or 64bit windows)

Nvidia – http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk or http://www.nvidia.com/Download/index.aspx?lang=en-us

AMD/ATI – http://support.amd.com/us/Pages/AMDSupportHub.aspx

Verify the Health and Operation of your Intel® Processor with the Intel® Processor Diagnostic Tool

A 32 and 64 bit version of the IPDT or Intel Processor Diagnostic Tool can be downloaded from here: http://www.intel.com/support/processors/sb/CS-031726.htm

You can also see a video on how to use it here: http://www.youtube.com/watch?v=tpPOqh_Bq78

You can use the diagnostic tool to test the various features of your Intel Processor and perform a stress test to ensure that it is operating in a  stable manner.

Intel Network Adapter Diagnostics May Wrongly Report that the Network Cable is over 100 Metres Long

When you run a Cable diagnostic using the Intel PROSet Network Adapter Diagnostics you may find that the utility incorrectly reports that your network cable is over 100 Metres and/or that the Cable is faulty/poor.

This issue can occur if you have a network switch that implements “power Saving” or “Green Ethernet” this feature is meant to reduce the power to a network port that is supporting a device with a short network cable run.

This “power saving” or “Green Ethernet” feature can cause the diagnostics to fail and can sometimes contribute to network drops and/or poor network throughput.  If you have a managed/smart switch then you can normally login via a browser and “Disable” this feature to correct the issue.

Microsoft Windows based Computers and Laptops – Slow System Startup with Realtek HD Audio Chipset

You may find that Windows based computers and laptops are very slow to startup and in some instances slow to shutdown.  This has been witnessed when out dated drivers are installed for the integrted Realtek HD Audio Chipset.

The Realtek HD Audio drivers offered on Microsoft Update are often dated 2005 and are many years behind those available directly from the Audio Chipset manufacturer.

You can verify your current Audio Chipset and Driver version from “Device Manager”

Please visit http://www.realtek.com/downloads/ to find and download the latest applicable drivers for your Windows system.  They will usually reference the drivers as “High Definition Audio Codecs (Software)” and then under Windows the list Operating System Compatability for each system and provide several download links based upon locations around the world.  Downloads from the Realtek site can be slow at busy times of the day so you may need to be patient and/or download outside peak hours.

As you can see from the table the current drivers from Realtek Support are dated 21st October 2011 and are usually updated every 1-2 months, it would be worth updating to the latest release to resolve your slow startup times and then add updating your audio drivers into your usual computer maintenance schedule.  Once you have updated remember to check Device Manager to ensure that the latest drivers are actually installed and that the device is operating correctly.