PDA

View Full Version : Giving up and sending it back



martin@ntl
2004-07-10, 13:11
I am in the same position. I'm half way through writing a detailed description to sent to the support people for Monday in case they can help. On a new clean installation of Windows XP, Slimserver is crashing Windows XP repeatedly, every hour or so, sometimes when it's nto even playing, and on a music filder containing only 30 songs. I wouldn't mind if I could close it in task manager. It's years since I used a program that was so bad that it crashed several times a day, and forced me to reboot the entire PC.

Several other people have posted problems with crashes in XP.... I think there must be a problem to be fixed here. I assume it's been tested with XP!

I've been monitoring slimserver for an hour now. IT was ok for an hour, with cpu usage at about 2%, and then cpu usgae started rising and slimserver is now using 98% CPU.. I expect it to crash again soon!

Martin

After a week of playing with the Slim Server settings, watching my computer
>grinding to a halt, having to constantly reset the Slim Box I've decided
>it's going back. It's a great concept but I don't have the time to strip
>windows down to the bare bones, remove all electrical devices nearby or
>whatever it takes to have both the computer and slim server talk to each
>other for more than a few songs.
>
>I've only had one day where it didn't crash the computer completely. Sorry,
>it ran for a day or two then I closed it and when I tried to restart it, it
>hung so I hit cancel, and tried again and ended up with two copies of
>slim.exe running and one of slimserver.exe, all 3 impervious to
>CTRL-ALT-DEL, when this happens (quite regularly) the computer won't even
>shut down, I have to hit reset or pull the power.

Ken Veasey
2004-07-10, 15:14
Its worth adding that since 5.2 I am experiencing the same thing
intermittently on XP. A power off/on off my PC is the only resolution
as it completely hangs.

Ken


On Sat, 10 Jul 2004 21:11:08 +0100, you wrote:

>I am in the same position. I'm half way through writing a detailed description to sent to the support people for Monday in case they can help. On a new clean installation of Windows XP, Slimserver is crashing Windows XP repeatedly, every hour or so, sometimes when it's nto even playing, and on a music filder containing only 30 songs. I wouldn't mind if I could close it in task manager. It's years since I used a program that was so bad that it crashed several times a day, and forced me to reboot the entire PC.
>
>Several other people have posted problems with crashes in XP.... I think there must be a problem to be fixed here. I assume it's been tested with XP!
>
>I've been monitoring slimserver for an hour now. IT was ok for an hour, with cpu usage at about 2%, and then cpu usgae started rising and slimserver is now using 98% CPU.. I expect it to crash again soon!
>
>Martin
>
>After a week of playing with the Slim Server settings, watching my computer
>>grinding to a halt, having to constantly reset the Slim Box I've decided
>>it's going back. It's a great concept but I don't have the time to strip
>>windows down to the bare bones, remove all electrical devices nearby or
>>whatever it takes to have both the computer and slim server talk to each
>>other for more than a few songs.
>>
>>I've only had one day where it didn't crash the computer completely. Sorry,
>>it ran for a day or two then I closed it and when I tried to restart it, it
>>hung so I hit cancel, and tried again and ended up with two copies of
>>slim.exe running and one of slimserver.exe, all 3 impervious to
>>CTRL-ALT-DEL, when this happens (quite regularly) the computer won't even
>>shut down, I have to hit reset or pull the power.

Michel Fombellida
2004-07-11, 00:46
Weird... I am running the latest nightly on XP (SP1 and recently SP2 RC2) for
quite a while now and I've never seen XP crashing. The only problem I've seen
with the CPU is when running iTunes at the same time (the CPU goes high for a
few seconds and usually at that time the audio stream drops), I've increase the
time between db rescan and it seems better.

Michel