conflitto con WInlive

[toty72]

salve e grazie per avermi accettato nel forum
ho installato l'ultima versione di JP ma quando lo apro sul mio notebook, spesso non parte ed esce una finestra di errore (vedi allegato).
Ho notato che succede sempre quando apro anche il programma WInlive 9 e credo vada in conflitto.
Per poterlo utilizzare sono costretto a reinstallarlo , tenendo aperto anche il Winlive
C'è un modo per poter ovviare a questo problema?
grazie a tutti per le risposte.
saluti

WIndows 10 - 64bit
memoria 8gb

[Couin]

Hi and welcome

I don't know WinLive 9.
I never saw the error type before, I don't know yet how to fix, if it is fixable.
If you launch JP withou Winlive at all, is the error occur ?
Do you have other errors -of the same type, so #429) ? If yes, can you report here the Function name and the Last known line number ?

PS: Please try to post in english (or french) if you can

[toty72]

hello and sorry if I wrote in Italian.
if I start the JP first then when I open the winlive it gives me an error.
Same thing, if I start the WL first, I get the error I posted.
I haven't seen any other errors.
I also tried changing the sound card in the settings, but nothing changes. Same errors.
I await advice
HI

[Couin]

Hmmm,
The "SwitchDarkMode" function is called on startup only, and if in the Settings, you check/uncheck "Custom colors" in the Interface tab, so there is no reason that the error occurs when you start WL when JP is already stared, or perhaps you don't give enough time to initialize (the splash screen should disappear and the main interface is displayed, to leave enough time to initialize).

The function and last know line number are not related with soundcard, but to the borders of frames.

Can you try to replace the exe with this one in the installation folder:
https://jinglepalettereloaded.com/files ... alette.exe

The frames borders will appears in red, but I would know if the error still appears, and if yes, copy it here.

[toty72]

I tried to do everything slowly and change the exe, but the error still comes out.
but this time he says
LAST KNOW LINE NUMBER: 17
instead of the previous 13.
by clicking on NO
other error lines appear:
3 - 206 - 77
However, I had to reinstall WL and it wouldn't open after launching JP
I await your news
Thank you
HI

[Couin]

I found WL9 and I get the same errors here, and after click "No" on each, JP does nothing (splashscreen still displayed and must kill process to exit)...
but honnesty, I don't know at all where to search the problem

[toty72]

let's say I'm not in a hurry, maybe if you can find the solution in your spare time, I would be really grateful.
I like JP too much and have been using it since Windows XP and at the time with WL 4.5 it didn't cause any problems.
I hope to hear good news from you.
Thank you and I wish you a good evening
HI

[Couin]

WL9 (I don't know about WL4.5) looks to be written in Visual Basic 6, like JP, and I can see there are some files also used by JP (COMDLG32.OCX, NSLIDE32.OCX, stdole2.tlb) but installed and registered in different directories (WL install them in it's installation folder instead of %system%).
That would explain why JP get errors.
If you reinstall JP, WL will display similar errors (object not found and unavailable licence).

[toty72]

I tried as you asked, but to no avail.
The only way to keep them both open is to start JP first and then by opening WL the error I attach appears.
I have to reinstall WL while keeping JP open and that's fine, but only until the next reboot.

[Couin]

You get what I got.
Each softwxare register the files where their installed copied them, so it can not run correctly for one of both. The better would be WL9 install files in the system and register them (registering an OCX increment a coutner of "softwares using this file").
I asked some help about on another forum to see if there is a workaround but if not are if need to change too much code in JP, I'm afraid the conflict still there.

Did you tried with a more recent version of WL ? I see on their website, the version is actually 13. Perhaps they changed files installations and registering ?