Welcome, Guest. Please login or register.

Author Topic: Was PCI for Amiga a good choice?  (Read 13646 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Cosmos Amiga

  • Hero Member
  • *****
  • Join Date: Jan 2007
  • Posts: 955
    • Show all replies
    • http://leblogdecosmos.blogspot.com
Re: Was PCI for Amiga a good choice?
« on: August 23, 2015, 06:40:58 AM »
Quote from: carvedeye;774654
PCI is fantastic with the amiga, I have the mediator lt4 it has given my amiga a new lease of life :)

Yes, Mediator is very good for us...

Sadly the 3dfx driver is a bit buggy for me : watch the little demo W3DStarShip with only 170 triangles running at only 300 fps...

170 triangles are nothing for a 3dfx GPU clocked at 166 Mhz... We can reach about 2000 fps with a bugfree driver I guess...

Or maybe the bugs are somewhere in Warp3D, I don't know exactly...

I feel bugs in the Voodoo.card, hope Elbox will have a look...


:)

Offline Cosmos Amiga

  • Hero Member
  • *****
  • Join Date: Jan 2007
  • Posts: 955
    • Show all replies
    • http://leblogdecosmos.blogspot.com
Re: Was PCI for Amiga a good choice?
« Reply #1 on: August 29, 2015, 05:41:46 AM »
Quote from: wawrzon;794635
warp3d ia an old crippled and outdated system that originates and represents the functionality of 68k era, which is, how you yourself worded that "stuck in the past". it took ages to have it ported and available for the cards, the systems you consider "modern" come equipped with. and this outdated form of 3d support is a result, that they apparently couldnt get gallium done.


Wawrzon : you are an old crippled and outdated human, I'm afraid...


Quote from: HammerD;794628
I have a GREX 1200 for sale if anyone is interested...

http://www.amibay.com/showthread.php?64283-G-REX-1200-with-Voodoo-3-Realtek-8029-and-Ess-Solo-1&highlight=GREX


Yes, GRex 1200 need BlizzardPPC rev2 : I'm still looking for any informations about this rev2 (which IC is updated, how Thomas Dellert updated the Blizzard without any soldering (by the miniPCI connector ?), rev2 jed files...)


Some said that there is a bug in the second batch of blizzppc rev0 which cause some weird crash. There are some bogus memory adresses too, never try to write them with the ppc or you will have some problems...

Any informations about this issue ? Wrong ceramic capacitors ? Wrong resistors ? CPLD problems ?


Ouch, I found this post :
"I tested MorphOS on some mobos with my blizzppc rev2.1 noscsi and the same setup. It worked on my old 2B motherboard (now fried) and on an 1D.4 and it doesn't work on my new 1D.1"


And this one :
"> then the "multitask-bug" a lot of persons have been experiencing, which also only happens on the BPPC

Not so. I can reporoduce the "multitask-bug" whenever I want on any system with a PPC regardless of it being CS or B. I'm not sure if it has to do with hardware or software, but I can guarantee that I can get Warp or PowerUP to crash taking the whole system with it in a matter of 30 seconds after a full and clean boot. Knowing how to avoid that is another situation all together. Keeping on topic though, it would be in thier best interest to release a product that's known to work on the csppc and continue testing for the bppc. Doing this will bring extra income that they did not previously have and can continue testing. Also, knowing that the base is being done so that they can have a full emulator on other platforms other than Amiga, it will help iron out any problems that they might not have seen or overlooked. Granted the extra cost for licensing of the roms, os disks, or bios images would not be all that cost effective at first however just a little funding would help a long way for the team at microcode. I'll say release it for the CSPPC and continue to test and develop for the BPPC"


And this :
"Well apparently it's not a bug in WarpOS afterall, but a error in the BlizzardPPC. MorphOS is said to have the same problems on Blizzards connected to anything but revision 1D mainboards. Maybe H&P and Ralph Schmidt could work together to track down this timing bug and make a workaround"






Any informations welcome !




:)