Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: XDelusion on June 22, 2005, 12:19:41 PM
-
Now when ever I goto Execute Command in the pull down window, it locks up my Amiga.
I just installed a 250 Watt Power Pack and my system is acting worse than before.
EDIT: Still works like a charm under WB 3.1.
Might this be because of my mis-matched RAM?
-
I vaguely remember that this is a known problem of OS3.9. Have a look at Greg Donner's OS3.9 FAQ (http://www.gregdonner.org/os39faq/os39faq.html), perhaps it is mentioned there.
Bye,
Thomas
-
This has been happening here too for some time. I wonder what is causing it. Probably related with AsyncWB since it only happens when AsyncWB is running.
Did anyone find out what is causing this?
-
Now when ever I goto Execute Command in the pull down window, it locks up my Amiga.
I just installed a 250 Watt Power Pack and my system is acting worse than before.
EDIT: Still works like a charm under WB 3.1.
Might this be because of my mis-matched RAM?
AsyncWB does have a problem. I use to get crashes when doing a few different things, this is one of them. I removed them from start-up and just start when I'm doing anything special that can use it.
Chris
-
AsyncWB does have a problem. I use to get crashes when doing a few different things, this is one of them. I removed them from start-up and just start when I'm doing anything special that can use it.
Chris
On a fresh OS 3.9 installation, it does not crash here. But on my normal system, it gurus or freezes Amiga (caps lock still works) from time to time.
-
I think I may have found something. When I press Amiga & E to call execute command window, it's not active by default and I have to press inside it to start typing. If I press a key before clicking inside it, this causes a freeze and sometime guru reboot.
-
Fixed the problem. Some files inside Classes drawer were overwritten by older ones from ClassAct. Replaced from Boingbag2 and the problem is fixed.