Author Topic: Changing Mountpoints?  (Read 3659 times)

Stephanie

  • Guest
Changing Mountpoints?
« on: April 15, 2010, 05:07:27 am »
I've read through this old thread about redirecting the mountpoint for 'Interesting Games' to the SD card:
http://boards.dingoonity.org/dingoo-hacks/relinkadjust-'interesting-game'-mountpoint/

I was wondering if it is difficult to change the mountpoints for these menu items?

I've got the HXF tool and have looked around inside the a320.hxf file but don't really know where to look.

What I'd like to do is to redirect the 'Interesting Games' one to the folder where I put my favorites, and the 'Native Apps' one to a folder where I put my favorite apps. This would still be on the internal memory, just aiming them to subfolders within /game such as /game/faves and /game/native or something like that.

Thanks!

omgmog

  • * Administrator
  • Doesn't sleep.
  • Posts: 786
    • omgmog.net
Re: Changing Mountpoints?
« Reply #1 on: April 17, 2010, 12:19:35 pm »
If I recall correctly from when I modified the mountpoints to B: from A: for games, because you're going to be hexediting the firmware you're limited with what you can enter. Straight out replacing one character for another (such as A > B) is fine, but adding in more characters for the path isn't feasible.

What I'd suggest instead is just keeping the games where they are, or moving them to microSD like in the thread you linked, and then change the menu strings for those two items to say "Favourite Games" and "Native Games".

Stephanie

  • Guest
Re: Changing Mountpoints?
« Reply #2 on: April 17, 2010, 02:34:37 pm »
Thanks for the info! I'm well-versed with the limitations of hex-editing binaries... way back in the 'old days' I was customizing the 'os' on my Tandy 102 portable. :)

I went through the ccpmp.bin file, that seems to be the main file for the whole system. I was able to locate the Native Apps mountpoint in there. The mountpoints are plain text ending with a null, and there were another three nulls before the next bit of text. So I changed it from "a:\game\" to "a:\game\10\" then set up my games subfolders with two-digit names.

It works!

I just have to figure out where the mountpoint for 'Interesting Games' is... I don't want to change all the a:\games\ references as I want to leave all the .sim, .cfg, etc files in there. (It was easy to find the native apps one as it had "*.app|*.dir" next to it.)

Edited to add: Also while I was mucking around in there, I noticed that there is a codec for AAC (m4a) audio files. And in the /system/res/filetypes directory there is an icon for m4a, but when I put m4a files into my music directory, they did not show up. When I went into the file browser, the files were there but with the 'unknown file' icon. So while I was editing the mountpoint, I went to the music one where it had all the music file types, i.e. a:\music and "*.mp3|*.ra| et cetera" and I changed the *.ape to *.m4a. Now my m4a files show up in the music player and they play fine, though they still have the 'unknown file' icon.

I'm going to try changing other ape references to m4a to see if I can fix the icon thing.

Has anyone else had problems with .m4a audio files? I'm just wondering why they'd have an AAC codec in there but not have the m4a files show up in the player...

Edited again:  Success!

The Native Apps mountpoint is in ccpmp.bin at offset 0x175784
The Interesting Games mountpoint is in ccpmp.bin at offset 0x1759AC
(This is from a 1.2 a320.hxf file - the offsets may be different in other versions)

In both cases there is enough room to add two more characters plus the trailing backslash.

For the AAC / m4a I just did a search for the "ape"... there were about a half dozen references that I changed to "m4a". I did not change all of them - only the ones where "ape" appeared along with a list of other music file suffixes. After having done this, the Dingoo recognizes all AAC / *.m4a audio files, catalogues them and they appear correctly in the music player.

Yay!

Cheers!
« Last Edit: April 17, 2010, 03:35:09 pm by Stephanie »

kswildside

  • Guest
Re: Changing Mountpoints?
« Reply #3 on: April 19, 2010, 02:34:04 pm »
Question does it play the ACC files with out issue if so we can play Itune files?

Stephanie

  • Guest
Re: Changing Mountpoints?
« Reply #4 on: April 19, 2010, 03:28:47 pm »
It won't play the m4p "protected aac" files, but it will play the m4a files that aren't protected.

I think it was about a year ago that iTunes switched to the unprotected / drm-free format, and it does play them just fine. :)

I've got it playing lots of stuff I've bought from iTunes over the past year.

kswildside

  • Guest
Re: Changing Mountpoints?
« Reply #5 on: April 20, 2010, 04:53:56 am »
WOW that is kewl but APE is FLAC format of music prety damn good format near flawless audio

Stephanie

  • Guest
Re: Changing Mountpoints?
« Reply #6 on: April 20, 2010, 03:10:16 pm »
Ah I didn't know that. I've never heard of 'ape' files myself which is why I picked that one.

However, there's other formats that could be replaced. Either way it would be a tradeoff, to get aac/m4a into the list, something else has to come out. Still seems a bit wierd that they included the aac codec but didn't include a way to play the files. :)

kswildside

  • Guest
Re: Changing Mountpoints?
« Reply #7 on: April 20, 2010, 04:28:13 pm »
Or we could figure out how it adds formats and just shoe horn a new type into the firmware I mean we already have learned to modify the Firmware with certain tools maybe the file format could just be added versus subtracting a format that kinda takes away from the whole point of the A320 to provide numerous formats of audio and video playback. Thats just IMO but to add is better then to subtract...

Stephanie

  • Guest
Re: Changing Mountpoints?
« Reply #8 on: April 20, 2010, 04:48:11 pm »
No question, it would be best to be able to add the format without having to replace something else. It's a limitation of hex-editing the binary though... for instance in the area that determines what file types are displayed when you go into the 'music folder' you'd need to add six characters:  |*.m4a  That then moves the rest of the file by six bytes, and suddenly nothing works any more, because half the offsets are now wrong. And that's just one example... there were about 6 areas I had to change, so that the .m4a files would show up, get the right icon, be indexed by the music player, and so forth. Each of those would be 4 to 6 more bytes that would further change the rest of the file's offsets.

If the firmware were opensource then it would be a snap to edit in what was needed then recompile it, but if all we have to edit is a precompiled binary it really limits what we can do.

Making a change like moving parts of the system folder into the accessable part of the flash (to make themes editable) are just a simple 1-character replacement - z:\system\res becomes a:\system\res so nothing actually gets 'moved' in the binary. Likewise, where I changed my games mountpoints, I was limited by only having 3 nulls available to convert into directory names (and one of them had to be the \) so I couldn't use a name like "favorites" but had to go with "00" or "01" etc.

I'd love to get my hands on the firmware source code :D but I can't imagine the manufacturers would opensource it - that would probably open the door to too many clones and knock-offs.

Cheers!

 

Post a new topic