Major problems with PJ64...

[Sabotage]

Okay, here's the deal... two different computers, on one of them, PJ64 works perfectly. But on the other, I get these error messages, in this order:

"Graphics Error:
Direct3D failed to initialize
Error code: 8876086A
D3DERR_NOTAVAILABLE"

I click "OK", then:

"Error:
The default or selected video plugin is missing or invalid.

Check that you have at least one compatible plugin file in your
folder."

I click "OK" again, then it takes me to the plugins window, where apparently, I have all of the default plugins.I click "OK", then:

"Graphics Error:
Direct3D failed to initialize your HAL device
make sure you have a properly configured 3D graphics card compatible with Direct3D 6.0."

I click "OK", and I see my old friend:

"Error:
The default or selected video plugin is missing or invalid.

Check that you have at least one compatible plugin file in your
folder."

Obviously I can't load any ROMs. And I know I have a graphics card good enough to play N64 roms, because I was playing stuff like Grand Theft Auto: San Andreas without a problem (But it HAS been a while). So what's the deal here? My computer (the one I'm having this problem with) is an Acer Aspire T690 running Windows Vista, with an Intel Core 2 processor and 2 gigs of RAM. Can anyone help me?

[Jale]

Check if hardware acceleration is enabled in DirectX (type "dxdiag" in Start --> Run).

[Sabotage]

Okay, when I go to dxdiag, there's no place to enable hardware acceleration, the closest thing I see is where it says DirectX Features but all I see is this:

DirectX Features

DirectDraw Acceleration: Not Available

Direct3D Acceleration: Not Available

AGP Texture Acceleration: Not Available

It's like the computer thinks there isn't a graphics card installed, but I know there is... like I said, I used to play 3D based games on it. Maybe there's something wrong with my card, or is there something simple I can do to fix it?

[Sabotage]

I got it working! It turns out my drivers were disabled! I just had to go to Device Manager and enable it. I can't believe I couldn't figure that out before. But still, thanks for pointing me in the right direction!

[Jale]

Good you could solve this problem, but how could your drivers were disabled?

[Sabotage]

Maybe I'm using the wrong terminology or whatever, but when I went into Device Manager, in Control Panel, and I clicked the little plus sign to expand under "Display Adapters", it showed Intel(R) 946 Express Chipset Family, and when I right clicked it, it gave me the option to "Enable".

So I clicked it and it's working without any major problems, except when I play Donkey Kong 64, it looks like some texture layers are missing, for example, the little numbers on the teleport pads (for those who've played the game) are missing. It's not a big deal, but I thought I may as well bring it up and see if anyone could help.

Another minor issue is that when I try and play Pokemon Stadium 2 and use the N-rage input plugin to emulate the transfer pack, when I try to load a GB ROM it says "Can't open SRAM file! Continuing with null savedata.". But that's probably due to something I'm doing wrong.

[Jale]

Maybe I'm using the wrong terminology or whatever, but when I went into Device Manager, in Control Panel, and I clicked the little plus sign to expand under "Display Adapters", it showed Intel(R) 946 Express Chipset Family, and when I right clicked it, it gave me the option to "Enable".

The weird thing is, why was it disabled? Some other app or game did it?

So I clicked it and it's working without any major problems, except when I play Donkey Kong 64, it looks like some texture layers are missing, for example, the little numbers on the teleport pads (for those who've played the game) are missing. It's not a big deal, but I thought I may as well bring it up and see if anyone could help.

That game has known graphic issues, even for non-integrated graphic cards. I've tested it with DirectX 8 and DirectX 9 cards. On DX9 cards I can see the numbers on pads, but pads are always opaque.

Another minor issue is that when I try and play Pokemon Stadium 2 and use the N-rage input plugin to emulate the transfer pack, when I try to load a GB ROM it says "Can't open SRAM file! Continuing with null savedata.". But that's probably due to something I'm doing wrong.

You're missing the save file (.sav).

[Sabotage]

It was probably an application that changed the setting, I suspect it happened when I installed a new firewall on that computer.

DK64 works fine on the other computer (one I'm using now) even though it's much older, but the newer one doesn't have anything added, it's all the stock hardware that came with it, and I think this one has a new (fancier) graphics card in it. So that makes sense.

[JoshM22]

I was currently playing Zelda: Ocarina of Time with the latest Project 64 1.6. I have gotten pretty far in the game. When trying to enter the Forrest Temple I can get as far as the spider blocking the door and it comes up with an error message. Error message as follows: Application Core Error Code: 801EEc88 Unknown 05 BD FF EO. What does this mean? Is it fixable or is the game just not compatable yet?

[JoshM22]

An answer to the question above would be greatly appreciated. I hate to be ignored. I thought I would atleast be graceful here. Thanks .