Forum: Official NEOCD/PS2 Forums - The official messageboard to the NeoCD/SDL port to the PlayStation2.


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: Launching NeoCD through uLaunchELF
  

Results 1 to 3 of 3
  1. #1 Launching NeoCD through uLaunchELF 
    jsnepo is offline Member
    Join Date
    Jul 2006
    Posts
    86
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Is it possible to launch just the ELF of NeoCD from the memory card or the hard disk through ULE? I asked because I tried it and it asked me for the BIN file. Though I have it in the same location where the ELF is, NeoCD still prompts for it.
    Reply With Quote  

  2. #2  
    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 jsnepo View Post
    Is it possible to launch just the ELF of NeoCD from the memory card or the hard disk through ULE? I asked because I tried it and it asked me for the BIN file. Though I have it in the same location where the ELF is, NeoCD still prompts for it.
    I'm not even sure what I/O devices NeoCD supports for any use, but it is quite normal for most homebrew applications to fail recognizing the launch folder properly when launched from HDD by the standard homebrew method (ie: launched via 'fakehost' driver). This means that the program will see 'host:' as being the launch device, which will allow access to HDD at first, but if the program then reloads IOP modules, then the link between 'host:' and the real launch directory on HDD will be lost.

    Use of the 'fakehost' driver is necessary to provide access to HDD launch directories through a single device path, since real PS2 HDD access paths are split over two different devices, each using a separate path string. There is no standard for how to pass real HDD paths to a program, and no current homebrews can deal with such. What we really need to do is to create a new standard for passing unified HDD paths and enforce its use for all new projects, but that still won't help old projects.

    If NeoCD supports 'mass:' (USB mass storage devices), then you may have better luck with that, as it allows passing the true launch path unaltered since mass: uses a single path string.

    Best regards: dlanor
    Reply With Quote  

  3. #3  
    jsnepo is offline Member
    Join Date
    Jul 2006
    Posts
    86
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    I see. So the best thing for me to do then is to make an ISO with the ROMs and load it using HD Loader. Thanks anyway.
    Reply With Quote  

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •