Important is that you have version 5.1 i dont care for minor fixes etc.

I just like that the 5.1 system is supported.

P.S. Tnx Alanoll for the latest MSI and for all your time.

Sorry alanoll i know you hate it when we tell you but ....there is a new version out

Edited November 17, 200520 yr by muiz

Why do they do this. A Winamp version is only actual for 1 or 2 weeks. Now I integrated version 5.111 and what do they do? Yes, 5.112 is released. Hmm, but better a fix for the bugs than a bugging software. So now I'm waiting for the msi.

It was the same with a,b,c,d,e versions... Like Nero, I guess they like releasing stuff and having lots of people going to their webpage to download the latest version. Anyway, what would be the meaning of "latest version" if they were not constantly releasing a new one to fix a bug or two.

has this msi been updated to the latest version?

I'm sure it is, in fact, knowing they will release a new one before this friday (this is a guess). If I was allanoll I would simply wait for 5.113 so I would not work for nothing. I still have 5.1 only and it's fine for the moment.

But remember allanoll is a student (or I think he his). The finals are coming in less than a month so I can also guess that just like me he has a truckload of work to do.

can i put this in the runonceex file? because i dont understand it really, and i want to make it work, with runonce

Here's my runonce code for winamp, just change the path of the msi file and the ini file to suit your needs.

REG ADD %KEY%\050 /VE /D "Winamp 5.111" /f
REG ADD %KEY%\050 /V 1 /D "%systemdrive%\Install\Winamp\Winamp5111.msi INI=%systemdrive%\Install\Winamp\winamp.ini /qn" /f

Note: the second and third line are really all on one line.

Edited November 22, 200520 yr by fly2279

Here's my runonce code for winamp, just change the path of the msi file and the ini file to suit your needs.

REG ADD %KEY%\050 /VE /D "Winamp 5.111" /f
REG ADD %KEY%\050 /V 1 /D "%systemdrive%\Install\Winamp\Winamp5111.msi INI=%systemdrive%\Install\Winamp\winamp.ini /qn" /f

Note: the second and third line are really all on one line.

so i can put that in my runoncefile, and then it works ? if its yes, thnx!

BTW: Must i fill my serial, in the ini file of in that rule?

Edited November 22, 200520 yr by Edwin1988

Now with the msi edition : try to uninstall it from the uninstaller in the app directory then go to the control panel and you will see that the uninstall enrty is in the list .

click remove and uninstaller loads again and uninstall winamp !!

why is that?

Now with the msi edition : try to uninstall it from the uninstaller in the app directory then go to the control panel and you will see that the uninstall enrty is in the list .

click remove and uninstaller loads again and uninstall winamp !!

why is that?

perhaps because the uninstaller in the Winamp folder is a remnant of the NSIS installer, where as the entry in the Add/Remove is created by the Windows Installer.

i think then it would be better if we have only the original uninstaller since the msi will only install the files that the original installer will install.

i think then it would be better if we have only the original uninstaller since the msi will only install the files that the original installer will install.

I must disagree. It would be better to use the uninstaller that is native to the installer that installed any given application. Since the original installer is NOT that, I must disagree. What would happen if i chose to modify the installer to add MORE files then the original? What if I accidentally added some old MilkDrop files instead of the new ones? They would not be removed by the original uninstallation process. The original uinstaller was left in the MSI simply because it's a file created during the original installation. It will be removed in the next release so that people don't get confused on which uninstaller to use.

you are right . Thankx .

Any ETA on v5.112 yet?

Any ETA on v5.112 yet?

You mean 5.12

http://forums.winamp.com/showthread.php?s=&threadid=232824