1.22 barf

[mccarthy1ca]

[Service-Team]

mccarthy1ca wrote:
> one album and get the following error:
>
> imgthread
> Read
> cover:Abba/abba+gold++greatest+hits

I think, this error is shown after the next start of the Silverjuke Program. Which error is displayed is displayed at the moment of the crash (most times a number in the form 1234:5678 or so)?

[Guest]

Service-Team wrote:
> mccarthy1ca wrote:
> > one album and get the following error:
> >
> > imgthread
> > Read
> > cover:Abba/abba+gold++greatest+hits
>
> I think, this error is shown after the next start
> of the Silverjuke Program. Which error is
> displayed is displayed at the moment of the crash
> (most times a number in the form 1234:5678 or so)?

No such number appears on the screen. It (Windoze) only says its generating an error log.
Where do I find this error log?

Anthony

[mccarthy1ca]

BTW
1.22 and these OGG files works fine on XP/SP2.
These OGG files are on a samba share sitting on a Linux box.

Anthony

[Service-Team]

Guest wrote:
> No such number appears on the screen. It
> (Windoze) only says its generating an error log.
> Where do I find this error log?

The logs are placed at C:\Documents and Settings\All Users\Documents\DrWatson\drwtsn32.log

However, normally Windows does display a message as "General protection fault at xxxxxxxx - generating an error log". This xxxxxxxx is the most interesting part for us.

[mccarthy1ca]

I am sorry to insist but no such number appears on the screen.

[mccarthy1ca]

I attach the log file

[Service-Team]

mccarthy1ca wrote:
> I attach the log file

Thank you. At a first glance, it is very likely that the problem are the Winamp Ogg-Decoder modules - esp. as you wrote the problem does not appear on another system (where I guess is a different version of in_vorbis.dll installed - some of the very new Winamp modules are known to make some troubles).

To get rid of these problems, we've reprogrammed our internal sound-processing for the next Silverjuke version and do not rely on winamp anymore. If you like, you can test this version - I guess this fill fix the problem.

Best regards,
Your Silverjuke-Team

[mccarthy1ca]

Thanks - that solution worked.

Anthony

[Service-Team]

We should really make the new 1.50er version official these days ...