Odd problem when using the Commodore 64 system

thirtywinter · Sun Dec 25, 2016 2:52 am

Hey all, I was very excited to discover mGalaxy as I liked the presentation (especially the premium ones, very nice)

Anyhoo, I was creating a database for the Commodore 64 and I installed Vice64 and pointed the roms and the executables as prompted and even added paths for the extra stuff like screenshots and whatnot.

Here's my main issue, it doesn't seem to be able to find any commodore 64 games that are actually incorporated into the database and the few hits it did get it didnt appear to update anything as the presentation was basically the filename and with a blue screen where the screenshot would be. Not only that, when I started the game it wouldn't even load the game in the emulator. Matter of fact, at first I tried the zip files and it appeared to be loading but nothing happened so I put the d64 and t64 files directly into the subdirectory for the roms, but then it said the folder was empty or that it couldn't read the roms.

The roms work fine mind you because when I run the directly from vice64 they work just fine.

Advice would be appreciated as I really wanted to like this one.

Aeliss · Sun Dec 25, 2016 9:59 am

Please try with database disabled (disabled in mGalaxyRunaway).

I m trying with vice 2.4 (x64.exe) rom in D64 format, for the moment it's working fine.

I m trying the database update online and same than you, no picture for the moment, need to check later (it can come from the online database)

, I was creating a database for the Commodore 64 and I installed Vice64 and pointed the roms and the executables as prompted and even added paths for the extra stuff like screenshots and whatnot.

Hu, you have first configure all the systeme and AFTER create the database ?

Sun Dec 25, 2016 10:03 am

Here's my main issue, it doesn't seem to be able to find any commodore 64 games that are actually incorporated into the database and the few hits it did get it didnt appear to update anything as the presentation was basically the filename and with a blue screen where the screenshot would be.

When you speak of "database", did you create a database from mGalaxy_Runway ("DB UPDATE" tab)...or do you mean "my list of files" ?

As a reply I will give you a little summary on how things should be

1. The roms should have file extensions recognized my mGalaxy (this info is listed in mGalaxy_Runway, just below the "Roms" field)

2. The screenshot must have the same name as the rom file and the file format is PNG (so, for a 'Zaxxon.zip' game the screenshots should be named 'Zaxxon.png')

Not only that, when I started the game it wouldn't even load the game in the emulator. Matter of fact, at first I tried the zip files and it appeared to be loading but nothing happened

This is a winvice related problem. I think that you must have a 'unzip.exe' application in the winvice folder to get the .zip compatibility!

I put the d64 and t64 files directly into the subdirectory for the roms, but then it said the folder was empty or that it couldn't read the roms.

At that stage, I don't know if there's still a folder with the zip files elsewhere in your rom folder?
If I were you, I would point mGalaxy-Runway to a simple folder with all the .d64/t64 files...mGalaxy will find them immediately!

Sun Dec 25, 2016 10:59 am

m trying the database update online and same than you, no picture for the moment, need to check later (it can come from the online database)

I'm creating a database right-now for the C-64 with a No-Intro set (1907 files) (Commodore_-_64_(Tapes)_(20120223) )...and everything is working as it should!

TheGamesDB, User intervention: None (unambiguous names only)

The same for Screenscraper

Aeliss · Sun Dec 25, 2016 12:02 pm

I m making a try with GoodGb64 database (17 000 files), 2 tries, 2 freezes but no pictures yet ^^.

Aeliss · Sun Dec 25, 2016 12:15 pm

Ok so new try with "no server", database created and working.
But if you don't have screenshot it's normal, only 320 for mGalaxy test and only 900 games present on the database (how you can have 1907 games found???) . I think it's a better idea to find a SS pack on google.

New try with zip format.

Sun Dec 25, 2016 1:11 pm

how you can have 1907 games found???

"New games found" is related to the user's file to tell him how many new file were found in the rom folder since the last update!

thirtywinter · Sun Dec 25, 2016 4:02 pm

mgalaxy wrote:
m trying the database update online and same than you, no picture for the moment, need to check later (it can come from the online database)
I'm creating a database right-now for the C-64 with a No-Intro set (1907 files) (Commodore_-_64_(Tapes)_(20120223) )...and everything is working as it should!

TheGamesDB, User intervention: None (unambiguous names only)

The same for Screenscraper

Hmm... I was using the goodGB64 roms. I'll give those a go then.

thirtywinter · Sun Dec 25, 2016 4:06 pm

mgalaxy wrote:
I put the d64 and t64 files directly into the subdirectory for the roms, but then it said the folder was empty or that it couldn't read the roms.
At that stage, I don't know if there's still a folder with the zip files elsewhere in your rom folder?
If I were you, I would point mGalaxy-Runway to a simple folder with all the .d64/t64 files...mGalaxy will find them immediately!

That's what I tried to do when I tried just the .d64/.t64 files and got nowhere. Just a folder and the roms and nothing else and still error messages that the folder is empty.

I do see that somebody else used a different set of roms than me and I'm going to give those a try and see what happens.

Sun Dec 25, 2016 4:09 pm

thirtywinter wrote:
mgalaxy wrote:
I put the d64 and t64 files directly into the subdirectory for the roms, but then it said the folder was empty or that it couldn't read the roms.
At that stage, I don't know if there's still a folder with the zip files elsewhere in your rom folder?
If I were you, I would point mGalaxy-Runway to a simple folder with all the .d64/t64 files...mGalaxy will find them immediately!
That's what I tried to do when I tried just the .d64/.t64 files and got nowhere. Just a folder and the roms and nothing else and still error messages that the folder is empty.

I do see that somebody else used a different set of roms than me and I'm going to give those a try and see what happens.

No, mGalaxy won't tell you that a folder is empty if there are roms (with allowed file extension) inside..sorry!

When you set your paths, did you think to click on 'Save' before quitting Runway?

thirtywinter · Sun Dec 25, 2016 6:55 pm

mgalaxy wrote:
thirtywinter wrote:
mgalaxy wrote: At that stage, I don't know if there's still a folder with the zip files elsewhere in your rom folder?
If I were you, I would point mGalaxy-Runway to a simple folder with all the .d64/t64 files...mGalaxy will find them immediately!
That's what I tried to do when I tried just the .d64/.t64 files and got nowhere. Just a folder and the roms and nothing else and still error messages that the folder is empty.

I do see that somebody else used a different set of roms than me and I'm going to give those a try and see what happens.
No, mGalaxy won't tell you that a folder is empty if there are roms (with allowed file extension) inside..sorry!
When you set your paths, did you think to click on 'Save' before quitting Runway?

Wow... ok. I can *assure* you I thought to click save after setting the paths. You seriously think I did not check and recheck that after the fact to make sure? I'm telling you the error message indicated either an empty folder or that the roms were defective. (Which they are not) I still haven't tried other roms, but when I have I'll post an update.

Like god damn, one would think you would know your own product.

jmd · Sun Dec 25, 2016 7:03 pm

Like god damn, one would think you would know your own product.

He does, for sure!
We are here to bring you help, so please stay nice with us!
Just an info: mGalaxy does NOT have warning about 'defective roms'...so the message is coming from elsewhere!

thirtywinter · Sun Dec 25, 2016 7:09 pm

jmd wrote:
Like god damn, one would think you would know your own product.
He does, for sure!
We are here to bring you help, so please stay nice with us!
Just an info: mGalaxy does NOT have warning about 'defective roms'...so the message is coming from elsewhere!

Sigh.. I'm looking at the error message right now in mGalaxy Runway. But it's fine, don't believe me and pat yourself on the back thinking you did an outstanding job today.

All I am doing is telling you guys what I am seeing, but if that falls on deaf ears so be it. I'm not here to argue, I'm just letting you know what I am seeing as an end user. That's it. That's all. Sorry you find that offensive. "Did you think to click on save" snort.

thirtywinter · Sun Dec 25, 2016 7:32 pm

Just wanted to add one more thing. I can't find the rom set that is referenced to (No-Intro set (1907 files) (Commodore_-_64_(Tapes)_(20120223))

Matter of fact, the latest No-Intro set I have I can only find .tap files (Pretty sure they are the same as .t64 files) and .nib files which I am assuming is for disc files. Is it possible to get a magnet link or something like that to this set that is being used? I've looked the usual places, but I can't find that particular set. So is there something I'm missing?

Sun Dec 25, 2016 8:00 pm

Sigh.. I'm looking at the error message right now in mGalaxy Runway

Once again, the message you're referring to indicates that the folder is empty OR filled with files whose extensions are not 'compatible' (understand 'not .d64, .t64, .zip')