Is it possible to extract contents of a ThinApp container?
Is there possible to extract such packages made by somebody else.
Ok, so if there is no general way of extracting such archives, which can be a huge exe file or tiny exe starter with huge packed *.bin file with main files of an app that is to be run in portable way - is there a way to set an option in compilation *.ini file or other way to make such package able to be extracted.
I remember I read somewhere that somebody created a tiny program (in was mentioned in vmware forums as far as I can remember, it was a crude thing coded for private use and I never managed to download it) to sit with main portable application and if such application has an open/save file dialog, it is possible to navigate to that program which virtually sits in the program files alongside main app from within the main app, and such program would scan all files that it can see and somehow is able to distiguish a real file from virtual one, and save all virtual files in a structure that is similar to the initial compilation folder from which portable app was created. I know that it is a very round-about way of doing things, but maybe the only one feasible.
Nevertheless any news on this front ? Do antiviruses can somehow unpack these things ? Maybe they must buy a code or license for it from VmWare ?
Edit: I found http://communities.vmware.com/thread/257433?tstart=600 and still trying to make sense out of this. Wrong, this was about moving old version of thinapp to win7.
extract portable
add a comment |
Is there possible to extract such packages made by somebody else.
Ok, so if there is no general way of extracting such archives, which can be a huge exe file or tiny exe starter with huge packed *.bin file with main files of an app that is to be run in portable way - is there a way to set an option in compilation *.ini file or other way to make such package able to be extracted.
I remember I read somewhere that somebody created a tiny program (in was mentioned in vmware forums as far as I can remember, it was a crude thing coded for private use and I never managed to download it) to sit with main portable application and if such application has an open/save file dialog, it is possible to navigate to that program which virtually sits in the program files alongside main app from within the main app, and such program would scan all files that it can see and somehow is able to distiguish a real file from virtual one, and save all virtual files in a structure that is similar to the initial compilation folder from which portable app was created. I know that it is a very round-about way of doing things, but maybe the only one feasible.
Nevertheless any news on this front ? Do antiviruses can somehow unpack these things ? Maybe they must buy a code or license for it from VmWare ?
Edit: I found http://communities.vmware.com/thread/257433?tstart=600 and still trying to make sense out of this. Wrong, this was about moving old version of thinapp to win7.
extract portable
add a comment |
Is there possible to extract such packages made by somebody else.
Ok, so if there is no general way of extracting such archives, which can be a huge exe file or tiny exe starter with huge packed *.bin file with main files of an app that is to be run in portable way - is there a way to set an option in compilation *.ini file or other way to make such package able to be extracted.
I remember I read somewhere that somebody created a tiny program (in was mentioned in vmware forums as far as I can remember, it was a crude thing coded for private use and I never managed to download it) to sit with main portable application and if such application has an open/save file dialog, it is possible to navigate to that program which virtually sits in the program files alongside main app from within the main app, and such program would scan all files that it can see and somehow is able to distiguish a real file from virtual one, and save all virtual files in a structure that is similar to the initial compilation folder from which portable app was created. I know that it is a very round-about way of doing things, but maybe the only one feasible.
Nevertheless any news on this front ? Do antiviruses can somehow unpack these things ? Maybe they must buy a code or license for it from VmWare ?
Edit: I found http://communities.vmware.com/thread/257433?tstart=600 and still trying to make sense out of this. Wrong, this was about moving old version of thinapp to win7.
extract portable
Is there possible to extract such packages made by somebody else.
Ok, so if there is no general way of extracting such archives, which can be a huge exe file or tiny exe starter with huge packed *.bin file with main files of an app that is to be run in portable way - is there a way to set an option in compilation *.ini file or other way to make such package able to be extracted.
I remember I read somewhere that somebody created a tiny program (in was mentioned in vmware forums as far as I can remember, it was a crude thing coded for private use and I never managed to download it) to sit with main portable application and if such application has an open/save file dialog, it is possible to navigate to that program which virtually sits in the program files alongside main app from within the main app, and such program would scan all files that it can see and somehow is able to distiguish a real file from virtual one, and save all virtual files in a structure that is similar to the initial compilation folder from which portable app was created. I know that it is a very round-about way of doing things, but maybe the only one feasible.
Nevertheless any news on this front ? Do antiviruses can somehow unpack these things ? Maybe they must buy a code or license for it from VmWare ?
Edit: I found http://communities.vmware.com/thread/257433?tstart=600 and still trying to make sense out of this. Wrong, this was about moving old version of thinapp to win7.
extract portable
extract portable
edited Feb 12 '16 at 7:05
Hennes
58.8k792141
58.8k792141
asked Dec 12 '11 at 8:48
rsk82
68261526
68261526
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
There is a way :)
After run the portable program, go to file-open or something to show you some dictionary of inside of the pack.
Then go to the main virtual dictionary of the software and copy in to other path.
You should do this in the virtual or portable program which is build with thinapp or other.
Now close software and go to the path which you copied files there.
That's finished and you can create a new setup with these original files.
add a comment |
Ran into this myself. Building on the anonymous answer above, you can copy the directory tree for the contained app. In my case the copied files weren't where I put them, instead they were in %appdata%thinstallappname.
The ThinApp manual goes into further detail about where it stores files created within the VM. See chapter 5. http://www.vmware.com/pdf/thinapp50_manual.pdf
Sorry about necro'ing a post, but this is the first one I found in my search so assume it'll be useful to others.
add a comment |
If understand well the question I think you'r looking for a way to read the .dat
file that thinapp generate:
I renamed the .dat
file to .exe
then I used Universal Extractor to extract the content.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f367102%2fis-it-possible-to-extract-contents-of-a-thinapp-container%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is a way :)
After run the portable program, go to file-open or something to show you some dictionary of inside of the pack.
Then go to the main virtual dictionary of the software and copy in to other path.
You should do this in the virtual or portable program which is build with thinapp or other.
Now close software and go to the path which you copied files there.
That's finished and you can create a new setup with these original files.
add a comment |
There is a way :)
After run the portable program, go to file-open or something to show you some dictionary of inside of the pack.
Then go to the main virtual dictionary of the software and copy in to other path.
You should do this in the virtual or portable program which is build with thinapp or other.
Now close software and go to the path which you copied files there.
That's finished and you can create a new setup with these original files.
add a comment |
There is a way :)
After run the portable program, go to file-open or something to show you some dictionary of inside of the pack.
Then go to the main virtual dictionary of the software and copy in to other path.
You should do this in the virtual or portable program which is build with thinapp or other.
Now close software and go to the path which you copied files there.
That's finished and you can create a new setup with these original files.
There is a way :)
After run the portable program, go to file-open or something to show you some dictionary of inside of the pack.
Then go to the main virtual dictionary of the software and copy in to other path.
You should do this in the virtual or portable program which is build with thinapp or other.
Now close software and go to the path which you copied files there.
That's finished and you can create a new setup with these original files.
edited Jun 22 '13 at 9:01
suspectus
3,65161931
3,65161931
answered Jun 22 '13 at 7:33
guest
1
1
add a comment |
add a comment |
Ran into this myself. Building on the anonymous answer above, you can copy the directory tree for the contained app. In my case the copied files weren't where I put them, instead they were in %appdata%thinstallappname.
The ThinApp manual goes into further detail about where it stores files created within the VM. See chapter 5. http://www.vmware.com/pdf/thinapp50_manual.pdf
Sorry about necro'ing a post, but this is the first one I found in my search so assume it'll be useful to others.
add a comment |
Ran into this myself. Building on the anonymous answer above, you can copy the directory tree for the contained app. In my case the copied files weren't where I put them, instead they were in %appdata%thinstallappname.
The ThinApp manual goes into further detail about where it stores files created within the VM. See chapter 5. http://www.vmware.com/pdf/thinapp50_manual.pdf
Sorry about necro'ing a post, but this is the first one I found in my search so assume it'll be useful to others.
add a comment |
Ran into this myself. Building on the anonymous answer above, you can copy the directory tree for the contained app. In my case the copied files weren't where I put them, instead they were in %appdata%thinstallappname.
The ThinApp manual goes into further detail about where it stores files created within the VM. See chapter 5. http://www.vmware.com/pdf/thinapp50_manual.pdf
Sorry about necro'ing a post, but this is the first one I found in my search so assume it'll be useful to others.
Ran into this myself. Building on the anonymous answer above, you can copy the directory tree for the contained app. In my case the copied files weren't where I put them, instead they were in %appdata%thinstallappname.
The ThinApp manual goes into further detail about where it stores files created within the VM. See chapter 5. http://www.vmware.com/pdf/thinapp50_manual.pdf
Sorry about necro'ing a post, but this is the first one I found in my search so assume it'll be useful to others.
answered Jun 25 '15 at 13:46
John Jones
1012
1012
add a comment |
add a comment |
If understand well the question I think you'r looking for a way to read the .dat
file that thinapp generate:
I renamed the .dat
file to .exe
then I used Universal Extractor to extract the content.
add a comment |
If understand well the question I think you'r looking for a way to read the .dat
file that thinapp generate:
I renamed the .dat
file to .exe
then I used Universal Extractor to extract the content.
add a comment |
If understand well the question I think you'r looking for a way to read the .dat
file that thinapp generate:
I renamed the .dat
file to .exe
then I used Universal Extractor to extract the content.
If understand well the question I think you'r looking for a way to read the .dat
file that thinapp generate:
I renamed the .dat
file to .exe
then I used Universal Extractor to extract the content.
answered Mar 20 at 9:46
Badr Elmers
216
216
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f367102%2fis-it-possible-to-extract-contents-of-a-thinapp-container%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown