On Wed, 21 Feb 2024 11:15:24 -0800 (PST), frank van nuffel <
fannuffel@gmail.com> wrote:
Can copying your files from the source to the destination be done from within Pocket OS? Iow, does Pocket OS recognize external volumes (even NTFS volumes), then try installing everything into your Pocket OS volume by hauling over from your source
volume, not via the Host OS?
Mind, i'm unfamiliar with Pocket OS, but it's worth trying
Frank
Thanks for the reply Frank.
Do you boot your device with PocketOS? Or does it run under a VM?
The device boots from Windows CE 7.0. I use a DOS emulator
(PocketDOS) to run my Clipper application.
The client is currently using an Intermec handheld device that runs
Pocket PC ver 3.0 OS. My goal is to port the Clipper application (scanning/data entry) to a newer (newish) handheld running Windows CE
7.0. The application that is currently running on the Intermec device
also runs under the same PocketDOS emulator, although an older version
that is designed to run under Pocket PC OS.
PocketDOS allows mapping drives to folders on the handheld. On the
Windows CE handheld device there is the root (\) where Windows/Program
Files, etc. live. Then there is a folder called "Application" where
developer apps live. The device can be "reset", which takes
everything except the "Application" folder back to a factory state.
IOW, if you have something you want to survive after a reset, it
should live in the "Application" folder. So I have the C: drive
mapped to the "Application" folder. The A: drive is mapped to a
virtual boot disk. I have the Clipper app running from a folder
called "Houser" (client's name) inside the "Application" folder. So
from a DOS perspective, the true root of the device (where Windows
lives) is hidden. It only knows about things in the "Application"
folder, because that's where C: is mapped.
Does Pocket OS support FAT32? Does Windows CE have known issues with FAT32? Better not use a NTFS volume, even if Pocket OS supports it!
Since the application runs under the DOS emulator, it doesn't know
about NTFS. It thinks it's running under DOS, so FAT32 is the file
system.
Do you combine the latest .libs for Clipper '87?
To the best of my knowledge. Keep in mind that the application has
run flawlessly for years under two generations of handheld devices
(Intermec and Janus). I haven't changed anything in my development environment.
Does mounting to another drive letter than C:\ changes anything
Possibly. I will probably try that next. Just caught Covid (again)
so not really in the mood to play with it ATM.
Can copying your files from the source to the destination be done from within Pocket OS? Iow, does Pocket OS recognize external volumes (even NTFS volumes), then try installing everything into your Pocket OS volume by hauling over from your source
volume, not via the Host OS?
Mind, i'm unfamiliar with Pocket OS, but it's worth trying
Not 100% sure I follow you.
The method of moving files from my dev box to the handheld is via
Microsoft's Active Sync/Windows Mobile Device Center. I develop the
handheld applications on a Windows 7 box running in XP mode (where
there is still DOS support) and then copy the .exe and database files
via XP --> Windows 7 --> Windows 10 --> Windows Mobile Device Center. Connection from handheld is USB.
PocketDOS *does* support network drives, so I may try mapping that,
leaving the application files on my dev box to see if that changes
anything. It's not a long-term solution, but it may provide some
insight.
I'll try installing on a different drive than C: when I get a chance,
although I'm not too hopeful it will help. I was really hoping that
following David's advice to move the application off the root of C:
would buy me something, but no joy.
If I can't make any additional progress, I may suggest to the client
that we try a handheld running Windows Embedded rather than Windows
CE. I've already tried an Android based device, but the DOS emulation available for Android leave a lot to be desired.
Thanks,
--
Scott at Scott dash(-) Coffey dot net
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)