After my computer comes out of hibernation, the XMD is no longer initialized and XM no longer works. The only way for it to start working again is to close FSRX and reopoen it to get it to initialize the XMD. Is there a way to have the program automatically re-initialize the receiver when it discovers it can no longer communicat with it?
I'm having this same problem, and its really, really inconvenient to have to unplug and re-plug the xm cable each time I reboot. I usually hibernate, which it does survive, but once in awhile hibernation fails and you need to reboot.Originally Posted by cletus323
What's causing this and how do we fix it? It's making the whole XM thing mostly useless.
I always close the XM app (and most other apps) before I hibernate, since I like to start fresh w/every boot.. but that's just my habit. ::shrug::
Why do you hibernate, if you close all your apps before ? I would think it takes longer to close everything then hibernate... as opposed to just shutting down... and i dont think hibernate would save you that much time on starting up if you include the opening everything up again...
just curious...
Pentium 4m 1.5GHz|MB896|Roadie Extreme|XM-Direct|Rikaline 6010|T-View 7"|Streetdeck|160gb Western Digital|1Gb DDR2-533 Ram
Mine never survives a hibernation. I dont' have to reboot the system to get it to work though. I just need to close FSRX and open it again. I think what's causing it is the fact that when you hibernate, the XMD gets its power cut. On the next boot, it powers back up but no initialization command has been sent to it from the computer. To get the command sent, you need to reopen FSRX as it sends the magic bits (or whatever it is called) upon opening. I think a easy way to fix it is to make it so that whenever FSRX detects a resume from hibernation, it should check for communications between the XMD and the app and if it doesn't exist to then send the initialization commands.
With my PC (Via C3 750MHz.. slow, I know) it takes about 20sec to hibernate, then abt 20sec to resume. Or, I can shut down completely in 5sec, but take 90sec to boot. I save time with my setup, yours might be different.
It would be nice if I could hibernate w/Frodo's satellite app, but I'd really like the app to start faster. On my system it takes like 10 seconds to come up, which is ridiculous IMHO.. but I'm grateful for the app and I couldn't code an app to interface w/the XM so I don't complain too loudly.
FSRX already reinitializes after hibernation.
Check your device manager to make sure you don't have the
XM Direct detected as a serial mouse. If you do, disable, not delete it.
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
So it does. After playing with it for a while I figured out what was causing FSRX to not reinitialize the XM Direct. I found that this happens when it is embedded in Centrafuse. When FSRX is running while not embedded, it survives hibernation flawlessly. It works even when Centrafuse is running in the background. The problem happens ONLY when it is embedded. Is this an issue with Centrafuse or is it a general embedding issue (will it work embedded in other frontends)?
Awesome program btw
Well, I'm not sure, it must not be recieving the hibernate message when embedded.
I can add a reset command if need be. But it won't be automated unless the embedded app can send it.
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
How come on my tv in my car, the channels look all scrunched together, and I can view any of them.. I'm running at 640 x 480 and at 800 x 600, its the same thing.. HELLPPP
Posting Permissions
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks