Welcome, Guest. Please login or register.

Author Topic: AmigaOS 3.2 problems  (Read 729 times)


0 Members and 1 Guest are viewing this topic.

Offline PunkTigerTopic starter

  • Newbie
  • *
  • Join Date: Feb 2002
  • Posts: 10
  • Country: us
  • Gender: Male
  • Don't look at me... I'm irrelevant!
    • Show only replies by PunkTiger
Re: AmigaOS 3.2 problems
« Reply #14 from previous page: June 02, 2023, 03:20:09 AM »
Well, since you already write that you are using 3.0 kickstart ROMs with 3.1, the “mystery” is solved - as Thomas mentioned above, it only works by luck because of a bug, and chances are high that if anything tries to fill up those 8MB of RAM, the system will crash. If you remove one simm, 3.2 kickstarts (and 3.1) will work. An option is to burn custom 3.2 kickstart ROMs with card.resource (iirc) from 3.1.4 kickstart, that miraculously managed to re-introduce the bug from 3.0.  You could also try to install 3.2 kickstarts and the load card.resource from 3.1.4 or 3.0 using LoadModule when you need pcmcia. But with all these “working” solutions, you run the risk of random crashes should something try to actually use all that ram (of which quite a few bytes of address space is pointing to the pcmcia rather than actual ram).

Modern RAM cards typically has reset options to switch between 4 or 8 MB of fast ram, so that we only boot to 4MB when we know we’ll be needing pcmcia. Like on one a600 I got, where I do the opposite, boot with 4MB fast RAM by default and only press ctrl-a-a a liitle extra long to get 8MB just occasionally when needed.

This is the most removed I've ever felt from the Amiga community. I now realize that I have neither the knowledge, nor the equipment (and in some cases, the software) to do pretty much any of the steps you've mentioned in your reply. I never realized getting the PCMCIA slot to work on the 1200 was such an absolute crap shoot, and that it was blind, stupid luck that I got a machine where it just miraculously worked.

As for Workbench 3.2, it's staying off my 1200. I give up. I've had enough. Another $50 that I shouldn't have spent gone right down the crapper. And now that my faulty hard drive is more sensitive than a sunburned back, the last piece of the karma pie is that I'll reformat it, reinstall WB3.1, and have the card slot not work again for literally no reason. But, I'm being defeatist. Tomorrow is another day, and all that.

Offline Thomas

Re: AmigaOS 3.2 problems
« Reply #15 on: June 02, 2023, 05:27:34 PM »
Apparently, it won't interfere with the PC slot, according to the link I just supplied.

Well, this information is incompete. A more precise explanation can be found on this page: https://bigbookofamigahardware.com/bboah/product.aspx?id=987

It says, if you install 8 MB RAM on the card, but set jumpers for 4 MB, then you can use the MagicMem program to work around the PCMCIA issue. But the memory will be divided into two address ranges and you loose 2.5 MB RAM.

Regarding your issues with CF cards: that the light stays on all the time is a well known issue with these CF-IDE adapters. It does not restrict the function.

And that the HDD disappears after a reset is also a known issue with Kickstart 3.0. Normally it happens with spinning harddrives, but sometimes also with flash memory. The usual fix is to cut the reset line of the IDE cable so that the drive's firmware does not shut down when the computer resets. Kickstart 3.2 should fix it, too.