Latest WACUP public preview for x86 & x64 is build #23960 (March 1st 2026) (x86 & x64 changelogs)
Latest restricted WACUP beta release is build #23960 (March 1st 2026) (x86 & x64 changelogs)

Author Topic: Cpro skin minimal - script error on launch  (Read 22559 times)

gravitas

  • Newbie
  • *
  • Posts: 4
    • View Profile
Cpro skin minimal - script error on launch
« on: August 15, 2025, 09:40:21 PM »
I'm trying to use a cpro skin (minimal 1 1 1 1), but this generates this skin warning message on every launch

After clearing the error it will launch but always it defaults to displaying the video tab instead of whatever smart view I had open in the media library before last close of the app .  Anything I can do to get rid of the warning message for good, and fix the default opened tab?

The skin I’m talking about is available here
https://winaero.com/download-download-cpro__minimal_1_1_1_1-skin-for-winamp/

ariszlo

  • Moderator
  • Hero Member
  • *****
  • Posts: 251
    • View Profile
Re: Cpro skin minimal - script error on launch
« Reply #1 on: August 16, 2025, 11:36:35 AM »
  • Open the skin with the 7-Zip file manager.
  • Enter the custom folder.
  • Right-click on custom_load.xml and select Edit in the pop-up menu.
  • Remove this line:
    <script file="@COLORTHEMESPATH@\..\..\Plugins\classicPro\engine\scripts\WinampVersionCheck.maki" param="2405;5.55"/>
  • Save custom_load.xml and close it.
  • 7-Zip will ask if you want to update the modified file in the archive. Answer Yes.
  • Exit 7-Zip.

gravitas

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Cpro skin minimal - script error on launch
« Reply #2 on: August 16, 2025, 06:26:46 PM »
That fixed it, thank you!

dro

  • Admin / WACUP Developer
  • Administrator
  • Hero Member
  • *****
  • Posts: 5645
    • View Profile
    • WACUP (Winamp Community Update Project)
Re: Cpro skin minimal - script error on launch
« Reply #3 on: August 21, 2025, 03:48:58 PM »
Will add a stub WinampVersionCheck.maki for the next build so the skins won't need to be modified to get them to load as that can't be expected for most to do. I can't remember if I just dropped that file from the cpro folder without checking enough what skins might be using or that most don't & this is just a small number of ones that could have issues & it wasn't in the copy of cpro distribution I was working from.