Citrite Two-Six-Niner-Niner
Monday, September 18, 2006
Gregarius » A Free, Web-based Feed Aggregator
Web based feed aggregator. Kind of cool. I wonder if I could keep up with feeds better this way...
Gregarius » A Free, Web-based Feed Aggregator: "Gregarius is a web-based RSS/RDF/ATOM feed aggregator, designed to run on your web server, allowing you to access your news sources from wherever you want." ¶ 7:09 PM
Gregarius » A Free, Web-based Feed Aggregator: "Gregarius is a web-based RSS/RDF/ATOM feed aggregator, designed to run on your web server, allowing you to access your news sources from wherever you want." ¶ 7:09 PM
Dave Gallinson » Blog Archive » Citrix and Microsoft
A great blog about looking at what OS SP to go with.
Dave Gallinson » Blog Archive » Citrix and Microsoft: "In a previous log I wrote “In Citrix Technical Support …we have issues like Connectivity, Application Compatibility, Product Integration and Microsoft deleting a Citrix Enhancement with a new SP. ” The real case scenario where content redirection was disabled after applying R2 to Windows 2003 sparked this reactive article - CTX109680 - and had us in Tech Support having to declare “Win2k3 R2 is a supported Citrix configuration.” The link to ”Microsoft Windows Server 2003 R2 Known Issues” – has run repeatedly in Tech Times." ¶ 6:50 PM
Dave Gallinson » Blog Archive » Citrix and Microsoft: "In a previous log I wrote “In Citrix Technical Support …we have issues like Connectivity, Application Compatibility, Product Integration and Microsoft deleting a Citrix Enhancement with a new SP. ” The real case scenario where content redirection was disabled after applying R2 to Windows 2003 sparked this reactive article - CTX109680 - and had us in Tech Support having to declare “Win2k3 R2 is a supported Citrix configuration.” The link to ”Microsoft Windows Server 2003 R2 Known Issues” – has run repeatedly in Tech Times." ¶ 6:50 PM
Sunday, September 17, 2006
How to decide which ICA Client to install on a Pocket PC
Here is a problem I have been doing a great job avoiding for the last couple of years. If you have a Pocket PC and you are going to install the ICA client, the easiest way to install it is to select the "All Processors" option at Citrix. But I don't want to do that anymore. Whether you want to save space or just make the download more efficient, let's take a look at how to determine what processor download to use.
The first step is to find out what the processor is. I guess that sounds pretty dumb, but what do we really know? If you go to Start > Settings > About there should be some hardware information.
For my Sprint 6700 it looks like this:
Processor: PXA270-416MHz
Memory: 49.23 MB
Expansion Slot: In Use
We really don't care about the Memory or expansion slot, unless we want to play with the installation location. But for the most part we now need to find out if this processor is ARM or not. I myself did a Google Search on the processor type and processor. What I got in this case that my processor was an XScaleTM PXA270 416MHz. Putting this into Google got me to this link at WikiPedia. Scrolling down the list of Intel XScale processors I found the 27x and verified that this indeed was my processor. They also point out that all generations are ARM processors so now I am all set.
Back to Citrix Downloads and the client for the ARM.
The scary part here is that the page says "The processor type of a Windows CE device is usually displayed in the About screen of the System control panel. You access this from the Settings entry on the Start Menu, though devices vary in this arrangement. Note that the distinction between ARM and ARM4I is rarely clear: a device which identifies itself as ARM or SA-number is usually ARM, but a device which identifies itself as a variation of ARM-XSCALE may be either ARM or ARM4I."
So I guess it is time to test.
I installed the ARM client and it worked.
If it didn't I would have tried the ARM4I. Here are a few interesting points.
1. Generically is there an easy way to identify the client for a specific handheld device?
No.
2. Can we figure out which one is installed on a given device? For example in the "About" on my Sprint PPC-6700 cell phone the ICA client is listed as 8.46.38624 does this indicate anything about which processor version I am using?
No.
3. It sure is confusing to try to figure out if my device uses a ARM or ARM4I processor. I don't want to use the 17MB all processor install; will the 2 ARM version clients hurt my device?
No. The PocketPC .exe download contains just the ARM and ARMv4i clients. It will not hurt; it will just install the appropriate client (ARM or ARMv4I).
4. Is there a way to know what client to install once I install the “All client versions” one?
The version number doesn’t give any clue to the CPU type.
5. I was under the impression that when I used the multi client install, it only installs the necessary package and then one can delete the 3mb file with all of the clients. So as long as you have the memory temporarily to install, deleting the file later is OK.
Yes the device will only download (for .exe install) or keep (for .cab install) the correct files, so it doesn’t waste space on the device.
6. Does it matter which ARM .exe client I use?
No. Both of the .exe's have both the ARM and the ARM4I client. (Wow! Those ICA client guys at Citrix are really smart!) Regardless of what exe you use, the process detects which processor you have and installs the right client. Relatively small download to the PC you are using for the Sync, and then only the right client gets installed, No Worries!
Here are the two clients: (as of 2006-09-17)
ARM
ARM4I
7. Does it matter which cab file I use.
Yes! The cab file goes to the PocketPC directly. You actually need to know the processor type to use the cab files.
So goes my adventure with the PocketPC ICA client.
Here is the summary of my findings.
When installing the ica client on a WinCE/ PocketPC device look at the following options:
1. The easiest way is the all processors option. The file size is larger, approx 17MB but that only applies to the initial download on the synchronizing PC. The actual client files are much smaller. Only the couple of MB that you need for ICA functionality have to be installed.
2. If you know you don't need x86 architecture processor support, then the next easier method is to choose either of the ARM or ARM4I/ ARMv4I .exe files. Both of the exe files listed on the Citrix Client download site contain both of the ARM client versions. So when you execute the exe for the ARM clients the appropriate version of ARM is installed. So, if you have a PocketPC then just execute the exe on the synchronizing PC and the right client gets installed.
3. The hardest method is to directly install one of the ARM cabs to the PocketPC. If it doesn't work then you install the other one. The only good part about this is that if you really wanted to find out what client cab you needed and what processor type was in your particular PocketPC device then this method would tell you. ¶ 5:29 PM
The first step is to find out what the processor is. I guess that sounds pretty dumb, but what do we really know? If you go to Start > Settings > About there should be some hardware information.
For my Sprint 6700 it looks like this:
Processor: PXA270-416MHz
Memory: 49.23 MB
Expansion Slot: In Use
We really don't care about the Memory or expansion slot, unless we want to play with the installation location. But for the most part we now need to find out if this processor is ARM or not. I myself did a Google Search on the processor type and processor. What I got in this case that my processor was an XScaleTM PXA270 416MHz. Putting this into Google got me to this link at WikiPedia. Scrolling down the list of Intel XScale processors I found the 27x and verified that this indeed was my processor. They also point out that all generations are ARM processors so now I am all set.
Back to Citrix Downloads and the client for the ARM.
The scary part here is that the page says "The processor type of a Windows CE device is usually displayed in the About screen of the System control panel. You access this from the Settings entry on the Start Menu, though devices vary in this arrangement. Note that the distinction between ARM and ARM4I is rarely clear: a device which identifies itself as ARM or SA-number is usually ARM, but a device which identifies itself as a variation of ARM-XSCALE may be either ARM or ARM4I."
So I guess it is time to test.
I installed the ARM client and it worked.
If it didn't I would have tried the ARM4I. Here are a few interesting points.
1. Generically is there an easy way to identify the client for a specific handheld device?
No.
2. Can we figure out which one is installed on a given device? For example in the "About" on my Sprint PPC-6700 cell phone the ICA client is listed as 8.46.38624 does this indicate anything about which processor version I am using?
No.
3. It sure is confusing to try to figure out if my device uses a ARM or ARM4I processor. I don't want to use the 17MB all processor install; will the 2 ARM version clients hurt my device?
No. The PocketPC .exe download contains just the ARM and ARMv4i clients. It will not hurt; it will just install the appropriate client (ARM or ARMv4I).
4. Is there a way to know what client to install once I install the “All client versions” one?
The version number doesn’t give any clue to the CPU type.
5. I was under the impression that when I used the multi client install, it only installs the necessary package and then one can delete the 3mb file with all of the clients. So as long as you have the memory temporarily to install, deleting the file later is OK.
Yes the device will only download (for .exe install) or keep (for .cab install) the correct files, so it doesn’t waste space on the device.
6. Does it matter which ARM .exe client I use?
No. Both of the .exe's have both the ARM and the ARM4I client. (Wow! Those ICA client guys at Citrix are really smart!) Regardless of what exe you use, the process detects which processor you have and installs the right client. Relatively small download to the PC you are using for the Sync, and then only the right client gets installed, No Worries!
Here are the two clients: (as of 2006-09-17)
ARM
ARM4I
7. Does it matter which cab file I use.
Yes! The cab file goes to the PocketPC directly. You actually need to know the processor type to use the cab files.
So goes my adventure with the PocketPC ICA client.
Here is the summary of my findings.
When installing the ica client on a WinCE/ PocketPC device look at the following options:
1. The easiest way is the all processors option. The file size is larger, approx 17MB but that only applies to the initial download on the synchronizing PC. The actual client files are much smaller. Only the couple of MB that you need for ICA functionality have to be installed.
2. If you know you don't need x86 architecture processor support, then the next easier method is to choose either of the ARM or ARM4I/ ARMv4I .exe files. Both of the exe files listed on the Citrix Client download site contain both of the ARM client versions. So when you execute the exe for the ARM clients the appropriate version of ARM is installed. So, if you have a PocketPC then just execute the exe on the synchronizing PC and the right client gets installed.
3. The hardest method is to directly install one of the ARM cabs to the PocketPC. If it doesn't work then you install the other one. The only good part about this is that if you really wanted to find out what client cab you needed and what processor type was in your particular PocketPC device then this method would tell you. ¶ 5:29 PM
