x
This website is using cookies. We use cookies to ensure that we give you the best experience on our website. More info. That's Fine
HPC:Factor Logo 
 

Palm-size PC SDK

Download Summary:

Support the Site
Become a HPC:Factor Plus Subscriber Member button
Support us on Patreon button
Support HPC:Factor in continuing to offer support and downloads to the community! Make a donation button.

Palm-size PC 1.1 Software Development Kit (SDK)

You are not currently logged-in. To download you must be logged-in and be a subscriber or have met our community quality and reputation requirements as a free user - Find out more · Subscribe
File Name:
PPC_SDK(CHS).zip
Version:
1.1
Developer:
Microsoft Corporation
Download Size:
27.71 MB
MD5:
79E80E4F6A96ABD94DE411CE0C3F6AD0
Release Date:
30/01/1999
Language:
Chinese (China)
Popularity:
3148
Number of Downloads:
0
Added By:
torch on 04/05/2024 8:25:29 AM

Overview:

Windows CE pre-built platform SDK Palm-size PC 1.1

We currently only have this available in Chinese Simplified. Do you have another language version that you could share with the community? If so, please get in touch.

System Requirements:

The Windows CE simulation environment has the following requirements:

Microsoft Visual C/C++ 5.0 (or equivalent) compiler, linker, and related desktop design tools.

Windows NT 4.0 or higher operating system.

Although you can install Windows CE on Windows 95/98 platforms, Windows CE emulators are not supported on Windows 95/98.

The Palm Emulation Environment allows developers to design and test Windows CE applications on Windows NT Workstation as if they were on a Palm device. This simplifies application development. This environment includes an emulation shell and object memory. Object memory is contained on the hard disk in a file called "Palm_Size_PC.OBS". This object store is located in the "...\wce\emul\Palm" directory. The SDK installation program will generate this file for you, and the object memory can be managed through the FILESYS.EXE program. Object storage includes registries, databases, and files. The tree structure is equivalent to real object memory on a handheld computer device. All semantics are the same. For example, the root directory is "\", and there is no concept of "current directory".

The handheld computer emulator is a well-running NT desktop application, and it must also have the ability to start and stop at any time according to the user's needs. This conflicts with the characteristics of a well-functioning handheld computer application: the handheld computer application does not work well with the user's terminal device. Therefore, some handheld applications may not respond correctly to emulated terminal devices. If the application fails to exit properly, the emulator will pop up a dialog box and provide the user with a tool to force terminate (interrupt) the non-current application.

For the emulator, the handheld computer uses the SHELL32.EXE program as the shell. It can be accessed from the Start menu via the Start\Programs\Windows CE Platform SDK\Desktop Palm-size PC Emulation item. The emulation shell and COREDLL.DLL give you the look and feel of a real handheld device. They contain the main functions. The system does not support running multiple emulation shells at the same time. The FILESYS.EXE program can be started directly or indirectly. It runs as a background task, so it doesn't run in a normal window. You can find the FILESYS.EXE program in Task Manager, and if the registry debug value is set to "console", the FILESYS.EXE program will be presented in a debug console window. In order to launch it indirectly, you can start a shell program (SHELL32.EXE) that can launch the executable. The SHELL32.EXE program can detect whether the FILESYS.EXE program is running and start it if it is not running. FILESYS.EXE will continue to run until the latest emulation application exits.

Executable emulation shells can also be launched directly or indirectly. The emulation shell runs in a fixed window that cannot be moved or minimized. To start an emulation shell indirectly, you can start an application designed for the emulator (see "Designing for the emulator" below). This is any application that links to COREDLL.LIB (DLL). COREDLL.DLL will detect if the shell is running and start it if not. FILESYS.EXE is started according to your needs. If you wish to run your application without a shell emulator, you can provide the application with the command line switch /NOSHELL. The Shell Application Programming Interface API will not work for emulated applications launched without a shell.

While every effort has been made to make the emulation of handheld devices as realistic as possible, the emulator relies on the Windows NT platform, so some minor visual differences may occur.

In order to switch between two active applications in the Handheld Emulator, you must use Task Manager or restart the second application through the Start menu.

This development kit has included Windows CE header files and libraries that implement ICMP Echo request/response functionality. Header files and libraries are only used on the device, not in the emulator environment. The files required to implement this feature include ICMPAPI.H, IPEXPORT.H and ICMPLIB.LIB.

This version of the handheld computer emulation environment does not support the Windows CE Mobil Channel. The system does not support the use of global clock applications that modify the time and date because it will cause the desktop time and date to change.

The Pocket PC 1.1 Chinese version emulator included in this release is a beta version, which does not fully support all features planned for the final release and does not achieve the goal of full localization.

Installation Instructions:

Recommended installation procedure

Compile for emulator only:

Please make sure that the emulator has the corresponding functions required to run on the Windows NT 4.0 platform. Emulators on Windows 95/98 platforms are not currently supported;

Install Microsoft Visual C/C++ 5.0 or other C/C++ compiler;

Install Windows CE Platform SDK. (H/PC);

Install Windows CE Platform SDK. (Pocket PC)

NOTE: The instructions provided above in "Designing for the Emulator Only" mean that the handheld computer will have to be designed using NMAKE via the command line. Programmers need to use the Windows CE Toolkit for Visual C++ 5.0 to design the handheld computer in the integrated development environment IDE.



Compile for emulators and devices:

Please make sure that the emulator has the corresponding functions required to run on the Windows NT 4.0 platform. Emulators on Windows 95/98 platforms are currently not supported;

Install Microsoft Visual C/C++ 5.0 or another C/C++ compiler;

Install Windows CE Toolkit for Visual C/C++ 5.0;

Install Windows CE Platform SDK - (handheld PC);

Install Windows CE Platform SDK - (handheld computer);

Windows CE Platform SDK (Pocket Edition) provides tools for designing applications for handheld computers. This release includes emulator support for handheld computers. The Windows CE Platform SDK for Handheld does not include the cross-compiler required to develop binaries that run on Handheld devices. These compilers are included in the Windows CE Toolkit for Visual C/C++ 5.0 provided by Microsoft or a C/C++ development environment that supports Windows CE.

The Windows CE Platform SDK enables you to uninstall the development kit. However, since this toolkit is a product released during the upgrade process, the uninstallation process will remove all current components. Users can restore the original components by reinstalling this toolkit.

Note: If the design path is not set correctly during the installation of the handheld SDK (you can find these settings in the "Directories" palette of the "Tools/Option" window in the integrated development environment), then please change the settings in H/ The directory names used in PC version 2.00 are copied to the settings of Handheld PC 2.11.



Remote debugging process of handheld computer equipment

In order to simplify the debugging process of handheld computer devices, we provide two upgraded files for users of Windows CE Toolkit for Visual C/C++ 5.0. These two files are PFILE.EXE and PFCOM.DLL. All these files are saved in the Program Files\Windows CE Platform SDK\Support\Updates subdirectory. Before you use the Windows CE Toolkit for Visual C/C++ to debug a handheld computer device, please back up the current copies of the two files PFILE.EXE and PFCOM.DLL, and then copy these files to the DevStudio\SharedIDE\bin subdirectory. in the directory. These files will also work on handheld PCs. The two files PFILE.EXE and PFCOM.DLL must be copied to this directory to replace the previous versions to achieve debugging of the handheld computer device.

Donate:

Support the Site
Become a HPC:Factor Plus Subscriber Member button
Support us on Patreon button
Support HPC:Factor in continuing to offer support and downloads to the community! Make a donation button.
HPC:Factor believes that the Internet is a better place without the constant displaying of adverts on community website resources and as such does not carry 'ad-words', banners, pop-up's or any other form of paid advertising.

Please help to pay for the download that you are getting from us today and help to support our desire to run the site without paid subscriptions or advertising by making a donation to the site. It doesn't matter how much or little you donate, but by donating you will help to ensure that we can continue to offer some of the Internet's most popular, rarest and unusual downloads for Windows CE devices for now and for the future.