Jump to content
  • 0

Nemu 64 Crash/Hylian Toolbox Crash


Setzer Gabbiani
 Share

Question

Whenever I open up Nemu64, it gives flashes of a few small windows, and then crashes before it can really let me do anything. I cannot find out the reason for this. I am running on Windows 7 64-bit.

 

On the other hand, Hylian Toolbox will successfully open and load the debug rom, however, it crashes without warning once I click on one of the names in the "browse" menu to the right.

 

Any ideas guys?

Link to comment
Share on other sites

Recommended Posts

  • 0

I do not believe I have any special drivers installed on my computer, just the basic ones that come with the machine, and the one for my wireless mouse. The directory that I am running it from is the basic Nemu64 folder (the one that contains config, gs_dll.dll, kailleraclient.dll, etc...)

Link to comment
Share on other sites

  • 0

Thanks a bunch for taking the time to do that, but it still doesn't work. This is leading me to believe it is a problem with my computer itself.

However, with yours, I get an extra error message before the crash. "Error accessing drive or invalid folder. Setting to C:" I'm just assuming that your directory isn't C:

 

Right after clicking OK, I get the same crash.

Link to comment
Share on other sites

  • 0

Place your ROM or nemu in at a path that doesn't have spaces. For example, place the ROM directly on your harddrive (C:ZELOOTMA.Z64). Nemu is picky about trying to open files that have spaces in their path.

 

As for Hylian Toolbox, yeah it does that sometimes. Flotonic programmed the API from scratch so I wouldn't doubt that he might have missed some conditions where the program could close unexpectedly.

Link to comment
Share on other sites

  • 0

Well, back to the start, my problem with Nemu is that I can't even get to a step that involves opening a ROM. I click on the program, and it immediately crashes once I am able to see the window itself.

 

I don't believe I have ever had this type of issue before. The problem has always been quite obvious and easily fixable, but in this situation, I can't pinpoint exactly what's going on.

Link to comment
Share on other sites

  • 0

Sorry for the confusion earlier, but when I was asking about the directory I meant its path, rather than its contents. Mine is "C:UserswareyaDesktopgamn64nemu64" -- note that it's 100% accessible to a non-administrator user and has no spaces in it. Nemu64 is known to have problems with paths that include spaces in them, both for launching and for loading roms. Just as a sanity check, you should make sure that it's not being run with anything weird set in its file properties (right click > properties > compatibility) -- nemu64 is known to load fine with none of those set. Also, Nemu64 can crash on plugin loading, in which case you should try to make it load with an entirely different plugin directory that's known to work.

Link to comment
Share on other sites

  • 0

C:UsersComputerDesktopZelda Moddingnemu64nemu64I feel so idiotic, I know exactly what directory means. I have no idea why I told you what I did, haha!

I removed the space in Zelda Modding, and yet it still experiences the same crash. After checking out the properties, I saw that none of the boxes were checked.

Link to comment
Share on other sites

  • 0

Alright, now rename your Plugin directory to something else (like Plugin_) and replace it with the dir in here: https://dl.dropboxusercontent.com/u/1811521/nemuplugins.zip

I have no idea if this will work or not but I've had nemu crash on startup due to a misinstalled Glide64 so I figure it might be a problem with Nemu to crash if something's wrong with a plugin in a really weird way; it's worth trying.

 

If it doesn't work you're free to replace this plugin directory with your original, of course, but it's just troubleshooting.

Link to comment
Share on other sites

  • 0

This is my entire Nemu64 directory as of a few days ago:

https://dl.dropboxusercontent.com/u/1811521/nemu64.7z

Put it somewhere without spaces (like C:emunemu64 for example) and run Nemu64.exe. If you don't have a good AV program or you're paranoid like I am then you may replace the nemu64.exe I provide with the one you already have, or one from a trustworthy emu site somewhere. See if it crashes the same way. If it does, there's some problem with your setup, and I won't be able to help troubleshoot anymore. It doesn't, then it's a problem with your nemu itself; uploading the whole nemu dir somewhere and letting me at it would be a good idea in that case.

Link to comment
Share on other sites

  • 0

It does appear that your Nemu is encountering the same error, so it is a problem on my end. This is an incredibly strange concept, though. I have no idea what would be wrong with mine. This computer in particular has never had any trouble opening or running anything until now.

 

I do want to thank you for taking your time to help me, though. It honestly means a lot to me. I'll just wait around to see if anyone else has another solution that might help.

Link to comment
Share on other sites

  • 0

http://www.mediafire.com/?af5ka6kurq7jrd6

 

That's the two screenshots I have before and after the error. If I would have taken about 10, I might have been able to capture the rapid moving windows that start popping up right when I click on Nemu64. They appear all around the main window, but disappear within about a half a second, then I get that error that you see.

 

Guess that was stupid of me. I forgot about the image tags. Posted ImagePosted Image

Edited by Setzer Gabbiani
Link to comment
Share on other sites

  • 0

Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.130318-1533) Language: English (Regional Setting: English)System Manufacturer: Alienware System Model: M17xR4 BIOS: InsydeH2O Version 03.72.24A10   Processor: Intel® Core i7-3630QM CPU @ 2.40GHz (8 CPUs), ~2.4GHz Memory: 8192MB RAMAvailable OS Memory: 8074MB RAM   Page File: 3280MB used, 12866MB available   Windows Dir: C:Windows   DirectX Version: DirectX 11

Link to comment
Share on other sites

  • 0

Running as administrator gives me the exact same results as doing it normally. The odd crash. I am unsure what plugins are set for it, because regardless of what they are, I can't get in the actual program to do anything. It just crashes right away. From the plugin folder I was given, I have "1964 video, Direct 64, Glide, Jabo, and Rice (Assuming those are all plugins)".

Link to comment
Share on other sites

 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.