View Full Version : slow PC, but on winXP --> which N64 emu should i use?
February 26th, 2003, 08:03
I had UltraHLE running on my PC for about 3 years on Win98 SE (P3 550MHz, 128MB SDRAM, 16MB voodoo3 3000) and for the most part, about 4.5 roms worked fine. I recently made upgrades to my system, relevant ones being a much bigger hardrive, 640MB of SDRAM, and winXP pro.
i just realized :( that UltraHLE isN'T compatable w/WinXP
my questions are:
--Is there a patch to allow UltraHLE to run successfully on WinXP?
--this SuperHLE, is it a "spinoff" of UltraHLE? (im having trouble finding some background info on it)
--I adequately meet the min reqirements for SuperHLE, but definately NOT the recommended requirements. Has any1 used superHLE on a PC w/similar specs as my own and can tell me how well it runs? also how it stacks up against to UltraHLE?
February 26th, 2003, 08:05
Run it in windows98 compatibility mode. With your system, other emus wouldn't really be enjoyable (e.g. sound skips, slowness, etc).
SupraHLE is a hack made by hex-editing and patches, all done without the source. It adds minor speed ups and some quite impressive compatibility upgrades (considering dominator did not have the source code at the time). Its requirements are the same as UltraHLE's. You should try UltraHLE2064, it's a complete overhaul done with the source itself (by dominator and some other known people.. Quvack, Aprentice, Mcleod, Malcolm, Dominator...), Much more compatible, and it supports Zilmar spec plugins. It uses the same HLE cpu core so requirements are about the same still.
February 26th, 2003, 19:43
ugh, I've done what you suggested and even installed glide2x.dll and glide3x.dll into my Windows\System32 dir as requested by the error message. Now I'm getting this:
AppName: ultra.exe AppVer: 220.127.116.11 ModName: unknown
ModVer: 0.0.0.0 Offset: 00000000
(there's also a detailed tech report, but it won't allow me to copy&paste it)
THis occurs after I successfully opne the UltraHLE window and right after i try to load my first rom.
I'm guessing im still missing some winXP specific files. Can any1 who was able to get Ultra to work on winXP point me in the right direction?
BTW, all UltraHLE roms oughtta be .v64 right? So if we see something's that's a .rom file, all we need to do is simply change the extension?
(my sys specs are of course, still listed on the first post)
February 26th, 2003, 19:59
Originally posted by ackmondual
ugh, I've done what you suggested and even installed glide2x.dll and glide3x.dll into my Windows\System32 dir as requested by the error message.There's the problem right there. You're not supposed to just copy those files into the system directory, they're supposed to be installed with the videocard drivers. I suggest you re-install your drivers for Windows XP (www.voodoofiles.com has loads of them). Do NOT use the drivers supplied by Microsoft, as they do not support Glide or OpenGL.
I believe N64 ROMs come with .Z64, .V64, or .ROM extensions. You shouldn't need to rename anything.
February 27th, 2003, 10:19
.... any suggestions on drivers? I've tried v3-w2k-xp-1.09-beta10, amigamerlin21, and vs-wxp-1.00.06-alpha so far. The last one worked great for a short while. Was able to get a rom going but going back to the desktop (either for save state access or exiting) froze the system. I've system restored 8 times now.
February 27th, 2003, 20:36
Yep, I would go with the v3-w2k-xp-1.09-beta10 from http://www.tdhq.com They work great.
February 28th, 2003, 06:06
do I have to uninstall my old WinXP video drivers before reinstalling any new ones?
I seem to be getting different results everytime I try even the same driver. For example, my best progress was the 1st time when installing amigamerlin21 (Voodoo drive) zip files (after extraction of course), i got a rom to work, but that driver messed up my desktop display after quitting the emu
when I install the same driver the 2nd time (after undoing the previous effects with system restore) I get this during the 2nd installation
Error:1904 ……………… HRESULT –2147418113
Now this is just confusing the heck out of me. The only other thing I did video-wise was install directX 9.0
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.