[PARPORT] Old Shuttle drive?


Michiel Toneman (toneman@phil.uu.nl)
Sat, 30 May 1998 12:26:21 +0200 (MET DST)


Hi everybody,

I have a really old Shuttle CDROM drive, which I would LOVE to get
working under Linux.

It is a "FREEPORT DATA INTERNATIONAL"
Shuttle-Series #09366 with a single speed Sony caddy type CDROM
model CDU-541.

The driver under DOS is called ASPISHT.SYS. Some info from
strings ASPISHT.SYS | less
which I hope is useful:

-------------------------------------------------------------

FREEPORT
ASPI_DRIVER
AURELEC V2.10

Freeport Data International Ltd.
FREEPORT ASPI Manager Version 3.04
Copyright (C) Freeport Data Int'l Ltd 1990-1992. All rights reserved.
Release Date: 17th July 1992FREEPORT ASPI Manager installed successfully.
Error encountered while initialising Adapter.
Driver cannot be installed.
$Developed byDevanathan N.R. & Rajendran G.

 Usage: DEVICE = ASPISHTL.SYS /Rxx /Wyy
 where xx is a read mode number
        yy is write mode number
 Select a read mode from:
 00 - NIBBLE zero 01 - NIBBLE one
 02 - NIBBLE two
 03 - UNIDIR zero 04 - UNIDIR one 05 - UNIDIR two
 06 - TOSHIBA zero 07 - TOSHIBA one
 Select a write mode from:
 00 - WRITE zero 01 - WRITE one
 02 - WRITE two
 Default options are marked with
                                   
device.cfg

 50-400L SCSI ROM BIOS Version 3.0
Aurelec 50-400X
FREEPORT
AURELEC V2.10

-------------------------------------------------------------

Has anyone ever heard of or seen this drive, and better gotten
it to work under linux?

I've tried to use it under the dos EPSA and EPST drivers without luck,
but I can use the ASPIHDRM.EXE driver supplied with EPSA.

I have also used the EPSA driver under Linux, but I get the following
messages.
 
-------------------------------------------------------------

lp1 at 0x0378, (polling)
epsa: autoprobe failed
scsi : 0 hosts.
Unable to handle kernel NULL pointer dereference at virtual address c0000000
current->tss.cr3 = 00f3d000, %cr3 = 00f3d000
*pde = 00102067
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<0180dc45>]
EFLAGS: 00010246
eax: 00000000 ebx: 00fcd298 ecx: 00000000 edx: 00000000
esi: 00000000 edi: 00000001 ebp: 018155ac esp: 00b99f00
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process insmod (pid: 7434, process nr: 41, stackpage=00b99000)
Stack: 00fcd298 00c72810 00000001 00b99f30 00000001 0180de5a 018155ac
0180dece
       018155ac 01815529 00000001 018155ac 006bd198 001157b4 0045ec0c
bffff610
       08057d58 bffff580 0011a753 0011a7d7 003d81b0 00fcd298 00000001
00c72810
Call Trace: [<0180de5a>] [<018155ac>] [<0180dece>] [<018155ac>] [<01815529>]
[<018155ac>] [<001157b4>]
       [<0011a753>] [<0011a7d7>] [<018154f8>] [<0181553c>] [<00111250>]
[<00111134>] [<00117d27>] [<0010a7cd>]
       [<0010a642>]
Code: 0f b7 11 81 fa 25 01 00 00 7f 28 52 68 3c c5 1a 00 e8 c1 11

-------------------------------------------------------------------

I'd really like to get this drive working. I don't mind doing
the hard work myself, but I don't know where to start. A tip how to
adapt the epsa.c driver would be a great help.

Thanks,

Michiel Toneman

-- 
Linus's Law

Given enough eyeballs, all bugs are shallow.

-- To unsubscribe, send mail to: linux-parport-request@torque.net -- -- 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:17:48 EST