Hi guys, I wanna ask you about a problem I'm experiencing when I try to use MesaFX on my SLI Voodoo2.

I have:
MSI K7N2 Delta-L
AMD Athlon XP 2500+
Asus TD9520 Video Card (GeForceFX 5200)
2 x Diamond Monster 3D II
Windows XP Home Edition with SP1a

I can't use FastVoodoo2 4.0 XP GE as-is, because of this: http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=644

So, when I try to use MesaFX, I had the Mapmen returned an error when trying to map memory

Are you gonna try to fix this problem, so we can use MesaFX?
Is there any other way to try it?.

Thanks.

QuoteOriginally posted by PanoramixDruida

Hi guys, I wanna ask you about a problem I'm experiencing when I try to use MesaFX on my SLI Voodoo2.

I have:
MSI K7N2 Delta-L
AMD Athlon XP 2500+
Asus TD9520 Video Card (GeForceFX 5200)
2 x Diamond Monster 3D II
Windows XP Home Edition with SP1a

I can't use FastVoodoo2 4.0 XP GE as-is, because of this: http://www.3dfxzone.it/enboard/topic.asp?TOPIC_ID=644

So, when I try to use MesaFX, I had the Mapmen returned an error when trying to map memory

Are you gonna try to fix this problem, so we can use MesaFX?
Is there any other way to try it?.

This error is not related to MesaFX. It's a Glide problem. I can't help much, because I never experienced it.

Can I help you somehow?

QuoteOriginally posted by PanoramixDruida

Can I help you somehow?

I wish you could. Does the problem reside with the NT core? I use XP only when absolutely necessary (ie: almost never, so it's only eating my HDD space).

Ciao Daniel,

QuoteDoes the problem reside with the NT core?

No.

That error is typcal when one Voodoo2 or Voodoo2 SLI and GeforceFX cards work on any Windows NT based system (like NT, 2k, XP).

QuoteI wish you could. Does the problem reside with the NT core?

Let me see if I could understand you. You wanna try it on Windows 9x/ME, don't you?. If this is the point, I can do it because I have dual boot. . Tell me.

Ciao,

Ok then, give it a try. I have "trial" boot (Win98SE+WinXPSP1+Slak9.1) and the least used OS is XP. The other two don't cause me troubles. Ehm... maybe because I use the V2 with a Napalm card.

@Glide:
Sorry, I must have been drunk... lemme rephrase: does the problem exhibit under NT core only (NT, 2k, XP)?

Ciao!

Many people get this error message "Mapmen returned an error when trying to map memory" using Voodoo2(s) with GeforceFX cards or with a nForce\nForce2 based motherboard: this issue arises with all FastVoodoo2 drivers on Windows NT/2000/XP OSes while there are not problems on Windows 98/ME.

The problem are glide2x/3x libraries: these, with some hardware configurations - see above - and Windows NT/2k/XP, cause mapmen error when try to run a GLide game like UT (for example) or OpenGL game like Quake 3 (for example) via Mesa or WGL.

Other people with Intel chip-set motherboard don't have this issue using Voodoo2 with any Radeon cards (9800Pro too) and Windows NT/2000/XP...

For more infos, you could read a big help topics number in this forum section.

Uhmmm... lemme see.

The main card has a physical address which gets mapped by winblows. The V2 has another physical address. During initialization, Glide2x/3x will try to map the physical address into linear space. It either doesn't find the space (very unlikely), tries to map over an allocated area (stupid) or doesn't do something right from the NT point of view (I guess NT takes memory protection way to serious - every sane person who feels THAT paranoid should switch to Linux, anyway).

Now, since I'm using V2 only with Glide / OpenGL applications, I don't even install it. When "whendoes" asks me about new hardware, I let it make its show, but when I am being asked for the driver files, I just postpone it. In order to use the card, I copy Mesa, Glide and FXMemmap into the game's dir. Of course, this means I loose that control panel, but I'm pretty skilled with envvars heheh. And it feels great doing things MY way. I also hate my HDD being bloated with a dozen files when I know I'm using only 3 of them. For DyrektEks you NEED to install the card, though. THEIR way.

Keep in mind that this doesn't mean FXMemmap won't die horribly. It all boils down to memory management, not a true HW conflict. I'll try and have a look.

Well, I've tried the following drivers on Windows 98 SE:

https://www.3dfxzone.it/dir/3dfx/voodoo2/downloads/fv2_4.0_ge.htm

and

https://www.3dfxzone.it/dir/3dfx/mesafx/download/index.php

and followed all the directives. I've not experienced the Mapmen returned an error when trying to map memory error.

I've only tried Quake. I've notecied that the guns and monsters are all white -yes, the color white-. I'll post some pictures as soon as I can. The HyperSnap is not working, so I have to fix it.

Thanks guys!

I took a horror trip into XP last night, w/o experiencig the "mapmem returned..." issue. At first, I thought the big behemoth indulges the small behemoth. So I stuck a crappy geffo as an alternative. Still works.

So, can you post step by step how do you do not to have this error?. For example:

1.) Installed FV2 4.0 XP GE drivers.
2.) Installed WinXP Fix for Mapmen returned an error when trying to map memory
3.) Copied glide[n]x.dll into [n] folder.
4.) Copied MesaFX.dll into [n] folder.
.
.
n.) Done.

Thanks Glide.

Easy: 3), 4), n)

Letting alone the joke, I need more info about YOUR installation (that is, the order in which you installed video drivers and so on). Worst case, drop me an email.

System Specs:

Motherboard MSI K7N2 Delta-L (http://www.msicomputer.com/product/p_spec.asp?model=K7N2_Delta-L&class=mb)
AMD Athlon XP 2500+ (Barton Core)
256Mb RAM PC400
Asus V9520/TD (GeForceFX 5200 http://usa.asus.com/products/vga/v9520td/overview.htm)
2 x Diamond Monster 3D II (8Mb. each one)
SM56 Motorola PCI Modem
HDD 80Gb.
Samsung CD-RW 48x12x24
Creative CD 52x
PSU 400W

Everything works fine!

1.) Installed Windows 98 SE/XP
2.) Installed nForce2 drivers
3.) Installed DirectX 9.0b Redist
4.) Installed Internet Explorer 6 SP1 -Windows 98 SE-
5.) Installed Norton Internet Security -Windows 98 SE-, Norton AntiVirus -Windows XP-
6.) Installed Asus V9520/TD Video drivers
7.) Installed Diamond Monster 3D II Video drivers -FastVoodoo2's-
8.) Installed Service Pack 1a -Windows XP-
9.) Installed Windows Updates
.
.
.
n.) Finished

So, does it work or does it not?

Have you tried to install the Voodoo2 drivers and give it a 3D run, using the main card as a VGA adapter only (no drivers for the primary card). I'm interested if the memory mapping conflict occurs due to HW physical addresses or linearly mapped addresses as built by drivers.