Forum: Official UlaunchELF Forums - Discussion for the most unofficial build of launchELF!


The above video goes away if you are a member and logged in, so log in now!




 
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!

 


User Tag List

Thread: Make uLaunchELF CD
  

Page 2 of 2 FirstFirst 1 2
Results 11 to 13 of 13
  1. #11  
    dlanor is offline Member
    Join Date
    Sep 2004
    Location
    Sweden
    Posts
    10,107
    Downloads
    5
    Uploads
    0
    Mentioned
    1 Post(s)
    Tagged
    2 Thread(s)
    Likes Given
    0
    Likes Received
    126
    Quote Originally Posted by Kimchi View Post
    ok. Thanks! How about any user menu on using uLaunchELF? I don't really know how this copy and paste works... I can highlight the files I want to copy by adding a * sign beside it and just copy? and it should copy all the files that has a * beside it?
    Like Bootlegninja said, anything marked by '*'-symbols will be included by the 'Copy' (or 'Cut') command, and if nothing is marked that way then the currently highlighted object will be the only one included. But here are some additional tips on how to use this efficiently:

    Pressing the 'Square' button will invert the marking state of all objects in the current folder, and doing this with nothing marked will thus mark all files/folders. So if you do this in the MC root before using 'Copy', and then navigate to an HDD folder and use 'psuPaste', that will backup each folder from that memory card to a separate PSU file in the HDD folder.

    Another useful fact is that there are two variables in the CNF file which may be set to gain additional information in the PSU filenames. Those variables can not be set by normal config menus though, so you will need to edit the CNF file in a text editor to fix it. These and many other special features are clearly described in the comments of the CNF file that is included with each uLE release package. Here follows a relevant quote from that file, relating how to adjust the PSU filename format, as well as the PSU overwrite behaviour on destination name conflicts.

    Quote Originally Posted by uLE Doc's in release copy of LAUNCHELF.CNF
    Code:
    # ----------------------------------------------------------------------
    # From v3.92 Two options for PSU gamesave files are saved here.
    # Set PSU_HugeNames non-zero to make PSU names contain both original
    # gamesave folder names and the gamesave titles (from icon.sys).
    # Set PSU_DateNames non-zero to make PSU names contain a timestamp from
    # the original save data, appended to the normal name.
    # Both options can be set simultaneously, for very detailed names, like:
    # "BESLES-5245800_Disgaea(1) Ep.1 LV1_2006-07-23_14-46-33.psu"
    # As yet they are not available in config menus. Use TextEditor instead.
    # ----------------------------------------------------------------------
    PSU_HugeNames = 0
    PSU_DateNames = 0
    # ----------------------------------------------------------------------
    # PSU_NoOverwrite was added in v3.93, to eliminate redundant backups.
    # It's only useful to set it non-zero when PSU_DateNames is also set, as
    # it is otherwise ignored. When used, backup of timestamped PSU files
    # check for an identical PSU filename at the destination, and if such
    # a file already exists the operation exits without error, as if a new
    # backup had been made. Thus you can select all saves on an MC and use
    # psuPaste to backup only those that have changed since last time.
    # This improvement was contributed by 'ffgriever' at ps2-scene.
    # ----------------------------------------------------------------------
    PSU_NoOverwrite = 0
    # ----------------------------------------------------------------------
    Hopefully that is clear enough, but just to clarify it even further, if you want to activate all three of those flags properly, then you need to edit the three relevant lines to be something like this:

    PSU_HugeNames = 1
    PSU_DateNames = 1
    PSU_NoOverwrite = 1

    If you haven't read through that CNF file before, then you really should do so now, as it contains the only fully up-to-date documentation on many uLE features, and is also the only proper source for information on those uLE features not available through the normal configuration menus.

    Best regards: dlanor
    Last edited by dlanor; 04-22-2007 at 01:36 PM.
    Reply With Quote  

  2. #12  
    dlanor is offline Member
    Join Date
    Sep 2004
    Location
    Sweden
    Posts
    10,107
    Downloads
    5
    Uploads
    0
    Mentioned
    1 Post(s)
    Tagged
    2 Thread(s)
    Likes Given
    0
    Likes Received
    126
    Quote Originally Posted by Bootlegninja View Post
    No. codebreaker can only handle its codes.
    That is both true and false.

    It is true that only CodeBreaker itself can install newly downloaded cheats to the MC, or handle user editing of those cheats, to add new cheats to the MC folder.

    But once such a folder has been created by CodeBreaker it is possible to use uLE for copying that folder to another memory card, even for use on another PS2. In such copying it shouldn't matter if you do it directly from one MC to another MC using normal 'Paste', or if you do it indirectly via a PSU file created and later restored by 'psuPaste'. Either way should work fine.

    So existing cheat sets saved to the "mc0:/PCB/" folder may be backed up and otherwise handled just like any normal gamesave. However, this might not be true of other file copiers than uLE, as they may not always preserve all the file/folder attributes and timestamps, like uLE can do in MC-to-MC 'Paste' or in all 'psuPaste' operations.

    This also means that even with uLE it's a very bad idea to use normal 'Paste' in copying such stuff to/from non-MC media, as that will cause some of the file/folder attributes and timestamps to be lost. That's one of the main reasons why we created 'psuPaste'. (Another reason is the inability of PC filesystems to handle some PS2 filenames.)

    Best regards: dlanor
    Reply With Quote  

  3. #13  
    Join Date
    Apr 2005
    Location
    Ky, USA
    Posts
    5,031
    Downloads
    2
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    9
    Likes Received
    39
    Quote Originally Posted by dlanor
    That is both true and false.
    You're right. I thought about that about an hour into my shift at work.

    Quote Originally Posted by dlanor
    It is true that only CodeBreaker itself can install newly downloaded cheats to the MC, or handle user editing of those cheats, to add new cheats to the MC folder.
    I completely forgot about CB using the MC for code storeage when the hdd isn't present (on 9.x +) since I haven't used a version that relied solely on mc in a long while now.

    Quote Originally Posted by dlanor
    But once such a folder has been created by CodeBreaker it is possible to use uLE for copying that folder to another memory card, even for use on another PS2. In such copying it shouldn't matter if you do it directly from one MC to another MC using normal 'Paste', or if you do it indirectly via a PSU file created and later restored by 'psuPaste'. Either way should work fine.

    So existing cheat sets saved to the "mc0:/PCB/" folder may be backed up and otherwise handled just like any normal gamesave. However, this might not be true of other file copiers than uLE, as they may not always preserve all the file/folder attributes and timestamps, like uLE can do in MC-to-MC 'Paste' or in all 'psuPaste' operations.

    This also means that even with uLE it's a very bad idea to use normal 'Paste' in copying such stuff to/from non-MC media, as that will cause some of the file/folder attributes and timestamps to be lost. That's one of the main reasons why we created 'psuPaste'. (Another reason is the inability of PC filesystems to handle some PS2 filenames.)
    Yeah, I do all my saves like you just described there. Any more I rarely use the regular paste function for any gamesave related tasks. But I appreciate that you brought the detail to better answer Kimchi.
    Reply With Quote  

Page 2 of 2 FirstFirst 1 2
Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •