pcw Posted October 18, 2004 Report Share Posted October 18, 2004 Great config first of all! Now to the less good part.. I'm experiencing alot of "crashes" with the config.. I tried Sam 1.55 version and now I'm trying the 1.60 to no avail... Are there any mysterious settings I've forgotten? Am I the only one that is experiencing random crashes with the cdcovers configs? I want it to work badly Link to comment
pcw Posted October 19, 2004 Author Report Share Posted October 19, 2004 I'll try to be more specific..I'm having big problems getting the cdcovers to work without randomly crashing on me (client.exe in ntdll.dll and client.exe in AdvancedMediaPlayerInfo.dll)..I've tried it with Samurize 1.55 (which it's "made" for).. I uninstalled 1.55... installed 1.60.. same problems (random crashes in the above modules)I read in the AMPI Faq that the AdvancedMediaPlayerInfo.dll must be the same version as Samurize... that was the case with Samurize 1.55 but now when I've upgraded to 1.60 in the about plugin in the config editor it says that the AMPI plugin is version 1.55.Another question I have is I really don't understand how the cdcovers work. Sometimes it loads up another samurize client so I have 2 running. Isn't it just to choose a config file like cdcoversBOX.ini and then the config should handle the rest (like taking care of when clicking on the cd it opens it up to show more detailed information and so on.. it shouldn't be necessary to open a new client for that should it?)I'm just wondering if there are any obvious settings I've forgotten or maybe "tweaks" to make to get it working without the random crashes.I would just love it to work because I think it's a truly great config!Peace Link to comment
hush66 Posted October 19, 2004 Report Share Posted October 19, 2004 I have Samurize v1.60 installed as well, and the AMPI plugin is of version 1.55. Album art configs using the AdvancedMediaPlayerInfo.dll work for me fine though. So I'm sure the difference in version numbers isn't the cause of your problems. Link to comment
pcw Posted October 19, 2004 Author Report Share Posted October 19, 2004 I have Samurize v1.60 installed as well, and the AMPI plugin is of version 1.55. Album art configs using the AdvancedMediaPlayerInfo.dll work for me fine though. So I'm sure the difference in version numbers isn't the cause of your problems.So what do you think I could be doing wrong then? Link to comment
pcw Posted October 19, 2004 Author Report Share Posted October 19, 2004 I just opened up the config file named CDCoversBOX.ini and it had this code at the bottom:AllowLink=1Link=SkinsGUiPodPlayerBezelsbezelizer.exe foobarControlsshowI don't have foobar installed... what does that mean exactly? Should I remove those lines from the config? Maybe it's that that's messing things up? Link to comment
hush66 Posted October 19, 2004 Report Share Posted October 19, 2004 I'm not sure actually. I just tried out CRNI's CDCovers configs and it's working fine for me. And I've never had random crashes with Samurize.With regard to the problem of 2 clients running, perhaps the 2nd client pops up because it's of a different Instance. Hover your mouse over the 2 Samurize tray icons. Are the Instance Names the same? Or is one Default while the other cdovers?Also, perhaps you could reinstall Samurize again. This time, uninstall Samurize first, reboot, reinstall Samurize, then reboot again.Edit: I have that code as well. And I don't have foobar installed too. It isn't causing me problems.Edit2: How are you loading up the CDCover configs? Just right-clicking on the tray icon and then selecting the config? Try launching the Samurize Instance Manager instead, then adding a New Instance (name it cdcovers), highlight this new cdcovers instance, Edit Instance, select the appropriate config and settings, then Launch Instance. Link to comment
pcw Posted October 20, 2004 Author Report Share Posted October 20, 2004 I'm not sure actually. I just tried out CRNI's CDCovers configs and it's working fine for me. And I've never had random crashes with Samurize.With regard to the problem of 2 clients running, perhaps the 2nd client pops up because it's of a different Instance. Hover your mouse over the 2 Samurize tray icons. Are the Instance Names the same? Or is one Default while the other cdovers?Also, perhaps you could reinstall Samurize again. This time, uninstall Samurize first, reboot, reinstall Samurize, then reboot again.Edit: I have that code as well. And I don't have foobar installed too. It isn't causing me problems.Edit2: How are you loading up the CDCover configs? Just right-clicking on the tray icon and then selecting the config? Try launching the Samurize Instance Manager instead, then adding a New Instance (name it cdcovers), highlight this new cdcovers instance, Edit Instance, select the appropriate config and settings, then Launch Instance.What config should the instance use If I want to use the CD box? CDCoversBOX.ini right? cuz there are two more of them... one CDCoversBOXopen.ini and one CDCoversBOXopenON.ini.. Link to comment
hush66 Posted October 20, 2004 Report Share Posted October 20, 2004 Yup, the CDCoversBOX.ini file. The other 2 are just expanded versions showing extra information (which you can expand by clicking on the top left). Link to comment
Exon™ Posted October 22, 2004 Report Share Posted October 22, 2004 I get the same problem pcw. Two different samurize opening. One is default and the other one is cdcovers, both showing the same thing. Link to comment
pcw Posted October 22, 2004 Author Report Share Posted October 22, 2004 I made myself a clean config file with just using the AMPI plugin using the function "getalbumcover". And it was on for a straight 24 hours or something without crashing. So there's got to be something in the configs of CRNI's cdcovers that makes it crash. So I guess I'll just create my own albumcover config.. Link to comment
hush66 Posted October 22, 2004 Report Share Posted October 22, 2004 I get the same problem pcw. Two different samurize opening. One is default and the other one is cdcovers, both showing the same thing.Like I mentioned, there are 2 configs because they are different instances. CRNI's configs are all meant to belong to the instance "cdcovers". But because you load one of his configs using your "default" instance, and then click on some part of the config (to expand or change the config for example), a different instance (and therefore 2nd config) will appear. Look at my post above (particularly Edit2) for correct instructions on loading the configs. Link to comment
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now