Hi there!
@Framiga
Ciao!
>> are you really saying thats ok having in MOSSYS:Devs/Monitors/
>> such a
>>
>> CVision3D.Z2
>> CVision3D.info
Yep,
at least for me MorphOS is picking the correct one depending on
the Zorro bus detected. You can see that this is the case cause
if you rename "CVision3D.Z2" to "CVision3D" you get the same
identical Exception 3 error, but for the drv name cause it's now
trying to load "CVision3D". The priority is
1 - "CVision3D" (if available)
2 - "CVision3D.Z2" or "CVision3D.Z3" (depending on the bus)
Because of this you can fool MorphOS to try to use the Z3 one
on a Z2 box by renaming CVision3D.Z3 to CVision3D, not
very useful but at least you get Ambient "talking" to you
See my serial debug.
@AmigaMancer
It does spin the HD and load some data after the first reset,
this is proved by:
a) I can hear it [not very useful unless you are next to me]
b) The Exception (did you see my serial debug) happens
-after- PPC_ColdBoot_603e which is succesful,
cause what fails is running CVision3D.Z2 and
logically this could not happen if the system did
not load it and try to execute it after the reboot, no?
I hope somebody can provide me with a CVision3D
friendly Ambient config/prefs file (see Crumb hint),
cause it's a huge task to open and rebuild the Micronik
tower twice just to create that file. Thanks!
Anybody out there?
Thanks,
-max