When I call fioRemove to remove a file it outputs :
remove file mc0:/BEDATA-SYSTEM/KL.DAT
mkdir name mc0:/BEDATA-SYSTEM/KL.DAT
I am not sure where these are being output from.
Anyway why is it creating a directory after it has deleted the file?
fioRemove
It's a well known bug in sony's RPC server for fio* functions... They forgot a break in the switch between fioRemove and fioMkdir... So, you have to fioRemove then fioRmdir.
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.
Is there any reason we haven't made ps2sdk work around this automatically?
Shoot Pixels Not People!
Makeshift Development
Makeshift Development
Several answers to that:
-) fioRemove is only a rpc call, which would work with different versions of the same irx, bugged, and non bugged. That's not up to that layer to have that fix
-) the correct layer that should have that workaround would be libc, with a rmdir() function (which would make up the path with the current directory, etc)
-) fileXio removes that bug.
-) fioRemove is only a rpc call, which would work with different versions of the same irx, bugged, and non bugged. That's not up to that layer to have that fix
-) the correct layer that should have that workaround would be libc, with a rmdir() function (which would make up the path with the current directory, etc)
-) fileXio removes that bug.
pixel: A mischievous magical spirit associated with screen displays. The computer industry has frequently borrowed from mythology. Witness the sprites in computer graphics, the demons in artificial intelligence and the trolls in the marketing department.