Yesterday i downloaded update 2 i ran into problems having also installed Enhancer 1.5 but this is not a problem i will do a clean install again.
Even if I use winuae I just wanted to ask this because in the changelog I didn't find anything in the "device" section
It seems that G-REX is no longer supported if I select G-REX as PCI no more "sb128" audio is detected and even the RTL8029-PCI network.
But if I use MEDIATOR everything works.
Not a problem this I just wanted to know if G-REX is no longer supported.
I did a clean install with MEDIATOR and everything works

do you know if G-REX is no longer supported because I didn't find anything in the changelog?
Thanks

separate note:
with update 1 G-Rex it worked

SOLVED
sorry i solved,
the startup-sequence is modified by update 2
it was enough to add again:
C: BootLoader COMMANDLINE = "Grex NoRamPager NoDiskPager"

@kas1e
I have not used ultraiso in depth, it only served me to modify the bootloader.
I can't recommend you any further but it was the most compatible.

@kas1e
ultraiso is compatible with amigaos and allows editing.
There was a little guide on EAB
http://eab.abime.net/showthread.php?t=99911

@Thellier
@All
a patch like "PatchWarp3D" would be possible
at least for some main functions for demo games and the like,
Thanks

@All
I also tried old versions of warp3D but it seems that the only one with AVENGER "drivers" is Warp3D 4.2a
Unfortunately I cannot test the other versions
I found some "Cosmos" updates but they seem to be written for 68k
I'm equally happy because 4.1FE works well with wazp3D (thellier)
But for example the use of Voodoo + Warp3D 4.2a enables functions that I couldn't use before example GrimFandango in opengl the ppc demos etc.
I was wondering if a "bounty" to write something like (Wazp3D) could be written to patch Warp3D 4.2a at least in its main functions it would be fine anyway it is an emulation and at the moment it works well and I think it can be improved.

Any suggestions or recommended programs are welcome
to test if it works.
Thanks again for your patience

separate note:
the files to be moved in ENV where they go I could be wrong in:
Prefs/Env-Archive ?
they seem not to work

it also seems that after starting the system on 16mb of video memory there are at least 10 megabytes left from the "sysmon" ratio so the graphics memory seems to be available.
Although initially it seemed that Voodoo didn't have enough video memory.
Now I don't know if "sysmon" has a real emulation ratio
thanks

@LiveForIt
Thanks for the reply,
I was reading about this warp3d problem which was not perfect, too bad because emulation works very well even a patch like rewarp would be fine.
I tried rewarp but unfortunately it doesn't work.
I guess the problem is warp3d 4.2a
I'll try other ways but I think maybe there is no solution

sorry if i ask again,
the problem i am having is this:
when i run the tests with Warp3D in ppc there are artifacts and transparencies.
While if I run the 68k version everything looks good.
Also if I start the tests included in the minigl package (latest version) everything is perfectly visible.
I guess the tests included in the minigl package are written in ppc?
Because they all work perfectly.
Is it a Warp3D bug?
Am I wrong configuration of Warp3D?

The warp3Ds I used are the ones I downloaded from the hyperion site

Thanks for any help
I leave the video here to explain better I hope to find a solution
https://www.youtube.com/watch?v=0MjXuyMSaUY

here i tried to watch for example the Encore Sulaco demo works fine but there are artifacts like in Warp3D
https://www.youtube.com/watch?v=09FeQHenapY

Sorry again,
Are the Warp3D 4.2.a for 4.1FE those downloadable from the hyperion site?
Thanks again

@Thematic
Thanks again
and thanks for your explanation

@Thematic
thanks for your advice
I have to get some experience on this new configuration.
Thanks again

@LiveForIt
perfect thanks

while sdl is always supported even using the Voodoo?

@Thematic
@All
Thanks for the reply
everything is working fine and a new thing for me.
With amigaos4.1FE do I also need to install CyberGraphX v3 / 4 for compatibility with other applications or is it not needed?
Thanks again for your patience.

I am testing the 4.1FE with Voodoo3
I have these libraries in the Warp3D / HWdrivers drawer:
W3D_AvengerLE.library
W3D_AvengerBE.library
W3D_Avenger.library

I noticed for example that instead for the Radeon or the Voodoo model 4/5 there is only one library and not three.
Why are there 3 libraries for the Voodoo3?
are all three needed?
Thanks everyone for any help.

@smf
thanks for the reply you were very kind

For amigaos4.1FE with Voodoo3 "pci mediator" you need to install special drivers or those included in the amigaos4.1FE cd are enough.
Thanks for any suggestions

@Cass
it probably doesn't help much
i use the 4.1FE with winuae and the jit works with the killing ground 3D II
the configuration of e-uae is similar to the one posted by Raziel but I also tried his and it works.
https://www.youtube.com/watch?v=Kzlk9RCwaDY

@tekmage
Unfortunately I never had real hardware so my experience is based on winuae only.
some little things differ in winuae however unlike real hardware.

If you just need to complete the internet connection then I recommend using RTL8029-PCI as a "driver"

If during use you happen to have lag or other problems then you can use ethernet.device is probably more compatible with your modem-router in this case.
But I advise you to try RTL8029-PCI first

You must also enable one of the two peripherals you have available in PCI bridgebords:
Mediator or G-Rex
Mediator is generally the recommended one.
I personally use G-Rex it allows to allocate more memory in winuae.
To activate G-Rex in the startup-sequence there is a floppy.adf in the 4.1FE CD in this case if you need some advice I'm happy to help you.

As an audio driver sb128 is currently the best choice.
Paula makes the sound heard and seems to work but in reality with more advanced configurations and while using the applications you will do later you will encounter problems.

The A2065 like RTL8029 can stop working in case if you try different configurations like choosing PCI etc.
But once you have your final setup this will never happen again except in very rare cases.

I made a small video on how to connect to the internet via RTL8029-PCI is also valid for Ethernet.device the procedure is the same:
https://www.youtube.com/watch?v=SF-Ivs0OZ_w

if you have to delete your old configurations the previous advice on how to do it is valid.
I hope it is useful, I am pleased to find people who use 4.1FE with winuae, currently there are not many who use it.

@Lio
thank!
@kas1e
thank you very much, now I try,
I saw in your video the use of DN is very useful.

dosbox works i can't just mount an .iso
https://www.youtube.com/watch?v=Z6ApMjY8Jfc

I wanted to try DosBox and it works I added DosNavigator to work better.
I tried from line without using DN command to mount an iso but I can't I used the following command:
imgmount C C: \ tombraider.iso -T iso
the message appears that the iso is mounted
the iso is mounted but I can't work with it.
Am I wrong something? dosbox for amigaos 4.1FE support access to iso?
Should I use another command?
Thanks for any suggestions

Hi tekmage,
if you have errors in the configuration in the wizard it is normal that it happens a few times in winuae after having already made a connection or having the wrong procedure.
Do it like this:
Start the emulation from Floppy and CD as if it is the first time you are installing.
Select Live CD
then delete in Devs / NetInterfaces / your configuration (ethernet) <---
then delete in Devs / Networks / the ethernet.device file <---
reboot your system normally and copy ethernet.device again
in Devs / Networks /
Restart normally and repeat the wizard, now everything will work.


separate note:
your configuration must be right so:
expansion -> network adapters -> A2065 enabled
then
network mode -> SlirpOpenPorts
just follow the wizard and choose automatic and the ethernet.device "driver"
I hope it's useful, that was what you were looking for?