[FIXED | NUMEROUS CHANGES MADE] WACUP won't start

[pimento]

Hi, I've installed the preview build over a fresh install of 5.666, it works after it's installed but then the next time I turn my machine on, WACUP doesn't start - it's in the task manager as a background process, but the window never appears.

This is windows 10 pro 64-bit on a surface pro 3. Anything I can collect for you?

[Juanus]

I have never seen it run on one of those surface pros before. I will bet that the skin just went off the top of the screen.
I am assuming the directory structure is the same as a normal install of windows.
Close WACUP
In the %AppData%\Roaming\WACUP folder there is a file named studio.xnf. Rename it to studio.old
Start WACUP again and see if that works. If it does. save that studio.old file. DrO might want you to send it to him.

[pimento]

Thanks Juanus. I don't have a %AppData%\Roaming\WACUP folder, but I do have a %AppData%\Winamp folder that had a studio.xnf file in it, so I renamed that one - no change.

I don't think it's as simple as not being on the screen as I don't get the icon in the system tray (I turned off the taskbar and turned on the system tray icon) at all either.

[Eris Lund]

The next best thing you can try is to rename the winamp.ini file to winamp.old and see if that helps any.

[dro]

If that doesn't help then I'd remove the install & reinstall wacup just by using it's installer as it handles the 5.666 install for you.

Also when it's running in the background, is it showing as using any processor time ?

And to double check, it was downloaded from the wacup site & not somewhere else like chip.de ?

-dro

[pimento]

So.. that's a little odd. After I renamed that file and it didn't work, I rebooted the machine to see if that would make a difference and it's worked ever since. I left off reporting back so I could test it a little more thoroughly to make sure.

I didn't know the WACUP installer did the 5.666 as well, that's handy.. but previously I had tried just that one (after uninstalling the Winamp 5.8 dealie (i was curious)) and it wouldn't launch at all then either, which is when I did the 5.666 install and then WACUP over the top of that. The WACUP installer was downloaded from here, and the 5.666 was downloaded from the old winamp site way back when. When it was stuck in the background I didn't notice it using processor time, certainly not much if any.

Anyway, seems it's fine now, I'll report back if it goes wrong again.

[Juanus]

Which file did you rename and it worked? The studio file or the winamp.ini file?

[pimento]

The studio file. I see that it's created a new one now though.

Also I just knocked the dock connector and seem to have killed things pretty good, I can't play anything of my network share anymore - but it's the same in Groove, so this isn't a WACUP/Winamp problem.

[Juanus]

Correct. When you start wacup it will create a studio file if there is one not already there. Sometimes the file gets corrupted.

Good luck with your duck connector.

[dro]

Also I just knocked the dock connector and seem to have killed things pretty good

*fingers crossed* you're able to get that fixed.

-dro

[pimento]

It's doing it again with the latest public build. WACUP and Winamp (32 bit) are running as backgound tasks in the task manager, but there's no tray icon or window appearing. If I end task on WACUP and Winamp and try starting again (via Start Menu shortcut) it does the same thing, just those two processes starting (not using any CPU or anything) but no program appearing.

If I doubleclick an MP3 file, I get another instance of WACUP starting under background tasks, but still nothing appearing or playing.

Oh.. I tried to open an album's worth of MP3s (select all, right click, Open) and now I have a while pile more WACUP and Winamp instances running there..

[dro]

Ok, that's the bit of information that we were missing & I assume the machine wasn't badly damaged in the end?

Currently interaction with Explorer / OS shell is not fully implemented (e.g. double-clicking or using the open actions in Explorer) and is noted during install but not clearly enough.

That's what is going to be causing the apparent hung processes or multiple ones to be started & is why the WACUP previews (and beta builds) generally try to run as portable only installs but if there's been an existing Winamp install then depending on where WACUP is installed, the OS associations might be present & so can be used & thus lead to the issues being seen.

I've still to track down what's going on to cause the processes to hang as my local testing has generally worked but I know some of the earlier beta testers have reported a similar issue with the processes just hanging around & I've only been able to replicate it a few times but couldn't debug it at the time so I'm still stumped. Fixing it & getting Explorer / OS shell integration completed is one of the blockers for a non-preview build which can functionally replace an existing 5.666 install.

-dro

[pimento]

This also happens when I run WACUP from the start menu, and at the moment it's happening every time I try to launch it - is there any debugs or something I can take for you before I try a restart?

[dro]

It happening from the start menu is definitely odd as there's no reason for that to be trying to load anything other than its current settings.

The best thing I can think off so I can check if it's corrupted settings or something odd is to make a backup of your WACUP install (using http://koopa.meggamusic.co.uk/backuptool/) & then pm me a copy of the zip & I'll have to see what I can find. But really I need to get the file association handling re-implemented so I can actually debug things instead of the initially crippled solution that the preview builds are currently running.

-dro

[pimento]

It's doing it again, so PM sent.