Amiga.org
Amiga computer related discussion => Amiga Hardware Issues and discussion => Topic started by: Rooster on June 14, 2005, 04:35:17 AM
-
Was there a change in the boot process on the A2000 vs. the A500? My 500 (from memory) would boot floppies when powered up/reset if it was present, and if not it would boot off the SupraDrive..
I've tried various floppies to boot on this A2000 and none of them seem to boot in it, yet they do in the 500. Only difference is 500 has 2.0ROM whereas 2000 has 1.3ROM. Thinking there's a configuration option somewhere? Help? (workbench 1.3)
-
KS 1.3, from memory, will only allow you to boot from df0: whereas KS 2.04 and above will let you boot from any floppy.
-
kickstart 1.3 floppies are NOT fastfilesystem
You can boot fastfilesystem floppies only in KS2.04 or above
If the floppies your trying to load with A2000 with KS1.3 are FFS, then no.. they cannot boot
The filesystem is unrecognised, meaning the bootsector is different, making the KS1.3 machine ignore the boot sequence.
Hope that helps
-
If they were FFS floppies, they would still be read normally once booted up, right? Because that's the case here..
-
FastFileSystem is not ROM resident inside the KS1.2 or KS1.3 Only with KS2.04 and above was the FastFileSystem made into the Kickstart ROM.
Your a500 with KS2.04 will recognise OFS, FFS and many other file formats, where as the A2000 with KS1.3 can only boot OFS (OldFileSystem or OriginalFileSystem) disks.
The file formats are different, the total storage of the disks is different. The code in the boot sector is different. You cannot "boot" from a disk the ROM cannot recognise.
KS1.3 Harddrives recognise FFS only when the FastFileSystem file itself is stored in the Rigid Disk Block.
If you need files from one machine to the other, format a floppy on the A2000 (OFS) and copy files to that floppy from the A500 (FFS)
-
There is one further possibility: I guess the SupraDrive is a HDD, right ? So if the guy who installed the HDD chose a higher boot priority for it than 5, then the Amiga will not even try to boot from floppy. The floppy drive's priority is 5 and the Kickstart always boots from the drive with the highest priority.
Also bootiing from df1..df3 with Kickstart 2.0+ only works if the HDD's boot priority is less than -3 because DF1 and prio -1, DF2 -2 and so on. Usually the HDD's prio is 0, so with a HDD attached it will only boot from DF0 if a disk is present.
Bye,
Thomas
-
This is what I was hoping for. A boot priority.. Where/how can this setting be changed? I don't know for certain what filesystem is on the floppies, but they've ranged in years sine I bought the 500, which was when it came out... Surely some of them must be 1.2/1.3's.. I would think!
-
:bump:
-
To me it seems like a hardware problem, misaligned fdd heads (if none of diskettes work) or maybe dust?
edit: sorry, I was wrong, you can read floppys once booted from supra? Why dont you softkick 2.04 (zkick or whatever) to be sure its ROM. BTW, you can get KS3.1 from Vesalia its about 18 euros