Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ciacara

#1
Hello AzzKickr and welcome :),
the installation procedure is correct, disabling the driver digital signature prompt.
The only thing to check is whether, when rebooting after installation, the driver digital signature request option is still disabled. If I remember correctly, this option is automatically re-enabled.
If this is the case, you either need to disable it on every boot or find a way to disable the driver's digital signature prompt permanently.

See you soon. :)
#2
Hi hardware hooligan and welcome,
write to this 3dfx enthusiast and describe your problem:
https://www.pct-server.de/~stephan/~hpage4/about-me/#contact

you will see that, if it is possible, he will help you out.

See you. :)
#3
Hi Smucek and welcome,
your Orchid sample is not the only one with 83mhz ram, I think it is related to the manufacturing date and the 3dfx chips installed on the voodoo2 board.

Yours is an A1 revision with code 09-00348-"02".



The 3dfx chips installed on your video card have a code "D18". On other cards with 83mhz ram that I attach, with code 09-00348-"02", you will see that the chips always have the initial "D18" or "D19".





From the A1 revision with code 09-00348-"03" you will notice that the 3dfx chip codes are newer and carry the initial "D21" or "D20". And the installed ram is different.





I don't think you will have a problem using them with any driver. One vogons user used them with Fastvoodoo drivers, which set the speed to 93mhz by default:

https://www.vogons.org/viewtopic.php?t=51060

His problem was related to a false contact on the pins of the 3dfx chips.
But after solving this problem, his voodoo2 worked perfectly.

See you. :)
#4
Hi Glide,
I tried the links but they don't work.
I did however find the drivers in the dedicated section:
v1.1
https://www.3dfxzone.it/dir/3dfx/drivers/?objid=1137

v1.0
https://www.3dfxzone.it/dir/3dfx/drivers/?objid=1136

but the download does not start.
Please can you check?

Thank you.:)
#6
Hi Dolenc, Grandma congratulates you on the first official release of your Wide drivers for 3dfx VSA-based graphics cards running Win98.

While waiting for a drawer to be dedicated for this release of yours, I have hosted your file at the following address:

https://www.dropbox.com/s/rquohyr7bobjy5y/3dfx%20Wide%20driver%20v1.0.zip?dl=0

I suggest you post the link to the first post of this thread of yours, referring to the explanation written in this last post of yours.

I need to set up the hardware workstation to test this release of yours, I can't wait any longer... ;)
Thank you very much for your work, now let's see if it works...[:p]
#7

Yes, I can admit that the Extended Resolutions version by Dolenc makes this video card run at 1080P!

Just to add some more spice to the bios mod and overclock issue, with vsa-100 220 I was also getting 205/206 mhz results. You installed rev 320's, if your v5 works and is compatible with this bios, could we see 220mhz too?...I daren't imagine... [:0]

I saw the two systems you are using:

Amd system
Athlon64 3200+ venice @ 2.2ghz
Gigabyte GA-K8VM800M rev2, s754

Intel system:
Pentium E5800 @ 3.2ghz
Asrock 775I65G v2, s775

You need an Asrock AM2NF3-VSTA with AMD Phenom II x4 980, or an Asrock 4Coredual-Sata2 with an intel X6800 / QX6800. With these monsters, you can exploit the full potential of this video card. I'm sure of it. :)
#8
Hi Dolenc, I'm your Grandma, I would like to say so many nice things to you but I can't because you would tell me I'm too loving....[:p]

Joking aside, thanks for sharing the files/drivers/tweacks, I want to test them, but I have to finish a long stopped project first ...

Personally I'm always interested in overclocking, I think you could achieve more with a doc modified version of bios. One such version of the v5 5500 agp bios, is 1.18 Modified - DramInit0:
https://www.3dfxzone.it/Voodoo5/bios/1.18%20AGP%20mod.zip?fbclid=IwAR3l9A9IGFugvIVVXLs5s95dkedkWjfeW21CmwjmQ5I6uC7peV2AeSNKPLQ

Bios with this wording next to the name imply that the memory timings have been modified to match previous revisions of the bios, which improves overclocking capability, as unmodified versions use more aggressive memory timings than previous revisions. Unless, the installed version has already been modified in this sense. It would have to be checked whether it is compatible with 128mb.

In Quake 2 I saw, for a moment, a resolution of 2048x1536 appear. Did you enter this by accident?

Is the v5 5500 a 1080p card? I'm too biased to answer that question, although from your tests it shows and answer is tangible.

My advice would be to include the hardware configuration and direct links to the Threads you created in the various online platforms, in the description of the videos, so those who will see it, even in the future, will have an idea of the whole thing...including your grandmother...
#9

https://ibb.co/FK8qZvK

Hi Dolenc,
sure, at a resolution of 1980 x 800, recovering almost 40fps, forcing rendering and textures to 16bit, is really a great result, congratulations!
You and v5 are doing a really good job.

Are the 128mb helping you a lot in this result, besides the 190mhz VSA/Ram overclock?

I see that override is disabled in 3dfxtool.
I also understood from what you wrote that mesa already has the override option and you enabled it.
So quake2 started at that resolution setting because it was natively set by windows, or did you edit the quake2 config file?

Maybe I asked a stupid question...[:p]
#10
QuoteOriginally posted by Backfire

Hello dear forum.

This is my first post here :-)

Many greetings
- Backfire -


Herr Backfire Willkommen,
I think this creature needs your hands and care.;)
Let's see if gravitonfield has solved the problem or if he wants to avail himself of your services.

See you.:)
#11
Well Dolenc, I see your progress is going well, and your monologues too...;)

After your elaborations, I understand, that you have a clean, bug-free version of Glide3x?
If that's right, that's already a good result. Too bad I can't help you, I have no experience in these things...[:(]
Anyway, thanks for your efforts and the time you are devoting to this project. :)
#12
OK for testing, let's wait until the changes are finished.

I hope you learn a lot more, along the way, so that you can push for further driver improvements. ;)
#13
Hi Dolenc, I see you have opened your own thread, perfect!

You keep making progress, that's a good sign, now we should start giving you some support, maybe testing your modified driver package. I, as soon as I can, will test everything with my v5 5500.

The search for source files for mesa 6.3 was unsuccessful. If I have any news I will inform you immediately.

I recommend adding a link to your second post, to link to your posts in "SFFT alpha drivers":
http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=1129&whichpage=124

Keep up the good work! :)
#14
Looking around for mesa 6.3 source files....;)

Let's say this is your own topic, so you could open a dedicated thread, since your mod is derived from several files and drivers.

This is my opinion, but I think Glide can confirm it.

Congratulations on your perseverance and results! :)

QuoteOriginally posted by Dolenc

Those are already built, need the source, will keep searching, think mesa 6.2 has that alt-tab bug.

Here are some preview files, if anyone wanna give it a try (pre-pre-pre-pre-release with no guarantee) (required timings are link a few post before)


https://easyupload.io/9ocf8t (link expires in 30 days)

(!Backup any existing files you have, so you can revert back!)
- glide2x_wrapper.dll, dont need this one, but I use it for testing, same as every other glide2xp build, rename to glide2x.dll and put in windowssystem or windowssystem32 for xp.
- glide3x_ks210.dll, build from KoolSmoky v2610 glide source, fairly stable, this one is in my testing a bit faster, has some gamma issues in some games, rename to glide3x.dll and put in windowssystem or windowssystem32 for xp.
- glide3x_sourcef.dll, build from sourceforges 4040 source found on sezeros github, has shaky 2d image(atleast for me) in xp and some red color tinting in both xp and win98, not sure whats up, early builds were working semi-fine, rename to glide3x.dll and put in windowssystem or windowssystem32 for xp.
- opengl32_mesa.dll, built from mesafx6.2 found on sezeros github, rename to usually Opengl32.dll and put next to games exe and pray it takes this one.

What I test with is raziel 1.06 for win98 and sfft 1.9 (or is it last alpha? forgot) for xp.
If Im spaming Sfft-s topic too much, let me know and Ill open another one.
#15
Sorry Dolenc but I didn't answer you because I didn't know how to help you. However, your 'Monologue' produced excellent results.;)

For the Mesa files, try having a look here:
https://www.3dfxzone.it/dir/3dfx/mesafx/archive/

QuoteOriginally posted by Dolenc

Well I have everything working, was wrong from the start, resolutions needed to be added to OpenGl too, so I used mesafx. (dont have the source for 3dfx opengl wrapper)

About a week lost experimenting with workarounds cus I was stubborn, happens :), at the end only resolution list had to be expanded.

Theres a smarter way of doing this, like those 2 wizzards from nGlide forum did https://www.zeus-software.com/forum/viewtopic.php?p=4397#p4397, but sice this isnt a wrapper, would need a bit of a re-write to handle different resolutions and what they do to the card(2pixel rend, sli, could be more ...) and since voodoo has finite resolutions that are usable and someone has to make the timings, lets stick to "dumb" solution for now.

I need a bit of help getting sources if someone has them, mesaFx 6.3 (have 6.2 now), something for glide2x, Ill try to get that glideXp wrapper going, but just in case, I see people using newer that whats posted on koolsmokys site. Appriciated if someone has anything.