Jump to content

Alanoll

Patron
  • Posts

    5,494
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Alanoll

  1. that was probally there after the last update for 5.0.7. As for what's different I don't think there are any real changes, except for version number. @larciel See, I just don't understand it with you people and trying that... Did you see a path for msiexec.exe when I posted it? or just on the MSI? I could have sworn is was JUST THE MSI. The INI entry will also need a complete path however.
  2. actually.... What primarily took so long on the 5.0.6-5.0.7 was that simply I knew a new was gonna be out in a week or less...so...waste of time, that and I lost the original files from the last MSI and had to start from scratch (which is why that WAV file bug came up again...). This one, used my method of applying new files, and rebuilt.
  3. I've already competed repacking the Winamp 5.0.8 Fast eh? I'm guessing the "bundled mp3" thing is the new thing they added (of which I didn't include)
  4. be more specific?
  5. yes. It's intended SOLELY for Tablet and MCE editions of XP
  6. alright, and now for the EASY answer for you to reduce the amount of work... remove QCHAIN.EXE Problem solved You didn't completely read the site, where it said to run the download, THEN copy the proper QCHAIN.EXE file. I'll try and make that more clear in the update (sorry for the confusion). Also, QCHAIN is no longer needed with Post-SP2 updates (what you're using) At the point you're at, this is probally the simple fix.
  7. ah geeze.... bloody hell.... oooh man....bad news for Winamp, this could very well be the FINAL edition (from NullSoft) anyway. Watch the credits, previous versons had "(for now)" at the opening, it's no longer present, as well as another original programmer left, leaving just Tag
  8. should be UnattendSwitch=Yes Search next time, and don't post your CDKEY. and use CODEtages.
  9. Does this mean you released the fixed version? if I hadn't fixed it, why would I have uploaded it, changed the date, AND uploaded the CAB version?
  10. I've spent almost 4 hours today writing....just thought I'd give alittle progress report. If I keep this pace up, you people might get a Christmas present
  11. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] "DAEMON Tools-1033"=- Should do it. [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run] Will delete the entire key "Run" and everything in it. the =- in the first code block, will narrow it down to ONE value. Just be sure not to also include the - in the path to the key
  12. then stay with the msiexec.exe code then. It is what is TRULY called when you call the MSI alone, or when you double click.
  13. SMACK! leave out the INI for now. WINAMP.MSI is in C:\ i take it? Can you execute it alone? without /qb or /qn? if it runs, cancel it. execute it with this line msiexec.exe /i C:\Winamp.msi /qb Leave the quotes out for now, just see if that runs. If it does, try it without msiexec.exe. If it continues to work, add INI= either AFTER /qb or before, I suggest after, but I'm unsure. FYI - You're the ONLY one with this problem, so it's something you're doing wrong. Also, redownload the MSI, it's best you do
  14. Sectioin = Thread ? j/k I really don't think it's neccesary. Why should there be a link to another forum, especially one two below this one? The member apps were included prior to them getting their own forum.
  15. put the /qb BEFORE the INI switch, and try again.
  16. the skin must be in the DESTINATION install directory, and use the NAME of the skin, not the filename of it.
  17. yes, but I've been trying to get the XREGAUD working as well, but my mother has been putting me to work since I came home for hte holidays....
  18. Try not to double post... I removed your second post that was exactly the same, and changed the title of this one to that one.
  19. I'll see about it...I got two others their own forum.... The difference being, WPI isn't ONE person developing, there's like 4 different versions, and they'd ALL be in there. But I guess that's just another forum to watch... But I agree, especially with this latest outbreak...WPI should get it's own forum.
  20. where did you get a 256 character limit? Windows XP SP2's WINNT.SIF file had a limit of....over 1000 or something....
  21. that shouldn't be TOO hard. Of course for this update, I would just put the same date at all the pages
  22. man, I'm really sorry. I know what it's like. Had my harddrive fail on me with all my Winamp MSI stuff on it... sure hope this doesn't hinder my little project....
  23. i thought bootcfg works on 2000, just that it's not included with 2000.
  24. @buzzman2005 This is your warning. You have posted THREE topics with problems you have been having with WPI. There is a WPI thread that you should post in. If NOTHING ELSE, you could have stayed in your FIRST topic, and just said you had another problem. If you post another WPI question in a new topic, or not in the FOUR above mentioned one, I will have to take more drastic measures. It is better to post in the WPI thread as people are subscribed to that and ONLY that and never look at the rest of the forum. If you want help, STAY WITH THE ORIGINAL THREAD! @all This actually goes for all, but buzzman2005 is the current example. So NO I'm not picking on him, but with THREE WPI topics in less then 4 hours of eachother...
  25. alright, you need to learn how to use tags when posting. use them WHENEVER you post code or regweaks or anything of that nature, and if it' really long, ATTACH it.
×
×
  • Create New...