Posts by Aldebaran_Prime

Quote from iljitsch

.... now the first three cards are all recognized, only the CV64/3D is missing from the list. So it looks like the bootROM has an issue configuring the CV64/3D cards, as well as any cards that come later in the AutoConfig process.

I also have a Cybervision C64 RTG-Card installed before the Buddha - so eventually the reason of my difficulties to boot from wb_2.x by the 3000 bootstrap-ROM is the same. But because at the moment everythings works well after the exchange of the Rom by an 3.x , it has currently not he highest priority for me to change the ROMS back and test an other order of the cards. But eventually I will do this to get my AMAX II+ Card to work - this requires Kick 2.04 and WB2.1..

Anyway it is impressive to see how good the support of icomp is!

I ordered and just installed the Kickstart 3.x Rom from Cloanto instead my 1.5 Bootstrap ROMs in my A3000.

Now the Buddha with latest buddhascsi.device boots perfectly from any CF card quickly and have support for larger disks that 4 GB. From my side I don't need a modified ed firmware anymore.

Edit by admin:

CAUTION: iComp does not recommend Cloanto products. If you have a Cloanto Kickstart in your computer, we can no longer provide support.

I seems, that Iljitsch and I worked in parallel. Yesterday I also downgraded my Buddah as suggested by Jens. I experienced also, that most CF cards (1GB-8GB) which ran well before the downgrade, were not recognized anymore after the downgrade.

But the whole time the Installation DOM was recognized as drive - but not the also inserted CF card.

Also the Boot menue and HDToolbox directly recognized the Buddha as 2nd scsi controller:

Booting from BUDDHA_INST worked with the downgrated firmware, but also the installation program on the DOM did not recognized the CF card.

I tried all my CF cards, which I used before the downgrade - only this one, which was installed by the Buddha Installer with WB2.0 and default partitioning before the downgrade worked as before:

This ones with the same capacity and and also formated with the orginal buddhaScsi firmware did not work with the old eb firmware:

O.K. I can give it another try. Just to be sure, that I will do the right things:

1. I use this wiki page as instruction: http://wiki.icomp.de/wiki/Buddha_flashing

2. I will use the procedure for "20-year anniversary edition"

3. The tool BFlashTool will not need to change any jumpers to realease for flashing - just hold left mouse button during power-on

But I'm not sure where to find the elaborate firmware your are referencing to - Google gives no real hits for this. Or do I find this in the download section for Buddha? Which one? http://wiki.icomp.de/wiki/Buddha#Download

So, I just tested the approach from my last post:

1. copied the FastFileSystem from the L: of the original WB 2.04 Disk to CF-Card L:FastFileSystem2.04

2. Opened HDToolbox and there under advanved options deleted the FastFileSystem version 44.6 and the added the FastFileSystem2.04 = 36.104

3. Renamed the CF partition to WB_2.x

4. Switch off/on

5. Boot/Load Kickstart from SCSI and checked, that the CF Partition is still OK and bootable by Boot-Options screen -> the downgrade of the FFS from 44.6 to 36.104 did not delete anything

6. switch off and disconnect the SCSI drive (now only the Buddha CF card with the WB_2.x is connected

7. switch on again

Result is, that it does not work!

The Boostrap ROM Kickstart Menue only shows the dialog to load a kickstart, but does not offer an Hard-Drive option, just Floppy als seen on the screen 2 post earlier.

So I have no glue anymore what else we may test. My assumption is, that the Bootstrap ROM only recognizes real SCSI Hard Drives to load the superkickstart.

The only option may be, that something in the blocks before the first partition of the HD/CFCard can be stored to support the Bootstrap ROM of the A3000

I thought further about reasons and solutions.

I checked now the versions of the AOS/FFS on the original SCSI hard hisk

And the AOS/FFS version on the CF card:

As you can see, the FFS version on the CF card is 44.6 where the FFS on the original SCSI drive is 36.104.

The reason may be, that I used HDToolbox from my current Workbench installation to to set-up the CF partitions, not the HDToolbox from thr orginal Workbench installation floppy.

Eventually this new Fast File System Version prevents the ancient super-kickstart bootstrap ROM from finding the Kickstart on the CF Card??

So next step is, to install the orginal WB 2.04 FFS version onto the CF partition, rename the CF partition again to WB_2.x, remove the SCSI drive again and give it another try. But not this night anymore...

Quote from Jens

To my knowledge, the device name must be WB_2.x:, so no matter what boot device you choose, it will always look for the Kickstart file on the WB2.x: partition in the DEVS: directory.

Yes, absolutely agree! That is what I tested first: I named the new CF-Card partition in the HDToolbox as "WB_2.x" also the Name of the HD on operating system level was "WB_2.x" - details above in the log text.

Quote

Your attempt of keeping a different Kickstart on a different partition cannot work - it'll always load the Kickstart from the WB2.x: partition. So you'll have to live with booting 3.1 from a partition with a different name

at first I disconnected my SCSI drive with the same WB_2.x device name and tried to boot the kickstart from the CF partion. But this did not work either.

So after all fails I re-named the CF partition from WB_2.x to WB_3.x to can differentiate better in the boot-menue. Thats the picture from. I just wanted to show, that both partitions have the AOS/FFS and are bootable - works just after loading kickstart from SCSI.

On both partitions is Kickstart 40.70 as kickstart file in the DEVS-folder.

Hi together I'm the one with the open German support case. I have also an Amiga 3000 25 Mhz with Superkickstart Boot Rom and no "real" kickstart on the mainboard and just bought an Buddha IDE card.

After successfull hardware installation of the Buddha and connecting to a CF card adapter at first is was not possible to start the Installation program on the DOM - there was presentation error of the tool-UI in combination with my Cybervisin 64 card or Kick3.1 on my SCSI drive - however I started with my kickstart-disk and my orginal WB 2.0 SCSI Installation disk in PAL-HIRES and then I was able to start the Installation program from the DOM and sucessfully partioned, formatted and installed WB3.1 on my CF Card.

After reset and boot from my SCSI drive the new partions where shown with all AOS content and about double speed against may Quantum LS52

But I was not able to fully boot up my Amiga with the newly configured IDE Drives. Based on internet search I found this story with a similar but even worse problem: https://amigax1000.blogspot.co…-part-1.html#comment-form

Based on the latest hint of Jens, I just was able to add the attribute "buddhascsi.device" instead of the "scsi.device" to the HDToolbox-icon attributes. With this, HDToolbox showed the IDE Devices and I was able to re-partition the standard-partitioning which was done on my 8GB CF Card. The first partiton was automatically set to 512MB which should be supported size. But the standard procedure uses not a Amiga-DOS/FFS format, but an "PFS3"-Format. Additionally the partion-name is "BDH0" instead of "WB_2.x" as it is needed for the Kickrom-load and it was not flagged as bootable. Also I found, that the "Start Cyl" starts with 2, where at my original SCSI-Drive the "Start Cyl" starts with 4.

So at first I backuped the whole BD0: Amiga OS 3.1 Installation to the Work: partion on the CF Card. Then I changed the BD0 partion to match all requirements for a Kick-Rom partion as decibed above - all data on BD0 was deleted as expected.

Next step: Format the new WB_2.x without international mode as described in the blog above.

Then: Copy the backup of the AOS installation again to the newly formatted partion

Then: Copy the original 3000 Kickstart from the SCSI: WB_2.x Partion/Devs to CF:WB_2.x/Devs

- eventually you must name the CF Card not WB_2.x, but just WB_2 for thsi copy step with connected SCSI and CF and after the copy disconnect the SCSI, Boot from floppy and rename the partition on CF to WB_2.x within HDToolbox.

In principle, I assumed, this should work for booting from IDE on a superkickstart A3000 - but unfortunately It did no work fully.

After power-off and disconnecting the SCSI drive and again power-on the A3000 just showed the kickstart-load dialog where you can select to load a kickstart from HD or Floppy, but the HD-Icon was grayed out.

So I re-connected the SCSI boot drive and tried again. Then, as to be expected, the Kickstart was again load from the HD, and it boots also from HD.

Next try: Just reset, without power-off, then hold both mouse buttons to show boot-selection screen of A3000. (have in mind: in this case the kickstart from the SCSI boot is still im RAM)

Then, the CF-Card "WB_2.x" is shown as "WB_2.y" in the boot menue - our Amiga is not silly and just counted up in case of a nem conflict

So select the WB_2.y and then boot from it.

YES: it boots up the Workbench from the CF Card BUT only, if the kickstart is already in the memory!

In the Blog above, it was mentioned to use the orginal Installation disk to get special parts on the boot-drive.

Again I formated the CF-Card WB_2.x partion on the CF card and then boot again by Kickstart disk without SCSI-H but with orginal WB2.04 HD installation floppy and installed WB2 by installer on the CF partition. It asked also if this is an superkickstart Amiga and for the Superkickstart floppy to be copied to the CF partion.

After finish of the installer I booted again and hope, that this time the CF partion is recognized and bootable - but i wasn't. I was the same as with the manual copy after reformatting the WB_2.x CF partion and manual copy AOS and kickstart to this partition.

So the current status is, that is is not possible to load the Kickstart from an IDE drive from the superkickstart-rom. But once the Kickstart was loaded in the RAM, it is possible to boot by the bootloader the WB from the CF card by holding down both mouse buttons after a reset.

So I'm wondering if there may be really a direct-boot solution for a superkickstart-ROM A 3000 based on IDE drives? Because the boot works fine once the kickstart was load into the RAM and the good performance of my CF card shows, that Buddha is a really good approach. For me in the exchange of the superkickstart-ROMS against a kick 3.1 on my mainboard still an option, if no better Ideas pops up here.

But til then:

- Eventually there is something in the 4 cylinders in the beginning of the SCSI HD which is needed by the Superkickstart Bootloader? But there is no "custom Boot Code flag" also for the original SCSI drive visible.

can whatever be brought from SCSI to the CF Card?

- exists eventually a HD copy program for Amiga where I can copy the 14MB SCSI partition to the 512MB CF partion by tracks not by files - I have somthing like this in mind - but I forgot the name of the tool.

Here are some Screenshots with details of the Wb_2.x Partition and BootOptin Menue as it is now after all this steps.

Name is here just WB_2 - later renamed to WB_2.x:

Here the Bootmenu after I renamed the CF Partition to WB_3.x - the WB_2.x is the SCSI drive