![]() |
![]() |
#1 |
Registered User
Join Date: Nov 2009
Location: Top of the world
Posts: 188
|
![]()
On the few Amigas that came with both SCSI and IDE one controller would be scsi.device and the other 2nd.scsi.device. And adding a Commodore Zorro SCSI-controller would make it 3rd.scsi.device (I believe some 3rd-party controllers also follows this standard).
This scheme supports nine controllers up to and including 8th.scsi.device, and lets HDToolbox* update the required "metadata" (sorry do not know the right Amiga-term) on the other disks in the system when one disk is added or removed form the system. The problem is that all this breaks down once you set "SCSI_DEVICE_NAME" in ToolTypes, then it will only find the specified controller. So my request is: Can we please have an option to set the names of uaehf.device and uaescsi.device to 2nd.scsi.device trough 8th.scsi.device, either manually or automatically like commodore controllers do? *Meaning the WB2.1/3.0/3.1/3.1.4 versions of HDToolbox, I have not checked how 3.5 3.9 versions work. Last edited by hceline; 04 January 2019 at 23:39. Reason: Spelling |
![]() |
![]() |
#2 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,609
|
No, sorry. At least some versions of setpatch will assume (*_)scsi.device = official Commodore driver and causes glitches/crashes if it gets patched.
(Why uaescsi.device? It is only for CDROMs, it makes no sense to use it with hdtoolbox) |
![]() |
![]() |
#3 | |
Registered User
Join Date: Nov 2009
Location: Top of the world
Posts: 188
|
Quote:
A mistake, I believed it was used for direct access to physical drives also. |
|
![]() |
![]() |
#4 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,609
|
I still don't want to do it because:
- 3rd party controllers should use custom device name. Those weird ones that use scsi.device are doing it wrong. - It can get really confusing if device initialization order change. - Use A590/A2091 or built-in IDE emulation if you want to use scsi.device ![]() - Sooner or later someone else renames the device without understanding all the possible side-effects: weird bug reports appear. |
![]() |
![]() |
#5 |
Registered User
Join Date: Nov 2009
Location: Top of the world
Posts: 188
|
Ok I guess I was wrong, I believed that this was the right way even for 3rd party controllers. Based on the fact that HDToolbox wants to keep the drives in sync by keeping a list with info of other drives on each drive. Which becomes impossible if you insert a 3rd-party controller which does not present the name 3rd.scsi.device (using a A4000T as example).
|
![]() |
![]() |
#6 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,609
|
HDtoolbox isn't (at least officially) supposed to be used with 3rd party controllers. (but it still is the best choice..)
I think it was OS3.5 or 3.9 version that added some device query option to make it easier to use with 3rd party device names. |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Feature Request] Filter-> Extra Line Option | Zilog | support.WinUAE | 2 | 17 July 2018 02:32 |
[Request New Feature] Filter Option | Zilog | support.WinUAE | 18 | 01 March 2016 18:00 |
HDToolbox and compactflash.device | burf2000 | support.Apps | 3 | 01 September 2015 10:01 |
Matching device names with volume names. | Thorham | Coders. System | 2 | 27 July 2015 12:20 |
uaehf.device and HDToolbox: Error 224 reading device description | Ebster | support.WinUAE | 3 | 16 September 2008 09:24 |
|
|