[inferno]

Hello,

I'm attempting to install jmIrc after upgrading to OS ver 4.0.0.198 on my 7100t and i'm getting a message "907 invalid JAR" when i click on "Download" from the installation screen. The link I'm using is http://jmirc.sf.net/jmIrc.jad

I also get the same error message attempting to install the reqwireless Webviewer software.

I'm also have problems with other third party network apps (BBToday and Verichat). BBtoday weather sometimes downloads and sometimes i get an error message (at the moment the error is "Unable to open connection").

Verichat will sometimes connect to all 3 of my IM services (AIM, Yahoo, and MSN), but then shortly after will disconnect from 2 or all of the services.

I'm using a 7100t with the 4.0.0.198 OS and BWC (not a BES subscriber). The signal strength usually fluctuates between -84db and -96db.

I HAVE successfully gotten the "using blackberry device as modem for laptop" thing to work. In fact, that's what I'm using right now, have been connected for about 15 minutes and received 633KB.

Thanks for any advice/help in advance,
Joseph

[sbass]

Sounds like you having the socket issue that many others are having as well. Are you on TMobile? Does this issue go away if you remove/reinsert the battery?

Shawn

[inferno]

Yes, I'm on TMobile, and popping the battery doesn't help.

[lloydg]

I had the same problem with AT&T when trying certain OTA installs (some Magmic games, the free games from mobile.blackberry.com). The "fix" for me was to download the new handheld OS release from AT&T last week, after installing that new OS I was able to OTA download the apps that caused failures before.

I know that doesn't help you with Tmobile unless they happen to have a new OS release, but maybe someone here knows what changed in the OS that helps.

[TheMatrix]

I too am encountering this problem. :/

Is there any other way to get jad/jar files installed?

[TheMatrix]

What's ever going to happen with this problem? I've heard it's affecting quite a few people.

[neutral]

Has there been a solution found to this yet? :o

[jibi]

try installing the cingular (7100g) or rogers (7100r) update (yes, on your 7100t). they're up to 4.0.0.219 now. delete the vendor.xml file before trying to update via app loader.

[TheMatrix]

I just did so, and it still doesn't work.

What a POS - must be a network problem. How many months are us T-Mobile users supposed to wait for such basic features!?

[neutral]

Originally Posted by TheMatrix

I just did so, and it still doesn't work.

What a POS - must be a network problem. How many months are us T-Mobile users supposed to wait for such basic features!?

How is this error message a network problem?

[TheMatrix]

I'm not sure. All I know is it doesn't work with any version of 4.0 so far on my 7100t - and since it appears other people using the same version but on a different network can, I can only conclude it's a problem with T-Mobile and not the 7100.

Either way, it's a basic feature that should work. Even if there's a problem with it, it shouldn't take 3 months to fix it.

I'm just frustrated at how long it takes for such simple things to be done. At the end of November, I, along with everyone else, lost the ability to use TCP. It wasn't until the beginning of March that it started working again. In my opinion 3 months for a multimillion (billion?) dollar corporation to adjust their network settings is unacceptable. Had I refused to pay them $20/mo because they took away some of my functionality, they would have thought themselves "ill used" (to quote Scrooge ;) ) but the otherway around, then "that's life" and I should "just deal with it."

[neutral]

Originally Posted by TheMatrix

I'm not sure. All I know is it doesn't work with any version of 4.0 so far on my 7100t - and since it appears other people using the same version but on a different network can, I can only conclude it's a problem with T-Mobile and not the 7100.

Either way, it's a basic feature that should work. Even if there's a problem with it, it shouldn't take 3 months to fix it.

I'm just frustrated at how long it takes for such simple things to be done. At the end of November, I, along with everyone else, lost the ability to use TCP. It wasn't until the beginning of March that it started working again. In my opinion 3 months for a multimillion (billion?) dollar corporation to adjust their network settings is unacceptable. Had I refused to pay them $20/mo because they took away some of my functionality, they would have thought themselves "ill used" (to quote Scrooge ;) ) but the otherway around, then "that's life" and I should "just deal with it."

I have no problems getting other java files. I'm wandering if it has anything to do with the sizebit indication 0 from their website?

[jibi]

could always just convert the jar/jad to a cod file (method is on this forum - search for midlet) and try to load it using javaloader (method is on this forum - search for javaloader).

[j0nkatz]

I'm having the exact same problems