Quote:
|
Originally Posted by vtecorona
Ok, I made it so you can add anything to the share list including individual files, maybe that will fix your problem. I never had a problem with adding any directory under any particular drive so I can't really think of anything else to try to fix this. I disabled sorting on the shares list too so you can add them in the order that you want them in the list.
|
I haven't tested those features at all, but I do have some other problems to report.
Quote:
|
I will release a new copy after I get a chance to hear from others about possible problems. In the meantime you can add any directories that the program wont allow you to by adding them manually into elflist.txt.
|
I've always managed my elflist.txt mainly by 'hand', using normal text editors. But I have run into some entirely different problems using the new version.
The disconnect detection uses too long detection delay, so if starting SMS from uLE with host: already enabled, your loader will not always detect the momentary disconnection, and so the old PS2client can remain active on the PC, though it has really lost the connection to its server. And at that point it goes insane, continuously stealing over 90% of all CPU time... (Basically due to bad design of Windows).
Edit: Early on I though that it would help to use an HDD with many partitions on it to slow down the initialization, but that was wrong. The problem can still occur.
If I try to close PS2ClientLoader at this time it complains about running instances of ps2client, and asks me to shut them down, in a special dialog box for that purpose. If I press 'Done' in that dialog box directly, the program sometimes returns some error code. (Possibly due to some proiblem caused by the lack of CPU time.) If I do terminate the instance it works correctly.
Btw:
I think a new option should be added, which when set should tell the loader that the user wants to skip the extra dialog when terminating the loader with active instances of ps2client. Such instances should then be terminated automatically without needing further attention by the user.
Even when the user wants that dialog box to be used for individual shutdown of instances, it should not also be preceded by that huge info box, as that's just one more irritating infoflash/click sequence for the user (especially irritating once you've read that box a few dozen times...). I suggest you try to include the vital parts of that info into the dialog box itself instead.
Best regards: dlanor
