The possibility to save the configuration on the second Memory Card (mc1:/).
When I started up OPL it automatically used the one on MC0 and didn't create a new one, it also saves updated settings to this one too.
Personally I think it would make more sense to create it's initial config on whatever MC it resides on regardless of slot 0 or 1, but this could be a limitation of the system, where it needs to progress through MC slots in order and picks the first one, I'm not sure.
(PS. This bugs me because I like to keep my apps card in MC1 slot thus leaving MC0 free for game saves because the games seem to default to looking in there first for autoloading and indeed some games won't autoload from MC1 if a card is present in MC0. I'm too lazy to load it manually... ;P)
thanks, but if this is the case then it's really not was i was asking/looking for. what i wanted was the IGR and ''exit to'' options to be separate, so that it would be possible to use IGR to go back into OPL, and from there select exit to go back into FMCB if desired. so instead of sharing the same option they should simply be separated. i'm really dying for this option, lol. i just want to be done with HDL once and for all, since only a few of my games don't work with OPL and only do with HDL.
btw: does OPL support the new HDDs with 4 kb sectors? because i've done some research and it seems that the whole 2 TB limit is because of the combination of the 48 bit LBA and 512 byte sectors, and if it were to support the 4 kb sectors then the limit would go up eightfold, to 16 TB. of course with an internal HDD we would need a SATA to IDE adapter to use anything larger than 750 GB (biggest IDE HDD), but once such an adapter is used all of the IDE disk size contraints are gone, and we can use the huge disks as they are released.
so now to the devs: does OPL support the 4 kb sectors of newer HDDs, allowing the use of disks in excess of 2 TB?
EDIT: please can we also have an anti-spindown fix for internal HDD as there was in HDL? it's sort of annoying when your game locks up after a period of inactivity... and i'm sure that this is just going to increase the wear on the disk some how, by increasing the number of uneeded spin-up, spin-down cycles.
and for those that don't mind, it could always be enabled and disabled via an option (?).
sorry for all of the requests/queries. you guys are doing a greta job. :)
i just had a thought... since Toxic OS does not seem to have the same limitations as HDL, and uses a different filesystem to my knowledge, could it be due to the reliance on the HDL-sepecific filesystem that OPL has the very same limitations?
i noticed that in the past there were discussions of using the PS2 PFS filesystem instead, which would allow you to store standard isos on a single parition. i would think that this would remove the whole 255/256 game limitation, but then i'm sure that i read somewhere once that PFS only allowed paritions up to 2 TB... so this would get rid of the installed game number limitation, but then we have a whole new issue of partition size...
assuming that the developers were to ever undertake the process of PFS implementation for internal HDD, would it support multiple PFS partitions on HDDs with sizes in excess of 2 TB? that would be the only way as far as i know to use HDDs any bigger than that.
That limitation has nothing directly to do with the HDL storage method. It is an arbitrary choice. In fact I'm not sure what limit (if any) would apply to the number of physical partitions, which is the factor of real interest here, since each HDL-installed game is a separate partition.Quote:
i noticed that in the past there were discussions of using the PS2 PFS filesystem instead, which would allow you to store standard isos on a single parition. i would think that this would remove the whole 255/256 game limitation,
But I have always been of the opinion that having so many partitions as with the HDL game install method is a very bad thing to do to an HDD. And it shows clearly in the extremely long delays resulting whenever needing to refresh the partition list from scratch (such as when using HDL after any installs by WinHiip). No HDD device drivers, nor any HDD firmwares, have ever been optimized to deal with so many partitions. Normally both are optimized to deal only with a small number of partitions, with very fast access within those partitions. But the routines for digging through the lists of partitions are not optimized at all, since normal PC usage never allows for so many partitions.
Sure. Some size limit will always exist. But with the average game size of appx 2GB a 2TB drive will serve well for appx 1000 games, so that is not a limit I worry much about.Quote:
but then i'm sure that i read somewhere once that PFS only allowed paritions up to 2 TB... so this would get rid of the installed game number limitation, but then we have a whole new issue of partition size...
Anyone who has bought more than 1000 original games probably has more than one PS2 to play them on anyway...
And for limit-free usage there is always the possibility of using some future version of OPL with a modified SMB core not even limited by HDD sizes for modern PCs...
NB: Even normal Windows XP can 'mount' several physical HDDs inside a single fileshare folder. And that is nearly all it takes to let OPL access multiple PC HDDs. The missing part is to allow for subfolder usage within an OPL fileshare to find the games on each separate PC HDD that was mounted in the fileshare. But there are many different ways to implement that part.
No. That is inherent to the current PFS drivers with 48-bit LBA.Quote:
assuming that the developers were to ever undertake the process of PFS implementation for internal HDD, would it support multiple PFS partitions on HDDs with sizes in excess of 2 TB?
To increase that limit we would have to design or adopt some other HDD filesystem instead, probably with zero compatibility to the one currently used. And I really don't see that happening...
IMO the best chance for an unlimited game setup is to use the SMB core of OPL, with some slight modifications.
Best regards: dlanor
thanks dlanor, good explanations as always. it's good to hear that the 255/256 limitation was just an "artificial" limitation then, but i think that you misunderstood me in this part:
but then i thought that 48 bit LBA could really support up to 128 PiB, so why does the PS2 have this 2 TB limitation?
btw: do you or anybody else know if the PS2 supports the new 4096 sector drives? or should they be avoided like the plague...
im wondering if it is possible to switch disks(just for those games that multiple game disks) so we don't have to reset opl in the middle of the game?
it would not need a menu just a way to link the game disks together how it would be done im not sure but it would be nice