Well just incase anyone missed that...
Taken from :http://www.torque.net/parport/
> Probably been asked before, but what is the difference between bpcd and
> bpck? The Linux CD-ROM HOWTO recommends using bpcd, while PARIDE.TXT
> suggests bpck. When RH Linux v5.2 installs what does it use and when I
> selected "AutoProbe" what did it do?
It's probably a good idea to look at the dates on the various documents.
bpcd is obsolete.
bpcd was a simple driver that supported only certain models of the backpack
family. It was replaced about a year ago by the PARIDE suite of drivers
and protocol modules. It was only ever an official part of the 2.1
kernels between about 2.1.30 and 2.1.80 ...
bpcd was roughly equivalent to pcd+bpck+paride.
PARIDE is easier to maintain, and contains a lot more functionality.
Now, to the RedHat story.
Long ago, back in the 1.3 days when bpcd was first developed, Donny and
Erik at RedHat agreed to put support for backpacks into the installer.
The "Microsolutions backpack" option in the installer still uses
an old version of the bpcd driver. The installed system, however,
has full support for pcd, bpck, etc.
The next version of RedHat will probably have the current pcd+bpck+paride
driver on it, but we are still looking for a better solution.
Frankly, SuSE and Slackware are both ahead of RedHat on support for
the PARIDE CD-ROMs for installation.
> I am using a BackPack CD-ROM Model 166550, SN: 17180214, parallel port
> address 03BC. Would the following be the correct commands and sequence to
> access the CD-ROM?
>
> 1. insmod paride
> 2. insmod bpck
> 3. insmod pcd drive0=0x3bc,0,14
You _should_ be able to just do
insmod pcd
in step 3. Since you are asking the question, I'm guessing that
something doesn't work. In that case, please do
insmod pcd verbose=1
and then extract all relevant messages from 'dmesg' and send them to
me. (The list doesn't need to watch us debug your setup.)
> (Do I need to cread the device "special files" at this point?)
In an earlier mail, I think you said you were using RedHat 5.2. If so,
you don't need to make any device nodes.
> 4. mount /dev/pcd0 /mnt/cdrom
If the module loaded, this should work.
> -----Original Message-----
> From: Cloghesy, Charles [SMTP:[EMAIL PROTECTED]]
> Sent: Monday, February 08, 1999 8:07 AM
> To: [EMAIL PROTECTED]
> Subject: CDrom Timing Out
>
> ARG!!
>
> I have been having problems with my Backpack Cdrom (#167550) with a
> standard
> PC parallel port interface. I am running Redhat 5.0 at the moment on
> two 486's, one laptop, one desktop. Both have the same problem. The
> problem being the cdrom times out when it has not been accessed in the
> last
> 3 to 5 minutes. I get a garbled screen after the computer tries access
> the
> CD after that time. Is there a problem with the BPCD driver?
>
> Thanks in advance
>
>
>
> __________________________________________________________
> Charles E. Cloghesy
> Piping and Plant Layout
> Bantrel Inc.
> Ph.(403)290 4072
> Fax (403)290 5050
> http://www.bantrel.com/
>
