PDA

View Full Version : ERRORs as soon as i run the .exe ... ???


Chrissii
October 22nd, 2003, 17:45
Okay, I'm not sure what's going on here... I'm new to the N64 Emulation world and such. But, when I try to run the nemu64.exe, i get one of two errors as soon as the window opens, before i can even click on anything...

"Nemu64 has caused an error in
LEMCOMBINEDEBUGGER.DLL.
Nemu64 will now close."

..hmm... now it's not doing it anymore, but before it was alternating between the above message and the same one except with "DEBUGGER.DLL" as the source of the trouble. :( can anyone help me out here?
RJARRRPCGP
October 22nd, 2003, 18:18
Those messages mean you have a crashing problem.

We are required to know what PC specs you have (PC hardware).
This includes:

1. motherboard

2. chipset

3. processor

4. video card

5. sound card
Chrissii
October 22nd, 2003, 18:25
Those messages mean you have a crashing problem.

We are required to know what PC specs you have (PC hardware).
This includes:

1. motherboard

2. chipset

3. processor

4. video card

5. sound card

okay... well to be honest i don't know where to find that information on my computer. :doh:
RJARRRPCGP
October 22nd, 2003, 19:30
When you boot up your PC, do you see any hardware information?
Clements
October 22nd, 2003, 19:35
I'm no expert on hardware matters, but I do know that you can use a simple proggie called CPU-Z to find pretty detailed information about your system including motherboard that is often absent using certain built-in Windows programs. Helped me when I had my computer upgraded. Here:

http://www.cpuid.com/cpuz.php
Lemmy
October 26th, 2003, 14:23
try removing the file lemcombinedebugger.dll.

its in the plugin sub-directory of nemu.


hf
Lem

Okay, I'm not sure what's going on here... I'm new to the N64 Emulation world and such. But, when I try to run the nemu64.exe, i get one of two errors as soon as the window opens, before i can even click on anything...

"Nemu64 has caused an error in
LEMCOMBINEDEBUGGER.DLL.
Nemu64 will now close."

..hmm... now it's not doing it anymore, but before it was alternating between the above message and the same one except with "DEBUGGER.DLL" as the source of the trouble. :( can anyone help me out here?