Must Kill Poseidon!!!

[Dandy]

Jasper_K wrote:
Hi guys,

anyone looking through the Hardware Issues section will see a post i made about certain PPC software not running on my A1200 040 PPC.

Well, I have found the problem, and it wasnt the multitude of patches running on my system - it was bloody Poseidon!!!

If I prevent Poseidon stack and PSD modules from running in my Startup Sequence everything runs fine.

I was warned by a few Amigans that Poseidon was evil, but thought they having "a go at me".

Anywho, this now leaves me with a (smaller) problem. Its a royal pain to have to keep editing my startup sequence everytime i want to run something, so I need a way to purge Poseidon from my system whilst in WB.

Is there a way to do this?

I have tried AddUSBHardware REMOVE ALL, but that doesnt work.

Any help on this matter would be greatly appreciated.

Thanks.

have you already tried to contact Chris Hodges (the author) on this?
chrisly@platon42.de

[CLS2086]

Which release of Poseidon do you use ?
What is your PSU ?
Which patch do you use ?

[Varthall]

c64_d0c wrote:
the fantastic amiga computer ahead of everything else... at least it was ages ago... i am so happy i dont have to solve does amiga problems its a pain in the but and not much user friendly... thank bill *god* gates for winxp and plug and play...

Thanks God my A1 with Os4 is much better from this point of view: no stacks of hardware one plugged over the other, all the most relevant patches now integrated in the OS, etc.

Varthall

[mboehmer_e3b]

Well, I dont think I have ever had poseidon crash on me, but then I have been told that Poseidon conflicts with some other programs - WHDload is a main example.

Nope, sorry to correct you here. It's not Poseidon which is the bad guy.
Poseidon uses interrupts to communicate with the USB host controller. If another software package takes over the machine (like WHDload does, by disabling multitasking), interrupts will still be there (as WHDload doesn't know how to deactivate the USB ints) and will freeze your machine, as the USB int server will never be activated again.

Something similar will happen with other software which may use a buggy interrupt server (remember, Amiga uses daisy chaining with interrupt servers, so if one server closes the chain too early by mistake, you are done).

The best way to get around this is (like already proposed) to use a small utility checking the mouse buttons on startup, and changing the startup-sequence accordingly.

Michael

Michael

[CLS2086]

As A1 is not an Amiga (no Amiga Custom chip inside), it doesn't have this problem because every is emulated like on a PC... It's the same for Pegasos ...  :rtfm:

And why do you want to use WhdLoad when you've got a real amiga with the real game ?  :lol:  
Do you know you can also use E-UAE (like on A1 and Pegasos) and get the use of your USB devices ??  :rtfm: