WHDLoad problems with mediator

[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.