Suddenly startup takes 30 seconds plus!

[Mastiff]

I installed NetRemote on my new O2 XDA Atom Life, which has a 624 MHz CPU. In the beginning it worked very well, with startup times down from 9-10 and to 5-6 seconds! Loved it. Suddenly it has started to use more than 30 seconds to start. I have tried different CCF's, and that doesn't change a thing. I have disabled auto search for servers and JRMC covers, and just about everything else I can think of, but nothing helps. Does anybody know what this may be?

[tmorten]

That's an odd one... I wonder if it has to do with Girder sending over variable states? That often takes a while in my setup. Not sure why there would be more data now (or why that data would transmit more slowly), but perhaps a new source of interference? Just a thought... probably totally off base :).

[Rob H]

It's possible that there's WiFi interference which would slow down data transmission.

It may also be worth resetting Girder to ensure that there isn't a huge cache of data being transmitted.

[Mastiff]

Problem is this happens even if there's no server on the network at all! I gotta do a bit of testing by removing drivers to see what creates the slowdown, I think.

[mhwlng]

are you sure that your current JRMC playlist is not a few thousand tracks ?

that slows down startup considerably...

Marcel

[Mastiff]

Yeah. Actually I have the same startup time when my PPC isn't connected to the network at all!

[Mastiff]

OK, this is wireless AP connected (or half connected, since it doesn't connect properly - ha-ha!). When I'm connecting to the WiFi in my car (3Com OfficeConnect wireless router), it takes 30 seconds, and it won't be able to connect regularly to MediaBridge (I can get it to connect on the tests in the plug-in properties, but it won't see the instance in a CCF). When I'm connected to the inhouse network (where I have tried with Linksys, SMC and D-Link wireless routers and access points) it takes 4-5 seconds to start on my 624 MHz Atom Life and 10 seconds on my son's K-Jam (TI Omap cr@p - I hate that CPU!). And when I'm not connected to any network at all (with WiFi turned off), the startup time actually seems to vary after what I was connected to the last time!!!! Both on the K-Jam and the Atom Life it will start in the regular time if I had it connected to the inhouse WiFi last, and they will both take 30 seconds+ if they were connected to the carputer network the last time. I would very much like to hear an intelligent explanation for that one! Because I'm far from intelligent enough to understand it...

[tmorten]

Yikes, that's ugly. Is NetRemote the only app to show a difference? Are other network applications able to send/receive data sooner after having used the carputer network? It sounds suspiciously like a WindowsMobile "feature", but it would be interesting to learn what the blocking call in NetRemote is, and whether there's a way to safely time it out sooner to avoid the long startup case.

[Mastiff]

The thing is that I have had earlier versions connected to the carputer without getting that strange effect. As for other network appliances I have no idea since the carputer network isn't connected to anything but the carputer. Except for one thing: Pebbles Remote Commander (sort of like VNC). And that has worked when MediaBridge hasn't. I haven't tried to connect the PDA to the carputer network without firing NetRemote and then firing NR when not connected to anything, I may try that this weekend. I have a few other things I have to do with the carputer anyway.

[tmorten]

Gotcha; that sounds like it must be some difference in the NR start-up sequence then. I wonder how connecting to one network would have an impact on your next connection from a code perspective? From a network perspective, I would have expected that NR just opens some sockets, but there must be more going on there.

[Mastiff]

Seems so. I have taken the carputer with it's wireless network AP into the house, and I'm gonna see tomorrow what I can get out of it.