Creative CT4180 Getting Started Guide - Page 27

The CONFIG.SYS File Settings, Running DIAGNOSE with the /W=C:\WINDOWS parameter - drivers

Get Creative CT4180 - Sound Blaster 16 ViBRA Card PDF manuals and user guides View all Creative CT4180 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

u Running DIAGNOSE with the /S parameter updates the BLASTER environment with the resource settings from the PnP configuration manager. u Running DIAGNOSE with the /W=C:\WINDOWS parameter updates the SYSTEM.INI file in the Windows directory with the resource settings from the PnP configuration manager. For a description of the AWEUTIL utility, refer to the AWEUTIL.TXT file found in the audio software directory. The CONFIG.SYS File Settings If you install the low-level DOS device drivers under custom installation, the installation program adds the following statements to the CONFIG.SYS file: DEVICE= C:\SB16\DRV\CTSB16.SYS /UNIT=0 /BLASTER=A:220 I:5 D:1 H:5 DEVICE= C:\SB16\DRV\CTMMSYS.SYS The directory name SB16 may be VIBRA16 and the driver name CTSB16.SYS may be VIBRA16.SYS in your installation. CTSB16.SYS (or VIBRA16.SYS) and CTMMSYS.SYS are low-level device drivers that provide wave playback and recording for DOS applications, including third-party DOS applications developed using drivers (such as CTWDSK.DRV, CTWMEM.DRV, CTVDSK.DRV, and CT-VOICE.DRV) that require these low-level drivers. The drivers are found in the DRV subdirectory of your audio software directory. See "Optimizing Memory Usage" on page 3-2 to learn how to optimize your memory. To free system memory when you are using Windows applications or playing DOS games, use a text editor to delete or comment out the preceding two statements from the CONFIG.SYS file. If you later need the low-level device drivers for your software application, load them into memory by typing DIAGNOSE /A at the DOS prompt and pressing . This command adds the required statements to the CONFIG.SYS file. Understanding the Installation A-7

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
Understanding the Installation
A-7
Running DIAGNOSE with the /S parameter updates the
BLASTER environment with the resource settings from the
PnP configuration manager.
Running DIAGNOSE with the /W=C:\WINDOWS parameter
updates the SYSTEM.INI file in the Windows directory with
the resource settings from the PnP configuration manager.
For a description of the AWEUTIL utility, refer to the
AWEUTIL.TXT file found in the audio software directory.
The CONFIG.SYS File Settings
If you install the low-level DOS device drivers under custom
installation, the installation program adds the following statements to
the CONFIG.SYS file:
DEVICE=C:\SB16\DRV\CTSB16.SYS /UNIT=0
/BLASTER=A:220 I:5 D:1 H:5
DEVICE=C:\SB16\DRV\CTMMSYS.SYS
The directory name SB16 may be VIBRA16 and the driver
name CTSB16.SYS may be VIBRA16.SYS in your
installation.
CTSB16.SYS
(or VIBRA16.SYS) and CTMMSYS.SYS are
low-level device drivers that provide wave playback and recording for
DOS applications, including third-party DOS applications developed
using drivers (such as CTWDSK.DRV, CTWMEM.DRV,
CTVDSK.DRV, and CT-VOICE.DRV) that require these low-level
drivers.
The drivers are found in the DRV subdirectory of your audio
software directory.
See “Optimizing Memory Usage” on page 3-2 to learn how to
optimize your memory.
To free system memory when you are using Windows applications or
playing DOS games, use a text editor to delete or comment out the
preceding two statements from the CONFIG.SYS file.
If you later need the low-level device drivers for your software
application, load them into memory by typing
DIAGNOSE /A
at the
DOS prompt and pressing <Enter>.
This command adds the required
statements to the CONFIG.SYS file.