Posts by Timm

You must invoke "Restore to Defaults" from the Settings menu to make the mode visible if it's overlain by an old configuration.

I just updated the IndivisionAGAmk3 config tool and added a tutorial example that deals with that case:

http://wiki.icomp.de/wiki/Indivision_AGA_MK3/doc

For your information, thanks mainly to your feedback, we have improved the software package, out-of-the-box CD support, and installing e.g. OS3.2 from CD. We really hope it works better this time.

I don't get the problem, maybe because my Italian is a bit rusty.

Download is here: http://wiki.icomp.de/wiki/X-Surf-100#Download

For now I can just say that I've successfully installed 3.2.x many times from CD with our updated out-of-the-box setup and CacheCDFS.

That was the main scenario I was testing against for the updated software package.

Note that I had several CD drives for testing, of which a few did not work correctly, presumably due to their old age. With one drive I had a similar problem, contents were displayed correctly (albeit too slowly), and when running anything from the drive, errors were reported. The first thing to try would be to copy a CD's contents or at least some drawers to some other mass storage device, or RAM:, to see if that works.

Transferring the configuration file to an Atari per command line tool would be definitely a sound and reasonable option. Unlike some other things that are being concocted right now

Atari GUI programming, no way

Quote from Jens

My expectation is that you can read monitor profile data with the MK3, save that, and use the output modes in the ECS V2/V3 config tool. Timm?

No, that's not possible. There are subtle differences between the ECSv2/v3 and AGAmk3 not in the configuration format, but in the value ranges.

You should see a Work: partition as well. The vast majority of the free space on the CF card of that size goes into the Work: partition, while the WB: partition will be capped at around ~500MB. So the displayed size for the WB: partition appears accurate. What bothers me is that you didn't mention a Work: partition.

Maybe the installation procedure was not capable of creating a Work: partition of almost 64GB.

The biggest I have tested was a 16GB card. Please note that while we understand that it's increasingly difficult to find smaller CF cards, 64GB is an insane amount of space for a computer as small as an Amiga 500 with a 68000 CPU.

Are you running on a plain 68000 CPU? With any kind of accelerator card that brings extra memory there are no problems to be expected during installation even with a 64GB card.

acatool version 3.2 is now available, with this and several other bugs and quirks fixed: http://wiki.icomp.de/wiki/ACAtool

Thanks for the report.

I was about to write: "It doesn't expect the romfile option, just 'acatool maprom' should do. Do not use your internal ROM via the romfile option - only the internal ROM can be mapped without rebooting."

But oops, you're right! The standalone MAPROM option seems to be broken recently. Need to check this.

There haven't been significant changes for the ACA1233n for a while. For the time being you can use acatool 2.7 (attached) until we come up with a fix for newer versions.

Quote from HorseDemon

Been looking for the HDToolBox in the different folders but haven't found it as of yet. (Using the WB install that's on the ACA.)

HDToolBox is supposed to be in SYS:Tools after installation with the ACA1234 installer.

We have already tried resetting the configuration to defaults in the "F9 - Cloaking Device Mode Expert Menu" and "F10 - Normal Mode Expert Menu", haven't we?

Could you please reset all configurations, also "F8 - Global configuration and flash update", press "D" for resetting to defaults, "S" for saving to NVRAM, and the same with F9 and F10 if you haven't tried that before.

Sorry for the misunderstanding, I wrote already on Tuesday that it's unlikely that the CFs are at fault, and all tests successively provided the evidence, the most striking being that the installer didn't start with no card inserted either - while at the same time you could perform firmware updates and install OS3.1 manually.

The CF cards are not at fault - we know this since the automatic installer didn't start even with no CF card inserted, and also because the manual installation of OS3.1 worked. The software updates are also not the direct cause, since they work elsewhere, and after reverting to the old firmware the problem remained. I suspect that something went wrong during the updating process itself. We are investigating.

Gosh, you're right. Removed.

Transcend "industrial" has never caused a problem for me so far. Of course that doesn't mean that it's infallible, and others (such as Kingston 4GB with a flower printed on them) haven't failed for me either on the ACA500+.

Attached is lha and a lha archive that contains a few of the ACA500+ extras that would be installed by the automatic installer. (not much - mostly lha itself, the Kickstart files, and modernized filesystems. The tricky part is to actually install and use the modernized filesystems.)

Of course it is not satisfactory that the automatic installer doesn't start on your computer.

I have written the automatic installer for precisely the reason that the OS 3.1 installation is too much hassle and the result leaves too much to be desired. I may be as sad as you that it doesn't work for you yet.

With all the effort we have now at least excluded several possible causes, and you have an OS3.1 installation, while we need to discuss internally what may have gone wrong here, and to possibly come up with a remedy or fix.

Fine, we might never know why the automatic installer doesn't start on your computer, but we might get OS3.1 to install then.

Preferrably use your 256MB CF, because it is safer - a CF bigger than 4GB should work, too, but we'd not use more than 4GB of the card here.

In the "F10 normal mode expert menu", besides selecting "Virtual disk - WB3.1 Install" you also have to adjust to use "Kickstart v3.1 r40.63", roughly as in screenshot (1). Then press Return to start booting from here. The system should come up with the install disks. Next we need to setup your CF with HDToolBox (2), which is located on the Install3.1 volume.

First we're setting up the drive type (3), if there is an old definition, use "Delete Old" to delete it, then click "Define New...", and "Read Configuration" (4). (Don't worry if the size is displayed with a negative number, this is to be expected if the medium is bigger than 4GB.) Accept the new drive definition (5). In the main window, click "Partition Drive" (6). In the next window, check "Advanced Options" and "Bootable". The first (leftmost) partition must not exceed 4000 Meg - but please make a partition significantly smaller - even just 100 or 200MB would be perfectly sufficient for the system partition. More partitions can be added later.

If there are more partitions, delete them (7). Accept changes and save them to the card (8).

Next we must reboot - enter the ACA500+ menu by holding the left mouse button. Again select "F10 normal mode expert menu", Kickstart 3.1, and "Virtual disk - WB3.1 Install" as in (1), and press Return to boot wth these settings.

You'll then find an icon of the newly created volume. It needs to be formatted first (9). Give it a useful name, such as "WB31". To make sure that the CF can be written safely, prefer "Format" over "Quick Format" - but a full format may take an extremely long time with a big partition.

Then you can open the Install3.1 volume again, open the Install drawer, and Install OS 3.1 in your preferred language (a).

We all are at a loss., and I have spent many hours with this issue, too.

At least we know now that it's not related to the firmware, or firmware update.

Next ideas:

1. Do not insert any CF card at all, power on, F7 F1, do the OS 3.1 disks unpack and the installer start?

Because if they do, you can even now insert a CF card to Aux and install to Aux.

If that fails, next up to try:

2. Enter "F10 - Normal mode expert menu", use W key to select "Virtual disk - WB3.1 Install". Press Return. Do the OS 3.1 install disks unpack?