WM6.1 Running BBConnect 4.0.0.90 GOOD - JASJAR, XDA Exec, MDA Pro ROM Development

Ok,
So I got the Universal yesterday and spent all day trying to get BBConnect to run on it and after searching for days and days I was able to piece things together to get it to work. So here are the links to the tools I used and as far as I can recall the steps I took.
ROM: DFT WM6.1 19174
http://www.darkforcesteam.com/showthread.php?t=133
HTC64 Tools (to convert the nbf to a fat file)
http://forum.xda-developers.com/attachment.php?attachmentid=25416&d=1133971744
HEX Editor
http://www.rs.e-technik.tu-darmstadt.de/applets/frhed-v1.1.zip
BBConnect software
http://rapidshare.com/files/45075798/BBConnect_WM6_Professional_BB_4.0.0.90.exe.html
HTC NetworkWizard cab file
http://forum.xda-developers.com/attachment.php?attachmentid=80495&d=1207858578
Ok so here is what I did
Right click the ROM file "DFT.U.V1.WWE.rar" and extract this will put the files in a folder "Outputfile" containing the following files:
EnterBL.exe
GetDeviceData.exe
ROMUpgradeUt.exe
RUU.dll
UI.dll
nk.nbf
Next extract the HTC64 Tools folder this will allow you to launch:
HTC64 Extended ROM Tool.exe
Double click it and choose decode
point to the nbf file and choose extract
This will creat the following files in the "OutputFile" folder:
nk.fat
nk.prj
Now install the hex editor and launch it, then click Open to open the "fat" file
along the top of the address bar is a set of binoculars click on that type "HTC" and check the Unicode box change the letters Univer to Hermes the remaining letters sal change to ...
save the file
Use HTC64 tools and encode the file, then update your universal
Run the network wizard cab file, reboot, configure for your provider
Install the registry editor and go to the following location
HKLM/System/Version/AKU change it to .0.3.1 (yes that is a . at the begining)
Reboot
Ok now your ready to install BBConnect
I was able to connect and have been connected for about 5 hours now.

i was actually trying this out a couple days back with Tomal (Ranju) latest rom.
i got the client to startup but couldn't connect.
figured it's a problem with my account, which i gotta check with the network provider.
but can you explain why you had to edit the ROM to change the Universal to Hermes.. and the AKU version to 0.3.1?
does the BBConnect software check for these and refuse to work if they're not matching?

I read on a post that it had to do with the model of device that was sent to authenticate with the BB servers, the ROM edit from the information I gathered sends the device type as a HTC-Hermes which is an authorized BBConnect device.......

What's the chance of getting the BB connect software running on Tomal's 7.6 ROM by performing the same search-and-replace as you did? Or does it have to be the ROM you used?

Related

BtT: Easily customizing your splash screen for JAM, PDA2k

What you'll need:
CAB editor, such as OCP WinCE CAB Manager
Madkat's WM2k3 Boot Image Tool (attached)
Adobe Photoshop or other image editor
a compatible HTC device such as the Magician or Blue Angel
Summary:
Customized SplashX.nb files to be installed in \Windows directory of your device
Included:
Customizable Splash2.psd file for use with Adobe Photoshop
Steps:
1. Change the Splash2.psd file as necessary, then save a 24-bit BMP file called Splash2.bmp.
2. Use Madkat's Tool to convert the BMP file to an NB file.
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
4. Save the CAB file and run it on your device!
Magician devices have only one splash screen, and it must be saved as Splash2.nb.
Blue Angel devices have two splash screens, Splash1.nb and Splash2.nb. Use the above steps to incorporate both splash screens as necessary.
Splash screens will be retained even after a hard reset, so use this after the Anansky's Big Storage hack, or if you just want to personalize your device, such as in the unfortunate event that it's lost or stolen - unless they know this trick, they won't be able to get rid of it!
Have fun!
Thanks mate works like a dream!!
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
PS. I've have both tools on my pc and can repost them, but they are from this site!
hshortt said:
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
Click to expand...
Click to collapse
Tried that way myself a while ago but for some reason it refused to work for me? (could of been the fact i used a file called XDA2_bootimage_changer.CAB)?? anyway now I can use self contained cabs so I make some splash's for my friends
PS. I've have both tools on my pc and can repost them, but they are from this site!
it must be me, but what cab file are we using here ?
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
Click to expand...
Click to collapse
:?: :idea: :!: :?:
DOH! I forgot to include the file. It's there now in the top post.
3. Use the CAB editor to replace the Splash2.nb file with your version. WinCE CAB Manager may state an "Unspecified Error" when replacing the file. Instead, delete the original file, then drag the new NB file into the CAB file, hardcoding the \Windows folder as the install destination.
well, i'm using resco file explorer. i'm choosing on my pc to send the file to windows directory. he ask's me if i wanna overwrite it, i click yes and then it's done. i'm reloading, but still qtek logo on the screen(( what am i doing wrong?
ps. i tried to use WinCE CAB Manager but i didn't figured out how to use the program....
update:
oh, i needed to use a different file...
thanks guys! well done)
my version (unfortunatelly understandble only for russian speaking users) but maybe somebody will like it)
http://zhgun.ru/pics/i/draw/jamming_.jpg
http://rapidshare.de/files/2112736/jamming.cab.html
hshortt said:
Maybe it's just me, but I've read this post here and at Howardforums and I'm clearly missing something.
I've only ever used the nb_image_converter_859_418.exe to convert "any" bmp to the Splash2.NB file.
Then I drop that into my Windows Folder and use MDA3_bootimage_changer2.cab to apply the file. (Yes I'm using a Magician with this file!)
Soft reset and that's that. No need to do any cab file editing.
Cheers
Howard
PS. I've have both tools on my pc and can repost them, but they are from this site!
Click to expand...
Click to collapse
hi, can't seem to download the attachments, could you repost them?
If you don't like Bill's Stuff...
I wonder if anyone can put some help my way.....
I used the xda2 image changer before and I had custom images on my XDA2.
I use this and all I get is a black screen on startup. If I open the .nb file with the converter it shows as it should. (this same .nb works on my XDA2!)
I now have a plain black boot up screen!!
DOH!!!!
Any ideas......?
THanks
First i had the t-mobile splash... wich i didn't like.
Now, whatever bootsplash cab i make, or download here.. after running it, my bootscreen stays blank ( as in black ).
oh well... its an improvement over t-mobile pink
( or is it because i'm running an ancient rom : 1.01.00 WWE ?, only have the device for 3 days... will be upgrading this weekend tho )
Here are my 2 favourites Splashscreens.
The blue one ist for the silver Magician, the darker one is for the new O2 XDA mini (black edition).
Hi I've editted the o2 logo here's the jpg file
I tried to upload the psd so you can edit it but it doesn't work, to bad!
Step-by-step making your own splashscreen
Guys,
Simpler than this you will not find.
Goto
http://pocketpcdubai.infopop.cc/groupee/forums/a/tpc/f/582600994/m/138105069
and find everything you need to know.
It worked perfectly for me...
Excellent information, real easy to do
this is mine:
Awesome...
I saw this before, but I have just tried it... and it is really cool 8) ... it gives the device a whole new look...
thanks BTT
My way to splash changer.
Hi,
I thanks to BTT for Splash Changer how to. But it is troublesome to everytime run WinCE cab manager in order to put Splash2.nb to the .cab file.
I try to remove Splash2.nb from the .cab file (and renamed the .cab to splash_changer.cab). Afterthat, put the Splash2.nb manually to \windows on PPC. Voila....., no need to everytime run WinCE cab manager!!!!!
Process:
1. Edit .bmp file to your like (Must be 240x320 pixels, 24bit).
2. Use nb_image_converter_859_418 to convert .bmp file to .nb, and change the .nb file to Splash2.nb.
3. Put Splash2.nb file directly to your \windows on PPC. You can do activesync and explore it.
4. Put splash_changer.cab to \temp for you to easier found it.
5. Run file explorer on PPC, and tap on splash_changer.cab.
6. Done! You can check by soft reset the PPC.
Hope it is helpful!
Regards,
Arto.
can it work on normal pocket pc?
can it work on normal pocket pc? (x50v)
Re: can it work on normal pocket pc?
avi9899 said:
can it work on normal pocket pc? (x50v)
Click to expand...
Click to collapse
No idea....
Regards,
Arto.

Share your OEM Packages for Faria ROM Kitchen

Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool. Use ftp://ftp.xda-developers.com/Uploads/WIZARD/ROMS/Faria WM6 ROM Kitchen.pdf to read up on how to create OEM packages and how they work.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
When you provide the packages, try to provide it with the original package.rgu and/or package.dsm filenames (not with the GUID that was generated for you). People will then be able to just run the buildos.exe and the GUID will get created for them without changing filenames. Then just edit the options.xml file to use the newly generated GUID.
so screenshot + cab + short info + status: freeware/shareware/etc. would be fine?
mfrazzz said:
Hey all,
So that we don't all have to reinvent the wheel, is it possible where we could share OEM Package setup info to be used in the Faria ROM Kitchen. I know a number of your are adding your own packages, and this could save a lot of work for those of us just starting to look at customizing this tool.
What I'm thinking is that this thread could be a repository for packages (not for requests, but for packages people want to share). Bascially you would reply to this thread with what the package is for, and any special information and setup (or things people may want to look at and change), and then attach a zip file (or pointer to the package file) that people can then download and put into their devwiz folder. If its for a commercial (non-free) program, leave out the commercial program / dlls but just to have the other files setup and instructions on what to put into the folder could be very useful for people.
The only tricky thing here would be the guid for the files. I'm still new to this, so if someone has an idea how to handle that (maybe the person does the package.rgu and runs the program where it generates the guide, then unzips the files and modifies the guid to the new one in the right places).
Click to expand...
Click to collapse
The GUID is so simple, if you to use a package, just go to http://www.famkruithof.net/uuid/uuidgen . Then you just get a new GUID and paste it in all the different palces in the package, then you dont have to chnage file names then have them chnaged again by buildOS
I thik this is a good idea, would be good to share and also good for problem finding, cus i have one that i cant for the life of me get the today plugin to work how it is meant to!!!
GSFinder Package
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for GSFinder. This is a freeware file manager (like TotalCommander).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
MoDaCo NoData
[... This package has been updated and can now be found in post 23 of this thread ...]
This is a package for MoDaCo NoData. This is a freeware program that allows you to turn off and on what data sources will work on your device (so if you don't have a GPRS plan, you can turn off GPRS so your phone will not use it).
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
mUn Keyboard Skin
This is a package for the mUn keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is in the mUn aRTM WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
XPlore Keyboard Skin
This is a package for the XPlore keyboard skin. This is a freeware skin file to modify the look of the on screen keyboard to be like what is provided for the XPlore 2.0 WM6 rom.
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
NOTE: If you have other keyboard skin files in your OEM directory, you may get an error when you build this initially (or if more than one is selected). You can only have one of the keyboard skins selected.
mfrazzz said:
To use this, unzip this to your OEM folder. You will then run buildos.exe and press the green arrow to have it process. After it completes exit buildos.exe then edit the options.xml file and change the GUID to match the one that was generated for the .dsm file in this folder.
Click to expand...
Click to collapse
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
I'd noticed this when I was building another package. In my experience, I have to do a build without the options file, let the [GUID].dsm file get built, then create the options.xml file with the correct GUID in it and then rerun.
saeba said:
Thanks for putting this together!
I tried building via your instructions, but got an error (buildos.exe crashed). I deleted the options.xml file and then re-ran the build and it worked. Then copied back in an options.xml file and edited the GUID and it ran fine.
Click to expand...
Click to collapse
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
mfrazzz said:
Yep I figured this out an hour ago. The options.xml should be renamed until the first run of builos.exe completes, then rename it back and change the guid inside the file.
I'll redo the packages tomorrow and update the instructions on them.
Click to expand...
Click to collapse
Can i jst say that the chnace of the same number being used again in you kitchen is really high, so you should not have to chnage it!!! Try run the buildOs without chnaging anything!
Has anyone figured out how to move files yet?
RickoT said:
Has anyone figured out how to move files yet?
Click to expand...
Click to collapse
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Battery Status Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Reposting with generic Registry Entries (removing ADB100's custom settings he mentions in his post below)
WM5torage Package
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
mfrazzz said:
Here is the package for Battery Status. I initially put this together but had some errors in how I did things. Thanks to ADB100 for cleaning it up! This is the same one he reposted for me in the Faria Rom Kitchen thread.
ALso going with Funman's point that its unlikely to hit a duplicate GUID, so I'm leaving the GUID alone. So just extract to the OEM directory and you are ready to go.
This package contains Battery Status 1.04.202 Beta 3 Build 0195 (latest version at the time of this posting).
Click to expand...
Click to collapse
I should note that it is pre-configured with the following options:
General Tab - Show CpuSpeed, Show Mobile Operator
Indicator Tab - Show more Indicators, Use Small Fontsize, Show Powerdrain, Show Temperature
Tools Tab - DeviceLock on Wakeup, Lock if Display..., Backlight fix - 30-seconds
Omap Tab - Overclock to 247Mhz, Overclock on Wakeup, Remember last CpuSpeed, Overclock after reboot
Traylaunch Tab - All disabled
Not sure this will suit everybody so be warned...
Andy
Adobe Reader LE
[... This package has been updated and can now be found in post 23 of this thread ...]
Package for Adobe Reader LE. This is the "faria Adobe Reader" cab thats been posted, but then I've altered the .rgu to fix the registry entry for opening docs that have spaces in the name (Thanks ADB100 for pointing that fix out), and made a couple of fixes to the initflashfiles.txt (it had moves for files that didn't exist and I've added where it moves a shortcut into \Windows\Start Menu\Programs\Accessories
Just unzip into your OEM directory.
ADB100 said:
I should note that it is pre-configured with the following options
[... snip ...]
Not sure this will suit everybody so be warned...
Click to expand...
Click to collapse
I've reloaded the zip file in my post above for Battery Status and put the registry entries back to generic like a fresh install. If you want specific settings, then install BS, tweak it to your heart's content, then dump out the registry entries and replace them in the .rgu file.
mfrazzz said:
Package for WM5torage (version 1.73). Just unzip in your OEM folder.
Note, the package puts a shortcut in the \Windows\Start Menu\Accessories folder for WM5torage. Edit the initflashfiles.txt if you want the shortcut to be located someplace else.
Click to expand...
Click to collapse
Sorry mate but your package is not right! The .rgu was not setup right!
funman said:
Sorry mate but your package is not right! The .rgu was not setup right!
Click to expand...
Click to collapse
Arrrgh! Sorry about that. I was putting that one together and got interupted with a concall at work, and some other things. I went back to working on it, and I guess I didn't edit and fix what I thought I had done... Sheesh...
Thanks...
mfrazzz said:
The initflashfiles.txt moves the files (doesn't just make duplicates). So you just have to put a line in for everyfile to "move" it to a different location. The next post will be for BatteryStatus and you can look at that one as thats what it does. All the graphic images are moved into a directory it creates.
Click to expand...
Click to collapse
Are you sure, because I think I read in faria's rom thread that it copies the files, not moves them, (Unless im utterly retareded and misread it, which is very possible)

Wizard + WM6 + BBConnect setup help?

Hi guys,
I've been going nuts trying to get my wizard working with my bbconnect account. Can you guys give me a hand? Here's what I'm running as of now:
IPL/SPL 3.08
GSM 2.69.11
OS 10.1.0.811 (Jaguar 3.1)
BBConnect 4.0.0.67 (also tried 2.1.2.16 and 2.1.2.54)
I've read so many threads and tried so many roms but to no luck . I can't seem to establish a connection. I do, however, got a pin
CookieKid said:
Hi guys,
I've been going nuts trying to get my wizard working with my bbconnect account. Can you guys give me a hand? Here's what I'm running as of now:
IPL/SPL 3.08
GSM 2.69.11
OS 10.1.0.811 (Jaguar 3.1)
BBConnect 4.0.0.67 (also tried 2.1.2.16 and 2.1.2.54)
I've read so many threads and tried so many roms but to no luck . I can't seem to establish a connection. I do, however, got a pin
Click to expand...
Click to collapse
Same problem here since a couple of months...
You will be lucky if find an answer on this... I'll be monitoring this thread closely....
bumpity-bump
BBC4 will not work with a wizard. You'll have to unse version 2.1...54.
But first of all you have to hex edit the rom. Search the forum. It is easy to hex edit the rom.
aren't you suppose to use a specific configuration (ROM/Radio/BBC)?
No.
Actually I use NBD 9.1 Version rom 5.2.1620.
You must hex edit the rom to Version 5.1.195. This have no effect to the use of the rom. You can use every rom version but you must hex edit the rom to 5.1.195!
Before installing BBC you have to edit the registry HLM/system/versions/AKU-String to ".2.0.0" and do a soft reset.
Then install BBC 2.1.2.31 or 2.1.2.54 and it will work!
Any BBC 4.x version wil not work.
Radio version doesn't matter. I use 2.19.11
Do you need help to hex edit the rom?
Please tell me step by step how to hex edit a rom. Also, I can't seem to find the registry string that you are referring to ie. HLM Thanks
ROM Version 5.2.1620 (NBD9.1) and BBC Version 2.1.2.31
1) Use the attached decode prog to decode your nk.nbf file (decode.exe -x nk.nbf). After that you'll have a file to 8004000-os.nb.
2) Use Winhex or a diffent hex editor to edit the 8004000-os.nb file.
For ROM Version 1620 search for hex
653EA0E3043083E3452FA0E30510A0E302 and change it to
0C3EA0E3033083E3452FA0E30510A0E301 . This results in the new Rom Version 5.1.195. For your understanding:
Version 1620 in hex 654 and Version 195 in hex 0C3
3) Save the file (maybe you can choose a new name)
4) Start nb2nbf.exe.
5) click File1 and choose the hexed file. Leave the CID, Operater Version, OEM Version blank!!!!!!!!
6) Enter Start adress 80040000 and choose Image file OS
7) press translate and exit
8) Flash new ROM to your Wizard.
9) When installation finished change the registry HKLM\System\Versions\Aku to .2.0.0 and make a soft reset
10) Install BBC 2.1.2.31
That all
View attachment decode.zip
View attachment nb2nbf.zip

How can i integrate the serial to cab file

Dear masters?
Now, I have one soft for PDA (exp: resco exploer 2007) with the serial that both are seperated each other. How i can combine both of them into one file, i want to use one file only to install next time in full version (no need serial agin). Pls help me!
Rattana
Rattana said:
Dear masters?
Now, I have one soft for PDA (exp: resco exploer 2007) with the serial that both are seperated each other. How i can combine both of them into one file, i want to use one file only to install next time in full version (no need serial agin). Pls help me!
Rattana
Click to expand...
Click to collapse
if you have a file.exe. you must install that file on PC to your pocket PC by activesyn. during your installing you must enter the serial to register.
when finished. go to C/programs/activesyn you 'll file the cabfile for using in the future.
Found It Yesterday
Found This When Cooking My Rom Yesterday...
When You Register Resco Explorer 2007,
It Creates A File In The Windows Directory Called "Wmtrigger.dat"
Register Your Copy Of Resco 2007 And Then Copy That File From Your Device Into Your Cab.
Regards,
OllieD
There is no standart for sharewares
Every softwares has different methods to registering.
Somen's uses registry
somen's uses an encrypted data file
somen's patchs a file.
And you must use a cab editor for ( I can't give the links and names here )
which softwares have you crcked exe / registry keys to add or replace in cab file.
meanwhile...
this method is not always useful.
and not legal ( also your legal payed soft's too )

extract NBH from EXE

Hello,
I want to (re)flash WM6.1 from microSD, but can´t find a nbh. Flashing in softmode will hang up and freezing my screen on the tricolour.
Extracting from RUU_Kaiser_HTC_GER_3.28.407.0_radio_sign_25.83.40.02_1.65.16.25_Ship.zip
will create an exe-File.
Any chance to get out a kaiserimg.nbh from the exe or any link to a german WM6.1 Rom /NBH?
Regards
Check the Kaiser Wiki instead of starting a new thread. There're repositories for many versions of OEM ROM.
Of cause I´ve done this before. But the german ROMs I´m looking for will be extracted as exe-files, I couldn´t find the necessary hints.
Try open the exe using Winzip. You might see the NBH there.
Edit: I tried running the Kaiser_HTC_ASIA_HK_WWE_3.34.721.2.exe I have, it installs there should be folder containing RUU_Signed.nbh (your temp file folder?). Use this file, rename as KAISIMG.nbh and flash using SD method.
Get Uniextract, then right-click on this installshield wizard and select "Uniextract to subdir" .
Uniextract can do thousands of formats. It's nice program lol.

Categories

Resources