Multiple mass storage controllers on Amiga 500 or 2000
up vote
6
down vote
favorite
I'm in the process of restocking a lost collection of retro machines, including a couple of A500s, a 500+ and 2 A2000s (rev 4.1 and 6) in various states of disrepair. For one of the 2000s I would like to have the ability to transfer existing data and programs from a SCSI hard disk to an IDE unit but I really can't work out how I can have 2 mass storage controllers in a single machine, either on a 500 or a 2000.
For instance, I have an A500+ with a Wicher accelerator installed, along with an A590 hard drive. I can only access one mass storage controller at a time - if the Wicher is in, the A590 isn't available. In my head this is something like device ID conflicts and I would love to be able to archive off all this lovely stuff from both the A590 and the internal SCSI drive in one of the 2000s (Wicher experiments pending) - and I may get to a point where I want CD/DVD storage and more hard disks in the 2000 than the Wicher can provide. Does anyone have any pointers or hints, or even better any experience of doing the same without resorting to SCSI <-> IDE adaptors?
EDIT : The A590 is using an XT drive, NOT a SCSI drive!
amiga storage scsi ide
asked 17 hours ago
DrMistry
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
|
show 1 more comment
up vote
6
down vote
favorite
I'm in the process of restocking a lost collection of retro machines, including a couple of A500s, a 500+ and 2 A2000s (rev 4.1 and 6) in various states of disrepair. For one of the 2000s I would like to have the ability to transfer existing data and programs from a SCSI hard disk to an IDE unit but I really can't work out how I can have 2 mass storage controllers in a single machine, either on a 500 or a 2000.
For instance, I have an A500+ with a Wicher accelerator installed, along with an A590 hard drive. I can only access one mass storage controller at a time - if the Wicher is in, the A590 isn't available. In my head this is something like device ID conflicts and I would love to be able to archive off all this lovely stuff from both the A590 and the internal SCSI drive in one of the 2000s (Wicher experiments pending) - and I may get to a point where I want CD/DVD storage and more hard disks in the 2000 than the Wicher can provide. Does anyone have any pointers or hints, or even better any experience of doing the same without resorting to SCSI <-> IDE adaptors?
EDIT : The A590 is using an XT drive, NOT a SCSI drive!
amiga storage scsi ide
asked 17 hours ago
DrMistry
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Should theoretically be possible. Do you have RAM on both the Wicher and A590, and if so is all the RAM showing up properly? If not that might be part of your problem, you could try disabling the RAM on the A590 (JP1).
– mnem
15 hours ago
1
I tried both setting the RAM jumper on the A590 to Amnesia, and both removing the SIMM from the Wicher and disabling the onboard MMU. No change unfortunately!
– DrMistry
15 hours ago
Is the A590 showing up in autoconfig at least? Can you see it in sysinfo, etc?
– mnem
15 hours ago
1
Nope, no sign of it at all. The Wicher appears as desired whatever the RAM and IDE configuration is. I'm not in front of the machine right now, but I will as soon as I can.
– DrMistry
15 hours ago
1
That would make sense - I also have an A570 CD Drive which won't play with the Wicher. I'll contact the hardware dev and see what I can find out.
– DrMistry
13 hours ago
|
show 1 more comment
up vote
6
down vote
favorite
up vote
6
down vote
favorite
I'm in the process of restocking a lost collection of retro machines, including a couple of A500s, a 500+ and 2 A2000s (rev 4.1 and 6) in various states of disrepair. For one of the 2000s I would like to have the ability to transfer existing data and programs from a SCSI hard disk to an IDE unit but I really can't work out how I can have 2 mass storage controllers in a single machine, either on a 500 or a 2000.
For instance, I have an A500+ with a Wicher accelerator installed, along with an A590 hard drive. I can only access one mass storage controller at a time - if the Wicher is in, the A590 isn't available. In my head this is something like device ID conflicts and I would love to be able to archive off all this lovely stuff from both the A590 and the internal SCSI drive in one of the 2000s (Wicher experiments pending) - and I may get to a point where I want CD/DVD storage and more hard disks in the 2000 than the Wicher can provide. Does anyone have any pointers or hints, or even better any experience of doing the same without resorting to SCSI <-> IDE adaptors?
EDIT : The A590 is using an XT drive, NOT a SCSI drive!
amiga storage scsi ide
asked 17 hours ago
DrMistry
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I'm in the process of restocking a lost collection of retro machines, including a couple of A500s, a 500+ and 2 A2000s (rev 4.1 and 6) in various states of disrepair. For one of the 2000s I would like to have the ability to transfer existing data and programs from a SCSI hard disk to an IDE unit but I really can't work out how I can have 2 mass storage controllers in a single machine, either on a 500 or a 2000.
For instance, I have an A500+ with a Wicher accelerator installed, along with an A590 hard drive. I can only access one mass storage controller at a time - if the Wicher is in, the A590 isn't available. In my head this is something like device ID conflicts and I would love to be able to archive off all this lovely stuff from both the A590 and the internal SCSI drive in one of the 2000s (Wicher experiments pending) - and I may get to a point where I want CD/DVD storage and more hard disks in the 2000 than the Wicher can provide. Does anyone have any pointers or hints, or even better any experience of doing the same without resorting to SCSI <-> IDE adaptors?
EDIT : The A590 is using an XT drive, NOT a SCSI drive!
amiga storage scsi ide
amiga storage scsi ide
asked 17 hours ago
DrMistry
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 17 hours ago
DrMistry
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 15 hours ago
asked 17 hours ago
DrMistry
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 17 hours ago
DrMistry
335
asked 17 hours ago
DrMistry
335
335
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
DrMistry is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Should theoretically be possible. Do you have RAM on both the Wicher and A590, and if so is all the RAM showing up properly? If not that might be part of your problem, you could try disabling the RAM on the A590 (JP1).
– mnem
15 hours ago
1
I tried both setting the RAM jumper on the A590 to Amnesia, and both removing the SIMM from the Wicher and disabling the onboard MMU. No change unfortunately!
– DrMistry
15 hours ago
Is the A590 showing up in autoconfig at least? Can you see it in sysinfo, etc?
– mnem
15 hours ago
1
Nope, no sign of it at all. The Wicher appears as desired whatever the RAM and IDE configuration is. I'm not in front of the machine right now, but I will as soon as I can.
– DrMistry
15 hours ago
1
That would make sense - I also have an A570 CD Drive which won't play with the Wicher. I'll contact the hardware dev and see what I can find out.
– DrMistry
13 hours ago
|
show 1 more comment
Should theoretically be possible. Do you have RAM on both the Wicher and A590, and if so is all the RAM showing up properly? If not that might be part of your problem, you could try disabling the RAM on the A590 (JP1).
– mnem
15 hours ago
1
I tried both setting the RAM jumper on the A590 to Amnesia, and both removing the SIMM from the Wicher and disabling the onboard MMU. No change unfortunately!
– DrMistry
15 hours ago
Is the A590 showing up in autoconfig at least? Can you see it in sysinfo, etc?
– mnem
15 hours ago
1
Nope, no sign of it at all. The Wicher appears as desired whatever the RAM and IDE configuration is. I'm not in front of the machine right now, but I will as soon as I can.
– DrMistry
15 hours ago
1
That would make sense - I also have an A570 CD Drive which won't play with the Wicher. I'll contact the hardware dev and see what I can find out.
– DrMistry
13 hours ago
Should theoretically be possible. Do you have RAM on both the Wicher and A590, and if so is all the RAM showing up properly? If not that might be part of your problem, you could try disabling the RAM on the A590 (JP1).
– mnem
15 hours ago
Should theoretically be possible. Do you have RAM on both the Wicher and A590, and if so is all the RAM showing up properly? If not that might be part of your problem, you could try disabling the RAM on the A590 (JP1).
– mnem
15 hours ago
1
1
I tried both setting the RAM jumper on the A590 to Amnesia, and both removing the SIMM from the Wicher and disabling the onboard MMU. No change unfortunately!
– DrMistry
15 hours ago
I tried both setting the RAM jumper on the A590 to Amnesia, and both removing the SIMM from the Wicher and disabling the onboard MMU. No change unfortunately!
– DrMistry
15 hours ago
Is the A590 showing up in autoconfig at least? Can you see it in sysinfo, etc?
– mnem
15 hours ago
Is the A590 showing up in autoconfig at least? Can you see it in sysinfo, etc?
– mnem
15 hours ago
1
1
Nope, no sign of it at all. The Wicher appears as desired whatever the RAM and IDE configuration is. I'm not in front of the machine right now, but I will as soon as I can.
– DrMistry
15 hours ago
Nope, no sign of it at all. The Wicher appears as desired whatever the RAM and IDE configuration is. I'm not in front of the machine right now, but I will as soon as I can.
– DrMistry
15 hours ago
1
1
That would make sense - I also have an A570 CD Drive which won't play with the Wicher. I'll contact the hardware dev and see what I can find out.
– DrMistry
13 hours ago
That would make sense - I also have an A570 CD Drive which won't play with the Wicher. I'll contact the hardware dev and see what I can find out.
– DrMistry
13 hours ago
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
5
down vote
accepted
The Amiga can support multiple mass storage controllers, subject to the following necessary limitations:
- Any time multiple controllers are using AutoConfig, each controller must correctly support the AutoConfig protocol. This means it must pass the token to other controllers on the bus so that each controller gets a chance to configure itself.
- Each mass storage controller needs a device driver, and the name of the device drivers should not conflict.
I suspect you have an issue with #1 on your A500 because the CPU socket AutoConfig board does not allow other AutoConfig boards to co-exist on the Zorro bus. That's why the Amiga does not see the A590 when the CPU socket board is installed.
The Amiga OS has a specific solution for unique naming of the device drivers when you have both the internal IDE and a Commodore SCSI controller installed. The IDE interface will use "scsi.device", and the SCSI controller will use "2nd.scsi.device". Lots of 3rd party IDE controllers also use "scsi.device", making it compatible with this solution. And, lots of 3rd party SCSI controllers use their own driver (e.g. "gvpscsi.device") to also avoid naming conflicts when there are multiple mass storage controllers.
Of course, the usual way of cloning HDD's on an Amiga is by having multiple HDD's connected up to a single controller. That does not seem to be an easy option for your circumstances, since you have a mix of ST-506 and SCSI HDD's and limited no ability to move the controllers between machines. I think you are best off getting a second SCSI HDD for backing up the A2000 using its existing controller, whilst simply using floppies to backup the A590 without the CPU socket board installed.
answered 13 hours ago
Brian H
16.7k60140
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
1
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
accepted
The Amiga can support multiple mass storage controllers, subject to the following necessary limitations:
- Any time multiple controllers are using AutoConfig, each controller must correctly support the AutoConfig protocol. This means it must pass the token to other controllers on the bus so that each controller gets a chance to configure itself.
- Each mass storage controller needs a device driver, and the name of the device drivers should not conflict.
I suspect you have an issue with #1 on your A500 because the CPU socket AutoConfig board does not allow other AutoConfig boards to co-exist on the Zorro bus. That's why the Amiga does not see the A590 when the CPU socket board is installed.
The Amiga OS has a specific solution for unique naming of the device drivers when you have both the internal IDE and a Commodore SCSI controller installed. The IDE interface will use "scsi.device", and the SCSI controller will use "2nd.scsi.device". Lots of 3rd party IDE controllers also use "scsi.device", making it compatible with this solution. And, lots of 3rd party SCSI controllers use their own driver (e.g. "gvpscsi.device") to also avoid naming conflicts when there are multiple mass storage controllers.
Of course, the usual way of cloning HDD's on an Amiga is by having multiple HDD's connected up to a single controller. That does not seem to be an easy option for your circumstances, since you have a mix of ST-506 and SCSI HDD's and limited no ability to move the controllers between machines. I think you are best off getting a second SCSI HDD for backing up the A2000 using its existing controller, whilst simply using floppies to backup the A590 without the CPU socket board installed.
answered 13 hours ago
Brian H
16.7k60140
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
1
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
add a comment |
up vote
5
down vote
accepted
The Amiga can support multiple mass storage controllers, subject to the following necessary limitations:
- Any time multiple controllers are using AutoConfig, each controller must correctly support the AutoConfig protocol. This means it must pass the token to other controllers on the bus so that each controller gets a chance to configure itself.
- Each mass storage controller needs a device driver, and the name of the device drivers should not conflict.
I suspect you have an issue with #1 on your A500 because the CPU socket AutoConfig board does not allow other AutoConfig boards to co-exist on the Zorro bus. That's why the Amiga does not see the A590 when the CPU socket board is installed.
The Amiga OS has a specific solution for unique naming of the device drivers when you have both the internal IDE and a Commodore SCSI controller installed. The IDE interface will use "scsi.device", and the SCSI controller will use "2nd.scsi.device". Lots of 3rd party IDE controllers also use "scsi.device", making it compatible with this solution. And, lots of 3rd party SCSI controllers use their own driver (e.g. "gvpscsi.device") to also avoid naming conflicts when there are multiple mass storage controllers.
Of course, the usual way of cloning HDD's on an Amiga is by having multiple HDD's connected up to a single controller. That does not seem to be an easy option for your circumstances, since you have a mix of ST-506 and SCSI HDD's and limited no ability to move the controllers between machines. I think you are best off getting a second SCSI HDD for backing up the A2000 using its existing controller, whilst simply using floppies to backup the A590 without the CPU socket board installed.
answered 13 hours ago
Brian H
16.7k60140
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
1
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
add a comment |
up vote
5
down vote
accepted
up vote
5
down vote
accepted
The Amiga can support multiple mass storage controllers, subject to the following necessary limitations:
- Any time multiple controllers are using AutoConfig, each controller must correctly support the AutoConfig protocol. This means it must pass the token to other controllers on the bus so that each controller gets a chance to configure itself.
- Each mass storage controller needs a device driver, and the name of the device drivers should not conflict.
I suspect you have an issue with #1 on your A500 because the CPU socket AutoConfig board does not allow other AutoConfig boards to co-exist on the Zorro bus. That's why the Amiga does not see the A590 when the CPU socket board is installed.
The Amiga OS has a specific solution for unique naming of the device drivers when you have both the internal IDE and a Commodore SCSI controller installed. The IDE interface will use "scsi.device", and the SCSI controller will use "2nd.scsi.device". Lots of 3rd party IDE controllers also use "scsi.device", making it compatible with this solution. And, lots of 3rd party SCSI controllers use their own driver (e.g. "gvpscsi.device") to also avoid naming conflicts when there are multiple mass storage controllers.
Of course, the usual way of cloning HDD's on an Amiga is by having multiple HDD's connected up to a single controller. That does not seem to be an easy option for your circumstances, since you have a mix of ST-506 and SCSI HDD's and limited no ability to move the controllers between machines. I think you are best off getting a second SCSI HDD for backing up the A2000 using its existing controller, whilst simply using floppies to backup the A590 without the CPU socket board installed.
answered 13 hours ago
Brian H
16.7k60140
The Amiga can support multiple mass storage controllers, subject to the following necessary limitations:
- Any time multiple controllers are using AutoConfig, each controller must correctly support the AutoConfig protocol. This means it must pass the token to other controllers on the bus so that each controller gets a chance to configure itself.
- Each mass storage controller needs a device driver, and the name of the device drivers should not conflict.
I suspect you have an issue with #1 on your A500 because the CPU socket AutoConfig board does not allow other AutoConfig boards to co-exist on the Zorro bus. That's why the Amiga does not see the A590 when the CPU socket board is installed.
The Amiga OS has a specific solution for unique naming of the device drivers when you have both the internal IDE and a Commodore SCSI controller installed. The IDE interface will use "scsi.device", and the SCSI controller will use "2nd.scsi.device". Lots of 3rd party IDE controllers also use "scsi.device", making it compatible with this solution. And, lots of 3rd party SCSI controllers use their own driver (e.g. "gvpscsi.device") to also avoid naming conflicts when there are multiple mass storage controllers.
Of course, the usual way of cloning HDD's on an Amiga is by having multiple HDD's connected up to a single controller. That does not seem to be an easy option for your circumstances, since you have a mix of ST-506 and SCSI HDD's and limited no ability to move the controllers between machines. I think you are best off getting a second SCSI HDD for backing up the A2000 using its existing controller, whilst simply using floppies to backup the A590 without the CPU socket board installed.
answered 13 hours ago
Brian H
16.7k60140
answered 13 hours ago
Brian H
16.7k60140
answered 13 hours ago
Brian H
16.7k60140
answered 13 hours ago
Brian H
16.7k60140
16.7k60140
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
1
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
add a comment |
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
1
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
iirc the A590 supports using an external SCSI drive along with the internal XT-IDE one at the same time. Doesn't fix his Wicher problem, but it would let him use the same external SCSI drive with both the A500 and A2000 for making backups.
– mnem
12 hours ago
1
1
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
Thanks, that sounds entirely logical and in line with what I've read elsewhere. My current plan is to use the plipbox I have running on the A500 and get another running on the A2000 - I can then lha and shift things around via a local FTP server. Really I'm just holding the 590 and 570 for nostalgic reasons, and have a stock A500 I can use them with when the mood takes hold!
– DrMistry
12 hours ago
add a comment |
DrMistry is a new contributor. Be nice, and check out our Code of Conduct.
DrMistry is a new contributor. Be nice, and check out our Code of Conduct.
DrMistry is a new contributor. Be nice, and check out our Code of Conduct.
DrMistry is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Retrocomputing Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fretrocomputing.stackexchange.com%2fquestions%2f8507%2fmultiple-mass-storage-controllers-on-amiga-500-or-2000%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Should theoretically be possible. Do you have RAM on both the Wicher and A590, and if so is all the RAM showing up properly? If not that might be part of your problem, you could try disabling the RAM on the A590 (JP1).
– mnem
15 hours ago
1
I tried both setting the RAM jumper on the A590 to Amnesia, and both removing the SIMM from the Wicher and disabling the onboard MMU. No change unfortunately!
– DrMistry
15 hours ago
Is the A590 showing up in autoconfig at least? Can you see it in sysinfo, etc?
– mnem
15 hours ago
1
Nope, no sign of it at all. The Wicher appears as desired whatever the RAM and IDE configuration is. I'm not in front of the machine right now, but I will as soon as I can.
– DrMistry
15 hours ago
1
That would make sense - I also have an A570 CD Drive which won't play with the Wicher. I'll contact the hardware dev and see what I can find out.
– DrMistry
13 hours ago