Related
Guys, Have been searching the site for a couple of weeks now and cant find a solution to my problem.
I work for a company that deals with alot of XDA2 units, so far I have managed to develop a custom extended rom that works fine, but have not been able to find a way to remove links from the start menu and the program menu. seen several threat on the site but no solution. The links have to be removed if a hard reset occurs. At present It has to be done by cloning an image onto the unit (1600 in total)
Any help would be appreciated.
popeye
I would love a program which based on a txt file would "delete","rename"... files and/or registry.
Something that could be executed from config.txt
there was a thread about a .bat interpreter but i don't think they got it working.
M4io said:
I would love a program which based on a txt file would "delete","rename"... files and/or registry.
Something that could be executed from config.txt
there was a thread about a .bat interpreter but i don't think they got it working.
Click to expand...
Click to collapse
I'm using Restorator utility (search through the forum) to do the aforementioned things and much more. Works flawlessly with new Second Edition rom
thx, I completely forgot about that utility. I will defenitely give it a try
http://forum.xda-developers.com/viewtopic.php?t=9333&highlight=restorator
I finally found a method for backing up and modifying the Extended ROM on an XDA2i device.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=373&PN=1
Unfortunately, although this method is able to do most of what I want, some of the cab files do not self-extract successfully during the reset process.
Graham. -- Issue resolved. No spaces allowed in Cab file name --
Before you ask, yes the cab files do self-extract successfully if tried manually (i.e. outside of the reset process).
If anyone has any ideas why some cab files work and others do not, please let me know.
I played with the information in the article yesterday.. Some information in the article is incorrect. They state the ext. rom is 24 MB but when following the steps on the website this is incorrect !
Sure, extra drive reports a 24 MB drive but the what's backuped to the SD card doesn't include the whole 24 MB the ext. rom supposedly has !
What I'm typing below is more guess work than knowledge.
"d2s 80000000 3BF0000" probably means "dump to SD card" for a total length of 80000000 hex starting at 3BF0000 hex.
80000000 hex is 2147483648 in decimal. These aren't the amount in bytes that are copied.. I to honest it I have no real idea in what it are but when dividing it by 1024^2/100 you get 20,48. The / 100 is something I made up since that gives me about the amount in MBs I can put in the ext. ROM without having corrupted files. I don't want to experiment with larger values since I haven't studied the tools that are used in the article enough yet.
In short, be sure not to put more than say 20 MB in the ext. ROM and most likely your problems are solved. I personally put an executable sprite backup file in the ext ROM, packaged it in a way it will be copied to storage and run from there. It's the most effective way I could think of to fill an extended ROM. Simply with a fully installed but clean backup of the pocket pc.
Anyhow, that's it for now.
I considered it being a problem with size and reduced the amount of data in the Extended ROM by a huge amount (deleted several of the cab files that I did not need).
This reduced it down to around 13Mb for what it's worth.
All of the files installed to the ROM ok, but when the process which reads the Config.txt file reached the parts regarding two of the cabs I wanted to install, the files failed to self-extract without giving any feedback.
Several other cab files I wanted to install worked fine.
What all this means is that the problem (probably) lies somewhere other than the size of the Extended ROM.
Thanks for the post sparcle and if you find out anything more please let me know.
If anyone else can help here, please feel free to contribute.
Graham.
As above guide:
CE Rom size is 2700000 (hex)
Total backup size is 3BF0000 (hex)
So extended rom size is 3BF0000-2700000 = 14F0000 (hex) or 21,954,560 (dec)
So extended rom size shall not be over than 21,954,560 in total space.
-----------------------
But itsme's document
http://wiki.xda-developers.com/index.php?pagename=AlpineRomStructure
82700000-83f00000 extended rom
So backup range shall be 3F00000. (size = 66060288 (dec) which you can not use 64mb card, you have to use 128mb card to backup)
So sorry, I'll ask my friend ruchonburi to recheck again.
Just a quick note on the sizes you gave above:
83,f00,000 - 82,700,000 = 1,800,000 (hex)
= 25,165,824 (dec) (24Mb) for the extended rom.
83,f00,000 - 80,000,000
= 3,f00,000 (hex) = 63Mb for the whole rom
The document given at the site uses:
80,000,000 to 83,bf0,000 which may miss some of the extended ROM, which may explain my problem.
I will try using the numbers from wiki and see if it works.
Cheers,
Graham.
I tried using d2s 80000000 3f00000 to create the SD Card backup initially and I still had the same problem with some CAB files extracting successfully and some not.
Graham.
Looks like the issue may lie with spaces in the CAB filenames.
If it is I will kick myself for not realising it sooner and then post here to let you know.
Graham.
Ouch, ouch, ouch....
I've finished kicking myself.
The problem was indeed the space in the cab filename.
On the plus side it means that the process works fine.
Graham.
i just want to ask......by cooking Ext Rom....how much free space that can be use after that???? does it effect any upgrade in the future????
The Extended ROM is an area that you cannot normally write to and is not considered part of the memory (as far as I am aware) under Settings/Memory.
By cooking the ROM you can alter what applications get installed when the device is hard reset. The installed applications will take up their normal memory allocation so in that respect it will reduce the amount of memory available to further applications.
It is possible to increase the amount of memory available by cooking the ROM as there may be elements of the Extended ROM that came with the device that you do not actually want installed. This is done either by removing the relevant cab file completely or by removing the relevant entry from the Config.txt file (both should be done, but one or the other will have the same effect).
Hope this helps,
Graham.
gbird, thanks very much for that information. im sorry because asking question just about benefit, not about how and why. thanks again!
Hi fellow alpine owners
I'm keen to follow your tips and do some work in the kitchen.
I have downloaded all the relevant articles from the link provided so thankyou for that.
However i'm reluctant to take the first step with the thought of a unrecoverable disaster on my hands. MY NEW XDA2i!! So before i get started i thought i would consult the experts for any tips and traps for young players.
I've bought myself a large enough quality SD card to dump to.
I guess the aim of the exercise is to a remove unwanted programs and install some of the cool features of Special Edition ROM 1.2 including that really excellent anti theft tool.
Any assistance would be greatly appreciated, with what to remove/ install and how thanks in advance.
Miket
ROM version 1.11.00
ROM date 01/27/05
Radio version 1.03.00
Protocol Version 1337.42
ExtROM version 1.11.162 WWE
First tip, use the process to back up the ROM of the device and keep it very safe.
Since all you will be playing with is the Extended ROM (and not messing with the OS Rom or Radio Rom) the good news is that if you removed all of the files from the Extended Rom you would still be able to boot the device. This gives you an opportunity to remove files to see what they install. If it goes really wrong, you can restore the Extended Rom from the SD card backup.
The XDA2i device does have a lot of room on it for additional items so you can add in extra Cab files or Exe files if you wish. You need to modify the Config.txt file to make the Extended Rom run these extras.
As for which files do what, there is a lot of info available around this site and others and I am afraid I do not have time to go into it at the moment.
I will see if I get some time over the next few days, but work is a little hectic at the moment.
Hope you have fun,
Graham.
Thanks for the speedy reply Graham
Will endevour to make backup this evening and start chopping up extended ROM.
Any thoughts on the instructions provided by this web site.
http://en.pdamobiz.com/en/forum/forum_posts.asp?TID=373&PN=1
Obviously a highly regarded PDA hacker.
I will be working through these. It's a bumber that XDA2i is so arkward.
Thanks for now
Miket
The page is pretty good (that's why I pointed at it)
RomUpdate
The only bit that is a bit short on description is the stuff regarding using the romupdate tool at the top.
If you need a more complete description of this tool then I would take a look at:
http://en.pdamobiz.com/en/forum/PDAforum_posts.asp?TID=62&PN=1&TPN=2
Be aware that the addresses for the d2s command are different for the XDA2 and XDA2i
Rom Structure
The memory address information for the Alpine (XDA2i) is available at this site:
http://wiki.xda-developers.com/index.php?pagename=AlpineRomStructure
RomUpdate Commands
There is also a page describing some of the commands available in the romupdate tool:
http://wiki.xda-developers.com/index.php?pagename=HimalayaBootloaderCommands
XDA2 Cab Files
This site has a description of some of the XDA2 cab files which may interest you (though the XDA2i uses different cab files, some of which have similar names):
http://forum.xda-developers.com/viewtopic.php?t=6470
Soft Reset in the Config.txt File
The last bit I'm going to mention here is that the last item in the Config.txt file soft resets the device. If you remove this item for some reason then adding the line "RST: Reset" on the end of the Config.txt file will soft reset the device automatically for you.
Hope these are of use to you, I know they were all of use to me,
Graham.
Absolutely excellent thanks Graham
Have got as far as using the split tool.
Xp is throwing a 16bit error my way, so i will have to resolve that before i can go any further.
Are you suggesting that when i re-build extended ROM to include "RST:Reset" on the last line in config.txt?
Anyway it's time for bed.
Thanks for the great links, will read through these tomorrow.
Miket
With regards to the RST: Reset command, it is sometimes useful to soft reset the device at the end of the configuration.
This is because some of the Cab files will probably modify the registry and most of these changes will not be picked up until the device is soft reset (the device is still usable, just not using the changes).
Most of the builds that you may come across already do this as a last step in one of their Executables so they do not always include the reset line in the config file. Adding this line to the end will ensure that a soft reset always happens so that registry changes will be used.
Be warned, soft resetting the device will halt the configuration build at that point, so anything after the reset command will never happen.
I hope this makes some sense
Graham.
Hi again Graham
Finally sorted 16 bit issues with the PC. Have loaded SPLIT ROM and created the 3 components. Particularly ext.img
I have also created the virtual drive "X" with "ext.img"
File\properties tells me this is a 24MB file. All good until i wish to open. PC asks if i wish to format disk, i'm not able to read contents any ideas.
TA
Mike
I thought i would try downloading the cooked rom off en.pdamobiz.com as a test. The extended rom opened up perfectly in virtual drive creator. Mine however is an exact match size wise but wont open.
HMMM
I guess the next step is work out what i need and dont need in extended ROM. Assuming i can get past this stage.
Any guidance here would be appreciated.
Miket
Hello guys!
I'd like to modify my german extROM too but I have a little problem: when I'm starting the ntrw.exe (it lay in the basement of my HDD, in C:\) it closes itself!
So I mean, I can't use the ntrw.exe from the PDA-Miz guide to write the ROM-image to my HDD!
What can I do?
Thanks in advance
animelover from germany
Hi, after some research (German and Spanish ROM from HP, and dumped ROM from spgi), I present you a modest modification of prepare_imgfs which works with the ROMs is it supposed to.
Of course, the dumped ROM from spgi doesn't need it to be correctly extracted since it's a dump (and dumps are not encoded!)
to use it:
prepare_imgfs.exe CEOS.nbf -i (or -ipaqHW69xx)
and then to extract the content (a dump directory will be created):
viewimgfs.exe imgfs_raw_data.bin
Modifications "should" work but I cannot test it (I just did it for pleasure).
Of course: thanks itsme, mamaich and all gurus who share source code.
Modifications: rate=0x10089; step=0x10000; skip=0x89;
and now make_imgfs
USE IT AT YOUR OWN RISK...
make_imgfs.exe YOURROMFILE.nba -i (or -ipaqHW69xx)
Should work (tested by comparing a ROM with a decrypted and re-encrypted ROM => no change).
As addfile/delfile/buildimgfs works only in nosplit mode, the imgfs_removed_data.bin file could be invalid, so keep a safe backup of these data (just in case) and restore it before using make_imgfs. That way, the imgfs_removed_data.bin file will remain as valid as possible (if it's a CRC or sth like that... it could not work).
Try to make a very small modification (like a background image) to see if it works before cooking.
Good luck!
Need more info
Try to explain with more details.
Drahtman
I don't know!
drahtman said:
Try to explain with more details.
Drahtman
Click to expand...
Click to collapse
I don't even have a 6915!
All I know is:
-nobody made it for 6915
-based on a correct imgfs_raw_data.bin + correct imgfs_removed_data.bin + correct ROM (for bootloader and headers), you obtain a valid ROM
now you have to find how to create a correct imgfs_raw_data.bin and a correct imgfs_removed_data.bin. More informations are available on ROM kitchen making guides (all along the threads) and one of the already found methods may work (with small modifications)
I tried to make a buildimgfs, it should work but some things in the source code are obscure to me, and doesn't permit me to validate the tool...
But you can find it by yourself... I made those tools without having the device... you have the device, you could try WITH MASSIVE PRECAUTIONS! read all ROM problem threads to be sure you cleared every possible problems! Reading is the only thing important in such operations... Then try to create a ROM, see if this ROM can be dumped as an official one...
You need to try to use USB Monitor during an upgrade to see if more informations are needed (if we could be sure imgfs_removed_data.bin is useless, it would make the thing easier)
Read, Read, Read!
Many others problems (CID Unlock) seem to have be done, but nobody shares the how to, same for ROM Dump from device...
It's just sad the 6915 community doesn't try to solve their problems by themselves... I mean the community as an ensemble...
bumpity bump
Will Try Soon, And Post Results
I have did this about a 8 months ago, and got some error, my data cable is broke, so once my new one gets in I will post the results
This doesnt extract the ROM right? This lets us play with it after? We still need to find a way to extract the ROM without errors.
Backup Everything
Please man, If you want me to port a rom, I still need this with the errors,
mdelleman said:
This doesnt extract the ROM right? This lets us play with it after? We still need to find a way to extract the ROM without errors.
Click to expand...
Click to collapse
I have backed up everything I can with awizard. It is posted in your WM6 port thread pg 3. Awizard won't let me backup the radio but I have a copy of the OS. I'm not sure how we can get all of it, no one has had any luck getting a complete backup.
mdelleman said:
I have backed up everything I can with awizard. It is posted in your WM6 port thread pg 3. Awizard won't let me backup the radio but I have a copy of the OS. I'm not sure how we can get all of it, no one has had any luck getting a complete backup.
Click to expand...
Click to collapse
Try this one also, post that, in the meantime I will work with your awizard os backup.
(I posted this in the SmartPhone forum, but this is probally a better place)
I have the Verizon PN820 smartphone running wm5. I see roms for some GSM phones with wm6.1.
I would like to extract the WM6.1 from the GSM phone, and put it on my Verizon CDMA?
Is this possible? If so, is there a guide availiable that might lead me in the direction on doing this?
Thanks
yes you can flash the rom but your phone may not work after that
Well the goal is to have a working phone after the flash
So I won't be able to from from GSM to CDMA then I take it?
uhh no he just answered your question. it may flash but wont work. its like saying can u put diesel into a Corvette- sure, will it run- no.
Doh, so I guess it's no use trying it then if you are pretty sure it will brick the phone.
A Good Question
MrTek said:
(I posted this in the SmartPhone forum, but this is probally a better place)
I have the Verizon PN820 smartphone running wm5. I see roms for some GSM phones with wm6.1.
I would like to extract the WM6.1 from the GSM phone, and put it on my Verizon CDMA?
Is this possible? If so, is there a guide availiable that might lead me in the direction on doing this?
Thanks
Click to expand...
Click to collapse
I believe that the trouble lies within the hardware of a device.
Unlike PCs that have the ability to run multiple OSs phones may not share parts that, given the right instructions, allow them to work on different infrastructures (e.g., CDMA and GSM).
I've not looked into this fully but know that certain chip sets on board a device are compatible only with that type of network.
While a PC/Notebook owner can freely choose his or her ISP it is more difficult, in the Cell Phone industry, than just simply swapping a Sim Card.
I know that a certain GSM provider is looking into locking certain phones onto their network via hardware; think of the implications.
Somebody may come up with a relatively simple solder-in of a compatible chip set or, perhaps, board swap to make this happen but then the consumer would have to balance the risks, money and effort of this option over purchasing a new phone and hopping over to a preferred service.
If/when standardization trumps the proprietary then your dream comes true; but can you wait?!
To make this work, you would have to:
1. Dump your WM5 ROM.
2. Separate dump into SYS and OEM packages.
3. Extract XIP.
4. Build new XIP with WM6.1 MSXIPKERNEL.
5. Build new IMGFS with new WM6.1 SYS folder.
6. G'Reloc the entire ROM.
7. BuildOS to create a dump.
8. Use Tadzio's tools to create a .bin, then to a .nb file.
9. Flash the .nb file.
This is sure to work, but isn't simple to do. If you're new to ROM cooking in general, you'll have a lot to learn before you can even attempt this. I've been cooking ROMs for 4-months and I still have a lot to learn.
And it will not boot this way, you have to mess a lil with the kernel (nk.exe) of your original rom in order to boot WM6/6.1, but GnatGoSplat is right , you need to recook a WM6.1 rom for your device with your devices OEM drivers and software in order to work. You can not use GSM rom on CDMA device because the drivers are difrend
Hmmm....I wonder if it could be done.
At worst, If I have a bootloader in tact, I should be able to revert back,no?
I already extracted the WM5 ROM, and I extracted the XIP from a Startrek 6.1 rom already.
Yes, as long as you don't overwrite the bootloader, you should be able to revert back, but I'm not familiar enough with your phone to know for sure.
StarTrek 6.1 XIP won't work as-is, the only part you can use from it is the MSXIPKERNEL. When you use XIPPORT and click "Make Packages", you will find MSXIPKERNEL in the Files and also Modules. You would do the same thing with the XIP from your existing WM5, then replace your old MSXIPKERNEL with the ones from the StarTrek.
For both ROMs, before you do anything, do "Write Maps" in XIPPORT. Then you can compare and it will tell you if you need to relocate any modules in your device's XIP to fit the modules from the StarTrek (you'll probably need to). You relocate modules with M'Reloc.exe. You will also have to manually edit the imageinfo.txt for each module in order for Write Maps to work. After you've done that, do "Realloc P" to relocate the modules. After that, you'll need to Write Maps to make sure there are no conflicts. In Map.txt, if there are any !!!!!!!!!, that means you have a conflict and will need to try different addresses in M'Reloc.
Gnat,
Thanks for the help. I am really curious now that you say it can be done.
This is what I have done so far:
I started with the nbh file with WM6.1 from the StarTrek which I grabbed from here: http://forum.xda-developers.com/showthread.php?t=374397
I then used Dutty's NBH tool to decompile the NBH into NB
Then used the extracted OS.NB with nbsplit (nbsplit -sp?) to break apart the payload and extra.
I then tried to use the rommaster tool to extract the XIP, but I always get:
[Info] It is a common ROM.
[Error] File struct error, xip end offset is 0x77422c11, but file lengt
is 0x025a95b0.
I suspect this might be related to the nbsplit -sp parameter?
diffeent providers
Hey, what about using another providers rom on your phone? cuz for the phone I have telus has a 6.1 upgrade, while bell doesnt seem to... would that work by any chance?
thank you for any help (have been trying to find information for ages)
Danial
It can work, but usually you have to CID unlock the bootloader in order to flash another provider's ROM. I'm not familiar with Telus and Bell, but are they CDMA? If so it may overwrite some stuff like the provider setup info and PRL. You'll need to go into the EPST menu and make note of all those settings before you flash. After flashing, it would pretty much be the same procedure as getting a phone from that other provider to work on yours.
Definitely can be done though, my Touch Diamond is a CDMA Sprint phone that I use on Alltel.
GnatGoSplat said:
It can work, but usually you have to CID unlock the bootloader in order to flash another provider's ROM. I'm not familiar with Telus and Bell, but are they CDMA? If so it may overwrite some stuff like the provider setup info and PRL. You'll need to go into the EPST menu and make note of all those settings before you flash. After flashing, it would pretty much be the same procedure as getting a phone from that other provider to work on yours.
Definitely can be done though, my Touch Diamond is a CDMA Sprint phone that I use on Alltel.
Click to expand...
Click to collapse
Is there any forums, or FAQs or anything about doing this?? Bell will not release 6.1, and custom roms do not work....ridiculous that there is no support for this phone at all....
You might try http://forum.ppcgeeks.com/.
That forum seems to specialize in CDMA phones. If there's an unlocked bootloader available for your phone, then it shouldn't be too much trouble. Some providers lock the EPST menu (SPC lock I believe it's called) and in that case you'd have to find a program or method to get the unlock code to get into that menu. Dig around the PPCGeeks and you'll probably find more specific details. I only had to do it once so unfortunately I wasn't able to commit those details to memory.
GnatGoSplat said:
You might try http://forum.ppcgeeks.com/.
That forum seems to specialize in CDMA phones. If there's an unlocked bootloader available for your phone, then it shouldn't be too much trouble. Some providers lock the EPST menu (SPC lock I believe it's called) and in that case you'd have to find a program or method to get the unlock code to get into that menu. Dig around the PPCGeeks and you'll probably find more specific details. I only had to do it once so unfortunately I wasn't able to commit those details to memory.
Click to expand...
Click to collapse
Thx for the link.... but from wat iv read before my phone (HTC S720, HTC Libra) doesnt seem to have a bootloader :S....
the vox does have one, im not too sure if it would work on it or not?
and specifically this phone has no support on any website that i can see :S....
is there any guide or something as to find the SPC lock?
Thx alot by the way, your the first member whos actually replied to me about this
Danial
GnatGoSplat said:
Yes, as long as you don't overwrite the bootloader, you should be able to revert back, but I'm not familiar enough with your phone to know for sure.
StarTrek 6.1 XIP won't work as-is, the only part you can use from it is the MSXIPKERNEL. When you use XIPPORT and click "Make Packages", you will find MSXIPKERNEL in the Files and also Modules. You would do the same thing with the XIP from your existing WM5, then replace your old MSXIPKERNEL with the ones from the StarTrek.
For both ROMs, before you do anything, do "Write Maps" in XIPPORT. Then you can compare and it will tell you if you need to relocate any modules in your device's XIP to fit the modules from the StarTrek (you'll probably need to). You relocate modules with M'Reloc.exe. You will also have to manually edit the imageinfo.txt for each module in order for Write Maps to work. After you've done that, do "Realloc P" to relocate the modules. After that, you'll need to Write Maps to make sure there are no conflicts. In Map.txt, if there are any !!!!!!!!!, that means you have a conflict and will need to try different addresses in M'Reloc.
Click to expand...
Click to collapse
It's time to propose this idea.
The unbrickable ROM. Works regardless of GSM or CDMA, keyboard or no keyboard.
Technologically speaking, why can't this be worked on? Even if it takes 12-18 months, it's worth the effort and time to finally create "The unbrickable ROM".
this is the wrong place for questions,
please refer to the Q&A section
thank you
Hello,
Hoping someone could clear up a couple things for me. At my work we use the mc9090 RFID scanners which run windows mobile 6.1 currently. Currently we use motorola osupdate to push applications in a CAR file once the OS update util flashes the stock rom which are .sig files and .bin files. My question is do i have any chance of dumping the rom and if so would I be able to get it back on the device. Currently i was able to use imgfs tools to dump the os partition into a .raw files but that is as far as i got with dumping. So since they are signed files how would or is it possible for me to get them back on the device? I just didn't want to waste anymore time if i am not going to get anywhere on this. Also not saying that I would be able to use it but is package builder for wm what actually generates the .sig files?
Any ideas about how i could make this work would be awesome or any other ideas. The goal here is for us to have a base wm6.1 with all of our software on it and configured when we image a gun. I am sure motorola would hook us up with microsoft to do this but trying to figure out if anyway i could pull this off internally since we update so much..
thanks
jphilpot said:
Hello,
Hoping someone could clear up a couple things for me. At my work we use the mc9090 RFID scanners which run windows mobile 6.1 currently. Currently we use motorola osupdate to push applications in a CAR file once the OS update util flashes the stock rom which are .sig files and .bin files. My question is do i have any chance of dumping the rom and if so would I be able to get it back on the device. Currently i was able to use imgfs tools to dump the os partition into a .raw files but that is as far as i got with dumping. So since they are signed files how would or is it possible for me to get them back on the device? I just didn't want to waste anymore time if i am not going to get anywhere on this. Also not saying that I would be able to use it but is package builder for wm what actually generates the .sig files?
Any ideas about how i could make this work would be awesome or any other ideas. The goal here is for us to have a base wm6.1 with all of our software on it and configured when we image a gun. I am sure motorola would hook us up with microsoft to do this but trying to figure out if anyway i could pull this off internally since we update so much..
thanks
Click to expand...
Click to collapse
My suggestion is to set up one of your devices with all the setting and configurations exactly the way you want them, and then image that device using a program like Sprite Backup http://www.spritesoftware.com/ It's a tool I use to keep my device secure, since I do a lot of tweaking on it.This way, if any of my adjustments end up breaking it, I can always restore to a configuration that I know works. The same principal should work for what you need.
sprite
Unit ZER0 said:
My suggestion is to set up one of your devices with all the setting and configurations exactly the way you want them, and then image that device using a program like Sprite Backup http://www.spritesoftware.com/ It's a tool I use to keep my device secure, since I do a lot of tweaking on it.This way, if any of my adjustments end up breaking it, I can always restore to a configuration that I know works. The same principal should work for what you need.
Click to expand...
Click to collapse
We tried sprite clone in the beginning and didn't work out right. Some stuff didn't come across right, so not saying i havent learned
enough now to fix that stuff but as far as us implementing it i don't see that happening.
I will give it another look since we have 100 licenses :]