With AmigaOS 3.x that would be all applications. APIs in AmigaOS 3.x can only represent a 32bit number for the file size.
Only applications reading up until EOF will work properly. Any AmigaOS 3.x application that actually queries the file size first before processing that amount of data will fail. Many applications seeking in a file will fail randomly as negative return value from Seek() was commonly considered an error.
Easy example DirWork V2.1 written in 1994/95, like I say things display the wrong file size but they copy perfectly without errors, on DirWork (or DOpus for that matter) they can easily copy an 8.3GB DVD ISO from one partition to the other without any problems...

All I know is it work for me, I'm not interested in the technical details of how it works. It does what is required without error and for me that's all that matters...

Sorry but I'm not the type who cares how many nanoseconds it takes for something to do something or how many transistors will fit on the latest CPU or why my grannies bloomers always fell down due the fact that the consistency of the elastic in them was wrong...

Me I'm just happy that things work for me on my Amiga's the way I need them to and that makes me happy & satisfied...

PS:You've made me miss getting a home delivery from the Chippy as it's now midnight, now I'm gonna have to go and cook something instead before I sit down to watch Friday Night Smack Down where at least I can relax watching something a wee bit more intelligent than all this mind numbing stuff... :furious: