First post, by rain
- Rank
- Member
Hi everyone so i ve voodoo rush card trying use it with slot 1 motherboard pentium 2.
Using windows 98 but screen keeps flickering after windows 98 opening. Using true drivers but still flickers
-386-4MB-
Hi everyone so i ve voodoo rush card trying use it with slot 1 motherboard pentium 2.
Using windows 98 but screen keeps flickering after windows 98 opening. Using true drivers but still flickers
-386-4MB-
Its flickering only desktop , not in games
-386-4MB-
Any suggestions ":
-386-4MB-
Perhaps try adjusting the refresh rate of your monitor under Windows display settings? Alternatively, just run the Auto adjust feature on your monitor (appears that you're running it on an LCD/LED monitor).
Tried it before no luck
-386-4MB-
Does it work in OpenGL? Which drivers are you using?
Vogons Wiki - http://vogonswiki.com
Rush cards werent exactly a good product. Both Macronix and Alliance Semi chips came straight from garbage dump, failed chips with no market presence on their own. Macronix was actually making VGA chips from around 1992 https://www.vgamuseum.info/index.php/news/ite … national-co-ltd yet you never see any in the wild, I think Rush killed their ambitions 😀 Alliance chip was straight up broken, and Imo selling it constituted fraud.
Its possible mx86251 "160MHz Ramdac" is just that bad quality.
https://github.com/raszpl/FIC-486-GAC-2-Cache-Module for AT&T Globalyst
https://github.com/raszpl/386RC-16 memory board
https://github.com/raszpl/440BX Reference Design adapted to Kicad
https://github.com/raszpl/Zenith_ZBIOS MFM-300 Monitor
mwdmeyer wrote on 2023-12-27, 22:22:Does it work in OpenGL? Which drivers are you using?
http://falconfly.3dfx.pl/rush.htm
Mentioned before its flickers only desktop
-386-4MB-
And using cf card maybe its to blame
-386-4MB-
So, the 2D chip on the Rush can either be from Alliance or from Macronix. I know for sure that the drivers for the Alliance version are overclocked on the 2D chip by default and that can cause some graphics corruption in Windows.
My card has the Alliance chip, so I can't be too much help since it looks like you've got the Macronix. But you might want to double-check that you're using the Macronix version of the drivers. And then maybe also look into whether there might also be overclocking issues on the Macronix chip, but that would just be a shot in the dark.
It's certainly not Alliance Semiconductor chip
My dead Rush had many problems, one of - latest drivers caused memory problems
.inf file for it had the following lines which i removed to make them work:
[Driver.AddClock]
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",MCLKFrequency,,72
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",VG96_MCLKFrequency,,50
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",DualCycleThreshold,,90
Maybe you can dig through your driver inf file and find something suspicious?
From what I can see the MX cards don’t have frequency in inf file.
Vogons Wiki - http://vogonswiki.com
n0p wrote on 2023-12-29, 08:02:It's certainly not Alliance Semiconductor chip My dead Rush had many problems, one of - latest drivers caused memory problems . […]
It's certainly not Alliance Semiconductor chip
My dead Rush had many problems, one of - latest drivers caused memory problems
.inf file for it had the following lines which i removed to make them work:[Driver.AddClock]
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",MCLKFrequency,,72
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",VG96_MCLKFrequency,,50
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",DualCycleThreshold,,90Maybe you can dig through your driver inf file and find something suspicious?
Thanks but cant found " inf " file at windows windows/system
-386-4MB-
rain wrote on 2023-12-29, 08:09:n0p wrote on 2023-12-29, 08:02:It's certainly not Alliance Semiconductor chip My dead Rush had many problems, one of - latest drivers caused memory problems . […]
It's certainly not Alliance Semiconductor chip
My dead Rush had many problems, one of - latest drivers caused memory problems
.inf file for it had the following lines which i removed to make them work:[Driver.AddClock]
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",MCLKFrequency,,72
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",VG96_MCLKFrequency,,50
HKEY_LOCAL_MACHINE,"SOFTWARE\Alliance Semiconductor\Driver\HW Acceleration Settings",DualCycleThreshold,,90Maybe you can dig through your driver inf file and find something suspicious?
Thanks but cant found " inf " file at windows windows/system
Can you share Voodoo Rush driver package you're using?
Macronix Voodoo Rush V1.02.11B
-386-4MB-
-386-4MB-
Dated : 23 Feb 1998
-386-4MB-
Attached here
-386-4MB-
rain wrote on 2023-12-29, 09:31:Attached here
I did find any possible references to clock settings, but it does contain a very extensive registry list for video modes.
It looks like two custom property pages are added to display settings for Macronix, probably saved to registry/ini , is there anything interesting?
Have you tried setting custom refresh rate for display?
Driver also has strings for
M251INF.ini
m251dci.ini
m251mode.ini
VSyncMode
ManualFrameRate
n0p wrote on 2023-12-29, 10:16:I did find any possible references to clock settings, but it does contain a very extensive registry list for video modes. It loo […]
rain wrote on 2023-12-29, 09:31:Attached here
I did find any possible references to clock settings, but it does contain a very extensive registry list for video modes.
It looks like two custom property pages are added to display settings for Macronix, probably saved to registry/ini , is there anything interesting?
Have you tried setting custom refresh rate for display?
Driver also has strings forM251INF.ini
m251dci.ini
m251mode.iniVSyncMode
ManualFrameRate
Yes tried all refresh rates still same. Where can i find these files on windows maybe tweaking them fix this?
-386-4MB-