Installing a Sound Card and Software

Installing a Sound Card and Software

eventually, do permanent damage to the mentor. Also, setting floppy disks on top of unshielded speakers can damage the data on the disks.

MPC3 Specifications for Sound Cards

The MPC3 specifications for sound are listed below: They address all three of the stages of processing sound just discussed. The sound card must:

  • Support MIDI technology
  • Provide for either 8- or 6-bit DAC samples with PCM encoding
  • Use CODEC samples at a rate of 8.0, 11.025,16.0,22.05, and 44.1kHz with stereo channels
  • Buffer sound data from ISA to PCI by DMA transfers
  • Provide internal wavetable synthesizers capability with 16 simultaneous melody voices and six simultaneous percussive voices
  • Provide the direct audio output from the CD-ROM drive to the sound card, bypassing the CPU with volume control that can be manipulated through either hardware or software.

 

Installing a Sound Card and Software

Installing a Sound Card and Software

Most sound cards come with a device driver as well as all the software needed for normal use such as application software to play music CDs. The installation of a sample sounds and is described below. The sample card used is the Creative Lab’s Sound Blaster PCI128. It is Plug and Play and MPC3 compliant, uses a PCI slot, and supports a 128-voice wavetable. It will work under DOS 6+, Windows 95, Windows 98, or Windows NT. The card comes with drivers and software on a CD-ROM and a user’s guide.

Virtual DOS Machine

Remember that a virtual DOS machine isolates an application from the rest of the system by providing the entire DOS-like environment to the application. Because a common challenge that arises when a system is running Windows NT is having to run 16-

on the PDC is updated, copies are written to each BDC, which is called replication or automation duplication. BDCs use their copy of the SAM database to authenticate users as they log on, thereby relieving the PDC of the burden of authentication function. This sharing of functions improves performance in domains with many (more than 1000) workstations. Workstations on the domain are in the lower part. A Windows NT network can contain these Oss functioning in these ways Windows NT Server functioning as a PDC, a BDC, or as a stand-alone server (a server on the network that has no domain controller functions); Windows NT Workstation functioning as a workstation or as a standalone server, and Windows 9x.

User Accounts

User accounts are used on PCs to control who has access to what programs, files, and other resources on a PC or network. When using DOS and Windows 9x, the only all-encompassing security is a power-on password, which is a function of the ROM BIOS rather than the OS. Windows NT, however, provides an all-encompassing security feature to the PC. In order for a user to gain access to a computer, the user must have a user account on that computer, which is a workgroup, must be set up on each computer, or, in a domain, can be set up from the centralized domain sever. During the Windows NT installation, an administrator account is always created. An administrator has rights and permission for all computer software and hardware resources.

When Windows NT first boots, someone must log on before the OD can be used. The logon screen is displayed when you press the Ctrl, Alt, and Del keys together. (Remember that these keystrokes in the DOS and Windows 9x environment are used to soft boot). To log on, enter a username and password and click Ok. Windows NT tracks which user is logged on to the system and grants rights and permissions according to the user’s group or to specific permissions granted this user by the administrator.

Administering a Network Besidesacess to the network, permissions granted to a user, and the OS environment that the user has are also controlled by the administrator. An administrator can create user groups and assign restrictions and rights to the entire group that applies to all users. Or, an administrator can assign individual restrictions and rights to a single user. A user profile is a special file with a .usr file extension that contains information about the desktop configuration, sound, color, and resources that should be

a program, and the utility will examine your system to determine if all hardware present qualifies for NT. Use the following directions to use the NT Hardware Qualifier.

  1. Insert a bootable disk in drive A.
  2. From Windows, 9x Explorer or Windows 3.x File Manager, access the Windows NT CD-ROM and execute the program. \Support\Hqtool\MakeDisk.bat. Windows NT will then create the Hardware Qualifier disk.
  3. Boot from the newly created disk. The following message will be displayed on your screen:

Preparing the NTHQ

You can watch as NT tells you it is creating a RAM drive and copying files to it. Next a screen will appear informing you that the report the utility generates will take several minutes and will be written to the disk and saved as Nthq.txt.

  1. Print the report.

Below contain a portion of a sample report from the NTHQ. Note that the two devices listed at the top were not found in the NTHQ. To determine if these devices will work with Windows NT, check the latest HCL on the Microsoft Website or contact the manufacturer of each device.

Adapter description: CIRUS LOGIN PnP v34 MODEM

Adapter Device ID:   CIR1000

Listed in Hardware Compatibility List: Not found-check the latest HCL

 

Adapter Description:            OPL3-SAX Sound Board

Adapter Device ID:    YMH0024

Listed in Hardware Compatibility List: Not found-check the latest HCL

 

Adapter Description: S3 Inc. 801/928/964

Listed in Hardware Compatibility List: Yes

Leave a Reply

Your email address will not be published. Required fields are marked *

css.php