Tuesday, September 15, 2009

Convert .ivr files to .wma or .mp3 format using RealPlayer and a USB thumbdrive (Rev: 1.2)


The .ivr (Internet Video Recording) is a video file format used by the RealPlayer software from RealNetworks. The procedures to convert .ivr files to .wma (Windows Media Audio) or .mp3 (MPEG-1 Audio Layer 3) format using the free RealPlayer are different depending on your RealPlayer version. Assume that you are using Windows XP Professional SP3 Operating System (OS).




Procedures for RealPlayer v15 only (latest RealPlayer v15 as of 12 Oct 2012)


The procedures below show how to convert your .ivr files to .mp3 (MPEG-1 Audio Layer 3) format using the free RealPlayer Converter that comes with the RealPlayer v15.

  1. Please download and install RealPlayer version 15.0.6.14 (win32) or higher version from RealNetworks. In Windows XP OS, please click Start -> All Programs -> RealNetworks -> RealPlayer Converter.

  2. In RealPlayer Converter, kindly click "Add..." to add your .ivr files. In "Convert to:", please choose "MP3 Audio Only". The default MP3 quality is "128 kbps Stereo" and the default "Save in:" "Same directory as original" are fine with me. Click the "Start" button to start the .ivr to .mp3 conversion.




Procedures for RealPlayer v11 only (old)


The procedures below show how to convert your .ivr files to .wma (Windows Media Audio) or .mp3 (MPEG-1 Audio Layer 3) format using the free RealPlayer v11 and a USB thumbdrive or flash drive.

  1. Please download RealPlayer version 11.1 (win32) from RealNetworks or from here RealPlayer11GOLD.rar (12,893,466 bytes) MD5 checksum:
    395e96d4944fbd232408afb58490014a

    You can use WinRaR to unzip the RealPlayer11GOLD.rar.
    Kindly install RealPlayer v11.1 (basic version will do, no need to get Premium version) to your computer.

  2. Please plug in your USB thumbdrive or flash drive.

  3. In RealPlayer v11, click "My Library" -> "Playlists" -> "New Playlist". Give your Playlist a name. Then, click the "Add Clips" to add your .ivr files to this Playlist.

    Notes:


    a) If all the clip names are all the same after adding your .ivr files, it is advisable to change every clip names to a different name so that when RealPlayer converts your .ivr clips to .wma or .mp3 format, it will not stop at the first clip.


    b) If your .ivr files are stored in a folder name in Chinese characters, it is advisable to rename the Chinese characters folder name to English characters to avoid error in adding the .ivr clips into the Playlist.


  4. In RealPlayer v11, click "Burn/Transfer". If you have not install the VideoBurn plugin (11430 KB), RealPlayer v11 will automatically download and install it for you.

    In RealPlayer v11, at the "Current Burner/Device", click to select your USB thumbdrive. Then, at "My Library" on the Left Hand Side (LHS) of the RealPlayer, double-click "Playlist" -> "playlistThatYouHaveJustCreated".

    Click "Change Options..." locates at the bottom LHS of RealPlayer.
    Click the "Transfer" tab. You can choose to convert your .ivr clips to "MP3", "MP3 VBR" or "Windows Media Audio (.wma)" format. You can also choose the quality of the convert clips. As I want to convert the .ivr files to .mp3 format, I select "MP3" and set the quality as "192 Kbps Stereo".

  5. In RealPlayer v11, after setting your "Change Options...", click to select one of the clip names. Then, right-click and choose "select all" to select all the clips. Click the "Add Selected to Device" button to let RealPlayer convert your .ivr files to .wma or .mp3 format, and store the convert .ivr files to your selected USB thumbdrive.

Sunday, August 16, 2009

PostScript (PS) and Printer Command Language (PCL) printer drivers (Rev: 1.1)



In most laserjet printer, there are 2 types of printer drivers provided, namely PostScript (PS) and Printer Command Language (PCL). The PS printer driver is normally use to print Portable Document Format (pdf) document. For other document types (.doc, .txt, etc), please use the PCL printer driver.



HP 4500 colour laser printer

If you are printing a .pdf document to a HP 4500 colour laser printer using the HP Universal Print Driver for Windows PCL6 (v5.0) for Windows XP Operating System (OS), you will encounter the below printout error:

PCL XL error
subsystem: KERNEL
Error: UnsupportedProtocol
Operator: 0x0
Position: 0


The above error occurred because you are printing a .pdf document but you have use the PCL6 printer driver to print your document. Please change your printer driver to PS driver, eg: HP Universal Print Driver for Windows PostScript (v5.0) before printing.



If you are printing a .doc document to a HP 4500 colour laser printer using the HP Universal Print Driver for Windows PCL6 (v5.0) for Windows XP OS and you encountered the below printout error:

PCL XL error
subsystem: KERNEL
Error: UnsupportedProtocol
Operator: 0x0
Position: 0


The problem is caused by the HP Universal Print Driver for Windows PCL6 (v5.0) printer driver. You should delete the HP laserjet 4500 printer that uses the HP Universal Print Driver for Windows PCL6 (v5.0) printer driver. Then, install the HP LaserJet 4500 PCL6 Printer Driver and use it to print the .doc document to a HP 4500 colour laser printer.

Tuesday, August 4, 2009

Add 32 bits Samsung ML-4550 printer drivers on Windows 2008 x64 Enterprise OS server (Rev: 1.0)



Situation

We have a remote server running Windows 2008 x64 Enterprise Operating System (OS). A Samsung ML-4550DN printer is installed and shared at this remote server. When we tried to install “Additional Drivers...” of the Samsung printer for the 32 bits Windows 2000 or XP OS under the “x86 processor (Type 3 – User Mode)”, an error message of “Please provide path to Windows Media (x86 processor)” pop up and is asking for the ntprint.inf file from the i386 folder of the Windows media (x86 processor). As the server is installed with Windows 2008 x64 Enterprise OS, it does not has an i386 folder on the media.


Solutions:
  1. Please login to a 32 bits Windows XP/Vista/2008 computer (example: localx86PC) with administrator right.

    Please download the 32 bits Samsung ML-4551ND PS printer drivers for Win98/ME/2K/XP/2003/X64 OS version 1.61 or higher version into the localx86PC (assume Win XP OS). Extract the printer drivers to a folder, example: d:\SamsungPostScriptDriver.


  2. At the localx86PC, kindly click Start -> Run.
    Type \\remoteServerName (replace remoteServerName with your remote server name). Then, double-click on the remote share printer (example: Samsung ML-4550 Series PS) at the remote server to install the remote share printer to your localx86PC.


  3. A window prompt entitle "Connect to Printer" with the below content appears:
    "You are about to connect to a printer on remoteServerName, which will automatically install a printer driver on your machine. Printer drivers may contain viruses or scripts that can be harmful to your computer. It is important to be certain that the computer sharing this printer is trustworthy. Would you like to continue ?"
    -> Click "Yes" to continue.

    Another window prompt entitle "Connect to Printer" with the below content appears:
    "The server for the 'Samsung ML-4550 Series PS' printer does not have the correct printer driver installed. If you want to search for the proper driver, click OK. Otherwise, click Cancel and contact your network administrator or original equipment manufacturer for the correct printer driver."
    -> Click "OK" to search for the printer driver.


  4. After that, a window prompt entitle "File needed: Printer driver INF for Samsung ML-4550 Series PS" appears:
    "The file '*.INF' on (unknown) is needed."
    -> Kindly click the "Browse" button to copy the printer drivers files from the folder where you have extracted the downloaded printer drivers, example:
    d:\SamsungPostScriptDriver\Printer\PS\English\WinXP2K\.


  5. At the localx86PC, kindly click Start -> Printers and Faxes. Select the Samsung ML-4550 Series PS printer that we have just installed, right click on it and choose Properties. Click the Sharing tab. Then, kindly click the “Additional Drivers...” button.

    At the “Additional Drivers...” prompt, kindly click the Intel Environment (Windows 2000 or XP) selection box (default Installed is "No"). Click OK and the Samsung x86 printer drivers for Windows 2000 or XP will be uploaded to the remote server running Windows 2008 x64 Enterprise OS.


Reference
:


[1] Unable to add 32bit HP drivers to a Windows 2008 64bit print server with “Please provide path to Windows Media (x86 processor)” error

Saturday, August 1, 2009

Solved unknown devices in WinXP SP3 OS on Lenovo T400 2768-HJ8 notebook (Rev: 1.0)



After installing Windows XP Professional SP3 OS on the Lenovo ThinkPad T400 2768-HJ8 (Type: 2768, Model: HJ8) notebook, there are various unknown devices in the Control Panel -> System -> Hardware -> Device Manager as shown below:

  1. Base System Device
    (PCI\VEN_1180&DEV_0592&SUBSYS_20CA17AA&REV_11\4&8365E1C&0&04F0)
    Base System Device
    (PCI\VEN_1180&DEV_0843&SUBSYS_20C917AA&REV_11\4&8365E1C&0&03F0)
    Base System Device
    (PCI\VEN_1180&DEV_0852&SUBSYS_20CB17AA&REV_11\4&8365E1C&0&05F0)
    -> All the above 3 Base System Device drivers are Ricoh Multi Card Reader Driver v3.54.02 or higher version.

  2. Ethernet Controller
    -> Using Intel PRO 1000 LAN adapter v9.52.10.1003 or higher version.

  3. Fingerprint Sensor
    -> Using Lenovo Fingerprint Software v3.2.0.341 or higher version.

  4. Network Controller
    -> Using Intel PRO Wireless WifiLink 5100 v12.04.0000 or higher version.

  5. PCI Device
    -> Using Intel Matrix Storage Manager v8.8.0.1009 or higher version.

  6. PCI Serial Port
    (PCI\VEN_8086&DEV_2A47&SUBSYS_20EC17AA&REV_07\3&B1BFB68&0&1B)
    -> Using Local Manageability Service and Serial Over LAN (Intel AMT 4.0) v5.4.0.1074 or higher version. You need to install Microsoft .NET Framework 3.5 Service Pack 1 or higher version first before installing this driver.

  7. PCI Simple Communications Controller
    (PCI\VEN_8086&DEV_2A44&SUBSYS_20E617AA&REV_07\3&B1BFB68&0&18)
    -> Using Intel Management Engine Interface (Intel AMT 4.0) driver v4.0.1.1074 or higher version. You need to install Microsoft .NET Framework 3.5 Service Pack 1 or higher version first before installing this driver.

    After that, you can also download the Intel Management Engine (ME) Firmware (Intel AMT 4.1) to upgrade the Intel Management Engine Interface to 4.1.11.1051 or higher version. However, if your Lenovo ThinkPad T400 BIOS ID is 7VETxxWW, you cannot use this Intel AMT Management Engine Firmware.

  8. SM Bus Controller
    -> Using Intel Chipset v8.7.0.1007 or higher version.

  9. Unknown device
    -> Using Power Manager v1.60 or higher version.

  10. Unknown device
    -> Using Intel Integrated TPM (Trusted Platform Module) v4.0.1.1074 or higher version.

  11. Video Controller
    -> Using ATI Mobility RADEON HD 3400 Series, 3650 and FireGL V5700 v8.563.2.1-090401a-079920C or higher version.

  12. Modem Device on High Definition Audio Bus
    -> Using Modem driver v7.73.00.00 or higher version.

  13. Audio Device on High Definition Audio Bus
    -> Using Conexant Audio Driver v4.92.5.0/3.64.6.0 or higher version.


Integrated Camera Software v5.8.49004.0 or higher version and Bluetooth with Enhanced Data Rate Software v5.5.0.6400 or higher version are also installed as the Lenovo ThinkPad T400 2768-HJ8 notebook comes with an integrated camera and supports Bluetooth technology.

The below ThinkVantage Technologies software are also installed:

  • Presentation Director v4.30a or higher version. It is a display configuration utility for your Lenovo ThinkPad T400 2768-HJ8 notebook that enables you to create, manage, and use presentation and display schemes.

  • ThinkVantage Active Protection System v1.63 or higher version. It provides airbag-like protection for your hard drive.

There are other ThinkVantage Technologies software available but I have not installed to test it.


References:

[1] Drivers and software - ThinkPad T400 and T400s

[2] Unknown Devices after installing Windows XP with SP2 - ThinkPad W500, W700, W700ds T400, T500, R400, R500, X301, X200, X200s, X200 Tablet, SL300, SL400 and SL500

Tuesday, July 28, 2009

Add 3rd party mass storage drivers to Recovery Console (Rev: 1.0)


After installing Windows XP Professional Operating System (OS) on the Dell PowerEdge 2600 server that had a spoilt SCSI CDROM drive, I have also installed the Recovery Console in the Windows XP OS. When the Dell PowerEdge 2600 server runs the Recovery Console that is installed at the hardisk, the Dell PowerEdge 2600 server LSI Logic drivers PERC 4/Di is still needed to prevent the Blue Screen 0x0000007B error from appearing.

As the SCSI diskette drive might become faulty one day, I need to add in the Dell PowerEdge 2600 server LSI Logic drivers PERC 4/Di drivers information to the installed Recovery Console so that I do not have to press [F6] and load them from the SCSI diskette drive. The steps are as shown below:


1) Added the mraid2k.sys [Downloaded from Dell PowerEdge 2600 server support website -> Windows 2000 OS drop down menu -> "SCSI RAID controllers" -> "LSI Logic - Driver" -> "PERC 4/Di" (Please choose according to your types of RAID Controller. You can check it from the monitor screen when the Dell PowerEdge 2600 server is booting up] into the Recovery Console I386 directory.


2) Added the below content on top of the existing content of txtsetup.sif in the Recovery Console I386 directory:

; ======= txtsetup.sif_Start =============================

; Additional txtsetup.sif content of the Recovery Console at I386 directory
; in order to add Dell PowerEdge 2600 server,
; LSI Logic drivers PERC 4/Di driver info

[SourceDisksFiles]
; JackNg, For Dell PowerEdge 2600 server
mraid2k.sys = 1,,,,,,4_,4,1,,,1,4
; ---------------------------------


[HardwareIdsDatabase]
; JackNg, For Dell PowerEdge 2600 server_Start --------
PCI\VEN_101E&DEV_1960&SUBSYS_04711028 = "mraid2k"
PCI\VEN_101E&DEV_1960&SUBSYS_04931028 = "mraid2k"
PCI\VEN_101E&DEV_1960&SUBSYS_04751028 = "mraid2k"
PCI\VEN_1028&DEV_000E&SUBSYS_01231028 = "mraid2k"
PCI\VEN_1028&DEV_000F&SUBSYS_013B1028 = "mraid2k"
PCI\VEN_1028&DEV_000F&SUBSYS_014A1028 = "mraid2k"
PCI\VEN_1028&DEV_000F&SUBSYS_014C1028 = "mraid2k"
PCI\VEN_1028&DEV_000F&SUBSYS_014D1028 = "mraid2k"
PCI\VEN_101E&DEV_1960&SUBSYS_05111028 = "mraid2k"
PCI\VEN_1000&DEV_1960&SUBSYS_05181028 = "mraid2k"
PCI\VEN_1000&DEV_1960&SUBSYS_05201028 = "mraid2k"
PCI\VEN_1028&DEV_0013&SUBSYS_016C1028 = "mraid2k"
PCI\VEN_1028&DEV_0013&SUBSYS_016D1028 = "mraid2k"
PCI\VEN_1028&DEV_0013&SUBSYS_016E1028 = "mraid2k"
PCI\VEN_1028&DEV_0013&SUBSYS_016F1028 = "mraid2k"
PCI\VEN_1028&DEV_0013&SUBSYS_01701028 = "mraid2k"
PCI\VEN_1000&DEV_0408&SUBSYS_00011028 = "mraid2k"
PCI\VEN_1000&DEV_0408&SUBSYS_00021028 = "mraid2k"
; For Dell PowerEdge 2600 server_End ----------------


[SCSI.Load]
; JackNg, For Dell PowerEdge 2600 server
mraid2k = mraid2k.sys,4
; --------------------------------


[SCSI]
; JackNg, For Dell PowerEdge 2600 server
mraid2k = "LSI Logic/Dell PERC 2/3/4/CERC ATA100 (W2K)"
; ---------------------------------

; ======= txtsetup.sif_End ============================


References:

[1] How can I add 3rd party mass storage drivers to my installed Recovery Console so I don't have to press F6 and load them

[2] How to install and use the Recovery Console in Windows XP

Thursday, June 18, 2009

Install Windows XP Pro SP3 OS using diskette drive at Dell PowerEdge 2600 server (Rev: 1.1)



Introduction

The Dell PowerEdge 2600 server (2.4 Ghz * 2, 2 GB RAM, 6 * 73 GB 10K rpm hardisks) had a spoilt SCSI CDROM drive and the latest BIOS version A14 does not support booting from USB ports. A new SCSI DVD drive from Dell cost S$101.65 including 7% GST and delivery charge. The Dell server was bought on 25/2/2003 and was considered an obsolete model in today. Hence, it does not seems worth to buy the SCSI DVD drive that can only be used on the Dell PowerEdge 2600 server.

Dell officially support Windows 2000, server 2003 or 2008 x86/x64 Operating System (OS) for the Dell PowerEdge 2600 server, but it does not officially support Windows XP OS. As I can only use the diskette drive to boot up the Dell PowerEdge 2600 server in the DOS environment, I cannot install Windows 2008 OS as the setup.exe cannot run in the DOS environment.

My Windows XP OS installation method works only in a networking environment because I need to access the Windows XP CDROM content in another computer that is in the same domain as the Dell PowerEdge 2600 server.


Preparation

1) BIOS

I have placed only 1 SCSI hardisk in slot 0 of the Dell PowerEdge 2600 server. In the BIOS setup, make sure you have set the "Integrate Devices" as "RAID enabled". If the "Integrate Devices" selection is "SCSI", you will see the Blue Screen 0x0000007B error during installation of the Windows XP OS. If you change from "SCSI" to "RAID enabled", you will see the below message:

Warning: Detected mode change from SCSI to RAID on channel A of the embedded RAID subsystem. Data loss will occur ! Press [Y] to confirm the change, press any other key to cancel.

Hence, make sure you have backup your files before you change the "Integrate Devices" from "SCSI" to "RAID enabled". Please also make sure the BIOS "Boot Sequence" is set to boot from diskette first.


2) PERC/CERC BIOS configuration utility

During boot up, I pressed [Control] m to go into the "PERC/CERC BIOS configuration utility". I deleted the old existing configuration settings that used up all the 6 SCSI hardisks. Then, in the "Configuration" -> "Easy Configuration", I set the SCSI hardisk ID 0 online (A00-00) [Jack, July 2010: The SCSI hardisk must set as ONLIN (online) so that Windows XP or Windows 2008 Standard x86 OS can detect the SCSI hardisk. If the SCSI hardisk is in READY stage, Windows XP or Windows 2008 Standard x86 OS will not be able to detect the SCSI hardisk] as Span 1, RAID 0 and save the configuration. After that, I use the "Initialize" menu to initialize the logical drive 0 before exiting from the "PERC/CERC BIOS configuration utility". Please note that initializing the hardisk will destroy any data inside the hardisk.

During boot up, it will show "1 logical drive found on host adapter" and "1 logical drive handled by BIOS" messages. If you see the boot up messages "0 logical drive found on host adapter" and "0 logical drive handled by BIOS", the SCSI hardisk is not detected by the SCSI adapter. As a result, DOS will also not detect any hardisk.


3) Computer that share the Windows XP CDROM content

I use another Windows XP Professional computer that is in the same domain as the Dell PowerEdge 2600 server to act as a file server. I copy the Windows XP Professional CDROM \i386 folder content to d:\winxpsp3\i386 folder and then share the winxpsp3 folder using my user ID.


4) Bart's Network Boot diskette

Download Bart's Network Boot Disk, "BFD full package v1.0.7" and unzip it. Then, copy SmartDrv.exe (available from Windows 98 CDROM) to \disk1\bin directory of that extracted Bart's Network Boot disk directory. SmartDrv.exe is a disk caching utility that can speed up the copying process of files and is needed when installing Windows XP OS in DOS environment.

The Dell PowerEdge 2600 server has a built-in Intel Pro/1000 XT network connection interface. Hence, you will also need to download the "Intel PRO/1000 Network Driver v3.46 080803", e1000.cab v1.6 network adapter plug-in file and copy it to the \cabs\drivers\ndis directory of that extracted Bart's Network Boot disk directory. Delete any one of the existing network adapter plug-in .cab files in the \cabs\drivers\ndis directory because during booting, the pop up menu can only display 11 network adapters on the monitor screen.

Kindly open a command prompt. Go to the extracted Bart's Network Boot disk root directory, run "bfd msnet" and follow the instructions on the screen to create a network boot diskette.


5) Dell LSI Logic Drivers diskette

Surf Dell Support website to download the LSI Logic drivers for PowerEdge 2600 server. This is needed to prevent the Blue Screen 0x0000007B error during installation of the Windows XP OS.

In the Dell PowerEdge 2600 server support website, kindly select "Windows 2000" OS in the drop down menu. Then, go to "SCSI RAID controllers" -> "LSI Logic - Driver" -> "PERC 4/Di" (Please choose according to your types of RAID Controller. You can check it from the monitor screen when the Dell PowerEdge 2600 server is booting up). I download the perc-cerc-w2k3-6.46.2.32-A05.exe from the "Hard-Drive" category and extract it using WinZip or WinRaR software. Then, I copy all the extracted files to a floppy diskette.


6) gdisk.exe diskette

I copy the gdisk.exe file from Norton Ghost 2003 software into a diskette so that I can use it to partition and format the hardisk. I did not use the DOS fdisk.exe to partition the hardisk because it can only detects 4466 MB of total disk space and not the 73 GB hardisk size. Moreover, fdisk.exe is very slow as it always need to verify drive integrity.


Windows XP Professional SP3 installation using diskette drive in a networking environment
  1. Please make sure that the BIOS "Boot Sequence" is set to boot from diskette first. Kindly insert the Bart's Network Boot diskette into the server diskette drive and power on the server to boot from the Bart's Network Boot diskette.

    In the pop up menu options, I first choose the "Clean Boot" menu option because I don't need the networking environment as I just want to partition and format the hardisk. Partition and format the hardisk is needed to prevent the below error message during Windows XP installation:

    Windows XP requires a hard drive volume with at least 538 megabytes (564658176 bytes) of free disk space. Setup will use part of this space for storing temporary files during installation...

    At the DOS command prompt, eject out the Bart's Network Boot diskette and insert the gdisk.exe diskette into the diskette drive. I use the below gdisk.exe commands:

    # gdisk 1 /cre /pri /sz:40000 /for /q
    To create a DOS primary partition of size 40000 MB ( default FAt32 file system) on hardisk 1 and quickly format it. Don't use NTFS file system because DOS does not recognized it.

    # gdisk 1 /act /p:1
    To activate partition 1 on hardisk 1.

    After that, a reboot of the server is needed so that the new 40000 MB partition is recognized by DOS as c drive and SmartDrv.exe is able to read and write cache to the c drive. Hence, eject out the gdisk.exe diskette, insert the Bart's Network Boot diskette and reboot the server using [CTRL][ALT][DEL].

    After rebooting, I choose the "Boot with EMM386 (most compatible)" menu option in order to boot into the networking environment in DOS. Bart's Network Boot diskette cannot automatically detect the Intel PRO/1000 network adapter. I have to choose "MANUAL" -> "E1000 Intel PRO/1000 network driver v3.46 080803". In the TCP/IP pop up menu, I use the default "Enable DHCP" & "Load Packet Drive Interface". After that, I enter the "Logon as:" using my userid and enter the "Domain:" as my network side domain accordingly. After typing my password, the DOS command prompt appeared.

    # msnet
    To use msnet to map a share network drive as shown below:
    Drive: w
    Path: \\remoteComputerName\winxpsp3

    After typing my password, I have sucessfully mapped the content of the remote computer share directory winxpsp3 under the mapped drive w.

    # w:
    To go to w drive

    # cd i386
    To change to w:\i386 directory

    # winnt
    To start the Windows XP installation in DOS environment.


  2. During the initial startup of the Windows XP installation, quickly press [F6] (Immediately when you see the Press [F6] message that is shown at the bottom of the monitor screen) to install third party SCSI or RAID drivers. The below message will appear:

    Setup could not determine the type of one or more mass storage devices installed in your system...

    Press s to specify additional device. When prompt, insert the Dell LSI Logic Driver diskette and select "DELL PERC RAID Products for Windows 2000". Do not select "DELL PERC RAID Products for Windows 2003 (x86)" as it will caused the Blue Screen 0x0000007B error during Windows XP installation.

    After Windows XP Professional OS had copied the needed files to the 40000 MB partition (FAT32 file system), please remember to take out the Bart's Network Boot diskette before rebooting the server so that it can boot from the hardisk. After rebooting from the hardisk, please continue the Windows XP Professional OS installation as per normal.

Update device drivers in Windows XP Professional enviroment

In Windows XP Professional OS environment, we need to update 2 of the below device drivers:
  • Intel Pro/1000XT Network Connection (refers to the network adapter)
  • PE/PV 1x6 SCSI BP SCSI Processor Device (refers to the backplane)

Intel Pro/1000XT Network Connection

The Dell Windows 2000 Intel PRO Gigabit Adapters drivers does not work because it does not has the require e1000325.sys file. Please surf the Intel website to download the Intel PRO 1000/XT Server Adapters (PRO2KXP_v14_0.exe) for Windows XP. Kindly extract the PRO2KXP_v14_0.exe using WinZip or WinRaR software. Then, in Windows XP Device Manager, select the "Intel Pro/1000XT Network Connection", right-click and click the "Update Driver...". Point to the extracted PRO2KXP_v14_0.exe directory, \Pro1000\Win32 and Windows XP will copy the required driver files.

PE/PV 1x6 SCSI BP SCSI Processor Device

In the Dell PowerEdge 2600 server support website, kindly select "Windows 2000" OS in the drop down menu. Then, go to "SCSI nonRAID controller" -> "Dell - Driver" -> "Backplane". Download and extract the Backplane driver (DellBPA04.exe) using WinZip or WinRaR software. Then, in Windows XP Device Manager, select the "PE/PV 1x6 SCSI BP SCSI Processor Device", right-click and click the "Update Driver...". Point to the extracted DellBPA04.exe directory and Windows XP will copy the required driver files.


References:

[1] Bart's Network Boot Disk

[2] Dell Support, Dell Storage Controllers User Guide

[3] Intel PRO/1000 XT Server Adapter

[4] Norton: Introduction to gdisk

[5] Microsoft Windows XP Professional Product Documentation on Winnt, SMARTDRV Cache Status

Monday, May 25, 2009

"Fan error" in IBM T42 notebook (Rev: 1.2)



JackNg updates on 7 January 2010:

I have changed to a known good fan from another IBM T42 notebook. The "fan error" is solved as I can heard the fan rotating sound, but the IBM T42 notebook hang problem after using it for more than 1 minutes still occurred.

I have swapped the hardisk (same Hitachi model and 60 GB capacity) that came with existing old Windows XP Professional OS previously used by another person. The IBM T42 notebook still has the hang problem. I booted the IBM T42 notebook to Safe Mode, and it did not hang. I suspected that the hang problem might be caused by a software or OS fault. Hence, I restored the C partition from a clean Windows XP Professional OS backup. The hang problem is solved as the IBM T42 notebook works normally now.



JackNg updates on 14 November 2009:

The IBM T42 notebook boots normally on November 2009. After I have login to Windows XP Professional environment, the whole screen always hang: mouse not moving, keyboard has no response, etc. It took me half a day to realize that it was due to hardware fault: the CPU fan was not working and the CPU overheat problem might has caused the hang problem.

I have referenced to the "IBM Hardware Maintenance Manual - ThinkPad T40, T40p, T41, T41p, T42, T42p" on steps to take out the fan assembly, clean it and put it back. However, the hang problem still existed. Seem like it is time to buy another notebook.



When power on the IBM ThinkPad T42 notebook, "fan error" boot up error message was briefly shown and the IBM thinkPad T42 notebook automatically power off. I took out the notebook keyboard in order to see the CPU fan. During power on, the CPU fan was running normally. However, the "fan error" boot up error message still appeared and the notebook still automatically power off.

It took me a while to realize that the "fan error" was due to the uneven surface of the table. I place the notebook on top of a table where the pop up table "skin" has tilted the notebook slightly upward. If I placed the notebook on a flat and even table, the notebook boot up normally.