Winamp Backup Tool (v3.6.4 available, released on 19-12-2022)

[DJ Egg]

i take it that the start menu shortcuts are mandatory?

No. There's a "Don't create shortcuts" option/checkbox on that page.

[Koopa]

Don't understand the part with the mandatory shortcuts.

There is a checkbox at bottom 'Don't create shorcuts'

[Koopa]

MilkDrop saves all Presets, standard is about 200+ presets, so it takes a while.

Egg: Shall I move the Startmenu option to the components page? Maybe more simple, since the Desktop option is there too.

The only disadvantage is, that the user cannot change the Name of the startmenu folder (does anyone want such feature?)

[MrSinatra]

i guess i missed it, i just saw the checkbox for desktop shortcut. i suppose thats where i would've expected it.

[Koopa]

Winamp Backup Tool v1.0 Beta 3 available

I've spent a couple of hours and implemented a full working previous mode! The advantage is, if you don't want to backup/restore your skins or presets, the installer remembers this now.

That change required a lot of additional code and needs some testing, that's the main reason for Beta 3 release.

I've also added 2 more 3rd party plugins and made a couple of other tweaks, as you can see in the changlog.

Next beta will require a lot more time.

I hope some more people will test the tool in future.

[Koopa]

Winamp Backup Tool v1.0 Beta 4 available

The lack of feedback is really a shame. Don't fear the beta status. As you can see in the changlog, most things are new features and no bug reports.

Please test it, post feature requests, bugs or whatever.

If there's anybody out there interested in the tool, then gimme a 'Hell yeah'.

[evolution76]

When it backs ups.....were is the backup file (or files)......what folder does it goes in?

[Koopa]

Win2000/XP:

C:\Documents & settings\YourName\Application Data\Winamp_Backup

Vista/Win7:

C:\Users\YourName\AppData\Roaming\Winamp_Backup

I try to implement an info in the tool, where the backup folder is located. Also the user can in future choose, where he wants to save the backed up files.

[evolution76]

.....

Cool, i found it. Been waiting to for a tool like this for winamp. It is a bitch to reinstalling all my skins and plugins. I notice it did not keep my winamp skins that are in zip files, or the ones are in folders. But it is cool.... I can not wait for the finally release....

[Koopa]

If Skins don't have the proper file extension, which is clearly .wsz for classic skins and .wal for modern skins, you should blame the skin author.

I'll add skins with .zip extension to 'Classic Skins' section, since it should affect classic skins in 90% of the cases.

Backing up skins in folders is a bigger problem. I cannot detect if an extracted skin is a modern skin or a classic skins, so it won't fit in any category.

Also backing up default 'Winamp Modern' and 'Bento' skins makes no sense, since Winamp's installer overwrites both completely on each install.

Not sure, how I'll handle this.

[DrO]

If Skins don't have the proper file extension, which is clearly .wsz for classic skins and .wal for modern skins, you should blame the skin author.

we should blame the lazy people/old dev team who allowed .zip loading when like you say it should be .wsz (though i've a feeling that .zip support came before .wsz was created in the player)

I cannot detect if an extracted skin is a modern skin or a classic skins, so it won't fit in any category.

just have to look for skins.xml in the folder and assume it's a modern skin if that is present. though that can be fooled at times and it may be better to produce a NSIS plug-in to correctly determine the type of a skin (based on the Skin Manager loader core maybe).

Also backing up default 'Winamp Modern' and 'Bento' skins makes no sense

i agree with this unless file dates were checked to see if they differed from a known date (say that of winamp.exe i think) to determine if files have been altered or not as i'm sure kN0tte wouldn't be too happy about losing his modified files if using this

-daz

[Koopa]

i agree with this unless file dates were checked to see if they differed from a known date (say that of winamp.exe i think) to determine if files have been altered or not as i'm sure kN0tte wouldn't be too happy about losing his modified files if using this

-daz

Well, he will loose his custom tweaks anytime he upgrades Winamp. Same things happens for all people with rated MilkDrop presets. Winamp's installer overwrites them without mercy. In both cases Knotte and the MilkDrop preset rating guys should blame Winamp's installer - it has nothing to do with the Backup Tool.

Problematic will it be, if there were made some changes in Winamp.exe here and some changes in Bento there. User made a Backup of Bento, restored it a few weeks later and wonders that nothing works correctly, because Winamp.exe got some significant changes in a newer release, which requires an updated Bento skin.

Unless we have some fingerprint system or something like this, I will not backup the 2 default skins.

just have to look for skins.xml in the folder and assume it's a modern skin if that is present. though that can be fooled at times and it may be better to produce a NSIS plug-in to correctly determine the type of a skin (based on the Skin Manager loader core maybe).

Leave me alone.

[DrO]

Leave me alone.

never

the point about the skins is good & i'm glad you've replied with that. one thing may be to add some note/disclaimer as i'm sure there could be some people trying to use this which would be baffled by why their modified skin hasn't been preserved (though in that case it'd be better to have it in a different folder/skin zip).

interestingly, the backup of milkdrop takes longer than my ML files. i don't think i've ever altered those settings [for milkdrop].

this does raise a good point which i touched on with the modified skin files & that if the presets don't match a known file date than there's not much point in backing up the presets. though of course i can see why it'd be easier to just backup everything (as seems to be the case) so supporting files are also handled (unless a simple parser of the .milk files was created to determine if the preset needs additional files, etc).

also whilst i remember, http://forums.winamp.com/showthread.php?t=318183 may be of use to deal with all of the playlists in the ml folder being blindly backed up when only those in playlists.xml should be handled (as discussed out of this thread).... unless i've got to learn how to make NSIS plug-in's again to implement that handling as well as a better skin checker than just looking for the skin.xml file

-daz

[Koopa]

Still have to write a documentation. I'll add a note about the default skins then.

As for MilkDrop Presets, there are a lot advantages of backing them up:

- people can have downloaded presets
- people could've sorted their presets in different folders
- people won't loose their preset ratings, if they use the Back Tool before their upgrade Winamp and after Winamp upgrdae they can restore them.
- it's optional, if you don't want to back them up, uncheck it and the tool remembers your setting, great, huh?

At first I used a .milk backup mechanism, but it wasn't working, because some presets may ship custom bitmaps or presets are in subdirs and few other issues.

[DrO]

all i'm trying to convey is that if it is 'automatic' for a chosen option (which is a good idea) then it should be doing what it can to ensure that things are correctly done & obviously a complete backup of the folder is the easiest way to achieve that though it seems a bit of a waste to just blindly backup files which haven't been modified. i've no issues with preserving altered files but just copying something which hasn't been altered & so isn't important (if it has been altered then it's worth it) seems like a waste of resources.

now you did say you wanted comments, suggestions, etc

-daz