Originally Posted by
RAIST
it's more an issue of what space is left in memory after everything else is accounted for in the game. The PS2 has a limited amount of memory to use for all operations. It was designed with only so much space reserved for certain registers to ensure assets would be available for other processes. Granted, whether those assets remain unused and could be transferred could be open to debate. There could also be the issue that such unused resources might be needed for future plans, so they are unwilling to release them to something else.
As for the AH, that's a different animal I guess. Ever notice how long it takes for that list to load? Notice how it loads in chunks? And you can only scroll down so far, then you have to wait for the next block to load? It's like it is stacking blocks...kind of like how you have your normal inventory with the temp items stacked on top in a seperate block. When you auto-sort the temp block, it doesn't auto-sort your normal block--have to select a normal item to sort normal inventory because they are seperate containers. So, even though it may be possible to stack multiple containers in a list view, there is the performance issue that has to be taken into effect. Think about how bad things lag sometimes just loading the AH list. Imagine that happening in the field....mid fight, trying to unpack a toolbag or quiver, or gettting at that item you need right away that isn't on a macro.
There's a lot more to consider besides just whether it is possible.