Thauzar Posted January 31, 2005 Share Posted January 31, 2005 nice! Didn't even know there already was a d version out.But, how come we can't install it on a system with winamp already installed? Before I used to simply install over the previous version. Or maybe i'm having a flashback... Link to comment Share on other sites More sharing options...
Alanoll Posted January 31, 2005 Author Share Posted January 31, 2005 nice! Didn't even know there already was a d version out.But, how come we can't install it on a system with winamp already installed? Before I used to simply install over the previous version. Or maybe i'm having a flashback... whoops. Forgot to add upgrade paths and such (didn't generate a newID for the package). If it's really that big of a deal, I can make the modifications in a few days. Link to comment Share on other sites More sharing options...
ZileXa Posted January 31, 2005 Share Posted January 31, 2005 oooh djees... I posted a while ago an error "no burners found"..Now I found out it has nothing to do with the msi or winamp itself..I use the CDreader plugin from Copah... thats the problem... you need to use the in_cdda plugin wich is always standardly included in winamp... otherwise you won't have burner capabilities.Ofcourse if you don't use pro it doesn't matter.btw the reason problem was solved after (silent) reinstall: the in_cdda plugin is copied to the winamp folder... My runonceex deleted this file and placed the alternative plugin...so sorry for that.and thanks for the new great build! Link to comment Share on other sites More sharing options...
Thauzar Posted February 1, 2005 Share Posted February 1, 2005 nice! Didn't even know there already was a d version out.But, how come we can't install it on a system with winamp already installed? Before I used to simply install over the previous version. Or maybe i'm having a flashback... whoops. Forgot to add upgrade paths and such (didn't generate a newID for the package). If it's really that big of a deal, I can make the modifications in a few days. Well it just would be easier for me to upgrade all the computers at once without having to uninstall first. But if there is gonna be a E or F version sooner or later I can wait for the next release. But if this is gonna be "final" for a while it would be very nice to add the upgrade thing you mentionned, please Thanks again! Link to comment Share on other sites More sharing options...
svasutin Posted February 11, 2005 Share Posted February 11, 2005 In Browsing post I found quite a few .ini settings, and am wondering which are still in use, and which ones do what[SETUP]XFULL=0; 1 overrides and installs allXNAME="some user"; a stringXKEY=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX; is this neededXAllShort=0 ; 1 installs all possible short cuts, overrides the next 4XDesktop=0 ; if 1 installs short cutXQuicklaunch=0; if 1 installs short cutXStartmenu=1; if 1 installs short cutxtray=0; not too sure about this oneXSkinsetting=Specify the SKIN to use in Winamp.XMODERNSKIN=1XINET=2 ; 0-always 1-modem 2-never; this setting is the same as the next twoxintex=2 ; 0-always 1-modem 2-neverxtypecont=2; 0-always 1-modem 2-neverXregopt=1; ?XREGAUD=1; all audio files are registered, same as nextXAUDIO=1 ; all audio files are registeredXREGVID=1; all video files are registered, same as nextXVIDEO=1; all video files are registeredxagent=1; Installs the winamp svcXWRITEWAV=1; enables .wavXNSV=1; ?xlibrary=1; ?Xvisual=1; ?Xextra=0; ?XDCOUT=1; ?xdircont=1; ?xnetscape=1; ?Xhotkey=1; ?Xjump=1; ?Did I miss anything?[Edit]I just downloaded the cab files.So each X%cab% = 0 will skip the cab, and 1 will enable it?If the cab is not listed, then the x%cab% is not available?[Edit Edit]For some reason the image did not show up for me the other day, not even the "no image" red-x ... now I understand Link to comment Share on other sites More sharing options...
Dobby Posted February 13, 2005 Share Posted February 13, 2005 ...As for the removing of the CAB files, to be quite on honest, I wasn't sure how that would work I knew that if you didn't select them to be installed it'd be fine, but I would have though the installer would have prompted you for missing CABs if it needed em.<{POST_SNAPBACK}>Yes I've found this now. I don't know what I was on when I tested it last time. Guess I',ll be using the INI then Link to comment Share on other sites More sharing options...
durex Posted February 15, 2005 Share Posted February 15, 2005 Is it possible to set other options with this? IE: Notifier preferences, scroll title window in task bar, etc... Link to comment Share on other sites More sharing options...
Alanoll Posted February 15, 2005 Author Share Posted February 15, 2005 Is it possible to set other options with this? IE: Notifier preferences, scroll title window in task bar, etc...<{POST_SNAPBACK}>You'd have to copy over your WINAMP.INI file. I didn't want to get into all the different preferences as then the complexity of the switches would greatly increase. I just thought of something, but implementing that was well is also a great task.So I suggest, install Winamp, customize it how you like. The during your Unattended install, copy over your customized WINAMP.INI file (not the one with switches in it, but the one found in the Winamp directory after isntalled) to where yo installed Winamp, and that should set ALL your preferences (except maybe icons till first startup) Link to comment Share on other sites More sharing options...
durex Posted February 16, 2005 Share Posted February 16, 2005 figured as much... thanks! Link to comment Share on other sites More sharing options...
prathapml Posted February 16, 2005 Share Posted February 16, 2005 copy over your customized WINAMP.INI file (not the one with switches in it, but the one found in the Winamp directory after isntalled) <{POST_SNAPBACK}>Now you get what I mean, about calling your MSI options file as wa5inst.ini or something like that, and let winamp.ini not have multiple meanings... Link to comment Share on other sites More sharing options...
Alanoll Posted February 16, 2005 Author Share Posted February 16, 2005 copy over your customized WINAMP.INI file (not the one with switches in it, but the one found in the Winamp directory after isntalled) <{POST_SNAPBACK}>Now you get what I mean, about calling your MSI options file as wa5inst.ini or something like that, and let winamp.ini not have multiple meanings...<{POST_SNAPBACK}>It's all up to the user. The INI for this MSI is user determined, and can be called anything the want. Link to comment Share on other sites More sharing options...
prathapml Posted February 16, 2005 Share Posted February 16, 2005 ...After you have create your INI file, start the install withwinamp.msi INI="%CDROM%\Unattend\winamp.ini"..... winamp.msi INI="%systemdrive%\install\winamp\winamp.ini"<{POST_SNAPBACK}>I meant the filename example you have given there - that sets an example of sorts, and people continue following that precedent. Link to comment Share on other sites More sharing options...
a06lp Posted February 16, 2005 Share Posted February 16, 2005 I meant the filename example you have given there - that sets an example of sorts, and people continue following that precedent. <{POST_SNAPBACK}>I Agree. My install-ini is called winamp5.ini, while my prefs ini is winamp.ini(as it has to be) Link to comment Share on other sites More sharing options...
Rico.JohnnY Posted February 16, 2005 Share Posted February 16, 2005 I use 7zip to make a SFX install package of winamp, for the "INI=" parameter rather than specifying absolute path in the config.txt, can i use relative path?something like the below;!@Install@!UTF-8!RunProgram="StartX.exe /WAIT \"msiexec /qn /i winamp.msi INI=config.ini\"";!@InstallEnd@!Does it work? Link to comment Share on other sites More sharing options...
Alanoll Posted February 16, 2005 Author Share Posted February 16, 2005 I use 7zip to make a SFX install package of winamp, for the "INI=" parameter rather than specifying absolute path in the config.txt, can i use relative path?something like the below;!@Install@!UTF-8!RunProgram="StartX.exe /WAIT \"msiexec /qn /i winamp.msi INI=config.ini\"";!@InstallEnd@!Does it work?<{POST_SNAPBACK}>not at the moment no. INI doesn't support that, atleast using the VBS script I have. I started on an InstallScript thing (would also avoid the Norton issue) but put it on hold and now forget what I was doing I should get back to it....dunno when though Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now