WHDLoad problems with mediator

[kgrach]

okay anybody have a solution for this.
this was brought to my attention by a customer and I have tested it myself.

If I have voodoo int in the mediator set to Yes 95% of whdload programs won't work.

if I turn off Voodooint then whdload programs will work but then some Amiga apps start to get glacial in screen redraws.
Anybody have a solution on whdload settings neccessary for the mediator to properly work with whdload. without turning off voodooint.

Thanks for your help.

Kgrach

[Acill]

I've never got it to work with my setup very well. Maybe 1 in 20 games work.

[kgrach]

well if you go to prefs/envarc/mediator/voodooint change it to No then all will work.

I am just looking for a better way. or the proper way I should say

Kgrach

[Matt_H]

You could run an ARexx script in the global WHDLoad prefs (in S: by default, I think) to automatically change the ENV setting on starting, and set it back upon quitting.

[Acill]

Write one for us, I dont know how to write Arexx scripts.

[kgrach]

I know arexx not a problem but it looks like I have to reboot the Amiga after changing the envarc setting changing env doesnt cut it.

I was hoping it was something I could change in Whdload since i am not to familiar with it.

[lempkee]

VoodooINT must be set to "NO"! to get whdload working properly, this is a common thing.

the real question is, why do you have VoodooINT on "YES" ?

VooDooInt is the switch you use to make the 8mb window extended (hack wise (with interupts) ) so that you can benefit more mem/all from the card you use.

This feature is really only needed on Blizzard PPC cards and not on 68k! or a3*/4000 systems .

in the bppc sofware there is a bug in wos/w3d which forces you to use this trigger/intrerupts , atleast if you want warp3d to work! .

hope this explained enough for you guys :-)

anyway since i am a big fan of whdload + an Bppc/mediator user , well i have to use whdload with VoodooINT NO in one boot and with VoodooInt YES in my games(w3d games) in my normal system boot.


w3d = Warp3d
Wos = Warpos
Bppc = Blizzard Ppc

ps:there might be other +/- here but this is the general stuff.

[lempkee]

oops forgot 1 thing.

VoodooINT interupts is almost like Miami Dx interupts , they screw up whdload , but both are still under the knife in whdload but there aint any ways of going around it unless you.

1. reboot system with voodooINT = NO
2. Turn Off the Miami Stack (some systemes needs only OFFLINE , others require you to close it fully down (quitting)

cheers

ps:kickemu games will work fine with both voodooINT =yes and MiamiDx online , rest will have problems.

[kgrach]

yea with Voodoint set to No it does have some funky reaction with certain software even on the 060 based Amigas. Screen redraws get massively slow.
I have to dive into the code to figure out why and make a workaround. Busy and I don't have time right now.
But thanks for the help Lempkee. Its what I figured I just was hoping for a more elegant solution.

It took me several days to figure out that voodint was the problem.

BTW folks mediator settings are case sensitive
Yes = Yes but yes = No in the voodint setting that one will mess with your head big time.

thanks for your help

kgrach