Chip 1997 April (Special)

home *** CD-ROM | disk | FTP | other *** search

/ Chip 1997 April (Special) / Chip-Special_1997-04_cd.bin / panasoni / 720pcm32 / 720pcm32.exe / README.TXT < prev next >

Wrap

Text File | 1995-07-05 | 39.4 KB | 861 lines

This README file contains the following helpful and useful information. 1. ASPI Manager 2. CD-ROM Device Driver 3. MSCDEX.EXE 4. Error Messages when installing software 5. Sample CONFIG.SYS Files 6. I/O Base Address 7. Supplement and Troubleshooting Guide 1. ASPI Manager The following table lists the ASPI(Advanced SCSI Programming Interface) managers available with this PC card. ┌───────────────┬─────────────────────────────────────────────────────────┐ │ ASPIMNGR.SYS │ For when your computer has both Card Service and │ │ │ Socket Service. │ ├───────────────┼─────────────────────────────────────────────────────────┤ │ ASPIDBK.SYS │ For when your computer has only DataBook CardTalk. │ ├───────────────┼─────────────────────────────────────────────────────────┤ │ ASPI365.SYS │ For when your computer has neither Card Service nor │ │ │ Socket Service. This Driver directly controls the PCMCIA│ │ │ controller chip(Intel i82365 100% compatible LSI). │ └───────────────┴─────────────────────────────────────────────────────────┘ 1-1. Command Line Options DEVICE = <path>\ASPIMNGR.SYS [/port=<I/O base address>] [/socket=<slot No.>] [/int=<IRQ level>] DEVICE = <path>\ASPIDBK.SYS [/port=<I/O base address>] [/socket=<slot No.>] [/mem=<base address>] DEVICE = <path>\ASPI365.SYS [/port=<I/O base address>] [/socket=<slot No.>] [/mem=<base address>] /port=XXX Since the I/O port is needed for the PC card, add this line and specify the base address at XXX using a hexadecimal number. The PC card occupies 32 bytes of space starting with the specified base address. The factory setting is 300h. If the specified address is already being used, specify another base address from the following addresses. Also, depending on the computer, the I/O port may need to be specified in the Card Manager (ASPIMNGR.SYS, ASPIDBK.SYS). Refer to your computer manual. 240 280 2A0 2C0 300 320 340 380 (240h is not available in ASPIDBK.SYS) /socket=X When you are using a personal computer with more than two PCMCIA card slots, add this line and specify the slot at X meaning the slot you will insert the PC card in. If you specify 0 or you don't specify the slot, the installation program searches all slots, and uses the first slot available. Option effective with ASPIMNGR.SYS only /int=X This option sets the IRQ level of the PC card using a hexadecimal number. The valid numbers are 0 through F. The ASPIMNGR.SYS itself does not need interruption request, although some kinds of Card Services need this option to assign the IRQ level used in the Card Configuration process. (Compaq contura aero 4/33c : proved at present) Make sure this number does not conflict with another device. The IRQ level is not set without this option. If you're using the SystemSoft Card Service, choose a number from the "IRQ=" entries in the CSALLOC.INI file. Option effective with ASPIDBK and ASPI365 only /mem=XXXX Add this line and specify the memory space's base address to read the card information by the segment address (hexadecimal number). You need to exclude this specified address a in the EMS "X" option so that it will not overlap the region of EMS.If you don't specify the base address, CE00 is applied, and 8 KB of memory from CE000 to CFFFF is used. 1-2. Messages (1) ASPIMNGR.SYS The following message will appear. ┌─────────────────────────────────────────────────────────────────────────────┐ │ KME PC Card Driver Ver. 1.0 (94XXXX) │ │ for IBM Card Services 1.0.7 / 2.0.0 │ │ for SystemSoft Card Services 2.0.1 / 2.1.0 │ │ for Phoenix Card Services 2.0.0 / 2.0.1 / 2.1.0 │ │ (C) Copyright 1994 RATOC System Inc. All Rights Reserved. │ │ (C) COPYRIGHT 1994 KYUSHU MATSUSHITA ELECTRIC CO., LTD. All Rights Reserved.│ │ IObase = 0x 300, Socket = 0 │ └─────────────────────────────────────────────────────────────────────────────┘ ERROR MESSAGES: ┌──────────────────────────────────────┐ │ Card Services Program Not Loaded. │ │ Driver Unloaded. │ └──────────────────────────────────────┘ Possible Cause: The ASPIMNGR.SYS couldn't start because the Card Service program did not load. Solution: ∙ Reinstall the Card Service Program supplied with your computer. If your computer did not come with a Card Service program, a program is supplied with this player that will operate your CD-ROM. ∙ Confirm the description in the CONFIG.SYS. Check the CONFIG.SYS to make sure that the ASPIMNGR.SYS is located after the Card Service. If not, please edit. ∙ Edit the CONFIG.SYS to change the value of "X" at EMM386.EXE (EMS driver). ┌──────────────────────────────────────┐ │ Unable to get I/O Window. │ └──────────────────────────────────────┘ Possible Cause: I/O window which is specified at "/port=" is already being used. Solution: Edit the CONFIG.SYS to change the I/O base address which was specified at "/port=" option. Refer to 1-1 "/port" option or "Options for ASPI Manager" of the Operating Instructions. Then, restart your computer. ┌──────────────────────────────────────┐ │ Unable to get IRQ Vector. │ └──────────────────────────────────────┘ Possible Cause: The IRQ vector which is specified at default is already being used. Solution: Edit the CONFIG.SYS. Add "/int=" option and specify a suitable IRQ number. If you're using the SystemSoft Card Service, choose a number from the "IRQ=" entries in the CSALLOC.INI file. (2) ASPIDBK.SYS The following message will appear. ┌─────────────────────────────────────────────────────────────────────────────┐ │ KME PC Card Driver Ver. 1.0 (94XXXX) │ │ for DataBook CardTalk Socket Services │ │ (C) Copyright 1994 RATOC System Inc. All Rights Reserved. │ │ (C) COPYRIGHT 1994 KYUSHU MATSUSHITA ELECTRIC CO., LTD. All Rights Reserved.│ │ IObase = 0x 300, Membase = CE00, Socket = 0 │ └─────────────────────────────────────────────────────────────────────────────┘ ERROR MESSAGE: ┌──────────────────────────────────────┐ │ DataBook CardTalk Not Loaded. │ │ Driver Unloaded. │ └──────────────────────────────────────┘ Possible Cause: The ASPIDBK.SYS couldn't start because the DataBook CardTalk isn't running properly. Solution: ∙ Reinstall the DataBook CardTalk supplied with your computer. ∙ Confirm the description in the CONFIG.SYS Check the CONFIG.SYS to make sure that the ASPIDBK.SYS is located after the CARDTALK.SYS. If it is not, please edit. ∙ Edit the CONFIG.SYS to specify the "X" option of EMM386.EXE (EMS driver). Without the "X" option or "/mem=" option of the ASPIDBK.SYS file, there is a possibility of overlap between the memory from CE000h to CFFFFh and the region of EMS or ROM. Thus, add "X=CE00-CFFF" to EMM386.EXE. ∙ Make sure the value specified in "/mem=" option agrees with the area specified in "X" option of EMM386.EXE. ∙ Try to change the value of "/mem=" option and "X" option in EMM386.EXE. (3) ASPI365.SYS The following message will appear. ┌─────────────────────────────────────────────────────────────────────────────┐ │ KME PC Card Driver Ver. 1.0 (94XXXX) │ │ for i82365 direct control and dual socket │ │ (C) Copyright 1994 RATOC System Inc. All Rights Reserved. │ │ (C) COPYRIGHT 1994 KYUSHU MATSUSHITA ELECTRIC CO., LTD. All Rights Reserved.│ │ IObase = 0x 300, Membase = CE00, Socket = 0 │ └─────────────────────────────────────────────────────────────────────────────┘ ERROR MESSAGE: ┌──────────────────────────────────────┐ │ Card Information Not Found. │ │ Driver Unloaded. │ └──────────────────────────────────────┘ Possible Cause: Wrong memory base address which is specified at "/mem=". Solution: ∙ Reinstall the software. ∙ Make sure the value specified in "/mem=" option agrees with the area specified in "X" option of EMM386.EXE. ∙ Try to change the value of "/mem=" option and "X" option in EMM386.EXE. (4) Common to ASPIMNGR.SYS, ASPIDBK.SYS and ASPI365.SYS ERROR MESSAGE: ┌──────────────────────────────────────┐ │ Invalid Base Address. │ │ Driver Unloaded. │ └──────────────────────────────────────┘ Possible Cause: Wrong base address of I/O port which is specified at "/port=". Solution: ∙ Reinstall the software. ∙ Edit the CONFIG.SYS. Change the "/port=" option to conform to the base address of I/O port. 2. CD-ROM Device Driver CD-ROM device driver conforms to ASPI. 2-1. Command Line Options DEVICE = <path>\KMECD.SYS [/d:<DriverName>] /d:<DriverName> This option assigns a driver name to this CD-ROM drive. The driver name is the identification string to "/d:" option of MSCDEX.EXE. The internal name of KMECD.SYS is PCMCIACD. 2-2. Onscreen Messages The following message will appear. ┌─────────────────────────────────────────────────────────────────────────────┐ │ CD-ROM Device Driver │ │ KMECD Ver. 1.65 (95XXXX) │ │ (C) Copyright 1994 RATOC system, inc. Osaka, Japan │ │ (C) COPYRIGHT 1994 KYUSHU MATSUSHITA ELECTRIC CO., LTD. All Rights Reserved.│ └─────────────────────────────────────────────────────────────────────────────┘ COMMON MESSAGE: ┌──────────────────────────────────────────────────────────┐ │ CD-ROM SCSI_ID : 5:MATSHITAKME CD-ROM01 1.** │ │ Device name : PCMCIACD │ └──────────────────────────────────────────────────────────┘ ERROR MESSAGES: ┌──────────────────────────────────────┐ │ CD-ROM Drive Not Found. │ │ Driver Unloaded. │ └──────────────────────────────────────┘ Possible Cause: This message tells you that the CD-ROM drive does not respond. 1. Hardware trouble such as improper connection between the player and your computer (-> Solution 1). 2. Software trouble such as improper running of the ASPI Manager (-> Solution 2). 3. Card Services that are not supported are being used. (-> Solution 3). Solution: 1. Check whether the player is connected properly and if the power is turned on or not. Confirm that the SCSI ID is set properly. 2. Reinstall the software. 3. If the message still appears, copy ASPI365.SYS from your setup disk to your hard disk (copy A:ASPI365.SYS C:\CDRM). Edit your CONFIG.SYS file (refer to your DOS manual) from DEVICE=C:\CDRM\ASPIMNGR.SYS to DEVICE=C:\CDRM\ASPI365.SYS. ┌──────────────────────────────────────┐ │ ASPI Manager Not Installed. │ │ Driver Unloaded. │ └──────────────────────────────────────┘ Possible Cause: KMECD.SYS couldn't start because the ASPI Manager (ASPIMNGR.SYS, ASPIDBK.SYS, ASPI365.SYS) has not started yet. Solution: Reinstall the Software. 3. MSCDEX.EXE MSCDEX.EXE (Microsoft CD-ROM Extensions) enables your computer to assign a logical drive number to your CD-ROM drive. 3-1. Command Line Options MSCDEX [/V /K /E] /D:[DriverName] /L:[DriveLetter] /M:[Value] /V Displays a list of additional information including how much memory is being used by the buffers, the resident data and the resident code. /K Type this only when the CD-ROM media directory is written in Kanji (Japanese). /E Expanded memory (EMS) can be used if this is available in your system. This conserves about 16 KB of the main DOS memory. /D:[DriverName] The driver name is a required parameter to communicate with the CD-ROM drive. The internal name of KMECD.SYS is PCMCIACD, and should be substituted for [DriverName]. /L:[DriveLetter] The drive letter is an alphabetic character assigned to a CD-ROM drive. If there is more than one CD-ROM drive, the alphabetic characters are sequentially assigned starting with the entered drive letter. If no drive letter is entered, the next available alphabetic character is assigned. /M:[Value] MSCDEX allocates the memory as sector buffers for caching CD-ROM information. If no buffer size is entered, 10 buffers, each using 2048 bytes of memory, will be allocated. 3-2. Onscreen Messages The following message will appear. ┌─────────────────────────────────────────────────────────────────────────────┐ │ MSCDEX Version 2.23 │ │ Copyright (C) Microsoft Corp. 1986-1993. All rights reserved. │ │ Drive D: = Driver PCMCIACD unit 0 │ └─────────────────────────────────────────────────────────────────────────────┘ ERROR MESSAGES: ┌────────────────────────────────────────────────┐ │ Device Driver not found: 'PCMCIACD'. │ │ No valid CDROM device driver selected │ └────────────────────────────────────────────────┘ Possible Cause: 1. The KMECD.SYS is not set up, or it is unloaded because of errors. 2. The CD-ROM driver name specified on the (/D) option of KMECD.SYS is inconsistent with the one specified on the (/D) option of MSCDEX. Solution: 1. Edit the CONFIG.SYS to DEVICE=C:\CDRM\KMECD.SYS /D:PCMCIACD (refer to your DOS manual for instructions on how to edit). 2. Edit the AUTOEXEC.BAT to C:\CDRM\MSCDEX.EXE /D:PCMCIACD 3. Restart your computer. ┌────────────────────────────────────────────────┐ │ Not enough drive letters available │ └────────────────────────────────────────────────┘ Possible Cause: Insufficient drive letter (such as N:) is assigned to the CD-ROM drive. Solution: When a drive letter other than A-M is assigned to the CD-ROM drive, the display shows the above message. In this case, follow the instructions below. (For example) 1. Edit the CONFIG.SYS to LASTDRIVE=R (refer to your DOS manual for instructions on how to edit). 2. Restart your computer. 4. Error Messages when installing software ┌────────────────────────────────┬───────────────────────────────────────┐ │ Message │ Solution │ ├────────────────────────────────┼───────────────────────────────────────┤ │ Illegal Directory Name! │∙ Don't use more than eight characters.│ │ │∙ Don't use unavailable characters such│ │ │ as "\", "*", etc. │ ├────────────────────────────────┼───────────────────────────────────────┤ │ Disk Error! │∙ Make sure that your floppy disk or │ │ │ hard disk is not damaged. │ │ │∙ Don't install the CD-ROM Drive │ │ │ Software onto the protected disk. │ ├────────────────────────────────┼───────────────────────────────────────┤ │ File not found! │∙ Make sure that CD-ROM Drive Software │ │ │ has been installed onto disk inserted│ │ │ into drive A or B. │ ├────────────────────────────────┼───────────────────────────────────────┤ │ Your computer does not have │∙ Make sure that your computer has │ │ PCMCIA slot! │ PCMCIA slot. │ │ │∙ Make sure that the connection │ │ │ between your computer and the Card │ │ │ Slot Board has been made properly. │ └────────────────────────────────┴───────────────────────────────────────┘ 5. Sample CONFIG.SYS Files This section gives instructions about putting the device drivers (Card manager,ASPI manager, CD-ROM device driver) into your CONFIG.SYS file. Each driver must be in the CONFIG.SYS file in the following order. ┌─────────────────────────────────────────────────────────────┐ │ 1. Expanded Memory Manager (such as EMM386.EXE) │ ├─────────────────────────────────────────────────────────────┤ │ 2. Card Manager (Card Service / CardTalk) │ ├─────────────────────────────────────────────────────────────┤ │ 3. ASPI Manager (ASPIMNGR.SYS / ASPIDBK.SYS / ASPI365.SYS) │ ├─────────────────────────────────────────────────────────────┤ │ 4. CD-ROM Device Driver KMECD.SYS │ ├─────────────────────────────────────────────────────────────┤ │ 5. LASTDRIVE │ └─────────────────────────────────────────────────────────────┘ 1. Expanded Memory Manager (EMM386.EXE) It is necessary to set up the memory manager (EMM386.EXE) so that it does not occupy the memory space used for the CIS.(Card Information Structure) 2. Card Manager (Card Service / CardTalk) Both the ASPIMNGR.SYS and the ASPIDBK.SYS controls the PC cards through card managers. Therefore, the DOS system requires that the card manager be installed. Usually, the card manager is supplied through your PC vendor. 3. ASPI Manager The ASPI manager should be installed with the kind of card managers that fit it. An installation program (supplied on the setup disk) selects a suitable ASPI manager and installs it automatically. 4. CD-ROM Device Driver KMECD.SYS The installation program on the setup disk automatically installs the CD-ROM device driver after the ASPI manager. 5. LASTDRIVE Through the Lastdrive command, the final valid drive letter is set. The installation program on the setup disk sets this line after the CD-ROM device driver. 5-1. Sample for IBM Card Service (conforms to PCMCIA 2.00) EXAMPLE: ┌──────────────────────────────────────────────────────────┐ │ DEVICE=C:\DOS\EMM386.EXE 1024 FRAME=D000 X=C000-CFFF │<- (A) │ ....... │ │ ......... │ │ DEVICE=C:\THINKPAD\IBMDSS01.SYS /S0=1 │<- (B) │ DEVICE=C:\THINKPAD\IBMDOSCS.SYS │<- (B) │ DEVICE=C:\THINKPAD\DICRMU01.SYS /MA=C000-CFFF │<- (B) │ ....... │ │ DEVICE=C:\CDRM\ASPIMNGR.SYS /port=300 │<- (C) │ DEVICE=C:\CDRM\KMECD.SYS /d:PCMCIACD │<- (D) │ LASTDRIVE=M │<- (E) └──────────────────────────────────────────────────────────┘ ┌───┬──────────────────────────────────────────────────────────────┐ │(A)│ Installing EMM386.EXE(expanded memory manager) without │ │ │ allocating the memory window segment from C000h to CFFFh. │ ├───┼──────────────────────────────────────────────────────────────┤ │(B)│ Installing Card Managers. │ ├───┼──────────────────────────────────────────────────────────────┤ │(C)│ Installing ASPIMNGR.SYS (ASPI manager for Card Service) │ │ │ in the condition of I/O address = 300h. │ ├───┼──────────────────────────────────────────────────────────────┤ │(D)│ Installing KMECD.SYS(CD-ROM Device Driver) with internal │ │ │ device name. (PCMCIACD) │ ├───┼──────────────────────────────────────────────────────────────┤ │(E)│ Setting up the last valid drive to M:. │ └───┴──────────────────────────────────────────────────────────────┘ 5-2. Sample for SystemSoft CardService (conforms to PCMCIA 2.00) EXAMPLE: ┌──────────────────────────────────────────────────────────┐ │ DEVICE=C:\DOS\EMM386.EXE 1024 FRAME=D000 X=D000-DFFF │<- (A) │ ....... │ │ ......... │ │ DEVICE=C:\CARDSOFT\SS365SL.EXE /SKT 2 │<- (B) │ DEVICE=C:\CARDSOFT\CS.EXE /IRQ A │<- (B) │ DEVICE=C:\CARDSOFT\CSALLOC.EXE C:\CARDSOFT\CSALLOC.INI │<- (B) │ INSTALL=C:\CARDSOFT\CARDID.EXE C:\CARDSOFT\CARDID.INI │<- (B) │ ....... │ │ DEVICE=C:\CDRM\ASPIMNGR.SYS /port=300 │<- (C) │ DEVICE=C:\CDRM\KMECD.SYS /d:PCMCIACD │<- (D) │ LASTDRIVE=M │<- (E) └──────────────────────────────────────────────────────────┘ ┌───┬──────────────────────────────────────────────────────────────┐ │(A)│ Installing EMM386.EXE(expanded memory manager) without │ │ │ allocating the memory window segment from D000h to DFFFh. │ ├───┼──────────────────────────────────────────────────────────────┤ │(B)│ Installing Card Managers. │ │ │ Some computers may use SSCIRRUS.EXE, SSDBOOK.EXE or │ │ │ SSVADEM.EXE instead of SS365SL.EXE. │ ├───┼──────────────────────────────────────────────────────────────┤ │(C)│ Installing ASPIMNGR.SYS (ASPI manager for Card Service) │ │ │ in the condition of I/O address = 300h. │ ├───┼──────────────────────────────────────────────────────────────┤ │(D)│ Installing KMECD.SYS(CD-ROM Device Driver) with internal │ │ │ device name. (PCMCIACD) │ ├───┼──────────────────────────────────────────────────────────────┤ │(E)│ Setting up the last valid drive to M:. │ └───┴──────────────────────────────────────────────────────────────┘ Example for the CSALLOC.INI: CSALLOC.INI is the file referred to by the CSALLOC.EXE program. ┌─────────────────────────────────────────────────────────────┐ │ MEM=D000-DFFF │<- (A) │ IOP=100-16F,178-1EF,208-2E7,2F0-2F7,300-307,310-36F,380-3BF │<- (B) │ RIOP=170-177,2E8-2EF,2F8-2FF,370-377,3E8-3F7 │ │ IRQ=3,5,A-B,F │<- (C) └─────────────────────────────────────────────────────────────┘ ┌───┬──────────────────────────────────────────────────────────────┐ │(A)│ Specifying the memory window segment address "D000h-DFFF" in │ │ │ order to get card information. In order to avoid confliction,│ │ │ this window is not to be used as another program. Thus, you │ │ │ must specify "X=D000-DFFF" option of the EMM386.EXE on │ │ │ CONFIG.SYS file to reserve this area. │ ├───┼──────────────────────────────────────────────────────────────┤ │(B)│ Specifying the I/O address "100-16F,178-1EF,208-2E7,2F0-2F7, │ │ │ 300-307,310-36F,380-3BF" is available for the PC card. │ │ │ The address "308-30F" is not described in this case, so you │ │ │ can't allocate "/port=300"(300h-31Fh used) for our products. │ ├───┼──────────────────────────────────────────────────────────────┤ │(C)│ IRQ numbers available for the Card Service are specified. │ └───┴──────────────────────────────────────────────────────────────┘ 5-3. Sample for Phoenix Card Service (conforms to PCMCIA 2.00 and 2.10) EXAMPLE: ┌──────────────────────────────────────────────────────────┐ │ DEVICE=C:\DOS\EMM386.EXE X=C800-CFFF │<- (A) │ ....... │ │ ......... │ │ DEVICE=C:\PCMPLUS\PCMSS.EXE │<- (B) │ DEVICE=C:\PCMPLUS\PCMCS.EXE /WAIT=12 /ADDR=C8 /IRQ=10 │<- (B) │ DEVICE=C:\PCMPLUS\PCMSCD.EXE /BEEP /COM=2 /RS=4 │<- (B) │ ....... │ │ DEVICE=C:\CDRM\ASPIMNGR.SYS /port=300 │<- (C) │ DEVICE=C:\CDRM\KMECD.SYS /d:PCMCIACD │<- (D) │ LASTDRIVE=M │<- (E) └──────────────────────────────────────────────────────────┘ ┌───┬──────────────────────────────────────────────────────────────┐ │(A)│ Installing EMM386.EXE(expanded memory manager) without │ │ │ allocating the memory window segment from C800h to CFFFh. │ ├───┼──────────────────────────────────────────────────────────────┤ │(B)│ Installing Card Managers. │ ├───┼──────────────────────────────────────────────────────────────┤ │(C)│ Installing ASPIMNGR.SYS (ASPI manager for Card Service) │ │ │ in the condition of I/O address = 300h. │ ├───┼──────────────────────────────────────────────────────────────┤ │(D)│ Installing KMECD.SYS (CD-ROM Device Driver) with internal │ │ │ device name. (PCMCIACD) │ ├───┼──────────────────────────────────────────────────────────────┤ │(E)│ Setting up the last valid drive to M:. │ └───┴──────────────────────────────────────────────────────────────┘ 5-4. Sample for DATABOOK CardTalk V2.20 EXAMPLE: ┌──────────────────────────────────────────────────────────┐ │ DEVICE=C:\DOS\EMM386.EXE X=CE00-CFFF │<- (A) │ ....... │ │ ......... │ │ DEVICE=C:\PCMCIA\SOCKET.SYS │<- (B) │ DEVICE=C:\PCMCIA\CARDTALK.SYS /A /NOSHARE │<- (B) │ ....... │ │ DEVICE=C:\CDRM\ASPIDBK.SYS /port=300 /mem=CE00 │<- (C) │ DEVICE=C:\CDRM\KMECD.SYS /d:PCMCIACD │<- (D) │ LASTDRIVE=M │<- (E) └──────────────────────────────────────────────────────────┘ ┌───┬──────────────────────────────────────────────────────────────┐ │(A)│ Installing EMM386.EXE(expanded memory manager) without │ │ │ allocating the memory window segment from CE00h to CFFFh. │ ├───┼──────────────────────────────────────────────────────────────┤ │(B)│ Installing Card Managers. │ ├───┼──────────────────────────────────────────────────────────────┤ │(C)│ Installing ASPIDBK.SYS (ASPI manager for DataBook CardTalk) │ │ │ in the condition of I/O address = 300h. │ │ │ It specifies the memory window segment from CE00h to CFFFh │ │ │ in order to read the card information. │ ├───┼──────────────────────────────────────────────────────────────┤ │(D)│ Installing KMECD.SYS (CD-ROM Device Driver) with internal │ │ │ device name. (PCMCIACD) │ ├───┼──────────────────────────────────────────────────────────────┤ │(E)│ Setting up the last valid drive to M:. │ └───┴──────────────────────────────────────────────────────────────┘ 6. I/O Base Address You can usually use the base addresses of the I/O port listed under the description of "/port=" option in the ASPI manager. (See 1-1) However, some of them cannot be used on some computers. For example: ┌──────────────────────────┬────────────────────────────────────────┐ │ PC │ Unavailable Base Address of I/O port │ ├──────────────────────────┼────────────────────────────────────────┤ │ Panasonic CF-580C │ 240, 280, 2A0, 2C0, 320, 340, 380 │ │ (Card Service Version) │ (changeable by "/IOW=" option) │ ├──────────────────────────┼────────────────────────────────────────┤ │ Toshiba T1950C │ 300 │ ├──────────────────────────┼────────────────────────────────────────┤ │ NEC Versa 40E │ 240, 280, 2A0, 2C0, 320, 340, 380 │ └──────────────────────────┴────────────────────────────────────────┘ 7. Supplement and Troubleshooting Guide 7-1. Base address of the I/O on the DataBook Card Service If you use the DataBook Card Service, you must set the base address of I/O in the description of the Card Manager on the CONFIG.SYS file. EXAMPLE of the CONFIG.SYS: ┌─────────────────────────────────────────────────────────────────┐ │ DEVICE=C:\CARDTALK\TMB240.SYS /io:240 │ │ DEVICE=C:\CARDTALK\CTALKCS.EXE │ │ DEVICE=C:\CARDTALK\CARDTALK.SYS /A /IOW=300-31F /MEMW=D000-D7FF │<- (A) └─────────────────────────────────────────────────────────────────┘ As shown above in (A), specify the address of I/O using the "/IOW=" option. By default, it will assign 300-31F. When you use another device (such as a sound card) together with this CD-ROM drive, you will have to allocate the address of I/O to both of them by using the "/IOW=" option: DEVICE=C:\CARDTALK\CARDTALK.SYS /A /IOW=300-31F /IOW=280-29F ....... 7-2. Examining the PCMCIA controller LSI(i82365) When the PC supplies neither Card Service nor Socket Service, and has Intel i82365 (or 100% compatible) as PCMCIA controller LSI, the installation program on the setup disk installs the ASPI365.SYS file automatically. This ASPI manager controls the PCMCIA controller directly. The ASPI365.SYS doesn't operate on DATABOOK PCMCIA controller, because it is set on the condition of using Intel i82365. You can look at the PCMCIA controller LSI as follows: (1) At the DOS prompt, type 'DEBUG' This command usually exists in the directory C:\DOS. (2) Write '00h' into the 3E0h of the I/O port. (3) Read the returned value 3E1h of the I/O port. (4) Hit 'q' to quit DEBUG.COM ┌─────────────────────────┐ │ C:\DOS>DEBUG <enter> │<- (1) │ -o 3E0 0 <enter> │<- (2) │ -i 3E1 <enter> │<- (3) │ -83 │<- TEST RESULT │ -q <enter> │<- (4) │ C:\DOS> │ └─────────────────────────┘ A result value of 82, 83 and 84 indicates that the PC is using i82365 (or compatible LSI), and the ASPI365.SYS should operate. In case the ASPI365.SYS doesn't operate, follow the error messages on the screen. When 'FF' appears as the result value, you cannot use the ASPI365.SYS. In such a case, there is a possibility that the PC is using the DATABOOK PCMCIA controller. If so, you must setup both CardTalk and the ASPIDBK.SYS to use the CD-ROM drive. When the installation program of the setup disk cannot detect the Intel i82365 (or compatible LSI), a message will appear on the screen as follows. ┌─────────────────────────────────────────────────────┐ │ CardTalk(PC Card Manager) does not exist! │ │ Please install the PC Card Manager, and restart │ │ your computer, then install CD-ROM Drive Software. │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ Press any key to exit. │ └─────────────────────────────────────────────────────┘ 7-3. Using the CD-ROM drive with .WAVjammer(PCMCIA sound card) After operating the CD-ROM player, or after executing the setup disk program, install the .WAVjammer driver soft and restart the computer. In this condition, the Windows program will probably not operate, because the base address of the I/O for both the CD-ROM player and .WAVjammer are at 300h. You can solve this problem in one of the following ways. (1) Changing the address of the I/O for .WAVjammer to be other than 300h-31Fh. (2) Editing the address of the I/O for the CD-ROM drive by changing the "/port=300" option. (See 1-1) By using either one of the above methods, edit the CONFIG.SYS, restart the computer. (Ctrl+Alt+Del) Windows should now be operative. 7-4. In case the PC hangs up in Windows When operating the CD-ROM soft under Windows, there is a chance that the PC will hang up and you can not operate the CD-ROM software. The cause is probably a problem in the computer set-up. You can probably solve it in the following ways. Please also refer to the CD-ROM soft manual as well as the computer, DOS, and Windows manual. (1) Reserving memory for Windows operations Edit the CONFIG.SYS or the AUTOEXEC.BAT to reserve more memory for Windows. For example: Adding the 'NOEMS' option to EMM386.EXE. Remove EMM386.EXE from the CONFIG.SYS file. Remove SMARTDRV.EXE from the AUTOEXEC.BAT file. (2) Using 32-Bit disk access By using 32bit access, Windows will be able to access the hard disk devices without using BIOS. As a result, access to the hard disk drive will be easier and smoother. However, on some computers you can not do this setting. Please check with the following method. (1) Double click on icon 'Main'. (on 'Program Manager') (2) Double click on icon 'Control Panel'. (3) Click on button 'Virtual Memory...'. (4) Click on button 'Change>>'. (5) Click on check-box of 'Use 32-Bit Disk Access' and check 'X' mark. If this entry does not appear, you cannot use this function. 7-5. Playing music CD on Windows MediaPlayer If you wish to play a music CD on the MediaPlayer through Windows, you must add the "[MCI] CD Audio" driver program. (1) Double click on icon 'Main'. (on Program Manager) (2) Double click on icon 'Control Panel'. (3) Double click on icon 'Drivers'. If you find "[MCI] CD Audio" in it, you do not have to change its setting. Quit this procedure. (4) Click 'Add' button. (5) Click "[MCI] CD Audio" 7-6. Using SMARTDRV.EXE Ver. 5.0 for CD-ROM cache MSCDEX.EXE Ver. 2.23 (supplied on the setup disk) enables you to cache CD-ROM with SMARTDRV.EXE Ver. 5.0 supplied by DOS on your computer. By using this command, it enables the CD-ROM to read data at a higher speed. (Some do not follow this rule.) To engage this function, you should specify SMARTDRV.EXE after MSCDEX.EXE on the AUTOEXEC.BAT file. This CD-ROM installation program specifies MSCDEX.EXE to the top of the AUTOEXEC.BAT file. Therefore, after putting SMARTDRV.EXE in the AUTOEXEC.BAT and executing the install program, the cache operation will be operable. If you want to disable the cache, edit the AUTOEXEC.BAT file and move the added MSCDEX.EXE line behind the SMARTDRV.EXE line. 7-7. In case of shortage of computer's conventional memory You can get more conventional memory by using the MEMMAKER command supplied by MS-DOS (Ver. 6.2 or more). If there is a shortage of memory, and you can't operate your CD-ROM soft, try this program. Read your DOS manual for further details. 7-8. Connecting to SCSI I/F board on desktop computer If you are using the CD-ROM with a desktop computer, a SCSI board is necessary. If you are already using a SCSI board, before you apply this CD-ROM's installation program, check the CONFIG.SYS and the AUTOEXEC.BAT files to make sure there is nothing related to CD-ROM. If there is something like the following, please erase it. In the CONFIG.SYS file DEVICE=C:\<Path>\ASPICD.SYS /d:ASPICD0 DEVICE=C:\<Path>\CUNI_ASP.SYS In the AUTOEXEC.BAT file C:\<Path>\CORELCDX 7-9. Computers which have a PCMCIA slot and are using another company's SCSI card In the case where you will connect this CD-ROM to a computer which has a PCMCIA card slot, and you already are using another brand SCSI card, before you apply this CD-ROM's installation program, check the CONFIG.SYS and the AUTOEXEC.BAT files to make sure there is nothing related to the ASPI manager on the CD-ROM. If there is, please erase it. For example: In the CONFIG.SYS file DEVICE=C:\<Path>\ASPIMGR.SYS DEVICE=C:\<Path>\MA460.SYS DEVICE=C:\<Path>\ASPICD.SYS /d:ASPICD0 DEVICE=C:\<Path>\CUNI_ASP.SYS In the AUTOEXEC.BAT file C:\<Path>\CORELCDX 7-10. Operation of CD-ROM soft installed in the hard disk is slow By putting the hard disk in its best condition, operation will become faster. You can defragment your hard drive by using the DEFRAG command on your computer. (supplied with DOS 6.0 or later) Please refer to your DOS manual for details. 7-11. Terminator setting Please set the terminator switch according to the conditions of the CD-ROM player. ON: when used with desktop computer. OFF: when used with the attached PC card or when used to play just music. The PC card used even with the termination switch in the off position is designed so that no problems will occur. Using it in the OFF position also cuts power consumption. 7-12. Insertion / Removal of the PC card with the power on If you are using the card manager(Card Service/Socket Service), you can insert or take out the PC card with the computer turned on. For example, you have connected the CD-ROM player, and then you want to use the FAX modem card. Change the card to the FAX modem card and use. Then, change it back to the PC card and continue. However, in this case if you leave the computer power on, also leave the CD-ROM power on, and put the card into the slot. If there is more than one card slot, make sure to put the PC card back into the same slot as before.