Edit: Is there another device on the other side of the PCB. e.g. a 53C80?

If I had one of these devices, I would have done the following:
Plugged in a SCSI CDROM+terminator, (or a SCSI HDD if no cd drive available)
Plugged the kit into a PC running Linux (my flavour: Slackware).
For each Parallel Port SCSI module, do the following:
- insmod to insert the module
- check dmesg to see if the adapter+drive is recognised
- rmmod if it isn't and move to the next module.

This would give me a generic name to Google for a DOS driver and/or ask the folks here a question like this example: "Does anyone have the equivalent of the Shuttle EPAT parallel port SCSI drivers for DOS?".

It's complicated, but when Google fails, you'll need to experiment.

mdog69 wrote on 2021-02-02, 23:45:

Edit: Is there another device on the other side of the PCB. e.g. a 53C80? […]
Show full quote

Edit: Is there another device on the other side of the PCB. e.g. a 53C80?

If I had one of these devices, I would have done the following:
Plugged in a SCSI CDROM+terminator, (or a SCSI HDD if no cd drive available)
Plugged the kit into a PC running Linux (my flavour: Slackware).
For each Parallel Port SCSI module, do the following:
- insmod to insert the module
- check dmesg to see if the adapter+drive is recognised
- rmmod if it isn't and move to the next module.

This would give me a generic name to Google for a DOS driver and/or ask the folks here a question like this example: "Does anyone have the equivalent of the Shuttle EPAT parallel port SCSI drivers for DOS?".

It's complicated, but when Google fails, you'll need to experiment.

I opened it back up, took the boards apart and took another picture. Yes, there is an 53C80E present.
Totally forgot about the linux drivers though, will have to try that out. FYI, my favourite is also slackware
Looking into the linux docs now to find a possibly appropriate driver... though the first glance isn't very inspiring, I'll have to search the historical records.

As far as the Linux drivers are concerned, it's simply a question of trying the most likely candidates first. Loading the wrong driver should "fail safely".

I'd use this approach, as it's likely to yield quicker results than googling for the CPI-FDX/en92300 device, and wading through websites regarding parallel port SCSI on Neolithic kernels.

Use the kernel make menuconfig to identify modules, and dig through the kernel source for more detailed info on supported devices.

after some looking around, stumbling on some fake driver sites and remembering usenet... https://groups.google.com/g/comp.periphs.scsi … /m/bgbk-wYPap0J
which lead me to http://www.spudster.org/Always
and the archive site https://web.archive.org/web/20060702112426/ht … ter.org/Always/

the drivers should be located on the AL-1000E utility diskettes

... now to extract/write and test them.

mdog69 wrote on 2021-02-03, 13:34:

As far as the Linux drivers are concerned, it's simply a question of trying the most likely candidates first. Loading the wrong driver should "fail safely".
I'd use this approach, as it's likely to yield quicker results than googling for the CPI-FDX/en92300 device, and wading through websites regarding parallel port SCSI on Neolithic kernels.
Use the kernel make menuconfig to identify modules, and dig through the kernel source for more detailed info on supported devices.

I've done the make menuconfig way too many times, and the "fail safely" yeah.... maybe.
Anyway, I think i've found the link to the drivers using the old usenet archives on google groups.

now to test.