A friend of mine has a PCI Diamond Monster Fusion (3dfx Banshee) and is trying to get Diablo II to run on Windows 98SE. The Video Setup Test runs fine and recommends 3dfx Glide, but also offers DirectDraw 2D as the alternative (oddly, it doesn't offer a Direct3D option at all). Diablo II recommends DX7.0a which is what is installed. I am using the latest video driver from Diamond.
When she starts Diablo II and begins playing, it gives an error message, something about "textcompression[something or another]: mipmap cannot span 2MB boundary". I click Ok and it throws a similar error but it is worded slightly different, still mentions 'mipmap cannot span 2MB boundary'. Then it freezes the whole system.
I went into Glide properties and found a setting that 'limits textures to 2MB', so I toggle that to enable it, then restarted, but it doesn't help. I SWEAR I've seen this error on another computer with a Diamond Monster Fusion a long time ago, and I thought that Glide setting corrected the issue, but it does nothing on this system.
I went to Blizzard's support site and searched around, but could find no topic resembling this error. Anyone seen this before? I haven't applied any Diablo update patches yet, but that's my next step.
Oh, BTW, DirectDraw 2D mode runs fine, and the image quality is virtually the same, but MUCH slower.
When she starts Diablo II and begins playing, it gives an error message, something about "textcompression[something or another]: mipmap cannot span 2MB boundary". I click Ok and it throws a similar error but it is worded slightly different, still mentions 'mipmap cannot span 2MB boundary'. Then it freezes the whole system.
I went into Glide properties and found a setting that 'limits textures to 2MB', so I toggle that to enable it, then restarted, but it doesn't help. I SWEAR I've seen this error on another computer with a Diamond Monster Fusion a long time ago, and I thought that Glide setting corrected the issue, but it does nothing on this system.
I went to Blizzard's support site and searched around, but could find no topic resembling this error. Anyone seen this before? I haven't applied any Diablo update patches yet, but that's my next step.
Oh, BTW, DirectDraw 2D mode runs fine, and the image quality is virtually the same, but MUCH slower.