Amiga.org
Operating System Specific Discussions => Amiga OS => Topic started by: asrael22 on August 19, 2021, 11:59:11 AM
-
Hello.
I just recently installed AmigaOS 3.2 on a A2000. It had previously AmigaOS 3.1.4 and that was downgraded (or upgraded?) from 3.9.
As far as I can tell all the ReAction stuff doesn't work anymore.
The most prominently I got aware of it when AmiDock didn't load anymore from WBStartup.
Running SnoopDos shows that when double clicking AmiDock all seems to end at loading 'window.class'. Nothing else is being logged. But AmiDock doesn't show.
Similarly, no other ReAction/ClassAct window is showing.
Are there any known issues with this?
Cheers,
Manfred
-
@asrael22
Hello there. Is known that AmigaOS 3.9 application work fine with AmigaOS 3.2. I showed that on one of my streams that I am doing on twitch, and a record of it you can find at https://youtu.be/-G2ujYjEPgc , where you can see how you can resolve issues and the methodology to follow to recognize them.
But in your case I can't be sure if the problem comes from the updating path you had, from OS3.9->3.1.4->3.2.
In snoopdos, when it tries to load the window.class it fails? If yes, I would recommend to check if this class was not updated and it is an older version than the one that comes with AmigaOS 3.2. And while you are there, try to check the rest of the classes as well.
-
Thanks.
I'll checkout your video.
The class 'window.class' loads OK according to SnoopDos.
I've copied the 'Classes' disk again over the installation. So from what I can see it look all good.
So this is really weird.
Manfred
-
What version of window.class is it reported as with the "version" command?
-
Version 47.
I have the exact same problem now on a second system, an A1200.
WBStartup hangs on 'AsyncWB' and no ReAction apps actually work.
Both systems have Vampire cards. But I don't think this has anything to do with it.
Though on a third system (FS-UAE) the upgrade did work OK. This was also the same upgrade path: 3.9 -> 3.1.4 -> 3.2.
-
...Both systems have Vampire cards. But I don't think this has anything to do with it.
...
hmm that's actually a very important piece of information you left out on your first post and interested to hear from other Vampire owners on this issue as I know a few that have had 'issues' with AmigaOS in general and have reverted to the ApolloOS which is shipped with the Vampire
-
Are you able to try a partition where you directly install 3.2 without the upgrade path and see how that goes?
-
...Both systems have Vampire cards. But I don't think this has anything to do with it.
...
hmm that's actually a very important piece of information you left out on your first post and interested to hear from other Vampire owners on this issue as I know a few that have had 'issues' with AmigaOS in general and have reverted to the ApolloOS which is shipped with the Vampire
Well, I'm running 3.1.4 on Vampires just fine. No problems. So that didn't (or doesn't) seem to be the issue for me.
But I will give it a try to remove the Vampire board, or put in an ACA.
-
OK, I think I found the problem.
It seems that Executive somehow causes the trouble.
All is working OK when the Executive server is not started in my user-startup.
Still weird though. Maybe there is a workaround.
Manfred
-
That makes some sense. Executive is known to cause some problems.
-
I am pretty sure the installation guide for 3.2 recommended the removal of all hacks ("patches") prior install.
-
I am pretty sure the installation guide for 3.2 recommended the removal of all hacks ("patches") prior install.
That's a wise thing.
Now you just have to know that Executive is a hack.