dml needed sneek because the di module isn't having an sd driver. So, it couldn't locate the games folder on the sd card in uneek + di.
It's the di module that creates the diconfig.bin file that contains the gamelist.
With the neek overlay menu, you select a game from that list. In case of a gc game, that name is stored in another file (can't remember it's name)
After that, real nand BC is launched, and up you go.
In case of DM, the games are on the usb drive. The uneek di module is perfectly capable of locating them there. So, DM can be used with sneek and with uneek (sneek uses an usb driver buildin the di module to access the usb drive. uneek reroutes the calls to the es module which controls the usb drive as the emulated nand is on it.)
If you have the diconfig.bin game list with the gc games in them, you can even use uneek to launch a game in DML. It's just building that diconfig.bin that isn't working.
If you don't understand the technical background I am trying to explain here, please stop discussing about this. If you disagree with me on the technical part, fell free to try to convince me why.
I guess, while we are all patiently waiting for devolution and DM to come out, this kind of discussions keep us busy.
