Device names (DH0:, CDH0:, etc.) help on A2000

[blakespot]

Hey there.

I have a 4GB CF card that came to me preformatted / partitioned with some Amiga stuff on it. It's part of a SCSI / IDE converter board kit.

These are the partitions:

CDH0: 2GB
CDH1: 999MB
CDH2: 1GB

So I copied my old physical disk (720MB) content to CDH1: after formatting it. I then removed that disk (wanted it out). So the boot volume I want to go forward with is on CDH1:.

Is this fine? Is it ok to have my Work or Data volume the larger CDH0: (lower #)? A lot of my boot scripts reference DH0: so I need to change them to reflect the new device names. I could rename the devices I guess, to make CDH1: DH0: I guess, but I kind of like the C prefix for card.

Is it easy to just make the boot called CDH0:, renaming the 2GB part CDH1: for my own pref?

Also - how do I set default booting when the system comes up? It's a 3.1 ROM A2000. I can select with double mouse buttons at boot, but how do I make default boot one of these volumes in particular?

Thanks.




bp

[zipper]

You can rename them whatever you want - but you need to edit all assigns to the new name. Change the boot priority with HDToolbox - the highest bootable partition will boot; keep the priority under 5 (floppy).

[blakespot]

You can rename them whatever you want - but you need to edit all assigns to the new name. Change the boot priority with HDToolbox - the highest bootable partition will boot; keep the priority under 5 (floppy).

Thanks, edit the device name how (from cli)?




bp

[zipper]

HDToolbox

[blakespot]

HD Toolbox can't even see any of the disks on the system.

Am using a Phase 5 A2060's SCSI controller. I installed the latest Phase 5 SCSI-Tools and those tools seem not to let me rename a partition / volume. I can kill, create though.

Am I out of luck? Thanks.




bp

[nyteschayde]

As far as your scripts go, I've found it very helpful to make an assign early on for sys: to whatever partition you want then have everything relative to sys:. This decreases the number of places that you need to change if you ever do this again (or set up multi-os boot configs, etc...)

[blakespot]

As far as your scripts go, I've found it very helpful to make an assign early on for sys: to whatever partition you want then have everything relative to sys:. This decreases the number of places that you need to change if you ever do this again (or set up multi-os boot configs, etc...)

I have something like that going, but not fully - need to get on that.

Still, I would like to rename the devices, and HD Toolbox sees nothing on the system. Hmm.




bp

[Matt_H]

There's a tooltype in HDToolbox that tells it which device to check. By default it's scsi.device, so change that to whatever the 2060's device is called (2060scsi.device, maybe?)

[paul1981]

there's a tooltype in hdtoolbox that tells it which device to check. By default it's scsi.device, so change that to whatever the 2060's device is called (2060scsi.device, maybe?)

You beat me to it whilst I was going to extreme efforts to show the chap a picture. :laughing:
[attach]2971[/attach]

[zipper]

so change that to whatever the 2060's device is called (2060scsi.device, maybe?)

That's it.

[pVC]

These are the partitions:

CDH0: 2GB
CDH1: 999MB
CDH2: 1GB

So I copied my old physical disk (720MB) content to CDH1: after formatting it. I then removed that disk (wanted it out). So the boot volume I want to go forward with is on CDH1:.

Is this fine? Is it ok to have my Work or Data volume the larger CDH0: (lower #)? A lot of my boot scripts reference DH0: so I need to change them to reflect the new device names. I could rename the devices I guess, to make CDH1: DH0: I guess, but I kind of like the C prefix for card.

Is it easy to just make the boot called CDH0:, renaming the 2GB part CDH1: for my own pref?

One option is to keep those CDH0, CDH1 and CDH2, if you like them, but then add "Assign DH0: CDH1:" in your startup-sequence or user-startup (depending when you start pointing to that device on your own stuff, probably enough in user-startup).

For these kinds of situations it's good to make assigns and other configurations to SYS: rather than fixed partition names. Then you can copy system around more easily. SYS: points always to boot device.

I have also found useful to add for example Utils: assign and configure all programs to use that rather than fixed path again. Then it doesn't matter where or which disk the programs are located, until I have that assign set where ever I want it.

[blakespot]

Thanks, all.

Changing the tooltype to 2060scsi.device did it. I should'e thought of that.

I just went ahead and changed things to DH0: -> DH2:, terms I am used to. I have an assign to SYS: in my startup scripts, but not as early as it should be.

Actually, my startup scripts boot either WB1.3 or 3.1 on the same partition based on the ROM version - I have a switcher. Given that I am using the A2060 as the SCSI controller now, I can't really boot into 1.3 with that setup, I think, so I may just remove the extra script abstraction and keep to 3.1 always.

I do have an A1000 over on the other desk, so... :-)




bp