Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Brian on October 27, 2013, 12:57:25 PM
-
Is there a way to determine with a script and with some degree of surtanty that an inserted floppy is a Commodore 2090 boot disk? I'm thinking search expansion/hddisk.info for "product=514/1", search startup-seq for binddrivers and "assign SYS:" or "assign >NIL: SYS:" and search devs/mountlist for "hddisk.device".
That aught to be enough to determine it or am I missing something?
-
Does the 2090 bootdisk have a unique volume name? If so, you could do an If/Warn-type script with that. Or maybe if a file has a particular size?
-
Does the 2090 bootdisk have a unique volume name? If so, you could do an If/Warn-type script with that. Or maybe if a file has a particular size?
I wish it was as simple as finding a unique lable... as far as I know no unique file or filesize either.
-
Is there a way to determine with a script and with some degree of surtanty that an inserted floppy is a Commodore 2090 boot disk? I'm thinking search expansion/hddisk.info for "product=514/1", search startup-seq for binddrivers and "assign SYS:" or "assign >NIL: SYS:" and search devs/mountlist for "hddisk.device".
That aught to be enough to determine it or am I missing something?
Not sure what you are trying to do,but if you need the real bootdisk for the 2090 i believe this is it:
http://amiga.resource.cx/exp/a2090
-
Not sure what you are trying to do,but if you need the real bootdisk for the 2090 i believe this is it:
http://amiga.resource.cx/exp/a2090
I want to make a script that ask for the 2090 bootdisk and then copy files to it, however I don't want to force it to any specific drive and I also want to make sure the disk is actually a 2090 bootdisk before the script continues.
Since the label is not fixed, the hddisk isn't 2090 only and the mountlist isn't unique I need to check several things to get a good guestimate and with the checks I mentioned I think it should work quite well and I can always have the user confirm the "detection". :D
-
Well, the mountlist doesn't seem to be requiered in some circumstances so can't use that... damn.
-
It would take longer, but you could have your script ADF the disk and check the CRC of the image...
-
Sorry but that wouldn't work since a 2090 bootdisk can and should be edited depending on disks and partitions and what OS you're using it with.
-
You could simply pop up a selector if there is more than one disk in DF0:..DF3:, listing the volume names.