| Title: | AMIGA NOTES |
| Notice: | Join us in the *NEW* conference - HYDRA::AMIGA_V2 |
| Moderator: | HYDRA::MOORE |
| Created: | Sat Apr 26 1986 |
| Last Modified: | Wed Feb 05 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5378 |
| Total number of notes: | 38326 |
I installed a GVP HardCard in my A2000 recently. GVP assigns DH0:
to the hardcard even though it is a SCSI device. I am not sure why.
At any rate, this assignment makes it impossible (thus far) for
me to use the A2090 with my other drive (an ST-506 type). Even when
I attempt to define the first partition on the ST-506 as DF1:, the
system overrides that and calls it DH0:. When I do an INFO, the
list shows two DH0: (the GVP and the ST-506). Of course the ST-506
suddenly becomes the default, and accesses to the SCSI fail.
Anyone know why GVP chose DH0: and if it can be changed? I'd rather
not experiment. Just the facts ma'am.
Paul
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2197.1 | Modify MountList??? | DPDMAI::ANDERSONA | Tue Feb 07 1989 22:32 | 10 | |
I do not have a A2000 or GVP's disk but I do have a A500 and a C.Ltd
controller so I may be out in left field. But I thought that the
disk name was whatever you wanted it to be. In your sys:Devs/MountList
the first line tells the system what the device name is and what
driver it is to use. I use DH0: but I could have used HD0: or any
other group of characters. So maybe you only have to modify the
mountlist. That is unless GVP dos not use the standard mount method.
Alan
| |||||
| 2197.2 | When I don't know, I guess | TLE::RMEYERS | Randy Meyers | Tue Feb 14 1989 16:17 | 27 |
Re: .1 I don't have Commodore's controller or GVP's controller. So I could be way off base here too. >But I thought that the disk name was whatever you wanted it to be. In >your sys:Devs/MountList the first line tells the system what the device >name is and what driver it is to use. I use DH0: but I could have used >HD0: or any other group of characters. There is an alternative to the mountlist method of mounting a disk that may be what is causing trouble. One way to configure hardware to your system is to drop an icon for it in the "Expansion" drawer of the boot disk. When the system boots, it examines the expansion drawer, looks at the icons, checks to see if the device is attached to the expansion buss, and then runs the program associated with that icon. That program may, if it wishes, mount a device based on any special knowledge it has without looking at the Mountlist. I think Commodore uses this technique to automatically mount the first partition of the first disk connected to their controller. If GVP does the same, and they both hardwire the name DH0: for that partition, then their is a major conflict. If this is the problem, trusty NEWZAP, the binary file editor may help. Change the DH0: in one of the expansion drawer programs to something else. (So much for "I want answers, not experiments"). | |||||