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: ULE 4.12 freeze when accessing mass (3.79 works)
  

Results 1 to 4 of 4
  1. #1 ULE 4.12 freeze when accessing mass (3.79 works) 
    Jamirus is offline Registered User
    Join Date
    Feb 2005
    Posts
    22
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    I just tried 4.12, and it didn't work with one of my pendrives - the led just blinks, there's no access and ULE is freezing. 3.79 works perfectly.
    bootsector's latest emulator releases have the same problem. In SMS 2.8., the drive can be accessed, it is however shown as empty.
    Unfortunatly, the drive appears to be a no-named, nothing is readable on the drive itself, nor are there any indications on the packing. Are there any known brands (besides Kingston, from what I could gather) with similar problems, and give the symptoms any hint to what the problem might be with the newer USB code for this drive?
    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 Jamirus View Post
    I just tried 4.12, and it didn't work with one of my pendrives - the led just blinks, there's no access and ULE is freezing. 3.79 works perfectly.
    bootsector's latest emulator releases have the same problem. In SMS 2.8., the drive can be accessed, it is however shown as empty.
    Unfortunatly, the drive appears to be a no-named, nothing is readable on the drive itself, nor are there any indications on the packing. Are there any known brands (besides Kingston, from what I could gather) with similar problems,
    Probably many minor brands, but our user base is too small to find them all.

    and give the symptoms any hint to what the problem might be with the newer USB code for this drive?
    What symptoms ? All we get to see here is "It didn't work", and that's not much to go by.

    But generically I think that the problem is due to these drives using non-standard, possibly obsolete protocol versions.

    Best regards: dlanor
    Reply With Quote  

  3. #3  
    barf's Avatar
    barf is offline This product has been banned!
    Join Date
    Sep 2004
    Location
    /bin/trash
    Posts
    1,676
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    I have to use the mass storage driver from 3.80 still
    Reply With Quote  

  4. #4  
    Jamirus is offline Registered User
    Join Date
    Feb 2005
    Posts
    22
    Downloads
    0
    Uploads
    0
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Likes Given
    0
    Likes Received
    0
    Quote Originally Posted by dlanor View Post
    Probably many minor brands, but our user base is too small to find them all.

    What symptoms ? All we get to see here is "It didn't work", and that's not much to go by.
    By symptoms I simply meant the blinking led (begs the question how other non-working drives react, I guess, but still..), the working previous version, and the difference to the latest SMS 2.8 (the USB driver was updated there in the latest version). I mean it's not like I realisticly expected some fix or more specific insights than "Herben's driver is incompatible to a number of drives", but I was still curious and thought it'll be worth to ask if there's anything known about possible causes for regression. I don't know how standarized USB access is in the Ps2 homebrew scene, I'd figure that the latest SMS uses a somewhat different/modified driver now for instance.
    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
  •