Xex Menu File Corrupted - Apps Software From This

Ive noticed that behavior when trying to use the software from this thread, but eventually Ive realized that if moving to the internal hd the.xex emulators work.

This is known to be an issue with using multiple USB devices, as they can register with the same hardware IDs.

And I has seeing all the emulators in my Aurora, specifically on emulators - thats the why for the directories.

And, as I said in the beginning, Im testing with the Auroras interface and xexmenu.

Please be patient, until someone will react to your posting.

Of course is not something you can handle easily, and specially not with the Windows SO main tools.

But Neocazen have a valid point, may is something with the system not handling well my strange approach, may something with the 4096 bytes sector size Or maybe the HD should be set with the flag boot for the system to handle the.xex correctly.

The Xbox FatX is based on Fat32 with some custom features and can only access 2 TB per partition.

It doesnt matter which cluster size you choose, coz its a limitation from Microsoft.

So, I have MBR partition and no, the limitation for 2T was for a while a limitation for the 4KB sector size, something Windows 7 related, Im not sure the whys, but now is possible to handle up to 16T with address and Ive done that.

So, do I have to have the flag boot on the HD or something My problem is to run.xex files and not if someone believes that I can use memory address.

But Microsoft limited the partition size on WIndows os on 2 TB per partition.

If you fill your partition over 2 TB, your file tabel get crashed.

Try it out. It has nothing to do witch cluster size you choose on WIndows OS.

Xex Menu File Corrupted - Apps Software From This