Thread: Centrafuse 1.1 Bugs

When I click on the button to dial the internet, centrafuse dials all the way through, but then lags for about a minute or so. Eventually, a dialog box comes up as follows:

Failed to load resources from resource file
Please check your setup

This was happening the other day, so I completely reinstalled windows and everything on my system. I'm now shocked the the problem persists.

Any ideas?

I also had this error with RC5, but dialup works fine straight from windows.

Is it possible that it has something to do with the nexus skin?

Scott

Originally Posted by veetid

Does it create an error.log file? This must be the thread not getting closed when you issue the command from the hotkey, therefore running non-stop and causing the error...

I cannot reproduce, I just sent the hotkey from the keyboard over and over and it will not popup... I also use a powermate to send the hotkeys in my personal car and have used it for 3 months and never seen this...

does it create an error.log file? If so please post it...

david

Here's the error log.

Originally Posted by veetid

That is strange about the XM error, I didn't even open the XM files for this release, literally.... Sure no other programs have the port locked?

Yeup, I'm sure - the only possibility would be that some other CF 1.1 module had the port, but I went though them and there's nothing in what CF shows or any of the XML files.

Remember, a) CF _does_ open the port (confirmed by the monitor), it doesn't talk to it. b) If I exit CF and load Hyperterm, I can open the port and see the XM idle message. c) If I exit CF 1.1 and load AIMEE or CF RC5, XM works fine. It's really looking like it's CF 1.1.

Maybe it's related to the work you did on the COM port handler? (there's a reference in the release notes to support for > COM9)

You can easily make it not open your USB ports by disabling Auto Play in Settings...

I don't think this is an auto play issue, the H10 was plugged in long before CF was launched.

H10 plugged in, 20+ minutes passed, launched CF, CF browsed the device... etc.

Originally Posted by spdyscotty

When I click on the button to dial the internet, centrafuse dials all the way through, but then lags for about a minute or so. Eventually, a dialog box comes up as follows:

Failed to load resources from resource file
Please check your setup

Scott

I know this is probably not related to the problem Scott is having, but that is the same error message dialog box I get with the Volume dialog box issue I posted earlier today.

From the error log:

3/4/2007 5:06:44 PM
XmlLoader.Load(): Unexpected NodeType: None.
at System.Xml.XmlLoader.LoadCurrentNode()
at System.Xml.XmlLoader.LoadDocSequence(XmlDocument parentDoc)
at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
at System.Xml.XmlDocument.Load(XmlReader reader)
at System.Xml.XmlDocument.Load(String filename)
at weather.weather.loadWeather()

Originally Posted by spdyscotty

When I click on the button to dial the internet, centrafuse dials all the way through, but then lags for about a minute or so. Eventually, a dialog box comes up as follows:

Failed to load resources from resource file
Please check your setup

This was happening the other day, so I completely reinstalled windows and everything on my system. I'm now shocked the the problem persists.

Any ideas?

I also had this error with RC5, but dialup works fine straight from windows.

Is it possible that it has something to do with the nexus skin?

Scott

The > COM9 was just related to Destinator GPS, no changes in XM... Does it create an error.log file?

Auto Play would do as you described... You are thinking of Auto Start Music...

Auto Play means if a CD/DVD/USB devices is inserted while Centrafuse is running, no matter how long, it auto plays the device...

david

Originally Posted by midiwall

Yeup, I'm sure - the only possibility would be that some other CF 1.1 module had the port, but I went though them and there's nothing in what CF shows or any of the XML files.

Remember, a) CF _does_ open the port (confirmed by the monitor), it doesn't talk to it. b) If I exit CF and load Hyperterm, I can open the port and see the XM idle message. c) If I exit CF 1.1 and load AIMEE or CF RC5, XM works fine. It's really looking like it's CF 1.1.

Maybe it's related to the work you did on the COM port handler? (there's a reference in the release notes to support for > COM9)


I don't think this is an auto play issue, the H10 was plugged in long before CF was launched.

H10 plugged in, 20+ minutes passed, launched CF, CF browsed the device... etc.

Originally Posted by veetid

The > COM9 was just related to Destinator GPS, no changes in XM... Does it create an error.log file?

Yeup, I included it in the message above.

Auto Play would do as you described... You are thinking of Auto Start Music...

Ahh, my bad... I though you were talking about AutoPlay in Windows. I'll give it a shot.

[QUOTE=midiwall;1025255]Yeup, I included it in the message above.QUOTE]

sorry, I see your post... That is coming back from a Win32 class and saying it could not create the handle.

strange, I did not touch any of the serial or XM code in this release and it's still working on my end...

hopefully after my first updater test we can track down the remaining few XM issues...

david

hey dave,

problem with SMS in the Phone section. No error.log, but what happens is if you check an SMS it's fine but try and click OK to close it and it takes about 5seconds to close the message. On the up side, everything else in phone seems to work fine now.

Also, noticed 2 other things that I think should be looked at.

* It takes a lot longer to load CF when the Phone is enabled. Is there any reason for this and is there a way to make this load faster?
* When you load CF as shell it doesn't detect the bluetooth USB device and phone doesn't work in shell mode. Exit out and wait for explorer to load and then load CF again and it works. I wanted to add that I'm using a dongle with SiW drivers instead of the Widcomm/Broadcomm drivers but I'm not sure if that's the problem.