Menneisyys
11-13-2007, 03:39 PM
(Note that if you’ve never heard of ignore_my_docs, you can safely skip this article. It’s only meant for users of previous Windows Mobile operating systems that would like to know whether ignore_my_docs is still in effect.)
There is still a lot of confusion caused by ignore_my_docs explained for example in THIS (http://www.pocketpcthoughts.com/forums/viewtopic.php?t=2863) (this is the most important article!), THIS (http://www.pocketpcthoughts.com/forums/viewtopic.php?p=356212) and THIS (http://hardware.mcse.ms/archive31-2005-10-247853.html) threads / articles.
WM5 (and, of course, all subsequent operating system versions), finally, got rid of this, for several Windows Mobile users, pretty confusing feature as is explained for example HERE (http://www.pocketpcthoughts.com/forums/viewtopic.php?t=44488) or HERE (http://www.pocketpctweaks.com/pocketpc_tweaks/move_my_documents_storage).
In a nutshell: WM5+ is different from how earlier OS versions behaved if and only if they also contained an ignore_my_docs file in the root of the card and also a \My Documents directory. In this case, only the contents of \My Documents (and ALL its subdirs) were accessible, nothing else on the card. An example screenshot of my WM2003 HP iPAQ 2210 showing this in effect is in HERE (http://www.winmobiletech.com/112007AttachmentsAdd/wm2003removedignore_my_docs.png) (with removed ignore_my_docs) and HERE (http://www.winmobiletech.com/112007AttachmentsAdd/wm2003prsentignore_my_docs.png) (with present ignore_my_docs). As you can see, in the former case, the content of the other directories on the card aren’t listed, only those of \My Documents on it (and, incidentally, all its subdirs – as opposed to the case of WM5+, where this is no longer the case).
All in all, under WM5 and later operating systems, it doesn’t make any difference whether there’s an ignore_my_docs file in the root of a storage card or not: the standard file dialog will see all directories - one directory deep. The latter also applies to \My Documents, unfortunately, as has also been explained HERE (http://www.pocketpcthoughts.com/forums/viewtopic.php?t=44488). This problem still hasn't been fixed.
There is still a lot of confusion caused by ignore_my_docs explained for example in THIS (http://www.pocketpcthoughts.com/forums/viewtopic.php?t=2863) (this is the most important article!), THIS (http://www.pocketpcthoughts.com/forums/viewtopic.php?p=356212) and THIS (http://hardware.mcse.ms/archive31-2005-10-247853.html) threads / articles.
WM5 (and, of course, all subsequent operating system versions), finally, got rid of this, for several Windows Mobile users, pretty confusing feature as is explained for example HERE (http://www.pocketpcthoughts.com/forums/viewtopic.php?t=44488) or HERE (http://www.pocketpctweaks.com/pocketpc_tweaks/move_my_documents_storage).
In a nutshell: WM5+ is different from how earlier OS versions behaved if and only if they also contained an ignore_my_docs file in the root of the card and also a \My Documents directory. In this case, only the contents of \My Documents (and ALL its subdirs) were accessible, nothing else on the card. An example screenshot of my WM2003 HP iPAQ 2210 showing this in effect is in HERE (http://www.winmobiletech.com/112007AttachmentsAdd/wm2003removedignore_my_docs.png) (with removed ignore_my_docs) and HERE (http://www.winmobiletech.com/112007AttachmentsAdd/wm2003prsentignore_my_docs.png) (with present ignore_my_docs). As you can see, in the former case, the content of the other directories on the card aren’t listed, only those of \My Documents on it (and, incidentally, all its subdirs – as opposed to the case of WM5+, where this is no longer the case).
All in all, under WM5 and later operating systems, it doesn’t make any difference whether there’s an ignore_my_docs file in the root of a storage card or not: the standard file dialog will see all directories - one directory deep. The latter also applies to \My Documents, unfortunately, as has also been explained HERE (http://www.pocketpcthoughts.com/forums/viewtopic.php?t=44488). This problem still hasn't been fixed.