My medconfig/warp 3d report

[Mad-Matt]

if the med report is still current, then the error looks as simple as not having any gfx mem address set.

Be sure to be using latest warp3d from elbox site. nommu mode.

with the ppclibemu installed terminator must be 0 and nopatch1

also running through all the settings in med config and it will advise correct values.

[Mad-Matt]

Another option is too delete ppc.library and not have the emulation (at least for now) just to see if its conflicting with anything.  Also its a safe bet you can delete the 68k libs to be sure it is only using the libs built into the blizzar flashrom.  As long as terminator is 0 and nopatch is 1, then it should be a clean warpos environment with the bppcfix patch installed.

I havent checked the version numbers from your log, but as long as its latest Warp3d from elbox and latest WarpoS from os39 cd, that side of things should be ok.  dont install the beta warpos from the ppclibemu site as it will break stuff.

Also run showconfig. it will show the different memory banks on the voodoo. one of the values should be used in warpos gfx addr.

[Mad-Matt]

@Bamiga2002
Through personal use. ive found the latest official lib more stable then the beta on the ppcemu page not to mention stability with the ppclibemu itself.

As it stands I have 0 issues with warpos/warp3d/ppc progs, although i admit changing from bvision to med/voodoo wasnt without its headaches