mass issues

[radad1]

I have been having some issues with the mass driver. Basically uLaunchELF 3.41k worked, but now uLaunchELF 3.41l doesn't. I can't copy a file from the mass to the hdd anymore.

Also I posted a bug fix to ps2dev about directories and looking for a double 0 to find the last one. It never made it into the SVN. Could you put it in for the next release.

[E P]

I have been having some issues with the mass driver. Basically uLaunchELF 3.41k worked, but now uLaunchELF 3.41l doesn't. I can't copy a file from the mass to the hdd anymore.

That's odd no problems here and the driver is the same as it was in 3.41k. I wanted to update the driver with EEUG's changes but had problems like what you mentioned on my earlier test compiles. The driver was last updated by dlanor in 3.41h and that's the one that has been used ever since.

Also I posted a bug fix to ps2dev about directories and looking for a double 0 to find the last one. It never made it into the SVN. Could you put it in for the next release.

Sure although I doubt I can do to problems I have had from before but perhaps dlanor could implement your changes.

[dlanor]

Also I posted a bug fix to ps2dev about directories and looking for a double 0 to find the last one. It never made it into the SVN. Could you put it in for the next release.
Sure although I doubt I can do to problems I have had from before but perhaps dlanor could implement your changes.
Yes, but only if I have sufficient info on what to change. A vague mention of 'looking for a double 0' doesn't really tell me anything, as I've never done much with the internals of that driver myself. I've just recompiled it a few times, and merged minor changes from one source file to another. I can do that again, sure, but I'll need precise info, preferably in source code form.

Best regards: dlanor

[radad1]

Here is my original thread:

usb_mass problem (http://forums.ps2dev.org/viewtopic.php?t=2836)

[radad1]

That's odd no problems here and the driver is the same as it was in 3.41k. I wanted to update the driver with EEUG's changes but had problems like what you mentioned on my earlier test compiles. The driver was last updated by dlanor in 3.41h and that's the one that has been used ever since.


Actually, I think I had to rebuild uLaunch form source because of the 'double 0' issue in usb_mass I mentioned. I didn't use any of the irx fixes in the uLaunch source. Maybe there are other changes in uLaunch that are causing me problems.

[E P]

Actually, I think I had to rebuild uLaunch form source because of the 'double 0' issue in usb_mass I mentioned. I didn't use any of the irx fixes in the uLaunch source. Maybe there are other changes in uLaunch that are causing me problems.

OK, well I got my compile to work. Make sure you uncomment WRITE_SUPPORT=1 in the usb_mass makefile that was the problem I was having earlier. (Note: fat_write.c and fat_driver.c need certain changes for launchELF so please be aware of this).

As for the 'double 0' issue, please give us a solution if you would. I don't quite understand what the problem is as I have not experienced it myself. If you provide the source changes, I'll add it.

Dlanor, I updated the usb_mass driver, keeping your previous file changes to fat_write.c, and adding your prior changes to update fat_driver.c. I also left mass_rpc.c and mass_rpc.h alone as you did the last time you updated the usb_mass driver. The changes are in place for version 3.41m so no need to worry about it. :)

[radad1]

The exact fix is to change this line from fat_driver.c:

if (dsfn->name[0] == 0 && dsfn->name[1] == 0) {

into this:

if (dsfn->name[0] == 0) {

[E P]

The exact fix is to change this line from fat_driver.c:
if (dsfn->name[0] == 0 && dsfn->name[1] == 0) {
into this:
if (dsfn->name[0] == 0) {
Ok, thanks radad1, I added the change to 3.41m. I also tested it without any issues so the change is fine with me. :)

I'm still not sure when I'll release 3.41m though.

[radad1]

Are the uLaunchELF changes making their way back ps2sdk?

[E P]

Are the uLaunchELF changes making their way back ps2sdk?

No, well not at the moment anyway. All changes are currently added only to uLaunchELF. Neither dlanor, nor I have CVS err SVN commit access so you might be better off asking EEUG or ole to update SVN with your noted change.

Perhaps the time will come when it will be necessary to add some of our changes into SVN. I don't know when that will be. Although in the mean time we are still releasing all our source changes to LaunchELF, libcdvd, usb_mass, ps2ftpd, and parts of the ps2sdk.