[ISSUE]: HDD Identifier 'hdd#:' is unsafe, use a more direct identifier instead #63
Description
Checks
- I have checked existing issues for duplicates and found none
Describe the issue
Using a numbered upon scan as an identifier is incredibly unsafe. If your system has changed in it's array of available drives, that number would have changed on the next CLI call.
While it wouldn't happen often, if you scan for drives, choose let's say hdd4: and then remove an HDD (let's say an external HDD), hdd4: may change to being hdd3:, so specifying hdd4: for the next call would be for a different drive. This would be disastrous if that now refers to a non-PS2 HDD. Even if there are checks in place.
If hdl-dump ever had a format HDD command, or such like it, it could be seriously disastrous.
It also becomes even more problematic when GUI wrappers to hdl-dump begin to be used. Especially in scenarios where long batch installations would be done. E.g., imagine batch query, cdvd_info2, and finally an inject_* call, via a batch ISO file list. Someone let it run in the background and bam! they eject a drive. Now their work E:/ drive is being used, or the program will fail, or something disastrous happens.
Console model
SCPH-30003 R