1. CDv103.zip Driver
2. Readme.txt File Contents

Readme.txt Driver File Contents (CDv103.zip)

CD-ROM Drivers for Aleph One !PC system
=======================================

Please read all sections in order carefully. Do not skip or scan read any 
sections unless the instructions told you to do so.
========================================================================

INDEX
 1  Requirements
 
 2  Supplied Files
 
 3  General information
 
 4  Protected-mode Driver
 4.1 Safe List
 4.2 Installation
 4.3 Device Conflicts
 4.4 TroubleShooting
 4.5 CD Autochangers
 
 5  DOS Driver
 5.1 Installation
 5.2 Manual Install
 5.3 If using Windows95
 5.4 Error messages from HPC_CD.SYS
 
 6  Aleph One Support

---

1  Requirements
===============
These drivers needs !PC v2.00 or greater - ie 'PCPro'.
The protected-mode driver (CDHPC.MPD) is only suitable for Windows95.
The DOS (real-mode) driver (HPC_CD.SYS) will work with DOS or any version of
Windows.

PCPro is available from most local Acorn Dealers or direct from
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel:- (00 44) 1223 811679


2  Supplied files
=================
Readme.txt        1999.04.23, This file

Protected-mode driver:
 CDHPC.MPD  v1.03 1998.08.13, 32-bit CDROM driver (MiniPort Driver)
 CDHPC.INF        1998.04.16, Windows95 installer file
DOS driver:
 HPC_CD/SYS v2.0  1995.11.29, DOS device driver, from Aleph1
 NWCDEX.EXE       1997.12.19, CD extensions to DOS, from Caldera
 or 
 MSCDEX.EXE       1993.09.30, CD extensions to DOS, from Microsoft

 

3  General information
======================
These drivers will work with all CD-ROM drives (SCSI, IDE or Parallel
interfaces). You must already have the drive installed so that it can be
accessed on the RISC OS desktop, and have the correct number of CDROM drives
configured.

If you are using Windows95 you should use the new Protected-mode driver. See
'Protected-mode Driver' below for details.

If you are using DOS or Windows 3.x you should use the old DOS driver. See
'DOS driver' below for details.


4  Protected-mode Driver
=======================
The driver is implemented as a protected mode (aka '32-bit') SCSI miniport
driver for Windows 95. It replaces the real-mode DOS CDROM driver HPC_CD.SYS,
for Windows 95 and for DOS boxes within windows. It supports all CDROM drives
recognised by RISCOS, up to a maximum of 7 drives.

Because it is a protected-mode driver it supports full Windows95
functionality, including 'Joliet' format CDs (including Long Filename
support), autorun and auto-insert notification.

The old DOS driver is still needed for CDROM access under Windows 3.1 or 
DOS. The old DOS driver is also on the bootable floppy created by 
!MkBootDisc so that Windows95/98 can be installed from CD.

Note that !PCinstall (from PCPro 2) does not know about this driver, so if
you use the 'Install CDROM driver support' option it will only install the
old DOS driver. If both drivers are installed Windows 95 will use only the
new driver automatically.

This driver uses the same resources (the PC Card's 'HPC' interface), as 
other drivers already in circulation:
CD_HPC.SYS     Aleph One real mode (DOS) CDROM driver
ARMASPI.SYS    Andreas Walter's ASPI driver
ARMEDIT.SYS    Alexander Thoukidides' ARMEdit driver

The majority of users will be using at least one, the (DOS) CDROM driver 
from the drivers listed above and Windows95 will usually complain about 
'device conflicts'. This will not stop the installation or the working of 
the drivers if you follow all the instructions below.

This version of the driver does not support Audio functions, this includes
the CD+ format that has a mix of Data and Audio Tracks. This will be in
a later release.

4.1 Safe List
-------------
It is not compulsory to follow this section and you could skip to the 
install section, but some users will find that by completing the 
Safe List: instructions that 'device conflicts' is not reported and that 
the Device Conflict section may not be needed.

1) Load into your RISC OS text editor, 'Edit' or similar, the file called
Windows.Ios/ini which is in the Windows95 directory of your drive_c DOSDisc
file (partition).

2) Add the following lines at the end of the [SafeList] section.

	hpc_cd.sys	; Aleph One real-mode CD-ROM driver
	hpcaspi.sys	; Andreas Walter's DOS ARMASPI driver
	armedit.sys	; Alexander Thoukidides' ARMedit driver

Please remember that if you are using Edit to copy the [0d] from the end
of one one of the other lines and add them to the end of the new lines.

3) Save the file.

Again this next section is not compulsory but you may like to REM out
any lines in the config/sys and autoexec/bat relating to the same drivers 
mentioned above. These files are also found in you drive_c DOSDisc file. 

config/sys file
	REM DEVICE=<PATH>HPC_CD.SYS
        REM DEVICE=<PATH>HPCASPI.SYS
        REM DEVICE=<PATH>ARMEDIT.SYS

autoexec.bat
	REM <PATH>\NWCDEX /D:MSCD000

Again Please remember that if you are using Edit you will see a [0d] 
at the end of each of these lines.

You could delete the HPC_CD.SYS from the config/sys file and the
NWCDEX /D:MSCD000 from the autoecec/bat if you wish, as these would be 
deleted by the installer if they were not REMed out anyway.


4.2 Installation
----------------
You should have read the General information section and may have also 
carried out the Safe List instructions before you continue with the 
installation. 

NOTE:- Because of the number of versions of Windows95 you may find that
some of the buttons that are stated in the instructions below are not the 
same as you are presented with. Selecting a similar named button in such
cases normally works.

The installer will remove lines mentioning CD_HPC.SYS and NWCDEX or MSCDEX
from your CONFIG.SYS and AUTOEXEC.BAT automatically, (unless they are already
REMmed out or have been removed) and add the hpc_cd.sys, armaspi.sys and 
armedit.sys to the [SafeList] (unless they have already been added).  For
more details read Safe List section above.

1) Copy the files on this disk, or unzip them if supplied as a ZIP file, into
C:\DRIVERS\CDROM. If you can't easily do this (e.g due to this being on a
Direct SCSI drive you cannot access from the desktop) then unzip/copy them
onto another drive or a floppy disk - and change references to
C:\DRIVERS\CDROM below accordingly.

2) Remove all CD/s from CDROM drive/s and start !PC and Windows95

3) Go to Control Panel. Double Select on 'Add new hardware' to start the
wizard.

4) Select 'No' in answer to 'Do you want windows to search for your new
hardware?' Select 'Next'.

5) Scroll down the window to select 'SCSI controllers'. Select 'Next'.

6) Select 'Have Disk', and either browse to, or type in C:\DRIVERS\CDROM and
select 'OK'. 'Aleph One RISCOS-hosted devices controller' should be listed.
select 'Next'.

7) Even if there is a conflict found you will have a new window select 
'Next' and then 'Finish'.

8) You will be asked if you wish to restart your computer, select yes.

9) On restarting Windows95 go to 'My Computer' if no conflicts were found
   a CDROM icon will be shown and the installation is compete. If no icon
   is shown follow the instructions in the Device Conflicts: section below.


4.3 Device Conflicts
--------------------
These instructions only need to be carried out if a 'device conflict'
error was reported while installing the 32bit CDROM driver and no CDROM
icon is shown in Windows95's 'My Computer'.

NOTE:- Because of the number of versions of Windows95 you may find that
some of the buttons that are stated in the instructions below are not the 
same as you are presented with. Selecting a similar named button in such
cases normally works.

1) Run the Control Panel, System. 

2) Then select the Device Manager tab. 

3) At the SCSI controllers the if the symbol at the side of it is a '+'
    Select on it to change it to a '-' so that you can see the 
    "Aleph One RISCOS-hosted devices controller" which will have a red cross
    or a yellow disc with a black '!'.
    
4) Select the "Aleph One RISCOS-hosted devices controller" and then the 
   'Properties' 

5) Within the General window the "Original Configuration (Current)" 
    may not ticked. If so select in the small square to make it so.
    (One version of Windows will only tell you that the driver is disabled 
    so you will need to select it to enable the driver)
    If prompted DO NOT restart the computer select 'NO'
     
6) Go back to the Properties for the "Aleph One RISCOS-hosted devices 
    controller" if you have to and select Resources. 
    
7) Selected the 'Set Configuration Manually' button. All the information
    will be correct and no conflicts should be listed in the 'conflict
    device list' window. 
    
8) Select OK and then 'YES' to resetting/starting windows. 

9) You should now find that you have a CDROM icon within My Computer and
   the installation is complete.
   

4.4 Troubleshooting
-------------------
If you have installed the driver but no CDROM icon appears under 'My
Computer' then follow the instuctions in 'Device Conflicts' to see the status
of the "Aleph One RISCOS-hosted devices controller".

There are three possibilities:
* Red Cross icon:       The driver is disabled

  The device is not enabled in the current confuguration. Follow the
  instructions in 'Resource Conflicts' above to enable the device under the
  'General' tab.

* Yellow Disc icon:     The driver is not working

1) Most likely is that the resources are not set or Windows thinks there is a
   conflict. Follow the instructions in 'Resource Conflicts' above to 'set
   configuration manually' under the 'resources' tab. If there is a 'use
   automatic configuration' button that must be unticked.

2) Check that you don't have two copies of the driver installed (one
   will be 'not working', and should be removed). 

3) The driver has been loaded on a PC that is not a PC Card, or the version
   of !PC you have is before v2.00 so HPC is not supported. See
   'Requirements'.

* No Icon:              The driver is working normally

  If the driver is working normally and there is no CDROM displayed then the
  most likely cause is that either there is no CDROM available to RISC OS
  (check your icon bar), or the number of CDROM drives is set to 0. Change
  this by clicking menu on the CDROM icon on the icon bar and following
  'Configure -> Drives', to set the actual number of drives. 


4.5 CD Autochangers
-------------------
Windows interrogates CDs every second in order to notice when they
have been changed. This causes problems with autochanger CDROM drives, as
they take nearly a second to check all 4 discs so you can never actually do
anything. We can supply a special version of the driver which only recognises
the first drive to get round this problem, or you can disable the 'Auto
insert notification' and 'Auto Run' features for all the drives. This is done
in device manager under 'RISCOS HOSTED CDROM' properties.


5  DOS Driver
=============

The DOS device driver (HPC_CD.SYS) is necessary for the CDROM to be
recognised by the PC Card. The CD ROM extensions (NWCDEX.EXE or MSCDEX.EXE)
are necessary for DOS to use a CDROM drive. A modern version of DOS will
include a copy of NWCDEX or MSCDEX. Use that in preference to the one on this
disc, which is only supplied for those who do not already have a version of
the file.

Note that HPC_CD.SYS supercedes the older driver A1CD.SYS which will not work
with !PC v1.99 or later. Remove this older driver, which may be in your
C:\DOS directory, as well as C:\DRIVERS\CDROM.


5.1 Installation
----------------
The necessary files should be installed by !PCInstall, as described in
'Installation' in the main Readme. It is possible to install them manually if
necessary, as detailed below.

5.2 Manual Install
------------------
You need the HPC_CD.SYS file in the directory C:\DRIVERS\CDROM. It should be
put there by !PCInstall if using PCPro2. If not you need to read the
Unpackers ReadMe for details on manual unpacking. For PCPro3 the driver is on
the Aleph1 One Boot/drivers floppy in A:\PCP3_Drv\CDROM, but you will hardly
ever need to deal with it directly as the setup program is pretty competent.

[See Issue 6 (PCPro2) Manual section 6.11 CD-ROM, noting that the name of the
Driver itself has changed from A1CD.SYS to HPC_CD.SYS]

NB: Before editing DOS text and System files you must read the important note
in Section 5.5 of the Issue 6 (PCPro 2) Manual or Section 5.8 in issue 7
(PCPro 3) (Editing DOS text & system files).

HPC_CD/SYS is an MS-DOS device driver for NWCDEX.EXE/MSCDEX.EXE; you should
copy it from C:\DRIVERS\CDROM (PCPro2) or A:\PCP3_Drv\CDROM (PCPro3) into
your DOS directory either on the desktop, or with 
  COPY C:\DRIVERS\CDROM\HPC_CD.SYS c:\DOS\ 
at the DOS prompt, then and put a line in CONFIG.SYS similar to this:

  DEVICE=C:\DOS\HPC_CD.SYS /D:MSCD000
  
  Note that the /D:<name> means 'Devicename', not Drive D:, the drive letter
used is supplied automatically by DOS. Note that if you have a
LASTDRIVE=<letter> command then the letter must be high enough for all your
partitions, CDROM drives, network drives, etc. 
  You may also have to change the path, if you put the file somewhere other
than your DOS directory.

You should also copy NWCDEX.EXE to a suitable place, if you don't have it
already installed (check in your DOS directory) and include the line

  C:\DOS\NWCDEX /D:MSCD000

in your AUTOEXEC.BAT file. 

5.3 If using Windows 95
-----------------------
Normally you should no longer use this driver for Windows 95, but should use
the protected-mode Driver instead (see 'Protected-mode Driver' above).

If you do want to use this driver with Windows 95, the above instructions
still apply, unless you have a Windows 95 installation without DOS, in which
case you will need to put the HPC_CD.SYS driver in a different directory. We
recommend C:\WINDOWS\COMMAND.

You will also need to create CONFIG.SYS & AUTOEXEC.BAT files in the
root directory C:\ if they don't already exist.


5.4 Error Messages from HPC_CD.SYS
----------------------------------

ERROR! Invalid line in CONFIG.SYS

  Means some of the text following "DEVICE=HPC_CD.SYS" is incorrect. Currently
  you may only have the phrase "/D:name" after this. 'name' is the name by
  which NWCDEX will know the device driver - it should be no more than 8
  characters long. If you do not have "/D:name" the name will default to
  'MSCD000'.

ERROR! Cannot find HPC CDROM services
       This driver needs !PC version 2.00 or later
       
  One of Two reasons:
  1) You are running HPC_CD.SYS on a version of !PC prior to v1.99. Versions
     before this must use A1CD.SYS
  2) You are trying to run A1CD.SYS on a system which is not an Aleph One 386PC
     card, e.g. a normal DOS system or the Acorn PC emulator. 
                                                 
ERROR! No CD-ROM drives working

  The !PC application has been unable to find any working CD-ROM drives. This
  may be because the drive is switched off, or the Acorn CD filing system
  and driver (CDFS) is not loaded, or you have not configured CDFSDrives to 1.


6  Aleph One Support
====================
For users who are experiencing difficulties Aleph One Support can be 
contacted on any of the following:

E-mail:   support@aleph1.co.uk
Tel       UK (00 44) 1708 403028  
Fax       UK (00 44) 171 9199401