As the threadtitle, says...
|
|
|
|
Would you like to get all the new info from
PSX-Scene in your email each day?
Want to learn more about the team keeping you up to date with the latest scene news?
Read about them now! Check out our Developer bios, too! | ||
|
|
As the threadtitle, says...
what ddo you mean? if you mean where can you acccess a USB stick its under "mass".
VMC=Virtual Memory Card
Umh... i've seen u TnA on FreeVast thread so much, that i thought u know...
VMC is in HDProject app, it's not in any uLE.
Here's more info:
http://psx-scene.com/forums/official...-emulator.html
And kinda direct answer, where VMC is in uLE, it's in either mc0, mc1, cdvf(or whatever the name is), hdd0 or host directory under file management, if u did put the HDProject.elf in one of those.![]()
lol so that i got confused thought it could be something new i dont know ..VMC is in HDProject app, it's not in any uLE.
I knew/know this, butUmh... i've seen u TnA on FreeVast thread so much, that i thought u know...
VMC is in HDProject app,
not that.it's not in any uLE.
I thought I read something, that uLE is is direct VMC-Compatible and can also fetch it to RAM, like HDP does.
Maybe something new to implement.
Btw.: To which pfs does HDP mount the Partition?
VMC was implemented in uLE beta versions 4.12f and 4.12g, which do allow copying of files between VMC and other devices. If the so-called "uLE+" is based on v4.12g, then you should find "vmc:" in the filebrowser device list, with all the others. Using that entry should then lead to a fileselector where you can choose the vmc file to be used. After that choice this file is 'mounted' to the "mc0:" device using the MC emulator from the HDProject thread, and the filebrowser is automatically switched to "mc0:". The effect of this is that directly after choosing the vmc file you'll find yourself browsing its contents.
But that is just how I implemented things in uLE v4.12g. I have no idea if the same is true about that "uLE+" program, as I've never used it.
Please note that the method used for the beta VMC implementations were based on the so-called X-modules of the PS2 bios, and unfortunately those modules will corrupt the timestamps of all PSU backups created or restored from/to PS2 gamesaves, so that line of betas has been aborted. We still hope to reimplement VMC support in future uLE versions, using a fully homebrewed driver instead of the X-modules, but as yet no such driver is available...
Best regards: dlanor
AFAIK it has just HDL and maybe some other stuff embedded and is based on uLE Beta 4.12e.
Embedded:
-USBA
-VMC-Device-Hook (Game and original PS2-Browser, if we can return to that).
-SKIN (still switchable)
You may not like the idea about USBA and SKIN (as it may support piracy and blow up the elf), but the ELF's ever get loaded.
THX 4 knldg.
regards TnA
I'm opposed to embedding any material which I regard as unnecessary and/or not a natural part of the main program. And that includes media players, emulators, game launchers, as well as any files dealing only with cosmetics. No matter what skin we include, odds are that well over 50% of the users will never use it, preferring their own. So to all of them that embedding will just add dead weight (often stealing MC space).
As for VMC, we do plan to incorporate basic VMC device support, once we have a suitable device driver. But the in-game hooking you want is not something uLE will deal with. That needs to be implemented for whatever game launcher you use to launch those games.
Best regards: dlanor
dlanor: you said about those xmodules in the bios.. what if you let a option for the user add his own modules in ule just like a skin or a language file? Let's say, but the modules in the sys-conf dir in the memory card and make uLe look for it there? Or even better, look for the modules on a hdd? or, if you want to be really picky, look for the modules from the PS2 disc present in the ps2 drive?
Just a tough... but oh well.
| « Previous Thread | Next Thread » |