Powinno wystarczyć :D Paczka ze sterownikami do Fujitsu Siemens Amilo L7310GW WIN XP
**
**
** VIA Rhine Family Fast Ethernet Adapter
**
** RPL BOOTROM for remote-booting Windows 95
**
** v4.36 Feb 2005
**
**
Introduction:
=============
This document shows you how to configure the Remote-Boot service in Windows
NT Server 3.5, 3.51, 4.0 for remote-booting Windows 95 client.
Contents of the Subdirectory:
=============================
RPLWIN95.TXT This file.
RPL.LOM The bootrom binary file for Lan On Motherboard..
RPL.32 The 32K bootrom binary file for Network Interface Card.
RPL.64 The 64K bootrom binary file for Network Interface Card.
FETND.DOS The NDIS2 driver require for remote boot.
W95BB.CNF The configuration file require for remote boot win95.
PROTOCOL.INI The configuration file require for remote boot.
FETND3.INF The NDIS3 driver INF file require for remote boot
Windows 95 from NT server.
FETND3R.SYS The NDIS3 driver require for remote boot
Windows 95 from NT server.
Requirement:
============
* A Windows NT 4.0 server with the Remoteboot Service installed and
configured. Earlier versions of NT do not support Windows 95 clients.
* A workstation running Windows 95 with connections to the NT server.
This workstation should have a CD-ROM drive. If not, the NT server
must have a CD-ROM drive installed and configured for sharing.
* Windows 95 on CD-ROM. Make sure the CD-ROM contains the NETSETUP.EXE
program. You must purchase the correct licensed copy of Windows 95 for
network installation.
* An Rhine Family Fast Ethernet adapter with bootROM. You must be able to
remoteboot from the NT server with this bootROM.
Installation:
=============
Before starting the installation process, make sure that the adapter
is properly installed and configured. You can use the diagnostic program
(A:\DIAG.EXE) to make sure your connection with the network is correct.
Setup Procedure for DOS
-----------------------
1. The BOOTROM installation procedures are identical in Windows NT Server 3.5,
3.51, 4.0. First, install the Remoteboot Service on the NT Server:
Choose " Control Panel\Network\Add Software " and select " Remoteboot
Service " , follow the screen instruction to install.
2. Use " File Manager " in NT Server 3.5, 3.51 or " Windows Explorer " in NT
Server 4.0 to share the following directory:
\windows\rpl\rpl\rplfiles, suppose \windows is your Windows NT directory.
3. Copy all the MS-DOS 6.22 files as follow:
attrib -s -h -r c:\io.sys
attrib -s -h -r c:\msdos.sys
copy c:\io.sys c:\windows\rpl\rplfiles\binfiles\dos622
copy c:\msdos.sys c:\windows\rpl\rplfiles\binfiles\dos622
copy c:\dos622\*.* c:\windows\rpl\rplfiles\binfiles\dos622
attrib +s +h +r c:\io.sys
attrib +s +h +r c:\msdos.sys
4. Copy the NDIS2 driver for " PCI Fast Ethernet Adapter " as follow:
copy a:\bootrom\fetnd.dos c:\windows\rpl\bblock\ndis
md c:\windows\rpl\bblock\netbeui\fetnd
copy a:\bootrom\fetnd.cnf c:\windows\rpl\bblock\netbeui\fetnd
copy a:\bootrom\protocol.ini c:\windows\rpl\bblock\netbeui\fetnd
5. Run RPLCMD to add a bblock record for the adapter as follow:
net start remoteboot ;run in MSDOS prompt
rplcmd ;Follow the example below to enter data
Adapter Boot Config Profile Service Vendor Wksta [Quit] V
Add Del Enum: A
VendorName=004063 ;upper 6 digits of your adapter's ethernet ID
VendorComment=xx...x ;type your vendor string. optional.
Adapter Boot Config Profile Service Vendor Wksta [Quit] B
Add Del Enum:A
BootName=DOSV1
VendorName=004063 ;upper 6 digits of your adapter's ethernet ID
BbcFile=BBLOCK\NETBEUI\FETND\FETND.CNF
BootCommet=xx...x ;optional string
WindowsSize=0
Adapter Boot Config Profile Service Vendor Wksta [Quit] C
Add Del Enum:A
ConfigName=DOS622V1
BootName=DOSV1
DirName=DOS
DirName2=DOS622
FitShared=FITS\DOS622.FIT
FitPersonal=FITS\DOS622P.FIT
ConfigComment=DOS 6.22 FETND
DirName3= ;press " Enter "
DirName4= ;press " Enter "
Adapter Boot Config Profile Service Vendor Wksta [Quit] Q
6. Run " Control Panel\Services " , select " Remoteboot Service " and change the
" Startup " option to " Automatic " . Now reboot NT Server, remoteboot service
will be started automatically.
7. Run " Remoteboot Manager " from " Administrative Tools "
a. Choose " Remoteboot\New Profile.. " to create a Profile Name according to
the DOS 6.22 FETND configuration.
b. Choose " Remoteboot\New Workstation.. " to create a Workstation Name
according to the profile name and your Adapter Ethernet ID.
8. Now the remoteboot server is ready, boot your workstation with " BOOTROM
plug in PCI Fast Ethernet Adapter " , then you can access the NT Server from
your workstation.
Setup Procedure for Windows 95
------------------------------
1.Installing SBS for Windows 95 Clients
(1) On the server that will contain SBS files, create a shared directory
with 90 MB of space available. The shared directory can have any name.
(for example, \\server direcotry\sharedir as \\NT4S\SBS).
(2) As you share the directory, assign read-only permission for regular users
and full access for administrators.
(3) Install one regular Windows 95 client on the network or use an existing
one. You will use this client to configure the SBS server.
(4) Log on to the Windows 95 client using an account that has wirte access to
the shared directory on the SBS server.
(5) Make sure you use Windows 95 UPGRADE Version. Put the Windows 95
compact disc in the client CD-ROM dirve. In Windows Explorer, switch to the
Admin\Nettools\netsetup directory.
(6) Double-click Netsetup.exe
(7) In the Server-Based Setup dialog box, click Set Path, and specify the path
to the SBS server; then click OK, A network name for a server (for example,
\\server1\sharedir as \\NT4S\SBS).
(8) Click Install
a. Set the source path for Windows 95 files.
b. This is the path to the compact disc on the client.
c. If asked, specify that you do not want to create a default setup script.
d. Provide a CD Key number for product identification.
e. If you support only remoteboot clients, click Server.
f. If you support other SBS functions as well, click User choice.
g. Do not click Local hard drive.
h. Server-Based Setup copies Windows 95 files to the SBS shared directory.
(9) Copy driver file fetnd3r.sys from diskette to shared directory on SBS server.
For example:
copy [boot win95 by rpl]\fetnd3r.sys \\NT4S\system
(10) At the remoteboot server, put the compact disc containing the Windows NT
remoteboot for Windows 95 files into a drive. Run win95srv.bat to update
the Windows 95 files for remotebooting.
For example:
E:
cd \client\rpl\update
win95srv.bat & lt; dest & gt;
& lt; dest & gt; is the shared directory on the SBS server as \\NT4S\SBS
(11) At the remoteboot server, start Remoteboot Manager.
(12) On the Configure Menu, click Check Configuration to activate the new
configurations.
2. Installing the First Windows 95 Client
(1) Installing the first Windows 95 client requires booting that client first
to MS-DOS 6.2.x (Refer the section " Setup up procedure for DOS " ).
(2) Machines directories can reside on the remoteboot server.
Mkdir c:\rplmachines
Net share machines=c:\rplmachines
(3) Use the net logon command to log on using an account that has read access
to the SBS server and write access to the shared directory that will contain
this client machine directory.
(4) Synchronize the time and date settings of the client, the SBS server, and
the remoteboot server. Differing settings can interfere with Windows 95 Setup.
The format of this command is
net time /domain:server /set
for example : net time /domain:NT4S /set
(5) Use the net use command to map driver letters to the SBS server and machine
directory location, and then determine the highest drive letter in use on the
computer.
For example, if you have a local hard drive with one partition, C: will be
mapped to the remoteboot server, D: will be the local hard drive, E: is
reserved for use as a RAM drive, and F: and higher are available for use.
You would type:
net use f: \\sbs_server\win95_share as net use I: \\NT4S\SBS
net use j: \\mach_server\mach_share as net use j: \\NT4S\Machines
(6) Change to the drive letter mapped to the SBS directory.
(7) Run the Windows 95 Setup program by typing:
setup /t:temppath as follows:
setup /t:j:\client1.tmp
1. In the Server-based Setup dialog box, click Setup Windows to run from a
network server.
2. In the Startup method dialog box, click Start Windows form the network
(remote boot server).
3. In the machine Directory dialog box, when asked where to install
Windows 95, type the path of the machine directory (using the drive
letter specified in Step 4, for example, J:\client1).
4. In the Setup Options dialog box, click Custom setup.
In the Analyzing You Computer dialog box, click No, I want to modify the
hardware by myself.
5. Exculde as many hardware types and items form autodetection as possible.
If autodetection crashes, run Setup again and exclude more items form
autodetection.
Note: We sugget exeluding serial port detection. It conflicts your network
adapter easily.
6. In the Select Components dialog box, click to clear the Communications
check box (unless the client has a modem and you intend to use dial-up
networking).
7. In the Network Configuration dialog box, check that your network adapter
and desired.
Note: Don't remove Diup-Up adapter in installation procedure.
8. If there are no network adapters shown, you must add and configure your
network adapter.
Note: Make sure your adapter driver is for boot rom, not for Windows 95.
You can get these files in this folder.
9. In the Identification dialog box, make sure that the workgroup for this
client is the same as the workgroup or domain of the SBS server and
machine directory server.
10. When the Windows 95 Setup program is done, reboot the client. The client
will not yet boot to Windows 95; however you must complete more steps
first.
3. Create a profile for the Windows 95 client
At the remoteboot server (or a client running Remoteboot manager focused on the
remoteboot, start Remoteboot manager)
(1) Boot the client to MS-DOS 6.2x to confirm that the MS-DOS configuration is
correct. For details, see adding a New Clientt¡¨ earlier in this chapter.
(2) Copy w95bb.cnf to \\NT4S\RPL\BBLOCK\NETBEUI\FETND
(3) Use the rplcmd utility to add a boot block record for the new adapter
C:\NT4S\RPL & gt; rplcmd
Adapter Boot Config Profile Service Vendor Wksta [Quit]: B
Add Del Enum: A
BootName=W95V1
VendorName=004063
BbcFile=BBLOCK\NETBEUI\FETND\W95ND.CNF
All other parameters are optional
BootComment=Name of the adapter
WindowSize=0
Adapter Boot Config Profile Service Vendor Wksta[Quit]:C
Add Del Enum: A
ConfigName=Win95V1
BootName=W95V1
DirName=DOS
DirName2=Win95
FitShared=FITS\WIN95.FIT
FitPersonal=FITS\WIN95P.FIT
All other parameters are optional
ConfigComment=Windows 95 & lt; adapter name & gt;
DirName3=
DirName4=
(4) Edit the client workstation record to assign the client to the Widnows 95
profile.
(5) You must also copy \protocol.ini and \fetnd.dos NDIS driver to
c:\machine0\client1\suboot directory.
copy \fetnd3r.sys file to c:\sbsfiles\system directory.
note:
if you lost fetnd3r.sys file that win95 system will show the message
" you can now safely turn off your computer.if you want to restart your computer "
(6) Next, you must manually edit the following files found in the
C:\machine0\client1\SUBOOT directory
* AUTOEXEC.BAT
* MSDOS.SYS
* PROTOCOL.INI --- this folder
* FETND.DOS --- this folder
* SYSTEM.DAT
(7) To edit the registry file SYSTEM.DAT use REGEDIT.EXE to export its contents
to text file, edit the text file, then import the text file back into SYSTEM.DAT.
See the example below.
regedit /L:system.dat /E registry.txt
edit registry.txt
regedit /L:system.dat /C registry.txt
(8) Please note that REGEDIT must be run from the DOS command prompt. It
will not work as intended if you load it from a DOS session under Windows
95. The easiest way to do this is to remoteboot from your first Windows 95
client, and, when the message " Starting Windows 95 " appears, press the F8
function key. When the boot menu appears, select the Step-by-step
Confirmation option, answer Yes to each line except WIN.COM. When prompted
to start WIN.COM answer No. This will drop you to the DOS command prompt.
(9) Export system.dat miniregistry file as follows:
regedit /L:system.dat /E registry.txt
(10) Edit REGISTRY.TXT by searching and replacing all occurences of the new
PCI machine environment and driver name .
For example:
old register.txt new register,txt
" transport " = " *netbeui,*nwlink, " -- & gt; " transport " = " *netbeui,*nwlink,ndishlp.sys "
" netcard " = " " -- & gt; " netcard " = " fetnd.dos "
You should also modify following environment variable:
" BootDir " = " A:\\ " -- & gt; " BootDir " = " C:\\ "
" BootHost " = " A:\\ " -- & gt; " BootHost " = " C:\\ "
" WinbootDir " = " A:\\ " -- & gt; " WinbootDir " = " D\\winboot "
" HostWinBootDir= " A:\\ " -- & gt; " HostWinBootDir= " C:\\ "
(11) After modifying REGISTRY.TXT you must update SYSTEM.DAT by importing
the new information.
regedit /L:system.dat /C registry.txt
(12) Remove the hidden, system, and read only attributes from SYSTEM.DAT by
entering:
attrib -r -s -h system.dat
(13) copy new system.dat to c:\machine0\client3\suboot directory.
(14) At the remoteboot server run the Rpl\Bin\win95clt.bat program by typing:
cd & lt; systemroot & gt; \rpl\bin
win95clt mach_directory \\rpl_server profile_name
For example:
win95clt \\NT4S\machines\client1 \\NT4S w95rhine
(15) At the SBS server, edit machines.ini file in the SBS directory and add the
following lines for the new client:
[adapter id]
SYSDATPATH=g:\machine_dir
g=\\machine_dir\mach_share
For example, you might add the following lines to machines.ini:
[004064003021]
SYSDATPATH=j:\client1
j=\\NT4S\machines
(16) Reboot the Widnows 95 client.
The client will now boot to Windows 95 and complete the Windows 95 Setup
program.
**
**
** VIA Rhine Family Fast Ethernet Adapter
**
** NDIS Driver for Windows NT 3.51/4.0
**
** v3.50 Aug, 2005
**
**
Introduction:
=============
This document shows you how to setup the driver in Windows NT operating system.
Contents of the Subdirectory:
=============================
FETND4.SYS The NDIS4 driver for Windows NT.
FETND3.SYS The NDIS3 driver for Windows NT.
FETNDH.HLP The help file.
NTUTIL.DLL The user configuration library.
OEMSETUP.INF The setup information file.
WINNT.TXT This file.
Installation:
=============
Before starting with the installation process, make sure that the adapter
is properly installed and configured.
1. Open " Control Panel " - & gt; " Networks " , and choose the " Add Adapter " button.
The Add Noetwork Adapter dialog box appears. Select " & lt; other & gt; Requires
disk from manufacturer " in the list of Network Adapters, and then press
& lt; Enter & gt; .
2. Insert the driver diskette into your floppy drive, and specify the
path of the driver in the diskette(i.e. A:\) if necessary.
3. Select the correct Adapter, and start to copy the driver files to your
system.
4. After all the driver files have been copied to your system, a property
dialog box appears in the screen. You can enable the special properties
if you want to.
5. When the driver installation is completed, restart your PC.
Note:
1. In Setup Option " Flow Control " :
When setting to Hardware Default(Auto), the flow control setting is
according to the auto-negotiation result based on PHY hardware default
values. However, when setting to other values(Disable, Enable), driver
will just disable or enable flow control ability according your to setting.
Drivrutin till Synaptics Touchpad för Windows 2000/XP
Installationsanmärkning
Version 8.0.16
1. Installera drivrutinen till Synaptics TouchPad
-------------------------------------------------
Den här drivrutinen kräver Windows 2000/XP.
ANMÄRKNING FÖR ATT SPARA INSTÄLLNINGAR:
--------------------------------------
Windows 2000/XP sparar inte några användarinställningar för användare som tillhör
gruppen " Gäster " . Det här gäller speciella TouchPad-inställningar såväl som
andra användarinställningar. Om du vill spara dina inställningar,
kontrollerar du att ditt användarkonto inte tillhör gruppen " Gäster " via
programmet Användarhanteraren (du måste vara Administratör för att ändra
användarinställningar).
Installationsprocedur:
----------------------
För det första, om du har en ny TouchPad kopplar du in den och startar om
Windows 2000/XP. Windows 2000/XP identiferar sedan din nya TouchPad och installerar en
standard musdrivrutin som hanterar den. Du kan inte installera drivrutinen till
Synaptics TouchPad förrän den här processen är klar och din TouchPad fungerar som
ett normalt pekdon.
Logga på systemet som " Administratör " eller som en annan användare med
administratörsbehörighet.
Kör " Setup.exe " . Det här programmet installerar automatiskt drivrutinen till
Synaptics TouchPad så att den hanterar alla PS/2-pekdon och seriella pekdon som
har anslutits till datorn.
Du måste starta om Windows efter att installationen är klar. Om drivrutinen har
installerats rätt, bör du se TouckPad-ikonen i aktivitetsfältet bredvid klockan
efter att du har starta om Windows. Dessutom visas en dialogruta med namnet
" Information about your TouchPad " . Du kan förhindra att den här dialogrutan visas
i framtiden genom att markera kryssrutan " Stop showing me this message " .
Om du vill ha hjälp om hur du använder TouchPad, väljer du " Tell me more... " i
dialogrutan " Information about your TouchPad " , eller dubbelklicka på
TouchPad-ikonen i aktivitetsfältet och klicka på knappen " Hjälp " .
Om du vill ändra en eller flera av dina pekdon så att de använder en annan
drivrutin än standard Microsoft eller en drivrutin från tredje part ska du öppna
Musikonen i Kontrollpanelen och välja fliken " Allmänt " . Där väljer du pekdonet
som du vill ändra och klickar på " Ändra... " . Du kan sedan välja en annan
drivrutin som ska hantera enheten.
Windows 2000pSynaptics Touchpad Driver
CXg[É¢Ä
Version 8.0.16
1. Synaptics TouchPad DriverÌCXg[
-------------------------------------------
}`vZbT[Rs
[^ÉÖµÄ
---------------------------------------
ܾ±ÅÌmFÍūĢܹñªA±ÌhCo[Í}`vZbT[Rs
[^ÅàgpµÄ¢½¾¯Ü·B
CXg[è
-------------------------------------------------------
ܸͶßÉATouchPadð¨¿ÌûÍÚ±ðµÄWindows 2000/XPÉu[gµÄ¾³¢B·éÆWindows 2000/XPÍ»ÌTouchPadðF¯µW}EXhCo[ðCXg[µÜ·B ±ÌvZXª®¹µ ȽÌTouchPadªWÌ|CeBOEfBoCXƵÄ@\µÈ¢ÀèSynaptics TouchPadhCo[ÍCXg[ūܹñB
" Ah~jXg[^ " AÜ½Í " Ah~jXg[^ ð¼Ì[U[ " ÌÇ¿ç©Å Windows 2000/XP VXeÉOIµÄ¾³¢B
" Setup.exe " .ð쮳¹Ü·B±ÌvOª²gpÌRs
[^Ì·×ÄÌPS/2ÆVAE|CeBOEhCo[ðìµSynaptics@TouchPadhCo[ð©®IÉCg[µÜ·B
CXg[ª®¹µ½çWindowsðÄN®³¹Ä¾³¢BhCo[ª³µCXg[³êÄ¢éÆAWindowsðÄN®µ½ãÉAæÊÌ^XNo[ÌNbNÌ¡ÉTouchPadACRª»êÜ·BܽA " Information about@TouchPad " Ì_CAO{bNXª\¦³êÜ·B
±Ì_CAOðñ©ç\¦µ½È¢êÉÍA " Stop showing me this message " Ì`FbN{bNXÉ`FbNðüêľ³¢B
TouchPadÌwvðgp·éÉÍA " Information about your TouchPad " _CAO{bNX©ç " Tell me more... " ðIÔ©A^XNo[ÌTouchPadACRð_uNbNµÄA " Help " {^ðNbNµÄ¾³¢B
WÌ}CN\tgܽÍT[hp[eBÌhCo[ðgp·é½ßÉ|CeBOfBoCXðÐÆÂÈãwèµ½¢êÍA}EXRg[plÅ " General " ^uðIðµÈ¯êÎÈèܹñB»µÄϦ½¢|CeBOEfBoCXðIðµ " Change... " .ðNbNµÄ¾³¢B»êÉæÁÄfBoCXðì·é½ßÌÊÌhCo[ðIðÅ«Ü·B
Smart Link 56K Modem Driver
Version: 4.20.01MT14
(C) 1998-2005 Smart Link Ltd.
=============================
This document contains release notes and other information about
this product. Information in this document is the most current
available. For your convenience, print a copy of this file and
keep it with your user manual.
------------------------
How to Use This Document
------------------------
To view README.TXT on screen in Windows Notepad, maximize the
Notepad window.
To print README.TXT, open it in Windows Write, Microsoft Word,
or another word processor. Then select the entire document
and format the text in 10-point Courier before printing.
This file (README.TXT) contains:
--------
Contents
--------
1) Quick Start
2) How to verify installation
3) Uninstall procedure
4) Update procedure
5) Country selection
6) Call Progress Sounds
7) Known issues
8) Troubleshooting
9) Disclaimers
--------------
1. Quick Start
--------------
1) This driver supports HAMR5600, SmartRiser56, SmartRiser561, SmartRiser563,SmartPCI56,SmartPCI561,SmartPCI562,SmartPCI563, SmartPCI2800 and SmartLAN56 modem chipsets.
It also supports SmartRiser565 modem chipset (modem device for High-Definition Audio bus).
For SmartRiser565, this driver is compatible with motherboards based on Intel ICH6 chipset only.
2) For HAMR5600, SmartRiser56,SmartRiser561 and SmartRiser563 this driver is
compatible with motherboards based on Intel 810, 820, 815E, 820E, 845, 850,
ICH4, ICH5, 440MX (Banister), VIA VT82C686, VIA KT266, VIA 8231/8233/8235/8237,
SiS 540/630/96x, NVidia MCP/MCP2, ATI SB200/400 and ALI M1535/M1535D+/1563
core logic chipsets.
All riser card form factors are supported (AMR/MDC, CNR and ACR).
For up-to-date information about compatible motherboards, turn
to Smart Link web site (www.smlink.com).
3) This version of drivers is only compatible with Microsoft
Windows 2000, Windows XP 32bit (SP1 and SP2) or Windows Server 2003.
4) If any type of Smart Link modem is already installed in your
system and you want to update its' device driver you may either:
a) First uninstall existing drivers (See Uninstall Procedure), and only
then proceed to install the new drivers.
b) Install the new drivers using Setup.Exe (See installation Procedure).
5) Before installing a riser card modem, check your card for proper
jumper setting of Primary or Secondary Codec Mode. PCI modems
usually won't have jumpers.
Before installing SmartRiser565 modem, make sure that MS UAA bus driver for High-Definition
Audio bus is already installed. If it is not already installed then:
1) For Windows XP SP2 this driver is already included and should be installed automatically
2) For Windows 2000 SP4 and Windows XP SP1 use MS package - KB835221.exe
3) For Windows Server 2003 Standard (32-bit version only) use MS package - KB835221_srv03.exe
To install your modem drivers for the first time:
-------------------------------------------------
Option 1 - Automatic Hardware Detection
For Windows 2000, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2
or Windows Server 2003:
a) For riser modem card do the following:
1) Turn your PC off, and remove the power cord.
NOTE: SOME PCI 2.2 MOTHERBOARDS KEEP THE SLOTS POWERED EVEN
WHEN THE PC IS TURNED OFF. TO PREVENT DAMAGE TO YOUR MODEM
AND YOUR PC, REMOVE THE POWER CORD.
2) Plug in your modem card into a free slot (AMR/MDC/CNR/ACR slot for riser cards or PCI slot).
In case of SmartRiser565 modem, just make sure that modem device is plugged into High-Definition Audio bus.
b) Restart your PC.
c) Windows will instantly detect the modem and will start software
installation.
d) When requested, point to the drivers installtion directory on the
floppy disk or CD-ROM.
e) Modem drivers will be installed.
Option 2 - Setup.Exe:
Setup.exe is provided with the drivers and should be run from the
drivers installation directory.
For Windows 2000, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2
or Windows Server 2003:
a) For riser modem card do the following:
1) Turn your PC off, and remove the power cord.
NOTE: SOME PCI 2.2 MOTHERBOARDS KEEP THE SLOTS POWERED EVEN
WHEN THE PC IS TURNED OFF. TO PREVENT DAMAGE TO YOUR MODEM
AND YOUR PC, REMOVE THE POWER CORD.
2) Plug in your modem card into a free slot (AMR/MDC/CNR/ACR slot for riser cards or PCI slot).
In case of SmartRiser565 modem, just make sure that modem device is plugged into High-Definition Audio bus.
b) Restart your PC.
c) When Windows detects the modem and starts software installation,
press " cancel " to cancel the installation wizard.
d) Double-click on Setup.Exe and follow the instructions.
e) Modem drivers will be installed.
-----------------------------
2. How to verify installation
-----------------------------
To verify that the modem is installed correctly, follow these steps:
a) Click " Start & gt; Settings & gt; Control Panel & gt; Modem " : check for the
presence of a " Smart Link 56K Modem " .
b) In " Control Panel & gt; Modems & gt; Properties & gt; Diagnostics " click on
" Query Modem " button and check that the modem responds.
To Check that the modem is working properly:
a) Open " Hyper Terminal " .
b) Select the " Smart Link 56K Modem " or " Direct to port " option.
c) Type ATI1, ATI2 or ATI3 and make sure you receive the modem IDs.
Dial any accessible phone number, and see that that phone rings.
Dial to another modem (ATDTxxx or via the dial button of the
TAPI interface) and see that a modem session is established.
If you have successfully connected, then the modem has been
successfully installed.
----------------------
3. Uninstall Procedure
----------------------
a) Click " Start & gt; Settings & gt; Control Panel & gt; Add/Remove Programs " .
b) Select " Smart Link 56K Modem " .
c) Click the " Add/Remove " button.
d) An Unistall Wizard appears. Follow the instructions on screen.
You must choose to restart the system in order to complete modem removal.
e) Modem drivers will be uninstalled.
f) Now you may turn your PC off, remove the power cord and remove the
modem card from its' socket.
NOTE: SOME PCI 2.2 MOTHERBOARDS KEEP THE SLOTS POWERED EVEN
WHEN THE PC IS TURNED OFF. TO PREVENT DAMAGE TO YOUR MODEM
AND PC, REMOVE THE POWER CORD.
-------------------
4. Update Procedure
-------------------
To update your modem drivers:
Option 1:
- Uninstall previous drivers (see above procedure) and reboot your system.
- When the system detects the modem follow installation instructions (see above procedure).
- New drivers will be installed.
Option 2:
- Double-click on Setup.Exe (located in the updated driver installation directory) and follow installation instructions (see above proedure).
- New drivers will be installed.
--------------------
5. Country Selection
--------------------
To change the country setting, follow these steps:
a) Click " Start & gt; Settings & gt; Control Panel & gt; Modem Settings " .
b) Select the required country from the list.
c) Click " Ok " .
or
a) Using a terminal program (such as Hyper Terminal), issue
an AT+GCI command to select the desired country.
For information about the usage of AT+GCI commands, refer to an
updated version of the AT-Commands manual, available on Smart Link
web site (www.smlink.com).
To verify the change has taken effect:
a) Open HyperTerminal and select your modem
b) Type " ATI7 "
c) Verify that the correct country name is displayed
-----------------------
6. Call Progress Sounds
-----------------------
PCI and Riser card modems hardware typically support four methods
for monitoring call progress (dialtone, DTMF dialing, etc...).
SmartRiser565 modem supports only method (b).
The method you should use depends on your specific hardware:
(a) In hardware through AC-Link:
* Simply connect speakers to the AC97 audio speaker output
* Then enable and unmute " Telephone " or " Phone in "
in the Playback audio mixer from the speaker icon
that appears in the mixer tray
(b) In software through the audio subsystem:
* Simply connect speakers to the audio card speaker output.
* Next, click the right mouse button on SLLights in the
Windows System Tray while the modem is loaded in memory.
* Select the speakers on or off as desired.
(c) In hardware directly through the sound card:
* Connect the 4 pin header on the modem card to the TAM
header on the audio card/subsytem.
(d) In hardware using the optional buzzer that may be present on the
modem card:
* Nothing needs to be done to hear this. It is always on.
You can control the buzzer volume from the
Control Panel/Modem/Properties/Speaker Volume.
---------------
7. Known issues
---------------
7.1 On certain motherboards, call progress can be heard through
the system's speakers. This option is enabled by default, and can
be controlled only from Windows' " Volume Control " application,
using the " Telephony " slider. The 'Speaker' menu option (accessed
by right-clicking on the modem icon) can not mute the modem sound
on these motherboards.
7.2 The minimum RAM required for this modem under Windows 2000
is 64 MB. Under Windows XP the minimum RAM is 128MB.
Using a lower amount of RAM may lead to system instability.
7.3 When some systems get into " sleep mode " and an incoming call
is received by the modem, the modem answers but the screen stays
blank. This behavior is dependent on the BIOS and not on the modem.
Some BIOS vendors choose to let the modem answer, but leave the
screen blank.
7.4 Two Smart Link modems can not be installed on the same PC
simultaneously. Currently there is no workaround.
7.5 Specifically on NVidia MCP chipset: when on-board audio is
disabled from BIOS, the modem is also disabled. This is by chipset
design. Workaround: disable audio from Device Manager (relates to riser modems only)
------------------
8. Troubleshooting
------------------
If your modem does not work as expected:
8.1 If ERROR, NO DIALTONE or a similar message is received:
(a) Check whether the line is connected preperly to the modem.
(b) Use a telephone handset to make sure that the line is
active and that there is a dial tone.
(c) Check to see if the line is a PBX line or a direct analog
phone line. You may need to dial 9, before the actual
desired telephone number (i.e. ATDT9,123-4567).
If, after dialing 9, the modem still cannot detect the
PBX dialtone, try typing ATX3 before dialing.
NOTE that PBX lines typically can only support V.34
rates (33,600 bps, 28,800 bps, ...) and NOT V.90
rates (49,333 bps, 50,666 bps, ...).
8.2 If dialer application (i.e. Hyperterminal) does not detect modem:
Check whether HyperTerminal is configured to the right port.
You can find the modem's COM port number in
" Control Panel & gt; Modems & gt; Properties " .
If not, press disconnect and change the port that the dialer
is accessing.
8.3 If you cannot hear the dialtone and DTMF dialing while the modem
should be dialing out:
Riser card modems hardware designs typically support four
methods for monitoring call progress (dialtone, DTMF dialing,
etc...):
- In hardware through AC-Link.
* Simply connect speakers to the AC97 audio speaker
output.
* Then enable and unmute " Telephone " or " Phone in "
in the Playback audio mixer from the speaker icon in
the mixer tray.
- In software through the audio subsystem.
* Simply connect speakers to the audio card speaker
output.
* Next, click the right mouse button on SLLights in the
Windows System Tray while the modem is loaded in
memory.
* Select the speakers on or off as desired.
- In hardware directly through the sound card.
* Connect the 4 pin header on the modem card to the
TAM header on the audio card/subsytem.
- In hardware using the optional buzzer that may be
present on the modem card.
* Nothing needs to be done to hear this. It is always
on. You can control the buzzer volume from the
Control Panel/Modem/Properties/Speaker Volume.
Note: SmartRiser565 modems support only the second method.
8.4 If the Modem has connection problem try the followings:
(a) Enable " Safe Mode 1 " from Start-- & gt; Setting-- & gt; Control Panel-- & gt;
Modem Settings-- & gt; Modem Helper tab.
(b) Download a new driver from: www.smlink.com.
(C) Try to dial to the Internet with " Quick Connect " disabled.
Go to Start-- & gt; Setting-- & gt; Control Panel-- & gt; V.92 Settings-- & gt;
V.92 Features tab.
8.5 If SmartRiser565 modem device is not detected during installation,
then make sure that MS UAA High-Definition Audio bus driver is installed.
(refer to section 1 - Quick Start).
8.6 If you encounter problems during installation of SmartRiser565 modem on
Intel ICH6 platform which supports dual mode Azalia and AC-Link
(for example you get an error message saying the driver is not suitable
for the modem device), then check that BIOS is configured properly to
Azalia (for specific instructions how to check your BIOS settings,
refer to your motherboard manual).
--------------------
9. Disclaimers
--------------------
The following are important disclaimers as related to our products.
Proper use of our chipsets and drivers are clearly described.
Smart Link does not guarantee product performance or accept any
liability due to the improper usage of its drivers or chipsets.
* Modem is capable of receiving data up to 56Kbps. Actual send and
receive speeds may vary depending upon factors, such as connecting
modem and phone line connections.
* Modem must use the appropriate US or International chipset version
for the country to which it is shipped.
* Modem must use the appropriate driver version for the operating
system in which it is being installed.
* All trademarks are property of their respective owners.
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
VIA Machine INF Software User Guide
PatrickChen
Allanchen
34
457
2004-02-23T03:17:00Z
2004-09-13T02:18:00Z
1
1746
9958
VIA
82
23
11681
10.2625
90
Clean
Clean
0
2
MicrosoftInternetExplorer4
st1\:*{behavior:url(#ieooui) }
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:ªí®æ¤º¤å;
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent: " " ;
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family: " Times New Roman " ;
mso-fareast-font-family: " Times New Roman " ;}
VIA Machine INF Software User Guide
Updated: 2004.2.23
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Introduction
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
System
Requirements
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Multilingual
Support
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Distribution Package Contents
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Installation
and Remove
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows
UI mode
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Silent
Mode
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Package
Version Identify
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Verifying Installation of Driver
Introduction
& nbsp;
The user guide intends to show how to install VIA
MACHINE INF package and why we need install it.
This setup package is using U-setup package
developed by VIA Technologies that have the following features for your
convenience.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
One setup, all system components
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
The setup packages could carry
tens software components that your system required.
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
The setup package only needs to
reboot once for all components if it is necessary.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
No more nightmare on downloading
multilingual package
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
The package default provide
multilingual user interface for over 30 languages.
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
The package support
international user interface but have small package size. This technology only
needs 7% file size to provide over 30 languages.
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
The setup will present the
language of your system automatically.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Smart suggestion for component
update
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
The setup will detect the
present component in this system and compare them with the executed package.
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
If the executed package carries
the newer component than this system, then it will suggest you to install it.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Clicking, chose components
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
For an advanced user on computer
management, now you could have the whole control for installed components. The
user interface provides you to select the desired components to be installed or
removed.
& nbsp;
About the function of VIA MACHINE INF package, I
list below:
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Installing NB driver which the
hardware ID of NB still not check-in to OS.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Installing AGP driver which the
hardware ID of AGP still not check-in to OS.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Installing SB driver which the
hardware ID of SB still not check-in to OS.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Installing VPX driver which the
hardware ID of VPX still not check-in to OS.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Installing special drivers on
our new chip.
& nbsp;
Back to top
System Requirements
& nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Hardware
This package
should be installed on the system with VIA North Bridge and south
bridge chipset. The setup program will not support to be installed on other
vendor chipsets.
& nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Software
This software
package only supports Microsoft Windows & copy; Platforms. The setup program will
detect the current platform and install proper driver on your system. The
supported platforms are list below:
& nbsp;
Windows
95, 98 and Millennium Platforms
Windows 95 & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; 4.00.950
and above
Windows 98 & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; 4.10.1998
and above
Windows
Millennium & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; RTM
& nbsp;
Windows NT
32-bits Platforms
Windows 2000 & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; RTM
and above
Windows XP & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; RTM
and above
Windows
Server 2003 & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; RTM
and above
& nbsp;
Windows NT
64-bits Platform
None
Back to top
Multilingual Supports
& nbsp;
The default-supported language in this package is in English.
If the executed Windows OS is in an un-supported language to this
package, the user interface will be & nbsp;represented in English.
& nbsp;
This setup package support & nbsp;34 languages as
& nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
East
Chinese( Simplified), & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Chinese
(Traditional), & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Indonesian,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Japanese,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Korean,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Russian,
Thai, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Turkish. & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
West
& nbsp; & nbsp; & nbsp;Basque, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Bulgarian,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Catalan,
Croatian,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Czech,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Danish,
Dutch, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; English,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Finish,
French( Canada ), & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; French(France), & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; German,
Greek, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Hungarian,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Italian,
Norwegian,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Polish,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Portuguese( Brazi ),
Portuguese( Portugal ),
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Romanian, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Serbian,
Slovak,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Slovenian,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Spanish,
Swedish.
& nbsp; All the language
sequence is arranged as alphabetical.
Back to top
Distribution Package
Contents
& nbsp;
In this section, we show the detail file
list of ZIP-compressed package in which include setup and driver files.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Setup files
0X0409.INI,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; INSTMSIA.EXE,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; INSTMSIW.EXE,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; ISSCRIPT.MSI,
License.rtf,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; PCIENUM.SYS,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; README.TXT,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; SETUP.EXE,
Setup.ini,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; SETUP.ISS,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; SETUP.MLF,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; SETUP.SCF,
viasetup.dll,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; VIASetup.msi
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Component
n & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
VIAMACH
VIAMACH \INFDrv.dll, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; VIAMACH \INFDrv9x.dll, & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; VIAMACH \Kompnt.cif
u & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Driver files: VIAMACH\DRIVER\
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows Server 2003
SERVER2003\viamach.cat,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; SERVER2003\VIAMACH.INF
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows XP
WINXP\viamach.cat,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; WINXP\VIAMACH.INF
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows 2000
WIN2000\viamach.cat,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; WIN2000\VIAMACH.INF
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows Millennium
WINME\viamach.cat,
& nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; WINME\VIAMACH.INF
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows 98SE
WIN98SE\VIAMACH.INF
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows 98
WIN98\VIAMACH.INF
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows 95
WIN95\VIAMACH.INF
Back to top
Installation and Remove
& nbsp;
There are two operation modes, Windows
UI and command line, to execute installation and remove. The most popular is
the Windows UI mode that provides convenient user interface and systematic
operation. The command line mode, also called as silent mode, need user append
more parameters behind SETUP.EXE as answer to make the setup program silence
without pop any dialogs.
There are possible two types setup
package you may have. One is compressed as a zip file includes visible setup
and driver files. Another one is made as a self-extracted-execution file. In
the following, we will show you the steps to complete driver installation and
remove with both package types.
& nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Windows UI mode
If the
downloaded file is ZIP-compressed format, please extract it to proper location
in your hard disk first. Then launch the SETUP.EXE by double-clicking.
Otherwise, you could double-click the self-extracted-execution file and wait
for few seconds for the self-extraction. The extracted file will be deleted
automatically after setup has been terminated.
& nbsp;
First time execution
If it is the
first time to execute the setup package, you will only have the choice of
installation.
Maintenance
After the
first time execution, you could have choice to make ¡§Update¡¨ and ¡§Remove¡¨. You
will see two options, ¡§Update¡¨ and ¡§Remove¡¨ in the first shown dialog. If you
are going to update the driver, please active the ¡§Update¡¨ radio button and
press next button to enter next steps. Else, if you are going to remove the
installed driver in your system, please active the ¡§Remove¡¨ radio button and
press next button to enter next steps.
& nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Silent mode
The silent
mode are usually applied to system maintainer for servicing hundreds systems
that won¡¦t have interactive user interface. They would execute the setup
through command line in console or batch file execution without closing any
popped dialog popped or pressing next buttons. In addition, the command line
parameters of these two types of downloaded file format get few differences.
& nbsp;
ZIP-Compressed Package
In this
type package, you could see a setup.exe in those extracted files. User could
append parameters behind setup.exe as command line in console.
The
present command line parameters are: -s and / z & quot;reboot ;remove ;kompnt:xx,yy,zz & quot;
& nbsp;
Parameter
Description
-s
It is a required command line parameter to enable
silent mode operation. If this parameter is missed, the setup
-z¡¨Param1;¡K; ParamN ¡¨
It passes predefined parameters to SETUP.EXE.
Each parameter, Param1;¡K ; ParamN ,
should be separated with semicolons.
The predefined sub-parameters are:
reboot
It causes Setup.exe
automatically to reboot after the silent mode operation completed.
remove
It is
a switch to cause Setup.exe to
remove components. If this parameter is absent, then SETUP.EXE will install
components.
kompnt:xx,yy,zz
It is
an optional parameter to assign specific component in this package to be
install/remove.
The xx ,yy,zz should be replaced with
component name in which is defined as same as the component folder name of
this package.
& nbsp;
Examples:
& nbsp;
Command line
Execution
setup.exe -s / z & quot;reboot & quot;
Silent install all component and reboot the
computer.
setup.exe -s / z & quot;reboot;remove & quot;
Silent uninstall all include component and reboot
the computer.
setup.exe -s
Silent install all included components but not
reboot the computer.
setup.exe -s / z & quot;remove & quot;
Silent uninstall all components but not reboot
the computer.
setup.exe -s / z & quot;kompnt:VIAMACH,VIAUDIO & quot;
Silent install VIAMACH and VIAUDIO components
only
setup.exe -s / z & quot;remove;kompnt:VIAMACH,VIAUDIO & quot;
Silent uninstall VIAMACH and VIAUDIO components
only
& nbsp;
Back to top
Self-Extracted-Execution Package
This
type is a single self-extracted-execution file. All necessary files are all
integrated together so that user does not need to extract it to specific folder
for operation. There is extra parameter to make the self-extracted shell to be
in silent mode.
The
present command line parameters are -s -a , -s and / z & quot;reboot ;remove ;kompnt:xx,yy,zz & quot;
& nbsp;
Parameter
Description
-s -a
It is a required command line parameter to make
the self-extracted shell program to be in silent mode. And it should be the
first parameter in command line.
-s
It is a required command line parameter to enable
silent mode operation. If this parameter is missed, the setup would not
executive in silent mode
-z¡¨Param1;¡K; ParamN ¡¨
It passes predefined parameters to SETUP.EXE.
Each parameter, Param1;¡K ; ParamN ,
should be separated with semicolons.
The predefined sub-parameters are:
reboot
It causes Setup.exe
automatically to reboot after the silent mode operation completed.
remove
It is
a switch to cause Setup.exe to
remove components. If this parameter is absent, then SETUP.EXE will install
components.
kompnt:xx,yy,zz
It is
an optional parameter to assign specific component in this package to be
install/remove.
The xx ,yy,zz should be replaced with
component name in which is defined as same as the component folder name of
this package.
& nbsp;
Examples:
& nbsp;
We assume
that you download a self-extracted-execution file named as IDE_MPD0001.exe.
Command line
Execution
VIAINFXXX.exe -s -a -s / z & quot;reboot & quot; & nbsp; & nbsp; & nbsp; & nbsp;
Silent install all component and reboot the
computer.
VIAINFXXX.exe -s -a -s / z & quot;reboot;remove & quot;
Silent uninstall all include component and reboot
the computer.
VIAINFXXX.exe -s -a -s
Silent install all included components but not
reboot the computer.
VIAINFXXX.exe -s -a -s / z & quot;remove & quot; & nbsp; & nbsp; & nbsp; & nbsp;
Silent uninstall all components but not reboot
the computer.
VIAINFXXX.exe -s -a -s / z & quot;kompnt:VIAMACH,VIAUDIO & quot;
Silent install VIAMACH and VIAUDIO components
only
VIAINFXXX.exe -s -a -s
/z & quot;remove;kompnt:VIAMACH,VIAUDIO & quot;
Silent uninstall VIAMACH and VIAUDIO components
only
& nbsp;
Back to top
Package Version Identify
& nbsp;
The setup program will display the released data
and version for this package.
There is specific version syntax for package
identification:
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Version field: X.YY
The X is
the major version of this package; and YY represents the minor version.
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
A, B, C¡K
It is
always appended after version field to represent the qualified by Windows
Hardware Qualification Lab. The A means the first package for the same driver
binary, B means the second released package for the same driver binary, and so
on.
Back to top
Verifying Installation of Driver
Please follow the steps to verify the
installed driver of VIA Machine INF:
1. & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Open & quot;Control Panel & quot; from & quot;Start Menu - & gt;
Settings & quot;.
2. & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Open & quot;System & quot; in & quot;Control Panel & quot; and select the
& quot;Device Manager & quot;.
3. & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; Select & quot;System & quot; and check if the & quot;VIA Standard Host Bridge & quot; & amp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
& quot;VIA CPU to AGP
Controller & quot; & amp; & quot;VIA Standard PCI to ISA Bridge & quot; & nbsp;
l & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; & nbsp;
Controller exists or
not.
4. & nbsp; & nbsp; & nbsp; & nbsp; & nbsp; If it is then your installation is successful.
& nbsp;
Back to top
Limitation
The package can¡¦t removed
& nbsp;
Back to top
& nbsp;
Realtek Semiconductor Corp. AC'97 Sound System Software ver:A3.76
Installation and Setup
Driver & Application Installation/Removal Procedure For Realtek AC'97 Codec:
=================================================================================
& lt; & lt; & lt; For Win2000/WinME/WinXP (WDM driver)/Win98 Gold(First Edition)/Win98SE & gt; & gt; & gt;
---------------------------------------
Setup Driver/Application at first time:
---------------------------------------
Step 1. Before installing the Realtek AC'97 Drivers & Applications, Press the
[Cancel] button if Windows detect the PCI Multimedia Audio device.
Step 2. Insert the " Realtek AC'97 Drivers & Applications " CD into the CD-ROM
drive and run the setup.exe program to finish the installation.
Step 3. Click on [Next/OK/Go] to continue the procedure. If the Windows popup
" Digital Signature Not Found " message, press [Yes] to continue the
installation.
Step 4. Finally, select to restart the system and press [Finish] to complete
the installation.
The system will reload the drivers and do some adjustments in the INF
file if so required.
----------------
Setup for Manual
----------------
1. Double-click the " System " icon to open the " System Properties " dialog from Control Panel .
2. Choose " Hardware " tab and click the " Device Manager " button .
3. Please right-click mouse on " MultiMedia Audio Controller " and choose the " Properties " menu item
to show the driver details.
4. Click the " Driver " tab and then click the " Update Driver... " button for update.
5. Please follow the instructions of the " Upgrade Device Driver Wizard " .
6. Choose " Search for a suitable driver for my device " and click the " Next " button.
7. Please specify the driver location/source and then click the " Next " button in this case,
" Specify a location " has been chosen.
8. If " Specify driver location " is chosen, the Wizard will ask for the path where the driver is located.
9. Click the " Next " button to install Audio Driver on " Driver Files Search Results " .
10. If the " Digital Signature Not Found " dialog is opened, click the " Yes " button to continue
the Installation.
11. After completing the above steps, the drier has been installed into the system.
Please click " Finish " button to complete the installation.
--------------------------
Update Driver/Application:
--------------------------
Step 1. Follow Step 2,3,4 described in [Setup at first time] above to complete
the procedure.
--------------------------
Remove Driver/Application:
--------------------------
Step 1. Go to Start\Settings\Control Panel.
Step 2. Select [Add/Remove Programs] icon.
Step 3. Select " Realtek AC'97 Audio " and press [Change/Remove]
button.
Step 4. Click on [Next/OK/Go] to finish the uninstallation.
Step 5. At the end of the procedure, select to restart the system and press
[Finish] to complete the uninstallation.
& lt; & lt; & lt; For WinNT 4.0 (NT4 driver) & gt; & gt; & gt;
---------------------------------------
Setup Driver/Application at first time:
---------------------------------------
Ignore Step 1, and follow the same procedure in Win2000/WinME/WinXP.
--------------------------
Update Driver/Application:
--------------------------
The same procedure in Win2000/WinME/WinXP.
--------------------------
Remove Driver/Application:
--------------------------
The same procedure in Win2000/WinME/WinXP.
& lt; & lt; Other Informations & gt; & gt;
--------------------
Silent Installation:
--------------------
Run " Setup -s -f2 & lt; path\LogFile & gt; "
i.e. setup -s -f2c:\mylog.log
Note: 1. AVRack only works fine under WinNT 4.0 after installing
Service Pick 3 or later.
2. Please update Directx version to DirectX8.0 or above.
---------------------
Version Informations:
---------------------
WDM driver for Win98/WinMe/Win2000/WinXP : 5.10.0.5900
WDM driver for Windows x64 : 5.10.0.5900
VXD driver for Win95 : 4.5.0.3019
VXD Software wavetable driver : 3.1.0.0
NT4 driver for Windows NT4 : 4.3.0.3040
NT4 software wavetable driver : 4.3.0.2002
RtlRack for Win98/Me/2000/XP : 1.10.0.0
AvRack for Win95/NT4 : 2003.4.4.1
Realtek Soundman : 5.1.0.43
Realtek Sound Effect Manager(CPL) : 2.2.0.48
Realtek Sound Effect Manager(RtlCpl) : 1.0.1.50
Realtek Sound Effect Manager for NT4 : 2.3.0.3
Driver/Application Setup Program : 5.16
--------
History:
--------
A3.76 -
1. For special customize settings.
2. Fix pop noise for ATI chipsets.
3. Fix recording noise when below 48K samplerate.
4. Fix C3 state issue for ATI chipsets.
5. For ALI 1689 chipsets can't record continue after power resume.
6. Make driver package to be 8.3 format.
7. Setup Package-Delete older inf file ( alcxwdm?.inf ) for updating driver.
8. Setup Package-General inf file name change to " Alcxau.inf " .
A3.75 -
1. For special customize settings.
2. Update Realtek 3D engine.
3. Support for the WMA Pro-over-S/PDIF Format.
4. Support DTS function for ALC850.
5. Fix ALI 1689 chipsets can't record continue after power resume.
6. Fixed driver package can't be removed on WinME.
A3.74 -
1. For special customize settings.
2. Fix SPDIF stream hang up by playing DVD.
A3.73a -
1. Driver general inf.
2. Setup package application size and progress backward problem .
3. Fixed driver package can't be removed on win98se .
4. HCT Scan on windows x64 os .
A3.73 -
1. For special customize settings.
2. Support codec ALC653.
3. Fix record from SPDIF IN have noise in hyper-thread mode.
A3.72 -
1. For special customize settings.
2. Modify initiate of DMA buffer allocate.
3. Fix abnormal THD+N performance on A-D test.
A3.71 -
1. For special customize settings.
2. Fix HCT 12.1 DRM test fail issue.
3. Fix playback and record could not been played in the same time issue for ATI and nVidia chipsets.
A3.70 -
1. Add some customized settings.
A3.69 -
1. Add some customized settings.
2. Add SPDIF IN pass throuth SPDIF Out item for some of ATI and nVidia chipsets.
3. Fix AC3 SPDIF blue screen issue when SPDIF-out force to 44K.
4. Change DMA Threshold from 06 to 10 to decrease noise for ATI SB400 chipset.
5. Update 3D engine to fix Half Life 2(Game) no sound issue and some noise issues.
A3.68 -
1. Add some customized settings.
2. Change DMA operation mode.
3. Fix SPDIF out issue for ALI1573 and ALI1689.
4. Fix SPDIF no output issue for digital and analog output mode in ALC658.
5. Fix SPDIF noise or no output issues in nVidia chipsets.
6. Fix audio can't be test in 3D Marks.
7. Fix UT2004 game noise issue.
A3.67 -
1. Add some customized settings.
2. SPDIF-out goes to AClink slot 6/9 for ATI SB400 when modem present.
3. Add New feature: Disable Analog CD.
4. Fix issue : mono-out volume synchronize with Master volume for ALC655 force 2 channel mode.
A3.66 -
1. Add some customized settings.
2. Enable Present ICH DMA hang up function in default.
3. Fix WarcraftIII game noise issue.
4. Add a new feature : Don't power taggle PR3 for ALC655 and ALC850.
5. Support swapping center Left function for nVidia CK804 chipset.
6. Support WHQL for nVidia CK804 chipset.
A3.65 -
1. Add some customized settings.
2. Fix SPDIF OUT no sound for ALC650 codec after power resume.
A3.64 -
1. Add some customized settings.
2. Update Realtek 3D engine.
3. Support AC3 SPDIF and 8 channels for nVidia CK804.
4. Fix EAPD issue after S1 or S3 resume.
5. Fix getposition not acceurate for ATI chipsets.
A3.63 -
1. Add some customized settings.
2. Fix underrun noise issue by changing threshold value for ATi chipset.
3. Fix 'Winbench' application issue in 4 channel mode when Sensaura engine is disabled.
A3.62 -
1. Add some customized settings.
2. Fix SPDIF Copy protect issue in Mediaplayer.
3. Support AC3 SPDIF and 8 channels for Ali1689 chipsets.
4. Reduce POP noise with EAPD for power change.
A3.61 -
1. Add some customized settings.
A3.60 -
1. Add some customized settings.
2. Add workaround code when pause DMA engine for ICH6 / Hance Rapid.
3. Fix bug for " Force 44K SPDIF " feature when disable direct sound acceleration engine.
4. Set Surr-out pin as HP-out pin for ALC655 when disable multi-channels function.
A3.59 -
1. Add some customized settings.
2. Add channel status information of SPDIF output for ATi chipset(SB150/SB200/SB250).
A3.58 -
1. Add some customized settings.
2. Fix some UI issues for Realtek control panel.
3. Fix some issues for ATi chipset(SB150/SB200/SB250).
4. Solve pop noise for noise suppression feature.
A3.57 -
1. Add some customized settings.
2. Fix some issues for the certain page of control panel.
A3.56 -
1. Add some customized settings.
2. Update directsound acceleration engine.
3. Fix the issue which control panel shows the improper item in
" Microphone " tab under some situation.
A3.55 -
1. Improve the algorithm of Jack sensing.
2. Add some customized settings.
3. Support ICH6.
4. Improve the algorithm for ALC250 Hardware EQ feature.
5. Fix the issue which AUX volume register will be set the improper value.
6. Improve the algorithm of Noise suppression feature.
7. Fix SPDIF output issue for " WaveCyclic " architecture.
A3.54 -
1. Add some customized settings.
2. Support Microphone Noise Suppression feature.
3. Toggle Vref before change Microphone jack type for AC97 2.3 codecs.
4. Modify Peak filter parameters for ALC655.
A3.53 -
1. Add some customized settings.
2. Add " Remove recording DC offset " feature.
3. Fix Hardware EQ noise issue for ALC250.
4. Support 1 nVidia chipset (CK8S).
5. Add workaround code for ATI chipset recording issue.
6. Support 8 channels playback feature for nVidia chipset with ALC850.
7. Fix the issue about SPDIF function type feature with ALC850.
8. Modify Peak Filter parameters for ALC655 and ALC850.
9. Fix side channel noise issue for VIA chipset with ALC850.
10.Add a new feature: SPDIF out can be sent to ACLink for ATI and nVidia Chipset.
11.Fix SPDIF slot assignment error for ALC850.
12.Support " Smart GPIO Volume Control " & " DC Voltage Volume Control " features for ALC250 and ALC203.
13.Turn on bit 14 of DC97_AUDIO_REG_INTERRUPT_ENABLE while audio playing for ATi chipset.
14.Add flexibility for " Preventing ICH hang up " feature.
15.Improve DirectMusic startup latency when HyperThreading was enabled.
16.Fix Pinball delay problem on Win2000.
17.This vesion does not include ALi 1535 chipset support.
A3.52 -
1. Add some customized settings.
2. Fix SPDIF output frequency issue for nVidia chipset.
3. Disable Hardware EQ first before restore Hardware EQ for ALC250 when resuem.
4. Disable Hardware EQ first before restore Hardware EQ for ALC250 polling function.
5. Turn on UAJ function for ALC850.
6. Set SPDIF control register to proper value when driver initialize.
7. Improve Read/Write codec register algorithm.
8. Reduce resume time.
9. Add " Remove Recording DC offset " feature.
10.Check ALC850 JD5 to decide if support 8-channels feature.
11.Fix SPDIF output slot assignment error for ALC850.
A3.51 -
1. Add ICH2, ICH3 and ATI Chipset IDs.
A3.50 -
1. Support ALC850.
2. Add some customized settings.
3. Use " Wave PCI " architecture for ATI chipset.
4. Improve Jack Sensing algorithm to eliminate noise.
5. Show " Real-Time SPDIF-in Monitor " node for nVidia chipset.
6. Remove ICH2/ICH3/ATi chipsets IDs.
7. Change JD bit definition of Front-out detection function for ALC658 (C version / D version).
8. Set " Direct DAC Mode " to Summation of DAC and analog inputs if H/w EQ is bypassed for ALC250.
A3.49 -
1. Modify some customize settings.
2. Fine tune some registers for ALC655 to avoid noise.
3. Fine tune Surround DAC Volume and Center/LFE DAC volume for ALC655.
4. Set ALC655 Vrefout as 4V for 1 customer.
5. Fix Intel audio device DMA hang up issue for some customers.
A3.48 -
1. Add some customize settings.
2. Turn on " Ignore SPDIF in Invalid Bit " option as default if codec support.
3. Set Pin 47 as EAPD pin and turn off SPDIF in function as default for ALC250 & ALC203.
4. Use " WaveCyclic " architecture under Windows 98 Gold version.
5. Modify Realtek control panel that don't detect UAJ automatically
while Windows start for some customer's request.
6. Fix the failures on HCT 9.6 (WinME) " KS Position Accuracy " test.
7. Fix the problems with SPDIF output through DirectSound.
8. Prevent potential discontinuities in 8-bit streams.
9. Prevent potential audio system hangs on badly behaved audio drivers.
A3.47 -
1. Add some customize settings.
2. Turn off SPDIF-In Schmitt Trigger Control for ALC655.
3. Fix the problem that AC3 stream will hang with the older revision of VIA8233 under Win98 SE.
4. Fix the problem that AC3 stream will be abnormal with Direct sound API.
5. Add hand-shaking protocol between audio driver and modem driver for ATI chipset.
6. Disable " Mic2 Select " node in mixer for ALC655/ALC658.
7. Fix the bugcheck D1 in HCT verifier for nVidia chipset.
A3.46 -
1. Add some customize settings.
2. Add Hardware EQ function for ALC250.
3. Support independent SPDIF engine for nVidia CK8 chipset.
4. Modify driver for UAJ function.
5. Modify UAJ thresholds for ALC658.
6. Fix audio driver bug for ATI chipset.
7. Fix audio driver bug about nVidia independent SPDIF engine.
8. Change direct sound acceleration engine.(New engine require DirectX 8.1 under Windows 98 SE).
A3.45 -
1. Add some customize settings.
2. Reduce resume time for VIA chipset.
3. Modify mixer volume control algorithm for multi-channels codec to prevent
the value of mixer out of range.
4. Implement ATI dedicate SPDIF DMA engine.
5. Support ALC250 and ALC658.
6. Fix the problem that Jack Sensing will hang in Windows 98SE.
7. Fix ICH5 pause DMA issue.
A3.44 -
1. Support independent SPDIF engine for nVidia MCP2 chipset under Windows 98 SE.
2. Improve the initialize procedure and the DMA access algorithm for VIA chipsets.
3. Add some customize settings.
4. Apply the Channel Order and FIFO Flush procedure for ATI A41 chipset.
A3.43 -
1. Support ALC203 UAJ function.
2. Add some customize settings.
3. Support independent SPDIF engine for VIA 8233 (Only for newer chipset version) under Windows 98 SE.
4. Fix hang up issue when system suspend for Ali 1563 chipset.
5. Fully support Jack sensing function with multiple language.
6. Fix Jack sensing problem with DirectX 6.1.
A3.42 -
1. Support ALC655.
2. Modify driver for some customized settings.
3. Add SPDIF function for nVidia chipsets.
4. Zero recording data when recording gain is muted.
5. Support independent SPDIF engine for VIA 8233 (Only for newer chipset version).
A3.41 -
1. Modify driver for some customized settings.
2. Support ATI SB200 south bridge.
3. Support Intel ICH5 south bridge.
A3.40 -
1. The setting of switching Center/LFE is saved before system is shut down, restored after system boot up.
2. Fix click noise generated by playing short time wave.
3. Fix some problem about AC3 stream for VIA chipset.
4. Add some customize settings.
A3.38 -
1. Fix some problem for Ali 1563 chipset.
2. Set 1 timer to check SPDIF in status for ALC650 ver. F
3. Save playback volume value to registry key when the mixer is adjusted.
4. Combine Cyclic WDM driver and PCI WDM driver.
A3.37 -
1. Update DirectSound 3D Positional Audio Engine to fix some noisy problem for
some DirectSound3D game (like Unreal Tournament 2003).
2. A3D compatible
3. Correct the gain settings of master volume for ALC650 ver.F
A3.36 -
1. Restore AC97REG_EXT_AUDIO_CTRL value first when resuming from suspend.
Otherwise, Sample rate can't be restored because VRA was not enabled.
2. Support 6-bits capability for Master Volume control if hardware support it.
3. Also set GPIO for Jack Sharing with ALC650 ver.E excecpt some special models.
4. Add 1 customized settings " Disable3DDepthLine " to disable 3D Depth mixer Line.
A3.35 -
1. change company name from " Avance " to " Realtek " .
2. add some new ID of motherboard
3. change some default settings for specific models
A3.32 -
1. compensate the gain for 3D sound when 2 speaker mode was selected.
2. support memory I/O for ICH4/ICH5 chipset
3. support SPDIF AC-3 playback using DirectSound API for ICH4/SiS chipset
4. correct DataRange declaration of S/PDIF pin to avoid blue screen on Win2000
with DirectX 8.1 installed.
A3.30 -
1. turn on/off EAPD by GPIO for specific model
2. correct EAX initial setting.
3. support I3DL2 interface
4. fix wake on ring problem
5. support DirectSound 3D positional audio by using HRTF algorithm
6. Add " Loudness " control for ALC202/ALC202A.
A3.29 -
1. Add " S/PDIF IN/OUT Pass-Through " mode for specific model
2. fix S/PDIF-In Realtime monitor noise issue
3. fully support EAX compatible sound effect
4. fix S1 suspend/resume failure problem for some specific model using SiS audio controller
5. only disable " 3D depth " line for specific model
6. duplicate analog input source according to output channel mode
7. support DirectSound hardware acceleration features by default
8. fix WinDVD problem when enabling video acceleration
A3.26 -
1. Improve compatibility with Agere software modem
2. Improve recording quality when IDE was in PIO mode.
3. Remove 3D Depth mixer line for some models
A3.23 -
1. Add " Loudness " mixer control for ALC650 front channel.
2. Add " SPDIF in pass through to SPDIF output " option for specific model.
3. Remove 3D depth mixer line.
4. Improve compatibility with WinDVD 4.0 playing AC3 bit stream through DirectSound API.
5. Improve recording quality for some specific models.
A3.22 -
1. Support S/PDIF-In function for ALC650 ver.E
A3.21 -
1. Fix Front Mic problem.
2. Turn off " Analog input bypass to surround " when enter D1 mode.
3. Change back the default volume of Master to the middle position.
4. Add " EnableDCVoltageControl " customized option for ALC202/ALC202A.
5. Support customized DirectSound 2D/3D Acceleration (bypass kmixer).
Add " EnableDS3DLibrary " customized option to enble it.
It is turned off by default.
6. Add " PreventRegisterReset " customized option for VIA8233.
7. Only ALC201 series and ALC650 series can use " Enable 3.3V support " customized option.
For ALC202/A, it is work autometically.
8. Reset DMA when change state to Pause for ICH4 to fix HCT DiectSound failure in WinMe.
A3.13 -
1. To avoid mapping lost on Win98SE by raising IRQ level and adding TagCount before get mappings.
2. Disable " Phone Line " for some specific models.
3. Improve S/W SRC (if needed) quality to meet PC99 requirement.
4. Mute SPDIF while master volume was muted.
5. Improve EAX 1.0 compatible issue.
A2.94 -
1. Modify mixer control for multichannel output - master/front/surround/center/subwoofer line.
a.The master volume/mute control will adjust all of front/surround/center/subwoofer
volume/mute now to avoid confusion.
b.The independent front/surround/center/subwoofer line offer volume control to balance the
multichannel output.
2. Support " Front Mic " instead of Mic2.
3. Support Center and LFE output swap function.
4. Turn off analog input pass to surround function when suspend.
5. To avoid mapping lost on Win98SE (it can also fixed by QFE).
6. Improve S/W SRC (if needed) quality to meet PC99 requirement.
7. Mute SPDIF while master volume was muted.
A2.84 -
1. Support ALC650.
A2.82 -
1. Support ICH4
2. Implement workaround for Intel 440MX audio controller
3. Set analog CD Maximum volume to 12dB.
A2.81 -
A2.80 -
1. Remove " SPDIF SRC " Node if turn on " Enable 48K SPDIF " option.
2. Turn on " Saving LED power " feature for G version
3. Save/Restore AC97 extended registers when Suspend/Resume
4. Modify Servie() function for set SPDIF Invalid bit.
5. Modify data 0 insertion method for SPDIF.
6. Fix C3/C4 issue.
A2.73 -
1. Support ALC202A.
A2.71 -
A2.70 -
1.set CD Maximum volume to +12dB.
A2.62 -
A2.61 -
A2.60 -
1. Fix 48KHz if SPDIF SRC was enabled.
2. Fix NT4 driver for IRQ sharing on VIA8233A
A2.58 -
1. Support ALC101.
A2.56 -
A2.55 -
1. update VXD driver for VIA8233A.
A2.53 -
A2.52 -
1. Support VIA8233A audio controller.
2. Eliminate the PCM noise while playing AC-3 stream through SPDIF-out.
3. Power down EAPD when master volume mute.
4. Fix HCT full duplex unstable problem for VIA8233 audio controller.
5. The driver now support only VID/DID/SVID/SSID entry for WHQL requirement
A2.51 -
A2.50 -
1. Fix HCT ACPI stress device I/O test for VIA8233.
2. Improve compatibility with software modem for power management.
A2.48 -
1. The driver now support the VID/DID entry
A2.46 -
1. Add customized options.
2. Mute volume when volume slider was adjusted to the bottom.
A2.45 -
1. Support ALC201A.
2. The driver only support the VID/DID/SVID/SID entry to meet the
INF requirement for PCI devices for WHQL logo.
A2.43 -
1. Add SPDIF Mute control and SPDIF SRC On/Off control.
2. Modify 3D depth control behavior.
When the slider was adjusted to the bottom,
the 3D depth will be turned off.
3. Sound Effect Control Panel now installed by setup program.
It will not be installed with INF file.
4. AvRack support CD track auto-load function.
A2.42 -
1. Add Mic2 select control
2. Improve MR card compatibility
3. Change volume default settings
A2.40 -
1. Enable ALC201 3.3V function (INF optional)
2. Auto Power down DAC/ADC (INF optional)
3. Avoid scandisk problem on some machines
4. Fix HCT system test for VIA 686 (ACPI / Stress Device I/O)
5. Change version number to 5.10.00.xxxx for WinXP versioning requirement
6. Save/Restore recording mux setting
7. Improve compatibility with PCTel MR card
8. Fix hang problem while burn-in PowerDVD on some machines.
9. Fix IBM ViaVoice Mixer problem.
10. Add MIC 20dB Boost control on recording MIC source line
11. Add Subsystem IDs