SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : All About Sun Microsystems -- Ignore unavailable to you. Want to Upgrade?


To: chunmun who wrote (23194)11/19/1999 6:21:00 PM
From: chunmun  Read Replies (1) | Respond to of 64865
 
has anyone read high noon the story of sun. if so could
you please post your review. thanks.



To: chunmun who wrote (23194)11/19/1999 6:32:00 PM
From: JC Jaros  Respond to of 64865
 
Has anyone used a ATI Rage Fury with 32megs of RAM with Solaris 2.5.1 for the PC and got it work? Thanks.

WHY?!

Why are you trying to cram a proprietary Canadian PC video card down an archaic Solaris version's throat? Are you a sado-masochist?

Write to ATI and ask them for the driver for this. <g>

-JCJ



To: chunmun who wrote (23194)11/19/1999 6:35:00 PM
From: David Kelly  Respond to of 64865
 
I would be very surprised if you could get a Fury working with Solaris. Here is the Solaris x86 Video display FAQ page: soldc.sun.com

Go to www.deja.com and search on: "Ati Rage Fury" this is thread about Fury and Solaris from early this month.

I bought a Matrox Millennium II PCI direct from Matrox's clearance store for my Solaris box.

david



To: chunmun who wrote (23194)11/19/1999 9:00:00 PM
From: QwikSand  Read Replies (2) | Respond to of 64865
 
Has anyone used a ATI Rage Fury with 32megs of RAM with Solaris 2.5.1 for the PC and got it work? Thanks

Sorry, no good news to report except I couldn't get one to work with Red Hat Linux 6.1 either. Ended up replacing it with a discarded Matrox Productiva G100 with 8MB which works fine. I think ATI, like most Canadian companies, is into changing register specifications just because they can, then not releasing the documentation.

--QS