Hacking Rominator for NDS

[hankchill]

The Linux one doesn't work for ANYONE. It's a RealBasic bug which I have no control over. Bug reports have already been submitted to them so all I can do is wait for the next revision...

 

[beedog19]

Yo Hank, first of all, thank you so much for all of the hard work that you've put into this great program here. I've been using it for a while with very few problems. Unfortunately a few minutes ago I did encounter something strange.

I was attempting to update to the latest database and in doing so I got Error 1074 that said rominator had to shut down. I closed it out and re-opened it and now I'm getting an error that I believe someone else was getting where it says:
"Rominator has encountered an Error: Error Code 1057" I hit ok and get:
"Rominator has encountered an Error: Error Code 1033" I hit ok and get:
"Rominator has encountered an Error: Error Code 1034" I hit ok and get an empty Rominator

Now, this could be something up with my comp as it is a piece of crap, but I figured if it's not there's no way it can be fixed if you don't know about it, so I'm also going to submit these errors to ya.

Thanks again for the great program and sorry to add to your work

And I too am really looking forward to the new version

Balls! I just got Error 1035 when trying to submit my errors so this is going to have to be my official Error report.

Edit: Durr, I'm using it on Windows XP SP2

 

[hankchill]

You're not the only one. Something REALLY weird is going on here...

I KNOW WHY!

I will fix it now!

 

[hankchill]

edit: fixed. You will need to delete ALL settings and re-update. Very sorry about that

edit2: I could have SWORN I hit the edit button :/

 

[Salamantis]

edit: fixed. You will need to delete ALL settings and re-update. Very sorry about that

edit2: I could have SWORN I hit the edit button :/

Good. Now it works.

 

[beedog19]

edit: fixed. You will need to delete ALL settings and re-update. Very sorry about that

edit2: I could have SWORN I hit the edit button :/

Cool thanks, updating now!

EDIT: Working here too, thanks!

 

[Steevsee]

Hello to all
Just tried to delete my settings and other data, following unsuccessful database upgrade, but initially unable to, as computer stated the files were still being used despite having shut down rominator. opened task manager and noted it was still running in background. stopped task and then able to delete files.
Have now successfully updated database (Thanks Henry for super quick fix!) and all seems to be back on track and looking good.

Just thought others might be experiencing similar problem with deleting old files.

 

[sepinho]

I've been having problems ever since I've deleted the settings: For some odd reason, it won't show release numbers, game icons or file infos for unzipped *.nds files. All of the zipped roms work flawlessly. Anybody else encountered this problem? It worked well before deleted the old data folder.

Awesome tool nonetheless, btw..

 

[Salamantis]

I've been having problems ever since I've deleted the settings: For some odd reason, it won't show release numbers, game icons or file infos for unzipped *.nds files. All of the zipped roms work flawlessly. Anybody else encountered this problem? It worked well before deleted the old data folder.

Awesome tool nonetheless, btw..

After deleting the settings, did you re-update?

 

[sepinho]

Now that's what I call I quick reply!

Yepp, I did update again.
In case it matters: I don't store my roms in Rominator's Games folder. They're hosted on a separate debian-based file server.

 

[hankchill]

It doesn't matter where you store the games -- If Rominator picks it up, then you're good.

Check what the update version is at the top of the window. Also, did you update AFTER adding in the games, or before? If it was After, press the Refresh button.

 

[sepinho]

Jeez, amazing support you guys are providing. I'm seriously impressed!

Romulator says "Update 1976".
I've just hit Refresh again for good measure, but it didn't help. Romulator does recognize recent roms, as long as they're not unzipped. When I right-click on an unzipped rom and choose "Auto-Rename Selected", the bottom bar of Romulator says "'such-and-such' has no database info!" I'm certain the files are valid, they were recognized before I deleted the settings after all..

 

[hankchill]

salamence502 is a buddy of mine, and he's learned most of the ins and outs of Rominator as well, so more than one of us are glad to provide support!

Try something for me: Remove the game from the list, and then re-add it. Does it recognize it?

 

[sepinho]

You rock! I don't know why, but that did it. Now all I have to do is delete a few (...) files from the list and re-add them.
Tomorrow though! It's a little late over here in Germany and I have to go to work early tomorrow. I'm off to bed. You guys have a nice sunday though!

Thanks a bundle hankchill and salamence502 (I've read your rather useful quickstart guide before I bothered you guys).

 

[hankchill]

You rock! I don't know why, but that did it. Now all I have to do is delete a few (...) files from the list and re-add them.
Tomorrow though! It's a little late over here in Germany and I have to go to work early tomorrow. I'm off to bed. You guys have a nice sunday though!

Thanks a bundle hankchill and salamence502 (I've read your rather useful quickstart guide before I bothered you guys).

Great, now go read the 70 page manual!

eh~heh

 

[shinji257]

Wow. That went quick. I missed the last database update so wasn't bit by that but I did get that odd bit about the game list. Removing and allowing it to re-list it took care of it. Remember that happening before though too. Usually after a database update and on ones that were previously unidentified.

 

[Salamantis]

Wow. That went quick. I missed the last database update so wasn't bit by that but I did get that odd bit about the game list. Removing and allowing it to re-list it took care of it. Remember that happening before though too. Usually after a database update and on ones that were previously unidentified.

Yeah, there's a small problem with the Refresh button in Rominator. Hank said he'd fix it

 

[techforumz]

I can't seem to get this to work with my linux box. It gives me three errors, dumps core, and exits. I used the chmod, gzip, and ./ like I am supposed to.
Error 1:

Runtime Error 4: Failed Assertion
Press OK to Continue
Press Cancel to Quit.

Please report what caused this error along with the information below.

../Common/loaderX86.cpp: 268
Failure Condition: lib->mLibraryHandle
Missing shared library /usr/lib/libc.so

Pressing OK gets me here:

Runtime Error 4: Failed Assertion
Press OK to Continue
Press Cancel to Quit.

Please report what caused this error along with the information below.

../Common/loaderX86.cpp: 282
Failure Condition: functionEntry
Could not resolve function 'time' in /usr/lib/libc.so

And then OK gives me yet another error:

Runtime Error 4: Failed Assertion
Press OK to Continue
Press Cancel to Quit.

Please report what caused this error along with the information below.

../Common/loaderX86.cpp: 282
Failure Condition: functionEntry
Could not resolve function 'localtime_r' in /usr/lib/libc.so

And then another 'OK' will yield the following error in the terminal:

Segmentation fault (core dumped)

Could this be an error with my installation? Or is this a glitch in the program. It would appear that it is exclusive to libc.so.

 

[Salamantis]

I can't seem to get this to work with my linux box. It gives me three errors, dumps core, and exits. I used the chmod, gzip, and ./ like I am supposed to.
Error 1:

Runtime Error 4: Failed Assertion
Press OK to Continue
Press Cancel to Quit.

Please report what caused this error along with the information below.

../Common/loaderX86.cpp: 268
Failure Condition: lib->mLibraryHandle
Missing shared library /usr/lib/libc.so

Pressing OK gets me here:

Runtime Error 4: Failed Assertion
Press OK to Continue
Press Cancel to Quit.

Please report what caused this error along with the information below.

../Common/loaderX86.cpp: 282
Failure Condition: functionEntry
Could not resolve function 'time' in /usr/lib/libc.so

And then OK gives me yet another error:

Runtime Error 4: Failed Assertion
Press OK to Continue
Press Cancel to Quit.

Please report what caused this error along with the information below.

../Common/loaderX86.cpp: 282
Failure Condition: functionEntry
Could not resolve function 'localtime_r' in /usr/lib/libc.so

And then another 'OK' will yield the following error in the terminal:

Segmentation fault (core dumped)

Could this be an error with my installation? Or is this a glitch in the program. It would appear that it is exclusive to libc.so.

It doesn't work for any Linux users. Hank already covered this problem many times. He is currently working with the RealBasic team to solve this problem. The only solution is to be patient

 

[techforumz]

Oh, sorry for not seeing that. But 102 pages, that's alot to read on a forum. Anyways, thanks for answering. I will be patient. Oh, and I don't know if he already covered this, but the windows zip is empty, maybe my download is corrupted, I don't know. Once again thanks for replying. And, Hank, that looks like a very nice app. Will be sure to try it out ASAP.

-- TechForumz