Recoveryone;165992 Wrote:
> And with the new Pioneer receiver I just got that has the ability to
> re-config compressed music files back to its original state (needs to
> be optically connected).
>
>
Ummm... if you think that it has the capablity to get the original
sound quality back from a c
Turns out my issue was not port related. I had an older screen saver
(worldclock.pm) that was causing the server to crash.
Seems like the worldclock screen save will not work with 6.5.x
--
gages
gages's Profile: http://f
its amazes me how such highly reguarded product has so many issue with
the software. I order a SB3 based on the recommendation of the reviews
on CNET also on the poor performance of my Netgear Mp101 DAR unit. The
one thing that push me to get a SB was the fact it had digital outputs.
And with th
Upgraded to 6.5.1, I also had to change my port.
Anyway to have the browser load with the new default port (9080)?
--
gages
gages's Profile: http://forums.slimdevices.com/member.php?userid=1788
View this thread: http://fo
I got the slimserver working with the revised settings in McAfee. I made
the recommended browser link to deal with the incorrect address on
startup.
I now have what seems a solid stable program running. I think it is now
safe to order the squeezebox.
I really appreciate the many people who helpe
Inniswhe;162558 Wrote:
> Thanks Ceejay.
> I finally have slimserver working stable. I turned off McAfee virus
> scan. I don't know how to set it up to skip certain files as
> recommended.
> If anyone knows how to do this in mcAfee Total Protection 2007 please
> let me know because I don't want t
Thanks Ceejay.
I finally have slimserver working stable. I turned off McAfee virus
scan. I don't know how to set it up to skip certain files as
recommended.
If anyone knows how to do this in mcAfee Total Protection 2007 please
let me know because I don't want to leave it off for long.
Is there a
could well be McAfee - see
http://forums.slimdevices.com/showthread.php?t=30531&highlight=mcafee
Ceejay
--
ceejay
ceejay's Profile: http://forums.slimdevices.com/member.php?userid=148
View this thread: http://forums.slimd
When you say "it crashes", what exactly are you referring to?
Slimserver stops, lights go out on the slim icon on the bottom of the
screen and the browser stops displaying info. Other IE pages will
continue to work fine so it does not appear to be an IE issue
Is slimserver itself stopping? If s
When you say "it crashes", what exactly are you referring to?
Is slimserver itself stopping? If so please have a look in the Windows
Event Viewer (via control panel / admin tools) to see if there are any
messages there.
Or is it the browser that's locking up? If so, did you by any chance
instal
Thanks Mark for the tip on the refresh click. It was the start
navigation click , I changed to None and that solved that problem.
I am still manually adjusting the browser address to port 9080 to see
slimserver on start-up but it is extremely unstable. It crashes every
few actions taken like brow
Inniswhe;161620 Wrote:
> I checked the file as recommended by BPA. The port was 9080. I opened
> the program and put the correct 9080 port number in and voila, there is
> the interface back again.
>
> Now every 10seconds something is happening but I am not sure what.
> There is a program trying
I checked the file as recommended by BPA. The port was 9080. I opened
the program and put the correct 9080 port number in and voila, there is
the interface back again.
Now every 10seconds something is happening but I am not sure what.
There is a program trying to access the internet or something
Installing 6.5.1 will not stop the port conflict which is stopping you
getting at the slimserver web page. The browser trying to open the app
(not slimserver) which has taken over port 9000 - that is why there is
no change after installing 6.5.1
netstat is useful to find what is using port 9000 b
I installed version 6.5.1 latest build as recommended by BPA and the
program will start but I get the following diplay on the browser:
.NETÁSystem.Runtime.Remoting.RemotingException: Tcp channel
protocol violation: expecting preamble. at
System.Runtime.Remoting.Channels.Tcp.TcpSocketHand
Inniswhe,
It looks like some other application is already using port 9000 and so
your browser can't connect to it as it is not a http based app so you
get protocol errors. You can find out the offending app by using
netstat.
Since slimserver will find out on startup it can't use 9000, IIRC
slims
I had the same problem, which was a conflict over the use of the port.
The reply below cured it (or at least partially, since after I removed
the conflict I discovered that 6.5 is extremely unstable! Try 6.3.
http://forums.slimdevices.com/showpost.php?p=158862&postcount=10
--
David Lawrence
--
17 matches
Mail list logo