Note: these are not necessarily requirements
latest git (as of yesterday) ; OPL/0.9.3+.1442-Beta-361883d
HDD
VMC+GSM+PADEMU+HIRES
When creating a new vmc with full +OPL partition, the program locks up.
Error message.
Attempt creating a new standard 8mb vmc with full +OPL partition.
It may be dumb question...
but does previous versions (e.g. 1436) also have this problem?
Was there ever any "safety switch" to prevent this from happening?
I mean "There is not enough space for creating VMC?" or something similar?
i'll have to build an older release and try it out. I'll post result in a few days.
If you want an older build you can also check e.g:
Here is OPL 1443 with newlib:
https://www.psx-place.com/threads/open-ps2-loader-v0-9-3.13415/page-48#post-240445.
@yoshi314, Please have you been able to test the problem with previous beta versions as
@jolek has suggested, or with OPL 0.9.3?
There is no message in the OPL like "There is not enough space in the device for creating VMC",
but if there is no space i think the program should not hang, just don't create the VMC, no?
I wonder if the same happens for example when wanting to install a game on the
internal HDD over the network using the HDLDump Helper GUI, and the
+OPL partition don't have enough free space.
The OPL freezes? or the OPL HDLDump server closes from the side of the OPL without
installing the game?
I've never had the HDD full or near to be full to test this kind of things.
Best regards.
not yet, but i will do a few tests today.
i have a 512MB +OPL partition, so it was rather easy to fill it 100% with files that are multiples of 8MB.
If you can test it with older betas, with the latest beta r1486, and with the
stable OPL 0.9.3 it would be great.
Best regards.
it seems all of them lock up attempting to create vmc at 0%.
I'll retest with the latest git build as well.
Thank you very much, you tried with the stable OPL 0.9.3?
Best regards.
From what I do remember, there was no check on the available space. It makes sense, but it has to be implemented individually for each device supported to be truly inclusive. Other than the UI itself, the drivers need to support the necessary functions.
Since our PFS driver was based on the Sony driver, it can be done for the HDD. But this might not be possible (yet) for USB disks and maybe SMB shares.
Most helpful comment
From what I do remember, there was no check on the available space. It makes sense, but it has to be implemented individually for each device supported to be truly inclusive. Other than the UI itself, the drivers need to support the necessary functions.
Since our PFS driver was based on the Sony driver, it can be done for the HDD. But this might not be possible (yet) for USB disks and maybe SMB shares.