Stermy57 Posted March 27, 2012 Share Posted March 27, 2012 (edited) Hello, I am Stermy57, like my nickname (lol ndr) I love retrobench and retroclocking with old CPU and GPU, but i have a problems with olds AGP cards with 3DMark 2001SE and Aquamark 3.... With the new rules it's impossible to make a score with old AGP Card (4/8/16MB) under Aquamark 3 like the ATI Rage PRO 8MB. Because under WinXP Aquamark 3 crashed at frame 5050... So I think to run it win Win98 like other peole: http://hwbot.org/submission/1093350_northwood_3400_aquamark_rage_pro_328_marksbut http://hwbot.org/submission/2122575_drswizz_aquamark_rage_pro_114_marks http://hwbot.org/submission/2163180_christian_ney_aquamark_rage_pro_496_marks But with the new rules the new version of Aquamark required NET framework 4.0 So it's impossible to bench and to put my score under Win98 So is necessary a new rule for the OLD card.... Is not true says that anyone bench under Win98 with Aquamark because Dr.Swizz and Northwood-3400 do it, but they do it with the old rules.... anymore can help me? I have a problem in the same time with 3Dmark 2001SE with AGP OLD Cards 8/16MB because the software says: "VIDEOOUTOFMEMORY" Edited March 27, 2012 by Stermy57 Quote Link to comment Share on other sites More sharing options...
Crew Turrican Posted March 27, 2012 Crew Share Posted March 27, 2012 dude those results you linked were done before the new aquamark wrapper was released and mandatory. just look at the submission date. now they have no chance to upload old results, because you need the result file. try another driver regarding the "outofvideomemory" problem. 16mb cards run for sure with the right driver, but for cards with 8mb or less the chances are bad. Quote Link to comment Share on other sites More sharing options...
Stermy57 Posted March 27, 2012 Author Share Posted March 27, 2012 dude those results you linked were done before the new aquamark wrapper was released and mandatory. just look at the submission date.now they have no chance to upload old results, because you need the result file. I Know those scores were old, but is not justification... Is not correct, because now it's impossible to scores under Aquamark 3 and old AGP cards So, to conclude I and other people can't put our score? try another driver regarding the "outofvideomemory" problem. 16mb cards run for sure with the right driver, but for cards with 8mb or less the chances are bad. I have this problem with the Ati Rage PRO and one TNT2 M64 16MB, Do you know what kind of driver is necessary? For the ATI Rage I used the last driver from the AMD site... For the Nvidia I used the Omega 61.77 Quote Link to comment Share on other sites More sharing options...
Crew Turrican Posted March 27, 2012 Crew Share Posted March 27, 2012 i don't like the situation as well, i hope we can do something here soon. try older drivers. Quote Link to comment Share on other sites More sharing options...
Stermy57 Posted March 27, 2012 Author Share Posted March 27, 2012 i don't like the situation as well, i hope we can do something here soon. try older drivers. Thanks Turrican Because you are the only one that want to help me Quote Link to comment Share on other sites More sharing options...
Stermy57 Posted April 9, 2012 Author Share Posted April 9, 2012 Thanks Turrican i used the TNT2 M64 16MB with the Detonator 30.82 and 3Dmark 2001 runs well Any news? Quote Link to comment Share on other sites More sharing options...
Stermy57 Posted August 26, 2012 Author Share Posted August 26, 2012 Any news? Quote Link to comment Share on other sites More sharing options...
Rasparthe Posted September 20, 2012 Share Posted September 20, 2012 I thought a crash at the end of the Massive Overdraw was caused by the .dll and if you erased it or used the newer one it worked fine. Been awhile since I've run into the problem though, so might be my memory. Quote Link to comment Share on other sites More sharing options...
Stermy57 Posted September 25, 2012 Author Share Posted September 25, 2012 I thought a crash at the end of the Massive Overdraw was caused by the .dll and if you erased it or used the newer one it worked fine. Been awhile since I've run into the problem though, so might be my memory. Which .dll i have to delete? Quote Link to comment Share on other sites More sharing options...
Crew Turrican Posted September 25, 2012 Crew Share Posted September 25, 2012 Which .dll i have to delete? Direcpll.dll Quote Link to comment Share on other sites More sharing options...
Stermy57 Posted September 26, 2012 Author Share Posted September 26, 2012 Direcpll.dll I tried it, thanks turrican Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.