Re: [PARPORT] BackPack Cdrom Woes

Stef Telford (
Sat, 18 Jul 1998 23:47:56 +0000 wrote:

> > The version i am running of PARIDE is v1.03 ...and below is the
> > output from the insmod/modprobe with verbose flag active
> >
> > modprobe pcd verbose=1 drive0=0x378,0
> > parport0: PC-style at 0x378, irq 7 [SPP,ECP,ECPPS2]
> Please investigate the CMOS settings for your parallel port. If possible,
> change the port to "EPP" mode.

Hurmmm, this can be either changed to uni-directioanl (spp if memory serves
me right)or bi-directional (which lists at ecp) tried both, but still no joy.

What _is_ strange, is the exact (and I mean _exact_) same configuration works
for the sparq
and laser printer. Can this be an undisclosed communication event on behalf
of the bantam cdrom ?

just for the record, I can mount the drive under dosemu (97.10), but this
doesnt allow me to redirect
new dos drives to linux (vice versa certianly).

The chipset for the motherboard on my laptop is a national semiconducters PC
87338, I cant realistcally swap out
the laptops motherboard, which is a pain in the ass. I can even give you the
setup control codes that are sent
to the parallel chip (if i am reading the bantam backpack testport utility's
output correctly :)

> > pcd: pcd version 1.03, major 46, nice 0
> > pcd0: 0x378 is parport0
> > pcd0: bpck: 0x378 unit 46 mode 0:
> 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 31
> Ok, the bpck protocol driver located your backpack, and was able to
> communicate with it - but it failed a data integrity test.
> The integrity test failed because of an oddity with your specific
> port, that MSI's driver's understand, but ours doesn't. If you can
> get into EPP mode, this specific problem should go away.

*grimace* doesnt. even when set to spp mode. what would the pcd
(using bpck protocol) trythat the pd (using epat) wouldnt (other than the
obv. disk geometry stuff). Anything ?

> > As you can finds something on major 46 mode 1 (if i _am_
> > reading this right)
> By pure coincidence, your drive happens to have an ID number of 46.

*heh* no, i actually read the documentation first (well, okay, *hands
raised*, after it didnt workfirst time, then i read it) and used the backpack
utility to convert it across.

> (That's the last two digits of its serial number.) 46 is also the
> major device number for the pcd driver - there's no relationship
> between them.

oohh...i thought there was, Okay. If you want i can try and get information
out of MicroSolutions about this??

> --------------------------------------------------------------------------
> Grant R. Guenther
> --------------------------------------------------------------------------


-- To unsubscribe, send mail to: --
-- with the single word "unsubscribe" in the body of the message. --

This archive was generated by hypermail 2.0b3 on Wed 30 Dec 1998 - 10:18:00 EST