Related
I would like to add the fonix voicedial application to my XDA2. I noted on the "my-xda.com" website that this application is supposed to be on the companion CD that comes with a XDA2.
Not mine!, purchased just 2 weeks ago.
My CD version is V1.0 sept 2003
Can anybody tell me if there is a later release that has it on please.
Can't see anywhere on the O2 websites where to download it.
Any suggestions would be greatly appreciated.
Regards
Chris
You can dowmload AppsuiteXdaII.zip from here.
You can dowmload AppsuiteXdaII.zip from here
Click to expand...
Click to collapse
Thanks I updated rom and installed the applications, works a treat.
Just got to re-install tomtom.
Thanks again
Chris
Two questions :
- Is it free ?
- Does it work on Qtec and T-Mobile MDA too ? (the app_suite_.exe i mean )
Yes its free,
I would assume it would work providing you are running the updated Rom.
I had to update to 1.72.00 WWE, before I could install the appsuite.
Good luck
Chris
That's weird, I'm running on 1.72.00WWE and it does not let me install...
Any ideas?
Rayan, did you try installing to a bare configuration, ie before restore?
It is not the OS version that counts (although it probably would have to be 1.72.00WWE) , but the extrom version (1.72.181 / 1.72.187). but i don't know which registry entries are important for this validation.
Doing a restore after upgrade does overwrite the registry (like cruisin implied).
Can anyone post the individual cabs inside this application suite?
I can have a look to make it more "ExtROM version independent"
(ie that it will also work with my 1.72.902 ROM)
I tried to create the myself from the appsuite.
Fonix cab seems to be faulty. Any experience with this?
Couldn't it be possible to just install the Fonix Voicedial on just any rom available?
That shouldn't be a problem is it?
edsub said:
Can anyone post the individual cabs inside this application suite?
I can have a look to make it more "ExtROM version independent"
(ie that it will also work with my 1.72.902 ROM)
I tried to create the myself from the appsuite.
Fonix cab seems to be faulty. Any experience with this?
Click to expand...
Click to collapse
I am not able to install any of this software.... Please Edsub maybe you can do something...
I am more than happy to sort this out, BUT: I need to get hold of a correct Fonix cab file. The one in the posted app. suite is faulty and cannot be used.
ah, logging on helps.
Thanks superperry.
i will have a look at the cabs.
bollocks!
The Fonix cab you posted is faulty too.
The cab identifies as a ZIP cabinet, instead of a WinCE Cabinet.
Also WinCE Cab manager is not able to open it, just crashes. Same as with my copy of the Fonix cab.
The other two cabs are fine.
Just by looking at the TrueFax cab I bet the version checking is doen via a new setup.dll. This should be do-able. Plz have a little patience as I do have a real job to do too . . .
edsub said:
bollocks!
The Fonix cab you posted is faulty too.
The cab identifies as a ZIP cabinet, instead of a WinCE Cabinet.
Also WinCE Cab manager is not able to open it, just crashes. Same as with my copy of the Fonix cab.
The other two cabs are fine.
Just by looking at the TrueFax cab I bet the version checking is doen via a new setup.dll. This should be do-able. Plz have a little patience as I do have a real job to do too . . .
Click to expand...
Click to collapse
:twisted: I guess they gave us faulty file, huh! :!:
Don't worry edsub, we can wait. :wink:
This is the file downloaded directly from O2.
Thanks dcs, the file you posted is exactly the same as the one I extracted the cabs from . . .
Did ANYONE try to get the Fonix Voicedial to run on their Himalaya??
What happened?
Did the install on the Himalaya run?
Did the app itself run?
Any error messages?
This Fonix cab is something different from all the other cabs I know of.
BTW: dcs, did you get Fonix installed (you seem to have a new 1.72.187 rom version on O2)??
edsub said:
BTW: dcs, did you get Fonix installed (you seem to have a new 1.72.187 rom version on O2)??
Click to expand...
Click to collapse
Yes I did. It runs, but haven't done much with it yet.
mmm, I guess we have to conclude that O2 (or Fonix) have found themselves a new method of installing software on the Himalaya . . .
@dcs: Do you remember whether the install ran as silent as other (normal) installs on the Himalaya? Did you see the zip-manager get used for installing (I ask this because the Fonix cab shows up like a zip-type of cab, instead of like a WinCE cab)
Hi,
Since the drivers in Magician is reputed to work for SD Wifi+256 card, I've been trying to replace the drivers.
There has been a couple of workarounds I've been trying. Insofar, I've only managed to get the Wifi working, but not the Memory part.
I was hoping that registry experts here can impart some knowledge on the stuff. Or better still, perhaps someone has the updated drivers can post it here? :wink:
Anyone has BSQUARE SDIO driver 1.2.0.0 in their Himalaya?
I'm having the 1.1.0.0 version on my 2.06 ROM, but the Magician version is 1.2.0.0. Does anyone has the 1.2.0.0 in their Himalaya ROM?
so you can use a sd wifi 256 mb Sandisk with a xdaII but only in wireless?
If yes, please post the driver pleaseee
l0rdsheva said:
so you can use a sd wifi 256 mb Sandisk with a xdaII but only in wireless?
If yes, please post the driver pleaseee
Click to expand...
Click to collapse
Here it is. It is to be used in conjunction with the PegasSDN.dll supplied by the sandisk pocket pc 2003 drivers for the combo card.
If you are able to use WinCab Mgr, you will find that the sandisk pocket pc 2003 drivers has a SDBusDriver12.cab inside. That also contains a copy of SDIO 1.2.0.0 drivers dated Feb 2004.
Anyhow, be forewarned that the new drivers is not that compatible with XDA2 device and will disable flash storage (means that your "Storage Card" folder will be gone). Not a very good trade to enable wifi using the combo card, if you asked me.
My pocket pc doesn't allow me to overwrite SDBusDriver.dll. Any idea?
yap said:
My pocket pc doesn't allow me to overwrite SDBusDriver.dll. Any idea?
Click to expand...
Click to collapse
I still wouldn't recommend trying it. But what the heck, remember to backup your files and be prepared for hard reset.
go to your registry and edit:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDBusDriver]
edit value "Dll"="SDBusDriver.dll" to
"Dll"="SDBusDriver.bak"
cold reset
copy the new SDBusDriver.dll over (it will override the function of the original version, but will not remove it).
cold reset
Storage card folder is disabled (as new SDBusDriver.dll is incompatible with XDA2, I reckon).
Install Sandisk Wifi+256 combo software from www.sandisk.com. This will provide the Wifi software and SDIO multi-function drivers for the SDIO slot.
Alternatively, if you know how to operate WinCAB mgr, replace SDBusDriver.dll in SDBusDriver12.cab in Pegas2577.cab of Sandisk Wifi+256 combo software. You can just install the Pegas2577.cab and all the required drivers and registry settings will be set automatically.
Sandisk combo card Wifi will work fine, even though Storage is still disabled.
I did tell ya, no point right?
But if someone can make both function works, I will have utmost gratitude. In fact, I'm waiting for my fantasy to happen - that some kind soul in MS or MS partners will release an updated version of WM2003SE ROM for XDA2 - complete with new SDIO drivers, BT stack and WMP10 mobile????
Can someone help me with this please:
I have just upgraded my M1000 to WM2003 SE using the guide on this forum. It all works perfectly apart from when I try and install an extended ROM - from the same sit...it tells me this:
'The program you have installed may not display properly because it was designed for a previous version of Windows mobile software'
The problem is the TP is inactive at this stage...so what can I do to continue the installation?
Thanks
Hi
That's preety sh...y situation.
One way to get around this is to edit your installation CABs with WinCE CAB manager and modify their winCE version information (so WM2003SE doesn't say they're old). Or: (simplier) just remove tpdisable.exe and tpenable.exe from extrom (or from config.txt if you have any in extrom). that will cause touch screen not to be disabled during extrom cabs installing.
Have fun.
If you're having problem in getting out from situation you're in, just put device in bootloader mode, place in cradle and reinstall Extrom with original shipped update. (you can delete nk_.nbf and radio_.nbf so that upgrade utility installs only extrom from ms_.nbf)
have fun.
Nice one thank you.
Hi fellas.
I was wondering if anyone here can see if there's a way to extract the iPAQ audio from hp rw6828 (from the extended ROM, etc) and right into the Atom?
I just tested HP yesterday, and I think it really improves the bass well without cracking up the sound!
Thanks!
audio.cpl file from rw6828
here is the .cpl from rw6828,
i havent got atom to try it on. copy the file to your windows folder then restart. it should be in your setting, system.
i am not able to copy the cpl file. says permission denied.
Thanks klikman!
The file is in "hidden" status, and which is why you can't copy it through activeSync. I copied it onto my miniSD card through an external writer, then used Recso explorer (with "show hidden files" setting) and copied it onto Windows folder.
The icon appears under settings, but your settings are not saved when you open it up next. Importantly, the audio controls don't work at all. It's merely a control panel, which seems to be controlling something which is still missing Perhaps something more to be extracted from the iPaq? Any idea how to view the extended ROM? it might be there.
probably a few .dll files
can you U/L the HP rom, i wanna try to install it my Atom.
audio file from ipaq rom
using card export in atom, you ll be able to see the extended rom, but in ipaq, we cant. my guess is there's no extended rom
the main memory size in ipaq 6828 is 58.5MB compared to atom, only 43 mb or so.
the extended rom in ipaq is merged with the main memory, 58.5MB!!!!!! that's the biggest compared of all pda phones.
whats atom's total program memory size? in ipaq, got 52.4mb.
here i upload all audio files from ipaq 6828. try it on
Copied the 2 dll files into windows directory.
Does not work
Re: audio file from ipaq rom
klikman said:
using card export in atom, you ll be able to see the extended rom, but in ipaq, we cant. my guess is there's no extended rom
the main memory size in ipaq 6828 is 58.5MB compared to atom, only 43 mb or so.
the extended rom in ipaq is merged with the main memory, 58.5MB!!!!!! that's the biggest compared of all pda phones.
whats atom's total program memory size? in ipaq, got 52.4mb.
here i upload all audio files from ipaq 6828. try it on
Click to expand...
Click to collapse
They have absolutly same ROM & RAM size,unlock hiden partition on Atom and you'll get missed 16.5mb,43+16=59mb.After all its exactly same devices inside.
I guess the whole audio player has to be exported. Thats the application that does the sound effects.
Why stop there? I'd love to see if it's possible to use the HP ROM on an Atom, and if there's anything to gain by it!
Well id personally like to put the Atom ROM on my RW6828.
The HP ROM has a few issues that need address, mainly just performance with games and unlocking the speaker to go louder would be nice.
I want to try this but if I was to attempt to put the Atom ROM on the HP wouldnt I just get an 'incorrect device' error?
Probably. But you could try entering bootloader mode before you try. That may help.
Well I cant try anything until HP release a ROM Update anyway, because I dont believe there is any download links to the default ROM.
All a matter of patience I guess, no doubt theres someone else out there with a 6828 thinking the same thing...
I like the way the Internet sharing works on the new ROM, with simply starting the program and plugging it in. Is there anyway to make this work for the old ROMs?
Thanks, Lew
P.S. I just cant stand the loss of soooo many hardware buttons on the Cing rom. I may try the test rom =)
havent tried this as it is embedded into the OS, not sure of the dependicies required also... i will do some testing tonight for you and let you know... have you tried copying the exe's from the new rom onto your old one and running them?
i was looking into this this past weekend and tried to get internet sharing off the new cingular rom working on the softbank rom (aku2.6). first of all, you can't just copy the files directly from the \windows dir, you have to unpack the os.nb file and pull the files off that way. i don't know what the dependencies are either so i just pulled four files:
intshrui.exe
intshare.dll
intshrui (shortcut in \windows)
internet sharing (shortcut in programs)
and two registry settings.
i put it all into a cab (attached) and tried to install it on the softbank rom but no go. i get an error that says something to the affect of "intshrui.exe is not a valid pocket pc application". i'm not sure if that means i'm just missing needed dlls or if the executable itself is hard-coded to look for an aku value > 3. if you guys figure out what dlls are needed, let me know and i'll update the cab.
Unfortunately, it can't be THAT easy - the BT stack has also been heavily modded in AKU3 to include the BT PAN (and to get rid of BT DUN) profile. Try including the MS BT stack-related DLL's too.
I dont "need" it to work over bluetooth (although it would be nice) I would settle for usb.
lewcamino said:
I dont "need" it to work over bluetooth (although it would be nice) I would settle for usb.
Click to expand...
Click to collapse
but i believe that the application has bluetooth dependencies so inturn will not load...
Has anyone managed this? I'd be interested in whacking this onto my Works's M3100 which won't get AKU 3.3 / WM6 until:
(a) Orange UK release it
(b) the IT chaps sign it off
Soooo the day after never !
I have a Softbank X02HT (a HTC Cavalier Smartphone) - they cripple Internet Sharing by removing the required bits (so that you have to pay big bugs for PC data).
I got the files and registry keys installed and I can see the GUI, but the content of the selection options for "PC Connection" and "Network Connection" are blank - (the values are missing)...
Has anyone else got this working yet?