I think those are controlled in an INI file in the simulator. Looks
like someone just forgot to update them :(
On 5/17/07, Douglas Handy <[EMAIL PROTECTED]> wrote:
David,
>Sadly, the 755P Simulator does not match the real device for either the
>companyID or the deviceID. The 755P Sim reports:
David,
>Sadly, the 755P Simulator does not match the real device for either the
>companyID or the deviceID. The 755P Sim reports:
>
>CompanyID: hspr
>DeviceID: D052which is the 700P deviceID...
Its curious that it uses 'hspr' instead of 'Palm', as actual devices have for
some time now s
Sadly, the 755P Simulator does not match the real device for either the
companyID or the deviceID. The 755P Sim reports:
CompanyID: hspr
DeviceID: D052which is the 700P deviceID...
For those who are keeping score at home, the deviceID-independent "Treo
test" I ended up using was:
if
from a real device:
company ID: Palm
Device ID: D060
HAL ID: P052
On 5/16/07, P. Douglas Reeder <[EMAIL PROTECTED]> wrote:
Is the HAL ID 'S052' or 'P052'?
On May 16, 2007, at 4:40 AM, Jan Slodicka wrote:
> Replying to myself as Palm DTS reacted to the same question with
> surprising
>
Is the HAL ID 'S052' or 'P052'?
On May 16, 2007, at 4:40 AM, Jan Slodicka wrote:
> Replying to myself as Palm DTS reacted to the same question with
> surprising
> speed. So, whoever wants to know it, here it is: D060
--
For information on using the ACCESS Developer Forums, or to unsubscribe,
Replying to myself as Palm DTS reacted to the same question with surprising
speed. So, whoever wants to know it, here it is: D060
Jan
- Original Message -
From: "Jan Slodicka" <[EMAIL PROTECTED]>
> Hi
>
> Anybody discovered that already? I just downloaded fresh new 5.4 SDK, but
it
> do
Hi
Anybody discovered that already? I just downloaded fresh new 5.4 SDK, but it
does not mention T755 at all. Some parts were not updated for T680!
With best regards,
Jan Slodicka
Resco, Palm Division
- Original Message -
From: "David Thacker" <[EMAIL PROTECTED]>
>
> And, the T
>> The whole point of this particular exercise was to know when to call the
>> HsGetVersionString API to get the Treo's ROM serial number, because some
>> Treo designer somewhere sometime decided that it would be too easy for
>> developers just to keep it available via the standard SysGetROMToken
On Friday 04 May 2007, David Thacker wrote:
>
> The whole point of this particular exercise was to know when to call the
> HsGetVersionString API to get the Treo's ROM serial number, because some
> Treo designer somewhere sometime decided that it would be too easy for
> developers just to keep it a
"David Thacker" <> wrote in message news:[EMAIL PROTECTED]
>
> I want to detect if the current device is a PalmOS 5.x Treo. I know I can
> check the sysFtrNumOEMDeviceID and compare against known Treos, and that
> is what I have been doing to this point, but I'd rather use a detection
> scheme
"Douglas Handy" <> wrote in message news:[EMAIL PROTECTED]
> David,
>
>>Does anyone have suggestions?
>
> As others have mentioned, some current Treos already don't use 'hspr' for
> the
> company ID. I also use a simple IsTreo() function which I update as new
> devices
> are known.
>
> But what
Neil,
Bummer!
Thanks for the CompanyID tip. I tested on real 600 & 650 devices, but only
tried against the 680 and 700p sims, which do report 'hspr' as the
CompanyID. I should have checked Hal Mueller's list also.
I already do have an IsTreo function that checks the known
sysFtrNumOEMDevice
I usually do both. First, I check for the features I need, regardless
of which device it is. This tells me if it's possible to perform the
task necessary. Second, I'll check the device against a list of
devices I've tested. If I haven't tested the app on that device, I'll
often put up a one-time w
David,
>Does anyone have suggestions?
As others have mentioned, some current Treos already don't use 'hspr' for the
company ID. I also use a simple IsTreo() function which I update as new devices
are known.
But what arguably is a better idea is to check for the existance of the
feature(s) you c
Not all treos use sysFtrNumOEMCompanyID == 'hspr'
device sysFtrNumOEMCompanyID / sysFtrNumOEMDeviceID
600 'hspr'/'H101'
650 'hspr'/'H102'
680 'Palm'/'D053'
700p'Palm'/'D052'
There is no simple way of future proofing your code. We have a simple
IsTreo function that is used throu
On May 4, 2007, at 11:23 AM, David Thacker wrote:
I was thinking that since all of the existing Treos use the
sysFtrNumOEMCompanyID of 'hspr' (Handspring), that I could just
check for
that CompanyID and a PalmOS version of 5.0+, and that would
indicate a Treo.
However, I'm not sure future
Hi all,
I want to detect if the current device is a PalmOS 5.x Treo. I know I can
check the sysFtrNumOEMDeviceID and compare against known Treos, and that is
what I have been doing to this point, but I'd rather use a detection scheme
that can detect both current and future PalmOS Treos. I don
17 matches
Mail list logo
