I've had WM2003, WM2003SE, WM5.0 Smartphone edition, and despite being
an ex-Network Support technician, and a current developer using MS
technologies, including Windows Mobile (in other words, I know a
reasonable amount about PCs, Smartphones, and Pocket PCs), I have
absolutely no idea how all the data connections stuff hangs together in
Windows Mobile. There appears to some kind of conceptual model which
I'm guessing only the phone hardware engineers and one MS person
understands.

While trying to set up GPRS/MMS/WAP, the settings seem to be in several
different screens, some settings seem to be hardcoded ('The Internet'
and 'Work' for example - which I have yet to see an explanation of what
these mean), and some seem to be dependent on other settings without
there being anything in the UI to indicate this - e.g. I believe you
can't do MMS without having a GPRS connection set up. Is that obvious
ANYWHERE in the setup screens? No!

Here's the locations I've found so far which has something to do with
data connections.

Start - Settings - Connections - GPRS (why is MMS, WAP etc set up in a
screen called GPRS?)
Start - Settings - Connections - Proxy (which seems to duplicate most
settings in the GPRS screens, but with additional options such as port
number)
Start - Messaging - MMS - Options - Account options - MMS - Edit - MMSC
Settings - Edit
Start - Internet Explorer - Menu - Options - Connections - Select
network (the options here bear no relation to any connection settings I
have input to the phone
I certainly don't remember this many screens on my Nokia!

I'd really REALLY like to know... Does anyone who isn't a phone
communication stack engineer understand how all these settings tie
together?
If so, can you draw me a nice diagram so the mental model used to
design the UI can be understood by the rest of us.

p.s. I could also have named this post "never let hardware engineers
design UI"

I'd be interested in comments

Hi

Some of this might help although it is really server side but I guess the
location might give you something to start from:

http://msexchangeteam.com/archive/20...03/424028.aspx

--
David @ Solsletta


"Nightdrive" wrote:

> I've had WM2003, WM2003SE, WM5.0 Smartphone edition, and despite being
> an ex-Network Support technician, and a current developer using MS
> technologies, including Windows Mobile (in other words, I know a
> reasonable amount about PCs, Smartphones, and Pocket PCs), I have
> absolutely no idea how all the data connections stuff hangs together in
> Windows Mobile. There appears to some kind of conceptual model which
> I'm guessing only the phone hardware engineers and one MS person
> understands.
>
> While trying to set up GPRS/MMS/WAP, the settings seem to be in several
> different screens, some settings seem to be hardcoded ('The Internet'
> and 'Work' for example - which I have yet to see an explanation of what
> these mean), and some seem to be dependent on other settings without
> there being anything in the UI to indicate this - e.g. I believe you
> can't do MMS without having a GPRS connection set up. Is that obvious
> ANYWHERE in the setup screens? No!
>
> Here's the locations I've found so far which has something to do with
> data connections.
>
> Start - Settings - Connections - GPRS (why is MMS, WAP etc set up in a
> screen called GPRS?)
> Start - Settings - Connections - Proxy (which seems to duplicate most
> settings in the GPRS screens, but with additional options such as port
> number)
> Start - Messaging - MMS - Options - Account options - MMS - Edit - MMSC
> Settings - Edit
> Start - Internet Explorer - Menu - Options - Connections - Select
> network (the options here bear no relation to any connection settings I
> have input to the phone
> I certainly don't remember this many screens on my Nokia!
>
> I'd really REALLY like to know... Does anyone who isn't a phone
> communication stack engineer understand how all these settings tie
> together?
> If so, can you draw me a nice diagram so the mental model used to
> design the UI can be understood by the rest of us.
>
> p.s. I could also have named this post "never let hardware engineers
> design UI"
>
> I'd be interested in comments
>
>