QUOTE(XaRaNn @ Jul 25 2006, 01:30 AM)

Way of trying reinvent the wheel.
If it's not broken, why fix it?
I just would like to share, that i think this is one of the most pedantic long drawn out useless request i've ever seen.
It amazes me sometimes, how close minded some can be. Just because you aren't using the emulators to thier fullest potential does not mean it's not broken.....this IS a major issue under certain setups. I've had teh same kind of discussion with the Xecuter forums and with the XBox Media Center forums about adding or improving things. I feel that i'm gracious, i thank the authors for what they have done, and i ask if an idea or improvement can be implimented in a new build.
Team Xecuter has given up on the original Xbox....no new bios will come out for the X3 chips....forget that you can't change the password of the chip's FTP server...forget that you can't run a dashboard from E:\Dashboard\Default.xbe. forget that the bank naming/selecting on this chip was over complicated for no reason. Forget that there was no support for enabling the use of a ShadowC drive.
Everyone on that board thought that there was no point in fixing these minor issues, because they all felt it was minor.....despite the fact that each of these issues combined caused me great headaches. despite that i paid $200 for all my Xecuter brand mods. Suddenly, everyone was a fanboy and no one could see any way to improve the bios.
XBMC has some major issues with the Programs section, especially the Emulators, where you are forced to either have all the emulator XBE files on the top level, or you are forced to have it as the directory structure....you can't have any sort of forced organization within the Programs to organize each emulator in a folder first by Company (Sega, Nintendo), and then by System in order of Release (NES, SNES, GBA).
The Profiles are coming along, and this was something i tried to suggest (i guess it was already in the works, though a few people denied it), so at least SOMEONE had an open enough mind to see the benefit of doing something like that.
As for Xport and the E:\SAve folder:
1. In order to be able to mod xboxes the same way each time (aka a Distrobution), i place the same apps, homebrew games and emulators in the same places on EVERY box.
2. Some boxes have stock WD drives (8gb). Theses boxes can have Roms anywhere, but there isn't much space.
3. Some boxes have stock Seagate drives (10GB). these boxes COULD have *SOME* roms on the E drive, but when space ran out there, one has to move the roms to the F drive.
4. Some boxes get thier hard drives upgraded. THese boxes could have ALL the apps, emus, etc on the F drive, but this would mean that i'd have to have a seperate distrobution for all 3 types. this consumes both time and hard drive space/media.
in order to keep the distrobution simple/uniformed among all my friends and family, the roms are moved into thier own folder on the F drive. All 3 types of xbox hard drives get the exact same install as far as apps, emulators, and homebrew games. the only difference is the location of the roms for the WD drive, which is too small to have many roms on it anyway.
furthermore, it makes it really easy to update...i can just make a new distrobution with the changed files, then delete the original program or emu, and copy over the new version, updating directly, instead of having to take the time to remove and replace roms.
this doesn't even mention the multiple use of the same emulator issue.
QUOTE(madmab @ Jul 26 2006, 01:46 AM)

Just a suggestion, but a better solution to the .ini file dilemna would be for the emulator to only store it in E:\saves if the current (aka RUN) directory is non-writeable. That would allow the .ini file to stay in the emulator directory with no prompting on the users part at all.
As for myself I've been able to work around these problems, but if it were to be changed, that'd be my suggestion.
this sounds pretty good too, actually! sounds even easier to do than what i was suggesting.