Note also, that while there are a number of
different
manufacturers of PocketPC devices (HP, Compaq, Casio, Toshiba, Dell,
etc)
the questions are almost 100% identical for all of the devices because
the PocketPC operating system is the same on all of them.
Soft Resetting your device will cure a high
percentage of user problems. Frequent soft resets such as
everytime you remove the device from the cradle or charger will prevent
many problems.
See your device manual to learn how to soft
reset your device. It is normally accomplished by inserting the
stylus or paper clip in a small hole marked "RESET" Do not
confuse a soft reset with a "hard reset" which can delete everything on
your device.
The web interface replacement is Microsoft NewsGroup "web interface" My experience with it is that I am too dumb to use it and I note today that the most recent post in the web forum replacement for the pocketpc nntp newsgroup is over a month old.
The above will uncover a number of other help/tip/chat/news/forum sites... fwiw, my personal favorite is Pocket PC Thoughts which is so fast and dynamic that it must be accessed and read on a daily basis or the articles will scroll off the front page into the archives before you return.
Historically, I have not posted any individual's PocketPC support pages for several reasons. First, I'm too damm lazy and incompetent to find the links and retain them long enough to get pack to the page editor and remember what they relate to.
Second, I've had some nasty experiences with links that changed hands and presented visitors to my page with very unpleasant content when they clicked on links with totally different expectations than what happened after they clicked.
Additionally, the links above are not only sufficient starting points to get to the most current content, the are normally up to date and added to as new info sites surface.
Finally, I have just returned from my first Microsoft "MVP Summit" and have established thirty something new friends that I don't want to hurt their feelings by not including their excellent sites as reference sources on this and other pages.
The exception that I make is for Chris
DeHerra's
site at www.pocketpcfaq.com
(formerly WindowsCE.net) that seemed to be
the standard technical reference site for all of the Mobile MVP's,
The original release in 2000 of the PPC operating system was officially known as WinCE ver 3.0, but that got complicated when an updated version was released just before 2002. It was also based on WinCE 3.x but was oficially referred to as "2002" so PPC3 became "2000"
Then came "Windows Mobile 2003" It's still based on WinCE but the kernel version toggled to 4.x with this release.
As of this writing, all PPC operating systems are based on the WinCE
kernels 3.x and 4.x, but there are very different, "flavors" that are
referred
to as "2000" "2002" "2003" and "2003SE"
I've been asked many times to give the reasons for choosing a PocketPC
over a Palm OS device, and the best descriptive answer that I can offer
is while it is absolutely amazing what a Palm OS device can do with the
limited resources that has, one has to understand that the PocketPC is
so close to a full Windows operating system, you have to be careful not
to focus on what it can't do.
The abbreviation "PPC" used here refers to the specific CE devices known as these "Pocket PC's" The term "PPC" also has an unfortunate history as it has used in the Mac world to refer to an Apple device and has led to some confusion when referring to it among other groups.
Similar to the "Palm Pilot concept," The CE operating system and CE devices are expressly designed to compliment an individual's work on a full desk or laptop Windows machine by making a subset of data and applications fit into an ultra portable device.
While I originally felt that PPC's were "supplimental" devices to their user's desk or laptop PC's, I have evolved over several years to the point where the device is now more important than my desktop, and I have been able to rely on it as a stand alone computing system.
That said, I would still strongly urge any new owner to approach the devices as devices that will suppliment and compliment their desktop machines to make the learning process as easy as possible.
While there used to be several different processors for the PPC 2000 operating system, SH3, MIPS, Intel and ARM, the PPC 2002 operating system reduced that list to only the ARM processor.
It was not long before the XSCALE processor slipped in and now more new processors are showing up, but, the good news is that they will run all apps compiled for the ARM processor.
With the advent of 2003 the PPC OS is designed to be a ".NET" platform and Microsoft is headed in the direction of PPC devices that will only run programs written for that platform.
In General all programs written for the PocketPC since 2000 will run on 2003, but you may have to download and install the PPC Visual Basic Runtime.
Programs written for the .NET environment will not run on earlier versions although there is a PPC .NET runtime environment that will allow 2002 devices to run some of these apps.
While we tend to think of "sending and receiving email" as the same process, they are, in fact, two independant processes and normally use two unrelated servers.
POP3 (the receiving side) is normally a server that remains open to the entire internet with no access restrictions other than needing a user id and password to access your messages.
SMTP is the sending server, and it doesn't know or care about how you receive your email, it just re-sends any and all messages you send to it. Very early on in the internet, "Spammers" abused this possibility and used any SMTP servers they could find to transmit their junk to the world. As a result, standard behaviour for almost all SMTP servers is to refuse to send any email that is not handed to it from an internet connection related to the ISP service which owns the server.
OK, so how does this info help you? At home, your PC is normally connected to the internet service that provides your email service, so the SMTP server is happy to send whatever you hand it. However, sitting at your local Starbucks and showing off your WiFispertise, when you ask your home SMTP server to send an email for you, it's response is that the connection you are using is bogus and it refuses.
The solution is to find the SMTP server address for each method that you use to connect and set up additional Inbox services that use the same POP3 service to receive email, but a connection specific SMTP server to send, so you might end up with HomeWifi, CellConnect, and StarBucks services to cover your bases. To find each address for these servers, you will need to search the web pages for these providers or call their tech support lines.
The first is to allow your current SMTP connection while you are connected and picking up your email... fine, except that most people, connect, get mail and disconnect, then reconnect to send responses, hence, sending fails again. Solution, use the "connect" button rather than the "send/receive" button to stay connected after you download... watch your connect costs though.
The next is "authentication" The theory is fine and it works if your id/password is the same for both servers... if not, sorry, you are left sol.
Some of the Web Mail interfaces are complex and some use Java which might prevent this... if so, check with your provider and ask if they have a PDA or CellPhone compatable mail page.
Tap start/settings/input/options and check the sound format that will be used for your notes... the PCM 8000mhz mono is a common format that can be played on most computers, but if you are a music creator, you may want to set a higher quality or different format for your needs. The important point is to create the recordings in a format that will be accessable when the .wav file is transfered to other machines... for example, the default format for the Jornadas is "HP Dynamic Voice" that will not play on most PC's unless a special codec plugin is downloaded from HP's site and installed on the PC.
While the hardware "record" button normally generates WAV files, there are two "gotcha's" to be aware of. If you "sync" to Outlook "Notes" these wav files will end up as Outlook PIM data on your PC rather than separate, accessable WAV files.
An important point to note is that even though these separate files "sync" as Outlook data and are not accessable as sound files, you can still copy the files directly to the PC or CF card and they retain their .WAV file status and become accessable to any program that can play a sound files in WAV format.
Know, however, if you are "in" a PocketPC document that supports sound objects such as a Notes or Word document, the recording that will be created will become an embedded "sound" object within the document you may not be able to converted it to a WAV file.
Despite the postings of others, I have, to date, never been able to open a notes sound recording (.pwi file) in anything other than outlook, and attempts to copy the sound object within oulook and paste it elswhere have all resulted in some type of disaster such as an 'out of memory,' app freeze or system lockup, so that solution will work for some but seems to fail for the majority... assume that the newer the system and versions of all software apps involved will eventually lead to a workable situation.
Some programs do create separate wav files, but you have to pay attention to each app's rules. One example is the HP Camera app. It will only create sound files when it's "recorder" icon is tapped, and they are stored as .wav files with the same name as the current image. The "confuser" is that if you press the hardware "record" button when in the Camera App, a recording will be made but by the Notes app according to the rules set there, totally unrealated to the current image on display.
Unfortunatly, afaik, there is no "standard" way to convert an embedded sound object in a ppc file to an external file such as a wav file. In the case of embedded sound "objects" you could find yourself "stuck" trying to access an important sound clip.
You can, however, copy thesed sound "object" and paste them other apps (i.e. word, notes) and this is important information since, if the recording will not transfer within a synced Pocket Word file and play on your PC, remember that you can copy the sound object into a Notes file where it will play on the PC from within Outlook.
If it is an important sound clip, there are two options to get it into an accessable audio file format. The first is to get an audio cable and connect your PPC's headset jack to your PC's "line in" jack on your pc and start C:\WINDOWS\SNDREC32.EXE and record the PPC's output when the clip is played.
There is also a program named "Total Recorder" that will capture the file directly from the PC's sound card when it is played... for example, open the note in Outlook, start Total Recorder with source to "Stereo Out" record, switch to Outlook, click the sound object and when finished, click stop in total recorder and save the clip as a WAV file.
For the techies out there, the embedded object in a notes.pwi file
is
actually a complete .wav file. If you go in with a HEX editor,
you
can find the wav file header information and copy from that point to
the
end of the sound binary code (fairly easy to spot) then create a new
file
from that clip with a .wav file extension and it will play as a normal
wav file. The same is not true for sound objects embedded in
other
file types such as pWord... it is my guess that in these cases, the wav
file is in the PIM database.
The confusing issue with PIE tags was that they do work sometimes, but because they often don't, many think that they don't work at all. It was really confusing to know that the tags on this page and others here work without any problem when this page is accessed over the web using a PocketPC, but the exact same html file would not work properly when it was accessed on the storage card where the source lives.
When yet another request was posted on the MS pocketpc forum by a user who needed the tags to access his html bible which used anchors to cross reference and find needed passages, the fact that it could work bugged me to take another look at the issue and run some experiments which finally yielded success... and uncovered another result of MS's attempt to force a "simplified" operating system on all users.
The key turned out to be the <space> character. Since most users try to store as much "stuff" as possible on their "Storage<space>Card" the trap is set.
When you access an html page on any storage device, and tap on a link to any point within that page (or any other page's tag) PIE apparently resolves the entire address to get to the tag... "file://\Storage Card\source\bhhpj.htm#ATAG" ...and chokes on that space in the card's address.
If I took the same file and move it to main memory at a location where the "path" contains no <space> such as... "file://\source\bhhpj.htm#ATAG" ...the anchor tags that failed when accessed on the storage card work.
So... the first "work around" is to move html pages with anchor tags
into main memory if space is available... and don't put them in the
"My<space>Documents"
folder ;-) In other words create a main memory storage location
that
uses short (8.3) filename paths.
Not only that, hard coding a full file path into an html file totally defeats the beauty of using relative addresses. One final thought is that one might use the current filename plus the tag... but one shouldn't have to.
Next, there is a registry patch that allows you to change the "official" name of the storage card from "Storage Card" to any string that you wish. To accomplish this, use a registry editor to find the key;
HKEY_LOCAL_MACHINE\Drivers\PCMCIA\ATADisk
Add a new "string" value (not a new key) to this key.
Name the new value "Folder"
Assign it any name that does not contain a <space> I strongly recommend the string "CF" since it is short and easy to type on a PPC, plus the "C" brings it to the top of a directory listing in File Explorer.
Perform a soft reset. Following the soft reset, html files stored on the CF card containing anchor tags should function normally. If they do not, check the path to the file and see if it contains any spaces... for example, is the file in or below the "My<space>Documents" folder.
The following is the entire contents of a registry (.REG) file that can be "imported" into the PPC's registry using most registry editors... simply paste it into a "text only" file with the extension .REG and copy it to a location where the PPC registry editor can find it.
REGEDIT4
[HKEY_LOCAL_MACHINE\Drivers\PCMCIA\ATADisk]
"Folder"="CF"
"FSD"="FATFS.DLL"
"Ioctl"=dword:00000004
"Prefix"="DSK"
"Dll"="ATADISK.DLL"
There is a similar key named;
HKEY_LOCAL_MACHINE\Drivers\SD\Detect\99
Although on the Axim the "SD" slot registry pointer is;
HKEY_LOCAL_MACHINE\Drivers\MMCDisk
The Axim tried to address at least part of this issue by renaming these cards with the simpler names "CF Card" and "SD Card" but these changes threw their own monkey wrenches into the mix by preventing Word and Notes from saving files to external memory.
Please Note!!! There is a very good chance that there are programs or processes that have the string "Storage Card" hard coded and will fail with this solution in place. I have not found any yet, and embedded processes such as Word and Excel have no problems finding and displaying files on the storage card with this patch in place so the cavaet "Use this Solution at Your Own Risk" applies. To revert to the default string of "Storage Card", use your registry editor to delete the value "Folder" in the key(s) and perform a soft reset.
I now have a copy of this file that allows me to easily update a registry that has been restored to default values by a hard reset. More accurately, I maintain a personal preferences registry file that contains all of the fixes, duns, patches and personal configuration settings that allows me to restore any PPC to my needs a few seconds after I install a registry editor.
Feedback on this and similar discoveries would be appreciated.
First, Adobe's whole design concept of pdf is to prevent any
document manipulation by the end user, so you may have three strikes
against you and your pocketpc before you begin.
First the installation... acrobat PPC reader is one of the few
PocketPC applications which needs to be installed on the PPC using
Activesync rather than installing from a CAB file. The reason for
this is that the installation process on the Sync PC also installs an
Activesync plugin which will attempt to add accessibility tags to any
pdf files which are syned from the PC to the PPC.
You can, however, obtain the cab files by extracting them from the
Activesync installation process. The trick is to run the install
without having the PPC connected, then go find the CAB files which were
extracted from the installation exe... unlike most ppc apps, you will
find them in a directory under the adobe name rather than the
Activesync folder.
The following assumes;
<Tap-Hold> the main screen in Acrobat. If you can select
"reflow" you should be good to go. Once
selected (it can be set as the default) you can zoom the text to an
easily readable size and it should then wrap to fit in the available
screen size.
If not, the document either does not have "accessibility tags" _or_ what you are reading is not actually text, but an "image" of text... for example, scanned test or a pdf of a faxed document.
If the pdf consists of ascii text, it may be possible to add
accessibility tags, but if the document is a scanned image of text,
there is no way to redisplay the text so it wraps or flows into the
available screen.
The sync process on the pc which was used
to install ppc reader will _attempt_ to
add tags to any pdf files which are synced to your device. PPC
Acrobat reader is one of the few files which must be
installed using activesync as the installation process also installs a
primitive "tagger" into the sync process.
You may be able to use "full ($$$)" acrobat to try
to add tags to a
document
using advanced/accessibility/makeaccessible
but this depends on the
level of
document protection and will fail if there happen to be any tags
anywhere in the document... for example, the author may have used tags
one in a table or text box in a large document which will prevent any
additional tags from being added.
Options with respect to "tagging"
While the async tagging operation output only goes to the ppc's main
memory, once synced, that tagged file in the ppc's main memory can then
be copied to the storage card. I also recommend copying (not syncing)
this tagged file back to the pc as the original file on the pc remains
untagged.
For those with serious pdf ppc access needs, consider purchasing a copy
of full acrobat as that is not only the easiest way to get tags into
untagged files, afaik, it is the only app other than the activesync
plugin which can do this job.
It does not have to be the latest version of acrobat... any version of
full acrobat from 5 up will do this job... I've been using the
"standard" version 6 for several years.
Again!!! ...many files can't be tagged by any means due to their
structure or protection levels.
Acrobat Reader on WM5, WM6
Adobe PPC reader should install and work on any of the Windows Mobile
os versions... I have sucessfully installed acrobat reader on _all_ ppc
os' from the original PPC3 (WM2000) to WM5 and know others who have it
running on WM6. This software will only run on PocketPC (PPC) devices
with or without phone but _will not_ run on any of the "Smartphone No
Stylus" devices.
There are a raft of reported install problems with all of the os' but,
they should be surmountable.
Bottom Acrobat Line
If the pdf has the design elements and tags necessary
to make it easily
accessible using a pocketpc, adobe's reader turns out to be one of the
best document viewers available dispite it's huge (6mb+) size. In
addition to offering fast searches, rotation, zooming, image support,
contents, the user interface and controls work well, but it's up to the
document generator to produce an easily readable file, since, if it's
not, it's difficult if not impossible to convert them after they have
been generated.
To see if the manuals you want to read on the ppc are tagged, open
them on your desktop and select FILE/DOCUMENTPROPERTIES and look for
"tagged"
To see what they will look like on your PPC, open acrobat on the PC,
then resize the document window so it's about the size of your PPC
screen, then select VIEW/REFLOW.
Note that while Acrobat 7 can now "reflow" documents which don't have
tags, the PPC reader requires the document be tagged to reflow.
Well... Windows Mobile 5 has highlighted Microsoft's schizophrenia with respect to the company's long standing battle to force all users to maintain all of their files in or under that infamous "My Documents" folder.
In all of the OS version prior to WM5, the os demanded that folder named "My Documents" must exist on the Storage Card's root directory for pocketpc "compliant" apps such as pocket word and excel to to be able to see their file types stored on the card. With the advent of PPC 2002, if you inserted a memory card in the device which did not contain a root folder named "My Documents" the os would place a "hidden" flag file named "ignore_my_docs" on the card's root which would prompt the os to only look at the card root.
With WM5, the os is oblivious to the existance of a My Documents folder on any memory card. (more on coping with WM5 specifically below)
Additionally, if the card contained many root folders or any of those folders contained a lot of files, the file displays in compliant apps' file menuss became so crowded and unusable.
On the comment that wm5 operated like older devices which had the "ignore_my_docs" flag file, I finally sat down and started rearranging my primary card's folder structure;
By removing the "My Documents" folder, when the card(s) were re-inserted into ppc's running 2002 and 2003 os' the older os's responded by generating the "ignore_my_docs" flag file, so, rather than trying to get wm5 to operate like other ppc os's with respect to the memory card, the only workable solution I have found is to get the older devices to act like wm5 by rearranging memory card files as above.
Another benefit of creating the folder(s) on the desktop or laptop machine is that when browsing the storage card in a card reader or pcmcia slot with Explorer, access to the folder's files is significantly faster.
Also, if there is any possibility of needing to access files created by the PPC on any device or computer that uses FAT16, stay in the habit of naming the files... or at least the folders with the old 8.3 format rules.
Here are a few personal favorites;
Ephemeris StopTime |
vxHPC vxIPConfig vxSniffer |
PocketPCTweak |
CabInstal Unit |
regedit & others |
(buy MS Streets & Trips at Sams or the Like) VoiceCommand |
|
|
I also carry a number of other app cab files on my storage card to meet seldom used or unexpected needs as they come up.
I say normally because, on a hunch, I "opened" one of the CE installation EXE files with Winzip and found that it contained a variety of CAB files whose extensions indicated the processor type. I was then able to unpack the appropriate CAB file, copy it to a Compact Flash card, and by clicking on the file using the CE Explorer, the install was initiated.
Some setup programs can't be opened using WinZip, so the installation process must be run on the PC. However, if you run the install process with the PocktPC disconnected from the PC, the setup program will extract the cab files and store them on the PC to wait for the next "sync." After the install process is finished, hunt them down by doing a "Find File" and they can be copied directly to the PPC for a stand alone install.
Note... virtually all "CABS" self delete themselves at the end of the install process. While this saves space, if you need to reinstall or install on a different machine, it's nice to prevent this deletion and it's easy... simply mark the cab file "read only"
I maintain a "Cabs" directory on my CF card, actually one for each processor type, where I copy the appropriate cab files, then mark them "read only" This allows you to keep seldom used apps with the PPC ready for installation when needed, but I find that this ability is more often used when helping someone with their new PPC... insert card, tap needed app's cab using file explorer, wait about 10 seconds for install to complete, remove card... that simple.
Next, there are several "Cab Installation" apps that allow you to both install Cabs directly, but also control where the install will take place plus nicities such as allowing the user to determine if the cab should be deleted by default after each installation. I have been using CabInstal for a couple of years and now prefer it to the above manual process. It can be "associated" with the .CAB file extension, but I find it more flexible to copy the executable to the "Cabs" directory on a storage card so that when installing an app for a client or populating a new device, it can be done without needing the file association to be registered.
Running MSDos on a CE
machine...
My recommendation is PocketDos,
and on the PPC, it works best "rotated left" This is the "pricy"
software at $40, but for this fossil who still uses and relies on Dos,
well worth it.
It's a full package, with the ability to run any dos program that does not require extended memory including the ability to access the com ports which makes it fully usable as a terminal. The interface allows quick and easy zooming and scrolling as well as a full keyboard including all cursor and function keys.
The FAT16 gotcha is at play here as well. The "My Documents" folder and any long filenames will be invisible to dos. PocketDos complicates the issue by being unable to see any long filename no matter where it was generated. In other words, you can "CD \MYDOCU~1" but the command "DIR \MYDOCU~1" will return a "file not found" result.
The solution is to get a third party tool that does file searches... My recommendation would be Kilmist File Quest that also allows string searches within files. The RESCO file explorer also allows file searches.
There is another double gotcha as well. One of "Find's" jobs is to hunt down large files when you run low on memory. First, it still only checks the My Doc... folders, and if you forget to blank the search string left from your last find...
PocketDos offers the option of quickly finding files using the old Dos DIR <filename> /S command. There are, however a couple tips and a gotcha.
The tip is to know how PocketDos deals with drive assignments and what the current assignment is. The problem is that the default assignments change depending on the presence of a compact flash card. Type SETDRIVE at the dos prompt to find out what the current setup is.
The "gotcha" is that damm "My Documents" issue. Doesn't exist as far as Dos can tell since it doesn't have the dual FAT directory entries. Back to the PocketDos SETDRIVE command to map that directory to a drive letter.
Bottom line... a DIR /S will not find any file
that has not been named with the 8.3 naming convention, and will not
find
any 8.3 filename that resides in, or below, any folder that has a long
filename.
Looking at network cards? Two tips. Get an NE2000 compatable card. The drivers in CE are native and the card will work as you upgrade. In addition, get a Compact Flash Type I format to assure that it is going to fit in the maximum number of devices.
Need another justification for a PocketPC network card? You can use it to sync if your PC is networked... fast, very fast.
Frames are a pain because you can't navigate, see or even scroll in some frames to the right, but another undocumented trick is to tap and drag unwanted frame borders and effectively slam unwanted frames closed. If there are multiple frames (top, left and bottom) the sequence of closing them may result in previously closed frames re-opening, but once you learn, it works.
The best reference tht I have found on understanding how the PPC IE access is going to function is found on Microsoft's site at http://www.microsoft.com/mobile/developer/technicalarticles/pie_dev.asp
While the vast majority of web sites are accessable using a PPC with either a modem, network or wireless connection, the small screen together with the speed limits of modems will drive you battty. For some approaches that will allow you to make valuable information sites fast and easy to access with a PPC, take a look at Some Fast Loading PPC Compatible Links
One anomoly... if you "Tap" on an image file, or HTML file for that matter, IExplorer will run it without issue. If you attempt to reference the same file from IE's address line, it will report that it can't find it unless you are extremely careful about the exact URL line syntax. Tap one to load, then copy and study the syntax.
The file on the Jornada PPC is \WINDOWS\HPSTART.BMP which is a 240x320x4bit BMP file... which resides in ROM although \WINDOWS contains RAM files.
The trick is to connect the PPC to the desktop and copy the replacment file over the existing file using Windows Explorer (remember you have to be able to see system files to do this) If you get tired of your replacement, delete it and the ROM file will take over.
Final note... Even though the screen is 240x320, make the image you want to use 240x300 as the bottom 20 pixel lines will not display due to the blue startup bar that takes up the top 20 screen lines.
Well... the "X" re-appeared when PPC 2002 was released but it took less than a few hours after the first machines shipped to learn that tapping that new "X" didn't close the app but left it running along with all of the memory that it demanded when the program was visible.
There is an easy solution, and that is tapping <Ctrl-Q> using the "soft keyboard" This command will close any app that allows you access to the keypad... even MSReader... hint, "find" something.
The Jornada comes with the limited ability to transfer your card or multiple "contacts" to any Palm device with an IR port and you can buy an upgraded version that will allow you to beam files back an forth.
What's surprising is that the only way you can take any IR action with a Windows laptop or other machine with an IRDA port is with the ActiveSync software. While all Win98 machines have IR file transfers built into Explorer, it's not possible to utilize the direct file transfers either way between a CE device and a Windows machine.
Nor is IR printing a default option. JetSend is packaged with the Jornada, but I have heard mixed reports on it's usability.
File transfers from within CE Explorer are built in and the use is fairly easy to understand.
Highlight the file or files (You can tap/drag or <ctrl-tap> to select multiple files) Tap and Hold, then select "send via Infrared"
On the other (receiving) CE device
If it's a Pocket PC, select IR receive from the START/PROGRAMS menu.
If it is a CE 2.x device, there should be a "Receive" option in the
File menu of CE Explorer
Back to the infamous "My Directory" issue, unlike CE 2.11, the Pocket PC "receive" function appears to place all received files in this central directory with no other destination options while the "old fashioned" CE 2.1 will put the received file in the currently selected directory.
However, on the PockePC platform, files, or series of files transfer easily from within the default apps such as Word and Excel. You can either send the file you are in or by tap/hold from the file menu or if you are editing a file, it can be transmitted while editing it. From the application file menu, you also have the option of receiving a file.
This ability alone has amazing potential, but would have even greater potential if you could send or receive a document to someone with a laptop instead of a PDA.
The maximum ir range appears to be about 3 feet although I would recommend keeping it to a few inches.
nn#\path\program.exe
where"nn" is the number of characters in the shortcut not including the leading "nn#".
Name the text file with the extension .lnk
Shortcuts work just like those on a PC. For example, they can include "arguments" such as
21#:MSFEXPLORE \
Which will run Pocket File Explorer but start it at the root directory of the PPC
Shortcuts can be made for documents and any "associated" file as well... for example,
21#\windows\welcome.html
Will lauch Pocket File Explorer and load the above file.
While you cannot create a shortcut directly on a PPC 2000 device
unless
you use a third party app such as Resco File Explorer, with the newer
PocketPC's,
you can easily create a shortcut, but it's not obvious how to do so;
Since the illumination was very even, it was easy to see every detail that was in the light, in short a great "flashlight" better in many respects to a MagLight. The best realization was that using it did not impair my night vision and as soon as I turned it off, my eyes were already adjusted to the ambient light from the stars outside. Remember this then next time you have to change a tire on the side of a dark country road.
The problem is that the Axim's jack is recessed, and in the image, you can see that the insulated shoulder of the plug is a smaller diameter than a "standard" plug of the same size, preventing the Ipaq plugs from fully seating in the Axim's power socket. While the Axim's sync cradle has the same jack, that one is not recessed and will accept the Ipaq power supply without issue.
Solution, a tiny bit of old fashioned "whittling" with the tip of a sharp knife to widen the recess. The plastic is soft and very easy to work if you have minimal carving experience.
My motivation to attack the case came from a number of power adapters and mounts that I had generated to provide power for either the Jornada and Ipaq, but now, with that minor mod, they include the Dell as well.
All of the PocketPC's that I have encountered to date use the same power supply specifications... a "nominal" voltage of 5vdc and most of the device power supplies run between 500 ma to 1500 ma. If you are going to use a power supply other than one from the device manufacturer, the voltage and connector polarity are critical. "Nominal" 5vdc is going to range from 4.5v to 6.0v... for example, the closest supply that Radio Shack offers at this writing is 6v and that is the voltage specification on their Ipaq replacement power supply. (Radio Shack was one of the original vendors for the Ipaq 36xx series PocketPC's)
Radio Shack also offers a versatile power supply system called "VersaTip" that provides a number of different tip configurations that fit on a single two pin connector that is a part of a number of different ac and dc power supplies. Reversing these two pins using the "Tip" and "+-" markings on this connector controls the resulting polarity of the tip. The last time I looked, they offered around twenty different power tips.
The ma (milliamp) rating is less important as the PPC will control how much current it will receive... if the power supply ma rating is too low, it will take longer to charge and, in extreme cases, may not provide enough juice and the device might take power from the battery as well.
If the supply's ma rating is high, the voltage and device specs will control how much current is actually used. For example, the Axim's ac adapter is rated at 400 ma and the HP 56x series adapters are rated at 1700 ma and since it seems to take about the same length of time to charge the Axim with either, I would guess that it is demanding less than 400 ma from the HP adapter when I use that.
There is a "quasi" standard on these coaxial connecters... the center or "tip" connector is positive and while most power supplies of this size that I have seen are 5vdc tip positive, I have seen some that are different polarity and different voltages, so test and confirm before you destroy your expensive device.
Finally, an "old timers" tip that you can use with the Jornada's rectangular power connector. If you need to determine the polarity of the plug, take a close look into the power jack on the Jornada itself... it's simply gold traces on the edge of the motherboard inside of the case. A close look with a magnifier will reveal that one of the traces is slightly longer than the other... the longer one is negative or ground... a trick to assure that any static electricity in the cord will be shunted to the case before the positive connection is made.
STEP ONE... BACK UP! All Jornada contents will be GONE when the battery is disconnected! As always, by opening any device, you assume full responsibility for any damage that results from doing so.
To remove the back, start with a slightly damp piece of cloth to work on (to drain any static charge) and use a small screwdriver to remove the four screws on the back... pull the cover free at the CF end and move the cover toward the jog wheel to clear it. The rest of what you need to know is in the image.
Be careful with the screws you remove... they are tiny, machine threaded, easy to loose, and probably impossible to replace.
The black board shown contains the ROM (non flashable) which can be
removed by pulling it up and away from the motherboard. I point
this
out as there have been a number of questions about changing the
language
on the 54x series, and I would assume if you can obtain a broken
Jornada
with the language you desire, swapping this board out should
achieve this goal.