scsi.device

Saghalie · 24 November 2017, 23:05

I think I missed something. I'm trying to get the TAPE device working in A1200 to do backups so I don't have to make a dirt load of ADFs ... but I can't get the TAPE device to work in A1200 because the scsi.device is not found.

The software for TAPE backups (ABackup, Diovolo, HDTools etc) all look for the scsi.device and won't work.

Using AMIX and a config for OS4.1 - I don't have an issue. It works great.

I'm just wondering if I missed something where the scsi.device isn't supported anymore in A1200, A500?

I attached DKB/GVP etc devices with no luck either.

Can someone give me some advice?

Thanks!

emufan · 25 November 2017, 00:18

in the icon information of the apps, look for a tooltype DEVICE (most often used), and try uaescsi.device.
DEVICE=uaescsi.device <push enter in that line then save>

in config expansion -> build in expansion -> you may enable A600/A1200/A4000 IDE (Commodore).

not sure if it will help at all, but take alook.

Saghalie · 25 November 2017, 00:24

Quote:

Originally Posted by emufan

in the icon information of the apps, look for a tooltype DEVICE (most often used), and try uaescsi.device.
DEVICE=uaescsi.device <push enter in that line then save>

in config expansion -> build in expansion -> you may enable A600/A1200/A4000 IDE (Commodore).

not sure if it will help at all, but take alook.

Thanks for the info, but ... I've tried that. I just loaded up my DataFlyerPlus - copied the disk to ADF and installed it. SCSIPlus doesn't work because it can't find scsi.device but the ExpXDS.device is installed and if I select it - it finds the TAPE device - but for some reason ABackup/Quarterback/Diavolo all want me to insert a tape. So far I haven't been able to find out how to do that.

EDIT: Found out "how to do that"

Got any tips?

Thanks!

emufan · 25 November 2017, 00:46

Quote:

Originally Posted by Saghalie

EDIT: Found out "how to do that"

good news, but how did you fix it?

#1) just found the prefs tool of abackup, got the same name, but after install it is in sys:Prefs
here one can change some settings, change backup target and scsi.device, for example.

Saghalie · 25 November 2017, 01:14

Quote:

Originally Posted by emufan

good news, but how did you fix it?

I was hoping you wouldn't ask that... hehe, I forgot to tick 'Read/Write'.

I've been trying all sorts of different configurations... I just can't get the system to find the TAPE device.

emufan · 25 November 2017, 01:31

the read/write in "Add Scsi Tape drive" ?
I just found that config, r/w is greyed out.

#1) with my experiments, i'm stuck with "TAPE: couldnt be opened". doesnt matter.

so your problem is now, abackup and others do not work, since they want you to insert a tape?

Saghalie · 25 November 2017, 01:47

Quote:

Originally Posted by emufan

the read/write in "Add Scsi Tape drive" ?
I just found that config, r/w is greyed out.

#1) with my experiments, i'm stuck with "TAPE: couldnt be opened". doesnt matter.

so your problem is now, abackup and others do not work, since they want you to insert a tape?

Nope, they all tell me the tape is there when I use ExpXDS.device - but when I go to do the backup, the program locks up. I can't run SCSIPlus because it's hardcoded to use scsi.device so it errors out.

EDIT: gonna try GVP

Saghalie · 25 November 2017, 01:50

Quote:

Originally Posted by Saghalie

EDIT: gonna try GVP

GVP seems to be working.

emufan · 25 November 2017, 02:03

Quote:

Originally Posted by Saghalie

GVP seems to be working.

while I still fight with the TAPE: volume not present (doesnt matter) - congrats

Saghalie · 25 November 2017, 02:12

Quote:

Originally Posted by emufan

while I still fight with the TAPE: volume not present (doesnt matter) - congrats

I'm using the GVP Series III drivers - found the disk online (from their website I believe) and copied the driver to the expansion folder and it all seems to work smoothly. Backed it up in QBack and am doing one now in Diavolo, will try ABackup next.

Thanks!

Saghalie · 25 November 2017, 02:23

Got it working with GVP

emufan · 25 November 2017, 08:11

Quote:

Originally Posted by Saghalie

Got it working with GVP

tested with the gvp expansion, but still no joy :/
and again, doesnt matter atm - will go back to it, another day

Toni Wilen · 25 November 2017, 09:32

TAPE is SCSI, not IDE. Don't attempt to use it with IDE controllers.
Otherwise: not enough information.

mark_k · 25 November 2017, 14:18

There were ATAPI tape drives. I don't know whether it was possible to use one on a real Amiga. Maybe with IDEfix97?

For using a backup program, a good alternative is to back up to a file in a shared folder, assuming the backup program supports that. I think QuarterBack does.

Toni Wilen · 25 November 2017, 15:30

I can hook scsi tape emulation to ATAPI but question is: what should identify packet device -command return?

Saghalie · 25 November 2017, 16:12

Quote:

Originally Posted by mark_k

There were ATAPI tape drives. I don't know whether it was possible to use one on a real Amiga. Maybe with IDEfix97?

For using a backup program, a good alternative is to back up to a file in a shared folder, assuming the backup program supports that. I think QuarterBack does.

On my A1200, I used a tape drive via the parallel port. It was a small unit that I got from a dentist office when they upgraded their computer system back in the 90's. Used a small 3M tape.

Yes QuarterBack can backup to a shared folder. I was doing backups via QB to a file on a shared folder to my server but thought I would do that with a TAPE drive instead. For something different.

Saghalie · 25 November 2017, 16:25

Quote:

Originally Posted by emufan

tested with the gvp expansion, but still no joy :/
and again, doesnt matter atm - will go back to it, another day

Make sure you put GvpScsi/GvpScsi.info in the expansion drawer of SYS:
then use gvpscsi.device as the TAPE device in the programs. I tested ABackup, Diavolo and Quarterback and they all work, although Quarterback always reports that the tape is not a valid QuarterBack tape (even though it is).

Hope you get it working!

mark_k · 25 November 2017, 19:26

Quote:

Originally Posted by Toni Wilen

I can hook scsi tape emulation to ATAPI but question is: what should identify packet device -command return?

A quick Google search seems to suggest that people did manage to use ATAPI tape drives with real Amigas.

Wouldn't the IDENTIFY PACKET DEVICE response be very similar to that for an ATAPI CD/DVD drive? Tape software would issue INQUIRY and check the device type and things would hopefully just work???

Toni Wilen · 25 November 2017, 20:19

Quote:

Originally Posted by mark_k

A quick Google search seems to suggest that people did manage to use ATAPI tape drives with real Amigas.

Wouldn't the IDENTIFY PACKET DEVICE response be very similar to that for an ATAPI CD/DVD drive? Tape software would issue INQUIRY and check the device type and things would hopefully just work???

Possibly but it would be nice to have contents that spec says (if it exists)

ATAPI Tape is now supported, idefix + scsiquery at least detects the type of device.

mark_k · 25 November 2017, 21:53

Quote:

Originally Posted by Saghalie

I tested ABackup, Diavolo and Quarterback and they all work, although Quarterback always reports that the tape is not a valid QuarterBack tape (even though it is).

Here's some info which will hopefully allow Toni to fix the Quarterback issue. (Maybe move this to a separate thread if this post is too long?)

I configured a tape drive connected to GVP SCSI and used QuarterBack 6.1 to back up a small amount of data then tried to restore it.

On starting Quarterback:
TAPEEMU: 12.00.00.00.24.00
TAPEEMU INQUIRY
TAPEEMU REPLY: 01.80.02.02.20.00.00.00.55.41.45.20.20.20.20.20.53.43.53.49.20.54.41.50.45.20.20.20.20.20.20.20.30.2E.31.20.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 1A.00.00.00.04.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.

On doing a (small) backup:
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 1A.00.00.00.04.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.
...
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.00.00.00.00.00.00.00.08.00.00.00.00.00.00.00.00
TAPEEMU: 05.00.00.00.00.00
TAPEEMU READ BLOCK LIMITS
TAPEEMU REPLY: 00.00.02.00.02.00.
TAPEEMU: 1A.00.00.00.0C.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.00.00.00.00.00.00.02.00.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 1A.00.10.00.1C.00
TAPEEMU MODE SENSE PC=0 CODE=16 DBD=0
TAPEEMU SENSE: 70.00.05.00.00.00.00.00.00.08.00.00.24.00.00.00.00.00.
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.05.00.00.00.00.00.00.08.00.00.24.00.00.00.00.00
TAPEEMU: 15.00.00.00.0C.00
TAPEEMU MODE SELECT BUFM=1 BDL=8 Density=0 NB=0 BL=512
...
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.00.00.00.00.00.00.00.08.00.00.00.00.00.00.00.00
TAPEEMU: 0A.01.00.00.C8.00
TAPEEMU WRITE 102400 (200, 1)
...
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
TAPEEMU: 1A.00.10.00.1C.00
TAPEEMU MODE SENSE PC=0 CODE=16 DBD=0
TAPEEMU SENSE: 70.00.05.00.00.00.00.00.00.00.00.00.24.00.00.00.00.00.
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.05.00.00.00.00.00.00.00.00.00.24.00.00.00.00.00
SCSI command 10, no direction specified!
SCSI command 10, no direction specified!
TAPEEMU: 10.00.00.00.01.00
TAPEEMU WRITE FILEMARK 1
TAPEEMU: 17.00.00.00.00.00
TAPEEMU RELEASE UNIT

On quitting QuarterBack:
On quitting Quarterback:
TAPEEMU: 12.00.00.00.24.00
TAPEEMU INQUIRY
TAPEEMU REPLY: 01.80.02.02.20.00.00.00.55.41.45.20.20.20.20.20.53.43.53.49.20.54.41.50.45.20.20.20.20.20.20.20.30.2E.31.20.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
TAPEEMU: 1A.00.00.00.04.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.
TAPEEMU: 1A.00.00.00.0C.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.00.00.00.00.00.00.02.00.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 01.01.00.00.00.00
TAPEEMU: REWIND. IMMED=1

The backup process caused WinUAE to create two files:
00000.tape is 102400 bytes long.
00001.tape is empty (0 bytes).
index.tape is 22 bytes long, containing this text:
00000.tape[linefeed]00001.tape[linefeed]

On attempting to restore the backup:
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 1A.00.00.00.04.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.
TAPEEMU: 12.00.00.00.24.00
TAPEEMU INQUIRY
TAPEEMU REPLY: 01.80.02.02.20.00.00.00.55.41.45.20.20.20.20.20.53.43.53.49.20.54.41.50.45.20.20.20.20.20.20.20.30.2E.31.20.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 16.00.00.00.00.00
TAPEEMU RESERVE UNIT
TAPEEMU: 1A.00.00.00.04.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.
TAPEEMU: 1A.00.00.00.0C.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.00.00.00.00.00.00.02.00.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 01.00.00.00.00.00
TAPEEMU: REWIND. IMMED=0
TAPEEMU: 05.00.00.00.00.00
TAPEEMU READ BLOCK LIMITS
TAPEEMU REPLY: 00.00.02.00.02.00.
TAPEEMU: 1A.00.00.00.0C.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.00.00.00.00.00.00.02.00.
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 1A.00.10.00.1C.00
TAPEEMU MODE SENSE PC=0 CODE=16 DBD=0
TAPEEMU SENSE: 70.00.05.00.00.00.00.00.00.08.00.00.24.00.00.00.00.00.
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.05.00.00.00.00.00.00.08.00.00.24.00.00.00.00.00
TAPEEMU: 15.00.00.00.0C.00
TAPEEMU MODE SELECT BUFM=1 BDL=8 Density=0 NB=0 BL=512
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.00.00.00.00.00.00.00.08.00.00.00.00.00.00.00.00
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.00.00.00.00.00.00.00.08.00.00.00.00.00.00.00.00
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 08.01.00.04.00.00
TAPEEMU READ 524288 (1024, 1)
TAPEEMU DIR: File 'C:\Users\admin\Desktop\WinUAE_shared\Tape_test\index.tape'
TAPEEMU: end of tape
-> READ 22 bytes
TAPEEMU READ FILE END, 523776 remaining
TAPEEMU SENSE: F0.00.C0.00.00.03.FF.00.00.00.00.00.00.01.00.00.00.00.
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
F0.00.C0.00.00.03.FF.00.00.00.00.00.00.01.00.00.00.00
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 03.00.00.00.20.00
REQUEST SENSE 32 (18 -> 18)
70.00.40.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00
TAPEEMU: 00.00.00.00.00.00
TAPEEMU: 1A.00.00.00.04.00
TAPEEMU MODE SENSE PC=0 CODE=0 DBD=0
TAPEEMU REPLY: 0B.00.00.08.

The problem seems to be, QuarterBack tried to read (up to) 1024 blocks. WinUAE should return the 102400 bytes, but instead it only returns 22, which is the size of the index.tape file (and not a multiple of the block size of course).
Also the EOM bit is set in byte 2 of sense data. It shouldn't be since you're not at the end of the tape.

25 November 2017, 01:31	#6
emufan Registered User Join Date: Feb 2012 Location: #DrainTheSwamp Posts: 4,545	the read/write in "Add Scsi Tape drive" ? I just found that config, r/w is greyed out. #1) with my experiments, i'm stuck with "TAPE: couldnt be opened". doesnt matter. so your problem is now, abackup and others do not work, since they want you to insert a tape? Last edited by emufan; 25 November 2017 at 01:41.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kickstart 1.3 with scsi.device	8bitbubsy	support.Hardware	53	06 February 2018 13:14
Which scsi.device for emulation?	MartinW	support.WinUAE	17	04 September 2017 00:56
What is 2nd.scsi.device	videofx	support.Hardware	2	25 May 2014 18:45
Instaling SCSI.DEVICE in CWB 3.9	paulo_becas	support.Other	13	21 April 2014 15:57
Which scsi.device?	dannyp1	support.Apps	7	25 January 2012 22:10

24 November 2017, 23:05	#1
Saghalie Registered User Join Date: Nov 2014 Location: FT Lewis, WA Posts: 374	scsi.device I think I missed something. I'm trying to get the TAPE device working in A1200 to do backups so I don't have to make a dirt load of ADFs ... but I can't get the TAPE device to work in A1200 because the scsi.device is not found. The software for TAPE backups (ABackup, Diovolo, HDTools etc) all look for the scsi.device and won't work. Using AMIX and a config for OS4.1 - I don't have an issue. It works great. I'm just wondering if I missed something where the scsi.device isn't supported anymore in A1200, A500? I attached DKB/GVP etc devices with no luck either. Can someone give me some advice? Thanks!

25 November 2017, 00:18	#2
emufan Registered User Join Date: Feb 2012 Location: #DrainTheSwamp Posts: 4,545	in the icon information of the apps, look for a tooltype DEVICE (most often used), and try uaescsi.device. DEVICE=uaescsi.device <push enter in that line then save> in config expansion -> build in expansion -> you may enable A600/A1200/A4000 IDE (Commodore). not sure if it will help at all, but take alook.

25 November 2017, 02:23	#11
Saghalie Registered User Join Date: Nov 2014 Location: FT Lewis, WA Posts: 374	Got it working with GVP

25 November 2017, 09:32	#13
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	TAPE is SCSI, not IDE. Don't attempt to use it with IDE controllers. Otherwise: not enough information.

25 November 2017, 14:18	#14
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,335	There were ATAPI tape drives. I don't know whether it was possible to use one on a real Amiga. Maybe with IDEfix97? For using a backup program, a good alternative is to back up to a file in a shared folder, assuming the backup program supports that. I think QuarterBack does.

25 November 2017, 15:30	#15
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	I can hook scsi tape emulation to ATAPI but question is: what should identify packet device -command return?

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)