PJ64 1.x doesn't like WinXP reinstallations it seems

neo_bahamut1985 · Post by **neo_bahamut1985** » Thu Dec 18, 2008 11:50 pm

So, as many of you know, I upgraded my system to a Quad Core CPU and everything is working very smoothly (for which I'm very happy about). But here's what doesn't make sense; out of all the programs that work like a charm (emulators such as GBA, Genesis, etc) Pj64 1.6 or PJ64 1.7.0.xx doesn't. I keep getting this strange error, and this isn't your typical error, either. Here's what I mean:

I have been using this emulator since its release back in 2001, and have never so much as seen this error before. I'm thinking this emulator doesn't like CPUs that have more that one core, but I'll just end up being wrong anyway. Is this OS related? Do I have to have to have a certain service pack installed? All my hardware drivers are up to date (video, sound, etc).
I've even gone as far as installing it in a new location, on another hard drive. Isn't there anything else I can do? I know my system specs are way beyond minimum requirements: CPU - Core 2 Quad Q6600 RAM - 2048MB DDR2 800 OS - WinXP Home Video - PNY GeForce 9600GT 512MB GDDR3 Oh, and I did get this version legit.

ShadowFX · Post by **ShadowFX** » Fri Dec 19, 2008 12:05 am

It's one of the reasons I stopped using it some time ago, next to the connection errors I was getting with the security system that has been built-in.

Did you try setting the affinity to only one CPU? In any case, it's not uncommon for these errors to popup with this emulator. My best bet is that you can do little about it right now. I got a legit v1.7 beta as well and I can tell that this beta is far more unstable than it ever was. Yes I know it's beta.

kick · Post by **kick** » Fri Dec 19, 2008 12:09 am

Try running it inside a Virtual machine (VirtualBox) or a Linux distro with WINE.

creaothceann · Post by **creaothceann** » Fri Dec 19, 2008 12:12 am

VirtualBox has OpenGL support now for guest OSes... maybe you'll get not much of a speed loss (haven't tested it yet).

neo_bahamut1985 · Post by **neo_bahamut1985** » Fri Dec 19, 2008 12:17 am

Setting the CPU affinity to one doesn't do jack squat. Funny how PJ64 1.6, which is official, has the same issue. Mupen64 plus 1.3 (or whatever the heck it's called) doesn't load, either. Only if people coded N64 emulators to use two cores...

franpa · Post by **franpa** » Fri Dec 19, 2008 5:35 am

PJ64 1.6 works fine on core 2 duo and penitum 4 with HT processors, it may be related to more then 2 cores/processors.

neo_bahamut1985 · Post by **neo_bahamut1985** » Fri Dec 19, 2008 5:40 am

Well, this motherboard supports Core 2 Duos as well, but changing the CPU just to get one program to work isn't worth it. If I had known that, I would've gotten a Duo instead...(crap). So, basically, until they find a workaround, I'm pretty much screwed. So, my earlier conclusion was right; N64 emulators in general are biased against multi-threaded CPUs. I know it wouldn't have to take advantage of all four cores, but the fact that it doesn't work with a CPU that's been out for less than two years is inexcusable. I've posted this issue on the PJ64 Beta Forum, so, I guess I'll wait to see what the PJ64 programmers say. Couldn't I just use an OS emulator?

Neo Kaiser · Post by **Neo Kaiser** » Fri Dec 19, 2008 6:24 am

Please post this on Ngemu forums to see if they can fix this.

franpa · Post by **franpa** » Fri Dec 19, 2008 6:37 am

how do you change how many CPUs it uses? do you change it after opening PJ64 or before? (there are tools to adjust exe files to launch using specific CPU/cores.

Also, do you have Service pack 3? it includes a hotfix for Core 2 DUO CPUs.

Deathlike2 · Post by **Deathlike2** » Fri Dec 19, 2008 6:38 am

Multi-core CPUs don't automagically make things better.

kick · Post by **kick** » Fri Dec 19, 2008 8:36 am

A fast Dual core is much better than a slower Quad (except for emulators like PCSX2 and Dolphin)

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 8:55 am

The error posted is not related to anythng system specific, but to the fact its a WIP beta with issues.

As to anything else, installing the latest Dx Bimonthly, VC6, 2005 sp1 and 2008 sp1 redists.
Application compatibility toolkits,

and disabling super fetching if using vista....

.....and do a Repair install of XP to update the HAL.

Btw.

Its YOU with the problem, its not an overall issue with Multicore setups, and the only issue PJ64 has with multithreading is it screws the VI counter up.

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 8:59 am

ShadowFX wrote:It's one of the reasons I stopped using it some time ago, next to the connection errors I was getting with the security system that has been built-in.

Did you try setting the affinity to only one CPU? In any case, it's not uncommon for these errors to popup with this emulator. My best bet is that you can do little about it right now. I got a legit v1.7 beta as well and I can tell that this beta is far more unstable than it ever was. Yes I know it's beta.

Latest Alpha's are far MORE stable... still crashes on JFG, but Zilmar is working on it.

ShadowFX · Post by **ShadowFX** » Fri Dec 19, 2008 9:47 am

Squall_Leonhart wrote:Latest Alpha's are far MORE stable... still crashes on JFG, but Zilmar is working on it.

An alpha that is more stable than beta... it defies logic. One would think that all the versions before this magical version you're talking about were alphas rather than betas. In any case, it's good to hear that zilmar is aiming towards stability again.

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 9:58 am

ShadowFX wrote:
Squall_Leonhart wrote:Latest Alpha's are far MORE stable... still crashes on JFG, but Zilmar is working on it.
An alpha that is more stable than beta... it defies logic. One would think that all the versions before this magical version you're talking about were alphas rather than betas. In any case, it's good to hear that zilmar is aiming towards stability again.

Banking on Logic isn't logical.

ShadowFX · Post by **ShadowFX** » Fri Dec 19, 2008 10:03 am

I totally forgot discussing stuff with you isn't going anywhere, forget what I said earlier.

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 10:59 am

ShadowFX wrote:I totally forgot discussing stuff with you isn't going anywhere, forget what I said earlier.

Logically.

anyway a number of issues have been fixed so far, both core and plugin wise.

neo_bahamut1985 · Post by **neo_bahamut1985** » Fri Dec 19, 2008 5:21 pm

Right, before I reinstalled XP (on the old motherboard) it at least loaded the game, likely due to the fact that I had service pack 3, but since I don't have the installed yet, that would explain why it's having issues. And where can I get the kind of program to specify which cores to use? I just go to the Task Manager and specify one CPU but that doesn't do anything (after I open it).
And clock speed isn't an issue with the programs I run; all others seem to run flawlessly. The fact that PJ64 1.6 isn't a beta I find equally confusing...

Edit 10:00AM: Ooookay... I checked the PJ64 beta forums and was instructed to try disabling DEP. I checked the DEP, and was selected to "Windows-essential programs only" (or rather, switched from "only have DEP for essential programs" to "have DEP enabled for all programs except for those I choose"; I chose to add exceptions to the DEP list). After doing that, I rebooted the computer and tried once more and the bloody program still refused to run a game. What else is there to do!? I was told that people are able to run it on a Quad Core. Obviously, this isn't the case. Like I said before, CPU discrimination. I shouldn't have to get an entirely new CPU just to get one out of several dozen programs to work.

Edit 10:25AM: And upgrading to the latest XP updates (SP3) didn't help, either.

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 8:26 pm

change /noexecute=optin to /execute=optin in the boot.ini

>.> still think theres something else wrong, since guru3d has screenshots from C2D owners of various games.

neo_bahamut1985 · Post by **neo_bahamut1985** » Fri Dec 19, 2008 8:28 pm

Originally, switching the plugins back and forth didn't do anything to resolve the issue. Well, apparently, glide has an issue with Quad Cores, not the emulator. Every other non-glide emulated plugin seems to load just fine. But, if that's the case, how could glide wrappers work before a reinstall and not after?! There's only one glide3x.dll and that's where it's supposed to be; the system32 folder.

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 8:39 pm

You shouldn't put that one in system32, its not meant to be a global wrapper, its only meant to work with the Glide64 plugin.

funkyass · Post by **funkyass** » Fri Dec 19, 2008 8:47 pm

glide plug-ins won't work because...

wait for it...

a bit more...

YOU DON'T HAVE A GLIDE WRAPPER INSTALLED!

Squall_Leonhart · Post by **Squall_Leonhart** » Fri Dec 19, 2008 8:48 pm

funkyass wrote:glide plug-ins won't work because...

wait for it...

a bit more...

YOU DON'T HAVE A GLIDE WRAPPER INSTALLED!

what do you think Glide3x.dll is?

yah, shut up and walk away now k.

neo_bahamut1985 · Post by **neo_bahamut1985** » Fri Dec 19, 2008 9:42 pm

I find it strangely funny by the fact that you assumed I never installed it in the first place; if that were the case, how else would I have been able to use it in the past? Here's glide3x.dll in the Plugin Folder
Here's glide in the root of the N64 folder If these are the wrong places, where should it go?

King Of Chaos · Post by **King Of Chaos** » Sat Dec 20, 2008 1:13 am

Meh, I notice PJ64 likes to pop up exception errors while playing Super Smash Bros (U), especially during the VS character selection. I believe this is a known issue though.