Database Info

Great Tool for remote controlling ppcs: VirtualDisp

I just installed VirtualDisp and it's a really kick-ass piece of software. So anyone who does not know it yet, give it a try! (http://world.kyuran.be/) It lets you use your computer's mouse and keyboard to control your ppc. The amazing thing is, its "client"-side only (you don't need any additional software on your mobile device!) - just activesync your device and you are ready to go. It "extends" your desktop in the way modern graphics drivers do when multiple monitors are attached. Just move your mouse out over one edge of your monitor and your cursor will appear on your mobile device's lcd.

Hi Registererer!
This post got me curios so I went and downloaded the demo version.
As I suspected, this functionality cannot be achieved without a server on the device side. They use a DLL which is a RAPI extension. They copy it silently to the device so you don't notice it. I found this out when I tried the free version on a WM5 device. It only comes with the DLL for WM 2003.
Any way, it's not that great since you can't see the PPC screen on the PC. There is a tool from Microsoft (completely free), called Remote Control (something, don't remember) and another tool from some company (not free) that shows you the PPC screen on the PC and lets you use the mouse and keyboard of the PC for input.
So this is a nice little app, but I doubt it will sell.

Levenum don't be so hard on the guy
The thing is Register that SOTI Pocket / Smartphone Controler is a kick ass app that is far more advanced than VirtualDisp... and not much more expensive.
So it needs to have something extra to catch the atention
But its a good start
Cheers,
Raul

Sorry, didn't mean to heart anyone's feelings!
It is a cute app. Perhaps if they add the functionality of using it as a virtual mouse without the PC connection (using the joystick). There was a thread here somewhere of people looking for just such an app.
By the way, have you tried it on WM5? I know from experience that just transferring a DLL won't do so they would have to install a signed cab. Does it connect as smoothly as it does on WM 2003. That is one strong point I noticed: They detect the AS connection immediately, and you don't have to wait before you can use the app.

Everything you need to know about USB networking in WM5

Everything you need to know about USB networking in WM5 - all secrets explained!
I’m cross-posting this, just-updated article to here too (originally posted to here) because it sheds light on a LOT of WM5 issues. Please note that the first part of the article was written way before AKU 2.2; I haven’t touched it now that 2.2 is out, just added a brand new, “UPDATE” section.
You will want to read particularly the second section because, as I also point out in there, switching back to the old networking model may be really advantageous in numerous cases and is, therefore, highly recommended for casual users.
The original article follows:
In my previous article on the secrets of ActiveSync-based Pocket PC networking, I've elaborated on the pre-Windows Mobile 5 Internet pass-through capabilities of ActiveSync.
As has been stated there, the ActiveSync Internet pass-through is in no way a full-fledged Internet connection. In no way can you access a Pocket PC through a simple, plain ActiveSync connection as a TCP/IP device.
With Windows Mobile 5 (WM5 for short) devices, the situation has changed a lot. Now, they're recognized as an entirely different, fully-fledged network card by Windows, as can be seen in this screenshot.
Also, if you, with, say, the great, (for individuals) free networking utility, vxUtil, check the IP it got from ActiveSync of your Pocket PC, you will see that it's no longer 192.168.55.101 (the IP ActiveSync gives to pre-WM5 devices) but a "true" local network IP; in this case, 169.254.2.1. The services of this PDA will, therefore, be fully accessible to your desktop computer (in this screenshot, you can see I can directly ping my WM5 PDA from my desktop computer) and, if you configure your desktop computer to forward ports (please read my previous article on the meaning of this!) to the PDA, to the entire outside world.
This means Windows Mobile 5 devices connected to desktop Windows PC's via ActiveSync are, now, fully accessible by TCP/IP-based applications. You don't need to build a(n additional) Bluetooth PAN or ad-hoc Wi-Fi connection between the two devices any more for the Pocket PC to become accessible.
The importance of this can't be stressed enough: a lot of - with pre-WM5 devices totally impossible - tasks become really easy:
you can run applications on your Pocket PC that behave like a server: for example, a lot of peer to peer (non-central server based), TCP/IP-based multiplayer games
chatter/VoIP applications like the very good Microsoft Portrait
IRC clients with fully usable DCC capabilities (without full, unrestricted Internet access, it's not possible to initiate DCC send/chat requests from the PDA)
FTP/Web servers for remote access
remote, TCP/IP-based Pocket PC controllers like SOTI's Pocket Controller, PocketVncServ, dotPocket and Microsoft Windows Mobile Developer PowerToys. Now, if your mate/client has a problem with his/her Pocket PC, you will be able to access it distantly without his explicitly logging in to a, say, unrestricted Wi-Fi network. All he'll need to do is doing some port forwarding with either WinGate or the built-in, free Windows Internet Connection Sharing to connect it to the Internet through his desktop computer.
Sharing the Internet (say, Wi-Fi) connection present on your PDA with the not directly internet-enabled desktop via my Web proxy server running on the Pocket PC as described here
And, the list continues...
Please note that you will still need to configure port forwarding (which is in detail explained in my previous, networking-related article). But now, at least this is allowed and can be done – unlike with previous Windows Mobile operating systems.
Kudos to Microsoft – this is a really-really welcome addition! With this, ActiveSync-based networking has become far-far easier!
Of course, every bean has its black. The new networking model does have its share of problems. For example, many firewall/viruskiller applications will sense the WM5 PDA as an intruder, unlike with previous Windows Mobile / Pocket PC versions. You will, therefore, may end up having to fine-tune/reconfigure your firewall/viruskiller applications (if you have any) to let your WM5 devices work. Still, I think the advantages the new networking approach has (for example, the much easier Pocket PC control capabilities from distant locations) far outweigh these minor annoyances/one-time configuration needs.
UPDATE (09/15/2006): Old networking model reintroduced in a later WM5 upgrade
If you have a WM5 device that has AKU (please read this article on what AKU's are) 2.2 or later, then, you have the capability of using the "old" networking model if you just deactivate (screenshot here) the, by default, enabled "Enable advanced network functionality" checkbox in the newly added Start / Settings / Connections / USB to PC applet (x51v screenshot here, HTC Wizard here).
The list of WM5 devices already having AKU 2.2(+) includes for example the HTC Wizard, HTC Universal and Dell Axim x51v - these are the WM5 devices I could test in this respect. Note that, as the 2.01 WM5 upgrade for the iPAQ hx4700 is still AKU1.1 only (screenshot of this here), it has no USB to PC applet and, tehrefore, you can't switch back to using the old networking model using this device (a screenshot showing the Connections tab is here; as can be seen, there is indeed no applet there).
In real life, unless you really need the advantages of the WM5 USB networking model outlined in the above article, it's preferable to disable this checkbox. The reasons for this are very simple: as no additional local networks are created when you connect a WM5 device to your PC, 1. there won't be firewall problems 2. the ActiveSync connection will be active (that is, the device becomes visible to the desktop) far earlier than in the other case (again, because no additional network-creating, IP assigning etc. handshake is needed).
As can be seen in thix vxUtil screenshot (compare it to the new model - that is, this one), the IP of the device will be the old, well-known "192.168.55.101". That is, everything I've ever published about the networking model of pre-WM5 devices' USB connections will be topical with AKU2.2+ WM5 devices with disabled WM5-type USB networking.

advice please: XDA Orbit / Graphite / Outlook / Gmail / CrossOver Office / HEADACHE!

Hi all, I’d like some advice please.
I am still fairly new to all this so please treat me as a noob.
This weekend I removed all traces of Windows from my two computers at home. It is now entirely Linux powered 
It is also upgrade time for me with my phone network (02 in the UK) and I’d like to get a phone that syncs up to one contacts list and does email. Wifi is a must, so I was thinking of the 02 xda Orbit, or maybe the Graphite (when it comes out)
I have also recently set up a gmail account. Busy time!
So now I am not sure what the next step is.
If I ran CrossOver office, would I be able to sync contacts/tasks/mails with (either) devices?
Should I just use gmail on the phone? (Trying to get my PST files into Gmail is proving a *massive* headache though!) and it looks like then the phone would have two contact lists? One for email and one for the phone.
Is there a better solution? I am quite happy to run thunderbird/evolution/something else on the computer, and or phone.
Nothing is set in stone here. I am completely flexible.
I am keen to hear whatever you recommend is the best solution.
Thanks in advance,
John

As ActiveSync would require direct access to the USB or Bluetooth, i doubt it unless the APIs are there (not to sure with CrossOver, but its not done for Wine).
Syncing in Linux with WM5 is a pain, at best you'll have to hand compile Synce and the OpenSync plugin, then setup OpenSync and Evolution. I currently export my info to vcal/vcf, do some script fu on them and bluetooth over to my mobile and use SkTools to remove any dupes.
Another option is to have QEMU running with Windows and ActiveSync on, then forward the USB device onto QEMU to use. I had this half working last night but the XP install i've got has issues with loading new drivers, i'll try again tonight

Thanks for that response - very very helpful.
I thought about the idea of using a host operating system, but I was concerned about processor speed and system load.
This would be for a laptop that is a few years old, and a mail client is the sort of thing I'd always have running. I am very keen to hear the results of your XP tests. If QEMU works, it may be the solution.
If not, I guess the alternatives are using a java gmail app on the phone and manually keeping the contacts inline.
Or wait to see what happens with this OpenMoko project.

I custom patched QEMU 0.8.2 with the USB Multi-interface mod (needed to pickup a HTC device) and tried to set it up, Devices is detected in WinXP but then errors like a hardware issue. It'd possibly work with VMWare as you can specifically assign a device to the VM but i dont think QEMU is up to the job quite yet.

Thanks for the update. I'll keep hacking, and if I have any success, I'll post about it here.
cheers

Stupid: DC++ Windows Mobile

Hello all,
I would have a question here: is there any DC++ Hub Viewer for Windows Mobile?
I googled all the search terms I could think of and here's the result:
http://sourceforge.net/projects/mobiledc (good if you got Symbian UIQ )
Maybe some would find a thing like this useful...
Anyway, ***have a nice day***.
--- PS ---
Saw that poll?

Yeah, Symbian gets tons of good software. You know, I'd love to try to run Symbian on my Dash.

Read-Me-First (?)
For those who don't know what's DC++ (2 votes, this is getting bad... ) :
--- ENCYCLOPEDIA: DC++ HUBS ---
DC++ Hubs are... well, some tech thingies. (This was the description)
The hubs are used to host users. (Well, what else could they do and make them popular?)
The users connected to hubs can:
- chat in a main chat and in personal messages (PMs)
- share files from their computer (mostly pirated )
- respect some rules
You can connect to the hubs with a DC++ Client or Viewer, like StrongDC++ or oDC (those are the most known).
Almost all the hubs require a minimum share (ex. 5GB). That means you need to have at least that share to connect to a hub.
--- ENCYCLOPEDIA: DC++ HUBS (END) ---
You want more info? Go to Wikipedia: http://en.wikipedia.org/wiki/Direct_Connect_(file_sharing)
Hope that helps, newbies to DC++! (I don't want any more votes at "What's DC++?" !!!)
*** Have a nice day! ***

I've never used DC on PC or other devices. However, WMTorrent is an absolutely great app if downloading is your thing.
If there's code on sourceforge for UIQ, and DC is an open protocol, you could try to knock together a client yourself. Not a quick solution, but c'est la vie
V

Thanks for the encouragement, V.
Knocking it toghether may be a solution, but if I am not mistaken, it takes the WM SDK and VB Studio (commercial )... or d'you know a free WM-development application?
And where on earth is the source code at SourceForge?!
*** Have a nice day! ***

eMbedded Visual c++ 4 is absolutely free together with WM 2003 SDK (I am too lazy for links so please search MS downloads)
Apps written with it will work on WM 5 and 6 and if you know how to play with linkage you can even get access to new APIs not supported in WM 2003 SDK.
They give you full functionality and in my opinion is still the best way of coding for WM.

levenum said:
Apps written with it will work on WM 5 and 6 and if you know how to play with linkage you can even get access to new APIs not supported in WM 2003 SDK.
Click to expand...
Click to collapse
Do you have a rough guide on how to do this? I did a search and it seems that people are much happy to pay for a £100+ new Visual Studio and do not borther to find ways to get a free dev env for windows mobile. I think (think) the software I'm writting now runs on WM5, but I think there are quite some API missing in WM2003-SDK. Do you think it will work if I were to throw everything *.h stuff from WM5-SDK to overwrite WM203-SDK?
Ref:
No free dev env for WM5-SDK, for eVc+ or the VS Express - http://www.pocketsoap.com/weblog/2006/07/1656.html
Q: Do you think the hobbyist and $10-per-program shareware market is important for Windows Mobile? If so, can you explain why Visual Studio 2005 Standard ($249) is required for targeting WM5? eVC++ 4 was free. The WM5 SDK cannot be installed on VS Express.
A: Jack2, there are various evaluation versions of Visual Studio 2005 available that you can try out before making a purchase decision, there is one for Visual Studio 2005 Professional edition (90 days) and one for Visual Studio 2005 Team Suite (180 days),
Click to expand...
Click to collapse
http://msdn.microsoft.com/chats/transcripts/mobileembedded/06_0125_msdn_ce.aspx

There are basically two ways to use missing APIs (personally I never found one I really needed except maybe "ExitWindowsEx" once).
1) Manually unpack the MSI file for the SDK you want. (Sorry, I do not remember the link for the extractor).
Then in Project->Settings->Link you can just redirect the default libraries to the folders of that SDK. What you need are the headers for the prototypes (h files) and the actual lib files.
2) If its just one or two functions you can use LoadLibrary and GetProcAddress to dynamically connect with the DLL. If I am not mistaking this is call "implicit" linking.
Note that if you use method 1 your app will not run on WM 2003. If you use method 2 it will run on 2003 but get NULL as function pointer and fail to execute the missing API so this way you can make widely compatible apps.
P.S.:
In my personal opinion, M$ gave away an IDE at first to gain a wide application base for its new platform. Now that Windows Mobile is an established and even leading mobile OS they are back to their usual policy of selling expensive, bloated and overcomplicated software.
They simply no longer need freeware developers for WM.

levenum said:
eMbedded Visual c++ 4 is absolutely free together with WM 2003 SDK (I am too lazy for links so please search MS downloads)
Apps written with it will work on WM 5 and 6 and if you know how to play with linkage you can even get access to new APIs not supported in WM 2003 SDK.
They give you full functionality and in my opinion is still the best way of coding for WM.
Click to expand...
Click to collapse
Yeah, eVC++ would be good (if you know how to fight with it), but the installer asked me for a serial. Why am I always cursed?

PocketDC++ for Pocket PC *Awesome*
I found this cool DC++ Client for Pocket PC called "PocketDC++". It seems like it doesn't have Download support yet. It wil be awesome if Download option is added.
PocketDC++ homepage : http://mistysoft.jino-net.ru/
External download Link : http://xpojnt.iglu.cz/download/tklienti/pocketdc0.1.8.9.rar

I have a copy of DC++ Source code and a copy of VS .NET and VB as well as Dephi I even altered a version of DC++ a while ago....but yeah I think it would be great for on the go downloaders for file checking and user checking/count....excellent idea

[Q] How to use non-http protocols in Palm OS Garnet 5.4

I made a mobile website for my petsitting business, and amazingly, it seems to work on everything. Palm TX/Treo/Pre (jQuery panels don't work but even the marginal javascript link functionality wasn't expected to work in blazer), Blackberry OS 5.0+, Windows CE, droid, iOS, etc. Unfortunately, however, after dragging all my old testers out of the closet and opening the browser, I noticed that my TX running Palm OS 5.4 can't open the mailto: or tel: links on the contact us page. Blazer simply says "unknown URL: tel:" or "unknown URL: mailto."
I know PalmOS 5.4, released in 2004, is the Windows 98 of mobile OS's, that is you're amazed at what it can still do but things still look weird and broken. However, the TX was also the best and possibly last million-selling PDA, and most are still in use. Many of our professional clients, whose pets we take care of while they're on business trips, have a Palm TX or Tungsten, Gen1 Blackberry Bold, or both. Most of our clients who complain about not having a mobile site use Palms or Blackberries, so I don't want to design something that only works on Android, iOS and BB10. The market share is infinitesimally small, but it seems every single one of the users is in our client portfolio.
So, since basic javascript, as in image swapping and ID scrolling, seems to work in Blazer, but that's about all it can handle, no jQuery or Fancybox, is there a javascript hack to open the Dialer or VersaMail apps without using the URI protocols? If not, is there anyway I could do this, or will I just have to add a useragent-conditional popup telling Palm users to open the app and enter the data manually?
There were originally official APIs for most of these apps, including supported URI schemes, and there's probably a simple proprietary protocol I can do this with, but when palm folded in 2011 they took all the contents of their website with them. The APIs are no longer online and there is no google cache, so I'm looking for a universal hack. But if someone does know where the APIs went that would be great.

PalmOS
I know the site, I think it was this onethat developped Palm Os Garnet 5.4 sometime ago.