Free wince cab editor software for pda

You are controlling a small prehistoric cave cab and it is your duty to safely navigate your passengers through treacherous obstacles and transport them to the desired destinations. The player must use the propellar on top of the cab to land and take off safely from the different platforms. If you collide with the rocks or land too fast, your cave cab crashes and it will end up as a pile of junk.
Each level gets more difficult with longer and narrower caverns to maneuver through. Points are awarded according to the difficulty at the end of each completed level.
Version restrictions:
- Ad-supported

A pattern like mystery circle can be drawn.

An application for updating SDP records on Series 60, specifically for making Bluetooth File Exchange on OS X usable with Series 60. Licensed under GPL.

OBEX File Transfer on Series 60, with Bluetooth File Exchange on OS X

This only conserns Series 60 2nd edition (and probably 1st edition, too), 3rd edition and Series 80 work as they should.

Overview

Ever since starting to use Series 60 phones with OS X, Ive been annoyed by the fact that Bluetooth File Exchange cant browse them. The only way of transferring files between them is by using OBEX push, that is, by sending individual files (which then on the phone end up in the inbox).

This is bearable, but sometimes youd want to send a bigger file straight to the memory card which doesnt even fit into the main memory of the phone.

I dont know about any OBEX FTP client for Series 60 either (is there any?), otherwise that would be a feasible workaround.

Initially, it seemed to me that Series 60 didnt work at all with Bluetooth File Exchange, since it only showed an empty folder. After quite some time, though, I figured out that it actually works, but not as one would hope. Uploading files works, and then the uploaded files are stored into the inbox. And in that case, the files which are in the inbox, uploaded using OBEX FTP earlier, are visible. But not files sent using OBEX push, and of course nothing outside of the inbox.

I had only tried using obexftp (which uses openobex) on Linux using USB earlier, and knew that that one works as I want to. Much later, when I tried using obexftp with Bluetooth, I found the same situation if one doesnt manually specify a specific RFCOMM channel. Using the wonderful tools in BlueZ (more specifically, sdptool), I could view a dump of all SDP (service discovery protocol) records on the phone, and suddenly everything made sense.

The phone advertises quite a few different services, among them a standard OBEX FTP service and OBEX PC Suite services. The RFCOMM channel one had to specify in order to make obexftp work was the PC Suite channel.

In other words, Series 60 advertises two services which speak the OBEX FTP protocol, one very crippled advertised with the ordinary OBEX FTP service UUID and one full-fledged service with a PC Suite-specific UUID.

One cant expect Bluetooth File Exchange to look for the non-standard PC Suite service UUID, and I dont know of any other OBEX FTP application for OS X. But theres still another (quite hackish) solution: make the phone advertise the PC Suite service using the OBEX service UUID.

Ideally, the hack would consist of a simple application on the phone, which investigates the local SDP database and makes the necessary modifications. Unfortunately, the SDP APIs on Symbian dont seem to provide any way of reading whats in the database, and the APIs for reading SDP records from other devices dont seem to be able to connect to the local SDP server. In other words, the investigation of the SDP database must be done on some other device.

Solution

Note, I take no responsibility whatsover for the effects of using these tools. They work for me, at least.

SdpBrowser

SdpBrowser is a tool for OS X, which more or less does the same as sdptool in BlueZ - its capable of listing all the SDP record data on a remote device. (Bluetooth Explorer in the Xcode Developer Tools does more or less the same, but only for the local SDP database.) This can be useful when developing Bluetooth applications for some other device than the local mac.

Since SdpBrowser is made specifically for this need, it also can try to parse out the necessary information from the SDP records.

SDP Editor

SDP Editor is a small tool for Series 60 for updating already existing SDP records on the phone. Enter a SDP record handle and a RFCOMM channel, and that record is updated to advertise the given channel.

The changes arent persistent, everything is back to normal after restarting the phone.

The APIs dont work too well if the given record handle doesnt already exist, on 6630 the SDP server crashes. Updating the wrong record makes some other service unusable. In all cases, restarting the phone should restore everything.

Usage

Using SdpBrowser, select Get PC Suite info in the Device menu, select the phone and click browse. If everything works as it should, it gives the SDP record handle of the OBEX FTP record and the RFCOMM channel of the PC Suite service.

Then start SDP Editor on the phone, choose Update channel in the menu, and enter the handle and RFCOMM channel given by SdpBrowser. Then, Bluetooth File Exchange should be able to browse the files on the phone.

The handle and channel shouldnt change as long as you dont install/remove any service on the phone, so in general youll only need to rerun the application on the phone with the last, working values.

If it doesnt give all the necessary information, you can try to read it manually from the raw SDP records. Select Browse in the Device menu, and select the phone. Look for a record with the text "OBEX File Transfer", and look for the number on the row starting with "0:" in this record (e.g. "0: 0x10006"). Thats the record handle (in hexadecimal). Also look for a record with the text "Nokia OBEX PC Suite Services". That record should have a row like "4: { { } }, { { }, { 0xc } }, { { } }". Here 0xc, that is 12, is the RFCOMM channel.

Further improvements

This already is quite an improvement to the original "functionalty" of the crippled OBEX FTP service. But e.g. the System-directory is hidden - if one would be able to directly transfer files there, the development process of Series 60 applications would get a big speedup. This directory is still accessible, if one is able to manually enter a directory to open. (Incidentally, obexftp does this.)

So, the final wish is a "Go to directory"-dialog for Bluetooth File Exchange, or obexftp working on OS X. (openobex can be compiled with USB support on OS X, but I havent gotten it to work... Perhaps Ill have to add support for OS X-bluetooth to it myself, sometime, if I have time and if noone else beats me to it.)

The all-in-one tool for creating installations for Windows, Windows Mobile, SmartPhone and Palm Devices. Modular architecture with plug-ins for the supported installation modules. Rapid development for all of your installation needs.
Windows Setup Features
- Builds compressed, self-contained, self-extracting windows setups.
- Flexible Windows Setups packing all the supported components in one single executable.
- Multilanguage support.
- Conditional installation depending of users language selection, ActiveSync, HotSync.
- Runs on all Windows verions, from Win95 to Vista.
Installation Modules
CAB Creator
- Supports creation of multiple installs for various platforms (e.g. ARM, SH3).
- Generated CAB(s) Files can be used for Over The Air (OTA) install.
- Very easy, point and click only, interface to generate CAB(s) Files.
- Wizard for making new CAB(s).
- Custom icon for Mobile Shortcuts.
CAB Collections
- Able to handle any number of CAB(s) Files, automated installation through ActiveSync.
- Conditional installing of collections.
Palm Files
- Module can handle any number of Palm Files.
- Automated installation through HotSync.
- HotSync User selection during installation.
- Conditional installing.
Redistribution Modules
- .NET CompactFramework and Mobile SQL supported.
- Fully customized settings. Multiple sets can be defined.
Win32 Module
- Conditional installing.
- Customized actions to run when installing or uninstalling.
Environment Features
- Easy to use interface.
- Project Manager for easy handling projects.
Licensing
The use of this program is free for personal use or freeware projects. For commercial use, this software must be registered. The registration fee is at the price of 29 Euros.
Main features:
- Easy to use interface, all the functions are one mouse click away.
- Can save/open created installation projects.
- Supports all the cabwiz tags and options.
- Supports creation of multiple installs for various platforms (e.g. ARM, SH3).
- Creates compressed, self-contained, self-extracting Windows setup program.
- One click for creation of .inf files, cab(s) file(s) and installation executable.
Enhancements:
- Vista Compatible.
- More advanced builder options for the windows setup wizard.
- Splash Screen for your installations.
- About Button with custom message.
- Beveled Label like InstallShield.
- Bugs within the the advanced builder options and relative paths fixed.
- Multi tabbed user interface. No more floating windows taking all the workspace.
- Registry Section Editor now can import registry entries from .reg and .rgu files.
- Updated User Interface of CAB Creator Module.
- Updated look and feel of Project Manager.
- Bug fixes.
System requirements:
- Windows

The Microsoft .NET Compact Framework 2.0 SP1 Redistributable contains the common language runtime and class libraries built for the .NET Compact Framework. In addition to supporting version 2.0, it also supports applications developed for version 1.0 and service pack releases before version 2.0.
Important: This redistributable enables running .NET Compact Framework applications on the Pocket PC, Pocket PC Phone Edition, Smartphone, and other Windows CE powered devices. To develop .NET Compact Framework applications, Microsoft Visual Studio 2005 or the Microsoft .NET Framework 2.0 SDK are required.
This package uses ActiveSync 4.0 and up to update the device, see the Windows Mobile Center for more information. Be sure to dock your device first before running NETCFSetupv2.msi. If your device is not docked, ActiveSync will store the CAB file until the time when you dock your device. Those not using ActiveSync can run the CAB files which match the device found in the install folder directly on the device
Enhancements:
- Added support for WindowsCE 4.2 in both the CAB installation and a Platform Builder Update.
- Added the option to install the global assembly cache to the storage card.
- Allow DataGrid cell drawing to be overridden.
- Added support for headless Windows CE 5.0 devices by adding a Headless catalog item in Platform Builder.
- Added System SR files to the Windows CE 5.0 Platform Builder catalog item.
- Enabled device debugging using mdbg.
- Included LogViewer tools to monitor network traffic.
- Included the .NET Compact Framework Remote Performance Monitor.
- Added the Serializable attribute