I've installed the preloader a long time ago.

Then i've updated my sysmenu to 4.1.

Now i want to reinstall the preloader but perhaps i will have a pb.

The preloader move the boot 0000000x.app to 1000000x.app and replace the 0000000x.app by himself. But when i've installed the new system menu, i've overrided the 0000000x.app (all is ok at this point) but what about the 1000000x.app. Is it still here? Does the installation of sysmenu delete it?

Because if not, whn i will reinstall the preloader, he will skip the moving of 0000000x.app because the 1000000x.app is here, doesn't t? And then i will have a 1000000x.app of sysmenu 3.2... Wich isn't very good at all.

You'll be fine. Even if the file was still there, which it isn't, the X of 0000000X.app would be different afaik. It's perfectly safe to reinstall preloader or priiloader (I advise the later). Also, this shouldn't be in the Coding section.

Sorry if this is the wrong section.

But i've checked between the sysmenu 3.2E and 4.0E and the X are the same. The boot index is 8. So if the 100000008.app is still here, i will have a pb because te preloader doesn't check if the 00000008.app and 100000008.app are the same (he can't do that, because he can't detect if the 00000008.app is the sysMenu or a previous version of the preloader... Imagine if i want to upgrade preloader to priiloader.... The priiloader isn't able to detect the origin of 00000008.app).

This is the worst scenario:

3.2 => installation of preloader, creation of 10000008.app
4.0 => update to 4.0, so i've 00000001.app (of 4.0) and 10000000.app (of 3.2)
4.0 => installation of preloader. 10000008.app is here, so skip the sysMenu moving phase

Now i'm in 4.0, but the sysMenu is corrupted because the 10000008.app doesn't correspond to all other contents.

So can you confirm me that the installation of a new sysMenu will delete 10000008.app (ie all unused file of the 00000001/00000002/content folder) ?

it just does. we dont need to confirm that, its a fact

Ok, thank you.

Quote
arasium
Sorry if this is the wrong section.

But i've checked between the sysmenu 3.2E and 4.0E and the X are the same. The boot index is 8. So if the 100000008.app is still here, i will have a pb because te preloader doesn't check if the 00000008.app and 100000008.app are the same (he can't do that, because he can't detect if the 00000008.app is the sysMenu or a previous version of the preloader... Imagine if i want to upgrade preloader to priiloader.... The priiloader isn't able to detect the origin of 00000008.app).

This is the worst scenario:

3.2 => installation of preloader, creation of 10000008.app
4.0 => update to 4.0, so i've 00000001.app (of 4.0) and 10000000.app (of 3.2)
4.0 => installation of preloader. 10000008.app is here, so skip the sysMenu moving phase

Now i'm in 4.0, but the sysMenu is corrupted because the 10000008.app doesn't correspond to all other contents.

So can you confirm me that the installation of a new sysMenu will delete 10000008.app (ie all unused file of the 00000001/00000002/content folder) ?

I'm pretty sure the X is different. Old WAD unpackers number all contents numerically, meaning System Menu binary is always 00000008, but that is not the actual number. NUSD unpacks them correctly, and on different System Menus the X is different. Anyway, like I and Daco said, it is fine, it'll work.