beta+frustration is a combination that goes without saying. Oops, I said it.
Operating System: Windows Vista™ Ultimate (6.0, Build 6001) Service Pack 1 Language:
Processor: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ (2 CPUs), ~3.2GHz
Memory: 8190MB RAM
DirectX Version: DirectX 10
1.5 installs and runs fine... Some internal clean up promotes Highest playback settings.
Have installed beta 2.0 on top of and cleanly after complete uninstall.
Before installing various .net items I did not get the error but the player crashes immediately after it displays it cannot locate the slingbox.
After installing various .net items and updating them all... I recieve a catastrophic error during the installation of the skins as the installshield app indicates the process.
Slingbox is detected but immediate crashes with Beta 2.0 and no luck at all with debugging.
Will attempt today the workaround noted in a seperate thread of renaming the particular file and reinstalling .net. and I'll post update. I am awaiting the arrival of my second slingbox. I just purchased a solo and I already own a classic.
Looking forward to the fabled Vista optimized versions that were hinted to us last year.
Would like to see more impressive bitrates for mobile devices.
Update pending - but I'm seriously frustrated with the BETA here.
wow not just one but 2 useless no brainer comments - and look both from the same source... thanks for bothering to reply? um then again... why'd you bother to post?
Can we avoid the clever commentary on Beta 2 threads please so actual information might be exchanged between parties that matter?
I'm sure you would rather be helpful than useless and redundant.
Updating thread.
Ok Beta 2.0 works well on my XP sp3 home laptop... updates firmware ( apparently to 1.2.7 from 1.0.99 classic slingbox) .Net 2.0 was implemented
Vista Machine posted above that had operational issues using 2.0 BETA can access the Slingbox using 1.5 version of slingplayer over my lan.
However, SLINGBOX MOBILE PALM CLIENT IS no longer able to access the box after the box has been updated with the 2.0 Clients needed firmware.
It locates.... ( skips connecting info) Displays "Starting..." but never goes anywhere after that.
Palm TREO 755p over Bluetooth Lan - Originally working near flawlessly with 15FPS at 180 to 230 average Kbps although often times it's much lower and requires me to do some unplugging of bluetooth Dongle or resetting the Treo or even reboots. A hassle at times, but I deal with it.
Let's hope we can consolidate issues here in this forum section so dev's and the community can solve all possible issues together.
UPDATE: 7:56 PM EDT 8/8/08
Apparently 2.0 beta suggests and or configures router rules for an internal IP of 192.168.1.199
Be wary that if you experience this problem - The inability to access your slingbox with your mobile devices after a BETA 2.0 update to a PC.... You my have 192.168.1.237 set as the slingbox IP or some other IP should you have done it manually for your own network configurations.
If this is the case.... you will have the same issue with the MOBILE CLIENT As I have AFTER you upgrade the firmware to 1.2.7 ( from the 2.0 BETA player)
To fix this issue you must access the REMOTE VIEWING - MANUAL SETUP in your Slingplayers properties.
and then alter your SLINGBOX IP to match your router rules for access.
I'd like to thank Chris from Tech support personally for helping troubleshoot this issue to resolution.
You're the BEST !!!!
First off, I wanted to say that I'm totally sorry for the light hearted comment. It's unfortunate you took it the wrong way, but boys will be boys as the name implies.
I should have been more direct, but hindsight is 20-20. Since you went out of your way to be a jerk and make a personal attack, I'll clue you in on a few things that you might have overlooked in your rush to frustration and judgment.
1. This is a community here, except when jerks post.
2. It's beta software, and you're complaining? Are you new to computers?
3. You run vista, and you're complaining?
4. And you wonder why you are frustrated?
5. You complain about a paid app not working when you CHOSE to run BETA software and firmware. Are you serious?
Keep us all up to date on your frustrations and explicit ignorance. Everyone likes to see a jerk flail.
I'm glad everything is working now Scrufboy, it was a pleasure to help you out with that, if you need anything else, just let me know.
Please folks, lets keep a support forum section dedicated to support so the beta can be properly administered and proper support given to those who need it. This way there isn't as many "Lighthearted" useless garbage posts to sift through for new readers. Those belong in off-topic
Again Thanks to those of you who helped via PM and thanks to car099 for solving the palm client issue with me.


RSS
