Need input

KachiWachi · Post by **KachiWachi** » Fri Nov 18, 2005 6:46 am

Some input is needed on how this Everest build works with the K6's on various platforms. Please try it if you can and let me know so I can provide feedback to Fiery. Thanks.

See -> http://www.lavalys.com/forum/index.php?&showtopic=1029

DonPedro · Post by **DonPedro** » Fri Nov 18, 2005 2:27 pm

where can I download the program with the build version in question? the latest available on the lavalys' site is 2.20 build 405.

KachiWachi · Post by **KachiWachi** » Fri Nov 18, 2005 4:45 pm

You can get the build in question from the post link I supplied.

Stedman5040 · Post by **Stedman5040** » Fri Nov 18, 2005 5:20 pm

Kachiwachi,

I have just downloaded the beta build from the site and have run it through all of the benchmarks on the benchmark page with no problems. I have gone through all of the other pages also with no problems. To now no freezes or anything peculiar to report. System tried on is as follows

K6-III+/450
Asus P5A (1.04)
256MB CL2 Hynix PC133
Creative SB 5.1
Voodoo3 3000
WD 20GB 5,400rpm ATA33
O/S Win ME

Regards,

Stedman

DonPedro · Post by **DonPedro** » Fri Nov 18, 2005 5:55 pm

also tested all 3 builds thoroughly. no errors occured.

Gigabyte GA-5AX rev4 5.2, ALI 5 chipset
K62+600
512 RAM
Elsa GF2-MX 400
SB live
Network Adapter D-Link DFE-530TX PCI Fast Ethernet Adapter (rev.A)

NT4 Svp.6a

KachiWachi · Post by **KachiWachi** » Sat Nov 19, 2005 6:44 am

There was a thought that the freezing was K6 related, but I just tried it on my PM7900 (M520) with an Intel CPU and it did the same thing.

The initial thought was that it might be VX related...it seems that assumption was correct.

If anyone has an FX, HX, or VX (i430 series) chipset machine, please try the Beta build and see if the freeze exists for you. Thanks.

KachiWachi · Post by **KachiWachi** » Tue Nov 22, 2005 9:24 am

In addition...anyone with a ALi Aladdin IV(+) chipset-based board...try this as well.

Note tha Build 469 has the new timer calculation turned off, so you would need to try a version prior to that to test for the bug.