8 APR 09 - UPD 25: Mods please lock this thread!

[oldman]

Originally Posted by redd214

i have a pretty unique question hopefully someone can help me out and i apoligize for the length of my post...

backstory: the reason i got a winmo phone is because of my work. we used to use palm software for our mobile applications but we just switched to winmo 6.1 to do the same thing

now they just released the new software for us and i have been having a VERRY tough time getting it to work with my ssk 1.5 rom. the help desk couldnt help me so i tried everything, deleting apps, hard resets, etc and still couldnt get it to work. i was using build 21015.

i decided that maybe the build of winmo might have been the problem and guess what, it was so i reflased with the stock build and low and behold it FINALLY worked. i alos tried every other build and the only one that worked was the stock one.

now the question i have is what is so diff. between the build numbers that would cause this?

i am still somewhat of a newb so i hope this isnt a dumb question and hopefully my story makes sense. if anyone could assist me or if you need more details any help would be appreciated cuz the stock build.... well it sux lol. i would much rather use the newer ones.

thanx in advance!!

Before any of the "smart" (not me) guys can help, they need a bunch more of info from you. Is it a Sprint or Verizon Phone? What type of app was it?
Did it require NetCF 3.5, sqeMobile, etc....What type of error messages were you getting? I'm not sure, because I'm just a user, not a hacker but i think that those different versions are newer MS ones that might appear on different phones and the "smart" guys figure out how to make them work with the Sprint or Verizon phones. The ROM you chose 21015 has been reported to have a few quirks that Scott will probably fix when he returns. The ones that have been reported as the most "reliable" are 20764 and 20931. But without more info, nobody can even guess why your app doesn't work.

Bob
Edit: SQL, not SQE.

[redd214]

Originally Posted by oldman

Before any of the "smart" (not me) guys can help, they need a bunch more of info from you. Is it a Sprint or Verizon Phone? What type of app was it?
Did it require NetCF 3.5, sqeMobile, etc....What type of error messages were you getting? I'm not sure, because I'm just a user, not a hacker but i think that those different versions are newer MS ones that might appear on different phones and the "smart" guys figure out how to make them work with the Sprint or Verizon phones. The ROM you chose 21015 has been reported to have a few quirks that Scott will probably fix when he returns. The ones that have been reported as the most "reliable" are 20764 and 20931. But without more info, nobody can even guess why your app doesn't work.

Bob
Edit: SQL, not SQE.

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

forgot sorry, the error message said that the "windows turboapp (name of the application) conduit cannot communicate with your device, please press ok to attempt again"

[impudent1]

Originally Posted by redd214

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

I've read that apps with netcf 2.0 have backward compatability issues. Now I can't seem to find the link since it wasn't what I was looking for before.... go figure. I did run across it with a google search though.

[RONMAC]

Originally Posted by redd214

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

forgot sorry, the error message said that the "windows turboapp (name of the application) conduit cannot communicate with your device, please press ok any attempt again"

Did you go back to the insanely laggy stock ROM? I remember Scott had set up one of his ROMs using the stock build but had cleaned it up significantly.

You might want to reach out to him when he gets back and check to see if the ROM is still around.

Was the Stock build 20764? If so, try the R4R ROM as it is the same build.

Anything to get away from the VZW LAG WARE!!!

[DigitalAttic]

Originally Posted by redd214

its a verizon tp. the app itself wasnt just a regular cab like everything else, it has conduits and could only be installed thru syncing if that makes sense. it actually didnt require netcf 3.5 just 2.0. i know 21015 was kinda quirky but i tried 20764 and 20931 as well and those didnt work either.

forgot sorry, the error message said that the "windows turboapp (name of the application) conduit cannot communicate with your device, please press ok to attempt again"

That's your problem right there: the stock ROM has NCF2 in the base, the custom ROMs do not. If you flash 21015 or better yet 21018, and install NCF2 from MS downloads, then install your app, all will be well in WM World. There's no issue running both NCF35 and NCF2, it is actually recommended and supported, just as it is on your PC. For that matter, same can be said about running different levels of Java.

Edit: This can be verified using the utility Bob posted below. Thanks Bob!

TTFN - DA

[zim2323]

Originally Posted by DigitalAttic

That's your problem right there: the stock ROM has NCF2 in the base, the custom ROMs do not. If you flash 21015 or better yet 21018, and install NCF2 from MS downloads, then install your app, all will be well in WM World. There's no issue running both NCF35 and NCF2, it is actually recommended and supported, just as it is on your PC. For that matter, same can be said about running different levels of Java.

Edit: This can be verified using the utility Bob posted below. Thanks Bob!

TTFN - DA

Why would custom ROM's not have NCF2? My experience so far is that all of Scott's ROM's have NCF2 left in. Why would someone not want that cooked into the ROM?

Thanks!

[zim2323]

What's the difference between the Slide2Answer included(?) in Slide2Unluck vs the S2A that everyone is including in their custom ROM's?

Thanks!

[zim2323]

Originally Posted by zim2323

Why would custom ROM's not have NCF2? My experience so far is that all of Scott's ROM's have NCF2 left in. Why would someone not want that cooked into the ROM?

Thanks!

Back to this question...

Is it better to cook .Net 3.5 in the kitchen or install afterwards?

Also... Is .Net 2.0 default in WM6.1 now?

[oldman]

Originally Posted by zim2323

Back to this question...

Is it better to cook .Net 3.5 in the kitchen or install afterwards?

Also... Is .Net 2.0 default in WM6.1 now?

Net 3.5 is Microsoft's latest version. I think (but not sure) that it's standard in all the latest builds.

The original Verizon TP had 2.0 (they are always a day late and a dollar short). Don't know about the new ones they are selling today....Probably the same.....I think that when they eventually come out with a ROM update, they will put in the Net 3.5. I really haven't heard any rumors or stuff about an upgrade, I'm just assuming that they will eventually see the light and upgrade their ROM.

Bob

[RONMAC]

Originally Posted by oldman

Net 3.5 is Microsoft's latest version. I think (but not sure) that it's standard in all the latest builds.

The original Verizon TP had 2.0 (they are always a day late and a dollar short). Don't know about the new ones they are selling today....Probably the same.....I think that when they eventually come out with a ROM update, they will put in the Net 3.5. I really haven't heard any rumors or stuff about an upgrade, I'm just assuming that they will eventually see the light and upgrade their ROM.

Bob

Maybe thats why we haven't heard from Scott. VZW hired him to create a ROM for the Touch Pro and he is hard at work right now making this the best damn $349 dollars ever spent for a phone!!!