|
|
|
|
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! | ||
|
|
Not quite. You should enter the name just as "OPL", as the "+" prefix is added automatically for all user partitions, so that the final name becomes "+OPL".
Those facts are not in any way connected.because i put my OPL.elf at
hdd0:\__boot\OPL.elf
Regardless of the location you launch the OPL elf from, any VMC it is to use must always be on the same storage medium as the game that VMC is intended for, and for games on HDD this means that the VMC must be stored in the folder "hdd0:/+OPL/VMC/".
It is not often needed to do this manually on a PS2, but now you do need it, in order to use games stored on HDD with VMC.i never create partition before
Use uLE FileBrowser to go into the pseudo device "MISC/", which contains various built-in subprograms of uLE. You should then start the one named "HddManager", which will then take some time to scan through the existing HDD partitions. When that scan is completed you will be shown a list of those partitions.
Next you press the R1 button to open a popup menu, where you choose the command "Create", which prompts you to enter a name for the new partition. Here you enter OPL and end the input with the OK command at bottom of this entry box, which brings you to the size selection screen. There you can use the right and left Dpad buttons to increase or decrease the new partition's size choice in units of 128 MB per step. Then you finalize the choice and let the creation commence.
How much size you need depends mainly on how many games you will use VMC for, as each VMC requires a minimum of 8MB. Personally I use a "+OPL" partion of 1024 MB (==1GB), as I like to have a safe margin for the future. But this is really overkill for my 300GB HDD. But for a really large HDD (like 750GB) well filled with games, it might even be on the small side... But that is a judgement call.
But hopefully you do know if you use networked games or not. Right ?and i dont know if my ps2 logs in as anonymous or not.
Because it is only for networked games that the login method matters at all.
There are links to extensive guides on the use of "Open PS2 Loader" near the top of every single page on this site, so there is absolutely no chance that you can have missed them.hope there a simple guide for me thanks
Use those links and read the tutorials thoroughly, and you should find most things clarified.
Best regards: dlanor
I know I've described this before in these forums, more than once, but I guess one more go at it won't hurt too much...
First you need to create the VMC file, which is done in the per-game menu of OPL.
With that done you can then transfer gamesaves into it using the uLE FileBrowser.
The uLE FileBrowser menu contains two commands that lets you 'mount' a VMC file as a virtual MC device named either "vmc0:/" or "vmc1:/" depending on the command used. And when you do this mounting the FileBrowser also auto-navigates inside the root directory of the mounted VMC.
Those virtual devices are temporary, existing in the FileBrowser root only until the next time you exit from the FileBrowser. But while they exist you can use them almost exactly like a normal MC, including copying gamesaves between this mounted VMC and a physical MC. And the changes made to VMC content naturally remain after such automatic unmounting of the "vmc?:/" device.
Some important things to consider:
1: Do not mount VMC files accessed over network using "host:/" device, as that is unsafe.
Copy them to a USB drive instead, so you can mount those copies in uLE using "mass:/".
2: Avoid copying files between a VMC file and another part of the same storage device that this VMC file is stored on. Doing so may cause a device driver conflict, and it also makes no sense to backup gamesaves to the same device holding the original VMC. Instead you should backup gamesaves from VMC on one storage medium to some other storage medium. Typically I'd do that by psuPasting gamesaves from a VMC on HDD to a backup folder on a USB drive, or vice versa, or from either of those to a PC drive via "host:/". (Just remember rule 1 above, so you don't mount VMC via "host:/".)
3: After pasting data to a "vmc?:/" device, do not turn off the console without first exiting from the uLE FileBrowser (easiest done by pressing 'Select' button), so as to ensure that the mounted VMC file is closed properly. (Else it may be corrupted.)
4: Do not attempt to paste an entire MC's content into a VMC file in one paste or psuPaste operation, as that may be unsafe. Instead handle only one gamesave at a time in that direction. Note that this restriction need not apply for when you backup the VMC contents to other media. That should allow safe Paste or psuPaste of multiple selected gamesaves, since you are not writing into the VMC files (which is critical because it is a write through two 'nestled' device drivers).
Best regards: dlanor
You find it inside the uLE FileBrowser, in the popup menu with commands opened by pressing the R1 button on the gamepad.
In the current version of uLE that menu will look like this:
So what you do is first to enter the FileBrowser (default uLE main menu has it defined as 'Circle' shortcut button), and then you navigate to the VMC file that you want mounted, using DPad to select that VMC file so it is highlighted. Then you press R1 to open the popup menu and use the "Mount vmc0:" command. That will add the "vmc0:/" entry to the root drive list and also auto-navigate into that new drive, so that you directly see the contents of this mounted VMC.Code:Copy Cut Paste mcPaste psuPaste Delete Rename New Dir New Icon Mount vmc0: Mount vmc1: Get Size
The new drive will remain in the list only for the rest of this FileBrowser session, so when you press 'Select' to leave FileBrowser and get back to the main uLE menu, this will close the VMC file and remove the "vmc0:/" entry from the root drive list again. And this is what you MUST do after modifying VMC contents, as it is the file closure which ensures that all modified data is written to physical storage (whether that is USB or HDD).
Best regards: dlanor
| « Previous Thread | Next Thread » |