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

[Koopa]

Found the issue for the log and ini file deletion issue, uninstaller doesn't read our Winamp_Ini_Dir path.

[Koopa]

Winamp Backup Tool v1.0 Beta 9b available

1.0 Beta 9b:

- [Installer] fixed uninstaller not deleting Winamp_Back_Tool.ini & Winamp_Back_Tool.log file
- [Installer] fixed uninstallation and previous mode handling for documentation file (Beta 9a specific only)

Hopefully this will address all uninstallation issues reported by Pawel.

Uninstallation of Start Menu entries is working fine here, need to test it with UAC enabled, though.

-Chris

[holeintheday]

My prayers have been answered! I have been going through a migration from XP SP2 to win 7 64, and finding your app was a real lifesaver.

for the last couple years I had been using ml import / export to backup my settings but had never actually tested importing with it until now. well that turned out to be a real pain in the ass as smart views and playlists were not stored, filenames with special characters weren't recognized, etc.

with your app it was a breeze, took me less than 10 minutes to backup from my old machine and restore on my new one. no problems that I have noticed so far. looks like all that is left for me to do is install some input plugins that were in my old profile and I'll be good to go.

Can't that you enough for this!

a minor suggestion to clarify some text in the interface would be to amend the following:
"Where do you want to save your backup?" to "Where to you want to save your backup to, or restore a previously saved backup from?"

[Koopa]

Thanks for your feedback.

For next beta:



I thought many times about backing up 3rd party plugins, but there were many disadvantages.

One big problem was, that I had to create a fat exclusion list for the official Winamp plugins, because a simple backup of the whole Plugin folder is no choice.

Another issue is, that some plugins install more than 1 single dll file. E.g. SNESAmp install an unrar.dll file and some help files etc. Maintaining this would be horrible with the many plugins, which are available.

So backing up the plugins itself is a user thing.

[Truth Unknown]

Maybe future 3rd party plug-ins can optionally include a file that Winamp Backup Tool can use to back up the plug-in.

[Koopa]

Most 3rd parties never got an update to support newer Winamp features/APIs, like multiple profiles, all media library features or the Winamp transcoder.

So I wouldn't expect any support for the Backup Tool.

Even if I'd add such functionallity and some plugins would support it, what shall I do with the other tons of plugins, which don't support it?

[Truth Unknown]

Yeah, a good chunk of the plug-ins I use are like that, but I can live with it. Although I might nudge a few programmers once in a while to add the new Winamp stuff with no luck. Anyway, I can see how difficult it would be to work in legacy support of plug-ins.

I'd say forget them, but allow the user customize the backup file script/list/instruction/????/profit for them. Maybe a part of the community can step up and analyze the old plug-ins and figure out what would be needed for backup. That might be hoping for to much though.

[DrO]

most of the issues with the plug-ins can be resolved via 'loader' plug-ins but it then becomes a lot more of a maintenance issue in ensuring things work correctly without random crashes or permission override issues, etc. i did make a mini plug-in core that does that (is used with the Waveform and SNESamp wrappers i've produced though they've highlighted the fragile nature of such 'man in the middle' operations that just applying it to every old plug-in (as much as i'd like to) isn't always viable.

also such older plug-ins can be looked at / simply fixed if source code is normally provided though most don't and it then falls into the previous category which i would do but time and resources are only finite and i've only ever really fixed plug-ins i've used or had suggested to be fixed.

-daz

[labrador999]

nonadmin user problem

Normally I am logged in as a non-admin user with limited rights (windows 7).
When I run BackupTools the windows UAC-windows pops up and forces me to enter an admin user.
The problem: Now all the data of this admin user is backed but not my data.

[Koopa]

UAC issues really don't surprise me, the tool was written mainly for users with full access.

I will try out some setups with limited user accounts and look at the issue. Maybe I find a workaround.

Edit:
Hmm, I tried it with a limited user account and have set UAC to max level. I got no uac prompt. Backup was done for the correct account.

Could you say, in which folder you've installed the Backup Tool? Are you running the 32 or 64 Bit version of Win7? Also could you please upload the Winamp_Backup_Tool.log file?

[labrador999]

1. I temporary changed my limited account to an admin account and all runs perfect.
2. I changed back to limited user and the problem is back.

So the problem is the UAC which pops up and forces me to use an admin account which of course tries to save his data but not mine.

Strange: when I run (1.) all data is saved and a log is created in the save-directory.
When I run (2.) admins data is saved but NO log is created. So I can't add a log of the problem run.

Winamp_Backup_Tool runs in C:\Program Files\Winamp Backup Tool
The saved data is stored in an external drive (but I tried STANDARD as well - same problem)

Access mode on both directories are set to FULL read/write for admins and for me as limited user.

Why does UAC _not_ pop up when you try it ? What could I test to help ?

[labrador999]

sorry - I missed one question.

I run Windows 7 home professional - 32 bit

[labrador999]

@Pawel

Your description helped me.
The following workaround does the trick:

1. I modified the contents of "C:\Program Files\Winamp\paths.ini"

from "inidir={26}\Winamp"

to "C:\users\MYlimitedACCOUNT\AppData\Roaming\Winamp"

2. Now I start WinampBackupTool - UAC pops up - I enter admin/password

3. In WinampBackupTool I do not use the STANDARD destination but enter a directory MyWinampSAVE which belongs to me. Now the correct data of MyLimitedAccount is stored in MyWinampSAVE.

[Koopa]

I could reproduce the issue and after some search, we saw, that UAC made trouble in NSIS since Windows Vista was released.

It's one of these UAC glitches, as soon as you enter the Admin name with password in the UAC prompt, it will read the path variable for the admin account, instead of the user account variable.

We will look into the issue and try our best to resolve it.

[Koopa]

labrador999:

This hopefully should fix your issue. Note that you better press the 'Default' button on first page, to refresh the correct path.