New: HomeBank (Sep 03, 2023), Platform 26.2.1 (Sep 17, 2023)
450+ real apps (49GB), 1.1 billion downloads, Please donate.
Jack Haller, Advisor and Father of Our Founder, Has Passed Away
I've digged the forum but did not find the answer to my question. I've tried PAC and it works nice. But if I move installed application to another drive, even if maintaning same folder structure, it does not work.
Is this a malfunction or am I missing something?
Thank you in advance
PS: Great app!
I try it when i'm on a computer with windows vista, and it says that i've got "RAC" or something like that, and i can't use the software. how do i get past this?
I tried making Fast Launcher portable. I know, it only writes data to
other than that, its portable.
But I get ERROR when it makes the final step:
aut2Exe Error : Error opening the destination file
And the app is not portable as result & still reads data from %user%\Appdata\DVAsoft\
Yes my files are not read only & not running eather
Noticed a small mistake in the packaging of Portable App Creator. When installed on on a thumb drive by extracting from the zip file and copying the folders and files under the PortableApps folder, the menu item - Portable App Creator - has no icon associated.
This is because there is no AppIcon.ico file in the Apps\AppInfo folder. There is a PAC Compiler.ico file and a Portable App Creator.ico file though. I didn't know if they needed to be named as such so I copied one of them and renamed it AppIcon.ico and now the correct icon appears against the menu item in the PortabelApps menu.
There appears to be a problem with the text being partially missing in the creator panel. Here's an example of what I mean: http://www.humyo.com/F/3418541-1433705695 This happens regularly throughout the install process, half a line of text missing at the bottom of a paragraph. The screen size I am using is 1680x1050.
A test for errors in apps creator with AutoIt3 Syntax Checker v1.54.8
I have not administrator rights.
>C:\Documents and Settings\Superlepopaul\Bureau\autolt\install\SciTe\..\au3check.exe "C:\Documents and Settings\Superlepopaul\Bureau\Portable App Creator 0·97·2\Other\Source\Portable App Creator.au3"
AutoIt3 Syntax Checker v1.54.8 Copyright (c) Tylo 2007
C:\Documents and Settings\Superlepopaul\Bureau\Portable App Creator 0·97·2\Other\Source\Portable App Creator.au3(110,54) : ERROR: undefined macro.
'EnableLUA') = '1') Or StringRight(@ProcessorArch,
C:\Documents and Settings\Superlepopaul\Bureau\Portable App Creator 0·97·2\Other\Source\Portable App Creator.au3(367,31) : ERROR: undefined macro.
C:\Documents and Settings\Superlepopaul\Bureau\Portable App Creator 0·97·2\Other\Source\Portable App Creator.au3 - 2 error(s), 0 warning(s)
>Exit code: 2 Time: 0.266
(I speak French but I learn English)
I tried PAC for the first time and it looks like doing things OK. I can run the Portable App now. But when I tried to use the PA Installer to create installer, there are errors.
I created the folders as per the requirements.
Anything I missed?
This program is not built up to the newest PAF standards, and has some various misnamed files and missing folders. As a result, it currently will not work in the PortableApps Installer Creator program.
Simplifying daily life through technology
If this does not follow the PA Installer standards, what should I do now.
I have created the portable version of the App using this tool but I'm stucked in making the installer. What's the next move?
I can not be bothered reading all the comments (6 pages worth), so I ask to please ignore this if this idea has been posted.
Instead of using the PA: drive, why not use the shortcuts current location as a base directory. That way, the portable-app can be used, in theory, in any location.
Again, if this idea has been posted before, please disregard this post.
EDIT: The AutoIT variables to use for relative paths are @ScriptDir and @WorkingDir
Good idea richo I don't know what the deal is with all these so called 'portable apps' programs that only work if you have your programs in the root directory of a usb drive.
It's so messy... Completely unnecessary. This is the year 2009 not were not using dos 6 any more. I really hope most people don't want to run all their programs from the root directory now days...
i found this tool very promising in creating portableapps.
is there any plan to update this to meet the new standars for new pac installer?
A couple of days ago, a got a trojans-alert from the pac.
It sayed the file was infected by TR/Dropper.GEN. Wenn I download the zip-file again, I get also an alert. Could You check, if the Your uploaded zip-file ist clean?
Thank (by the way: the tool ist cool!)
Totally FWIW, & hoping it might be helpful... my understanding is that taking the time to create a real portableapp & installer is preferred. I believe it's also preferred that the core app is open source, though free ware is recently accepted, & of course the wishes of whomever owns the app (if not open source) should be followed.
That said, I've often found the PAC to be a great tool for making a copy of an app I have the license for into a portable version, entirely for my own use. In that case an installer etc is irrelevant. Apps that make minimal changes to Windows &/or the registry are good candidates, in my experience the PAC process works best in XP 32, I use it in tandem with ERUNT to backup/restore the registry, & I use Regshot to test afterward. Apps that are already portable, I usually just put into a separate folder on the USB stick -- it would be easy to create a launcher, but as I'm just as happy launching an app from Windows Explorer, I just don't bother.
I start out by monitoring most every install, either with Regshot, Regshot2, or InstallWatch Pro. An app that makes a whole lot of changes throughout the registry, or adds files to the system folders, or that you want to integrate into the Windows shell, generally won't work well with PAC. An app that stores just 1 or 2 keys in the registry, &/or adds a single folder under XP's Docs & Settings is usually ideal. AS the number of registry entries grows & becomes more complex, the odds of PAC not working increase. It is possible to edit the virtualized registry entries PAC creates, but that doesn't always work. I've also run into cases where there were a lot of lines in the reg file PAC creates, & the portable app it created would only run so many times before needing a Windows/system re-boot to run again. In a nutshell, if you know PAC's limits, you shouldn't be disappointed. Consider it a shortcut & when it's not up to the job, consider doing it, creating your portable app I'd guess I'd say the *right* way.
As a quick example, I picked up an app that was given away by the developer the other day, & in the program's folder there was a text file explaining how to make it portable. 1) In XP Pro SP3 32, I backed up the registry using ERUNT. 2) I monitored the install to detect what registry entries it created, & the folder it added to Docs & Settings. 3) I followed the developer's directions to make the app portable, restored the registry backup, removed the added D & S folder, fired up Regshot to monitor things when I started the app. 4) I found unfortunately that the app still created a registry key, so after deleting that key I set up the folder structure on a USB stick with portable apps installed, copied the app into it, then used PAC, pointing it at the app's .exe file. 5) Now when the app started it created the same key, so PAC recorded & virtualized it, but I still needed to delete the key once again, then use Regshot to make sure PAC's created launcher did the job, which was a success.
I've also had good luck moving newly created folders, then putting them back in Documents And Settings while PAC was running & monitoring the app I wanted to make portable. And/or I've exported registry entries, removed them from the registry (or restored a backup), then merged them back after performing the 1st shot in PAC. PAC just has to see either created for the 1st time.
Whilst it's certainly possible to run PAC during an actual install, I normally don't because you still have to know what changes were made by installation so you can remove them [how else do you tell if it worked, &/or why else make it portable?]. I also don't want/need all the registry entries the installer inserts, nor do I want them bloating the reg file PAC creates. And finally, I can predict with almost certainty whether PAC will work or not.
It seems that the trojan alert was wrong. After reloading the App some days later, I dont get an alert anymore.
i tryed making a portable version of anything i can get my hands on
but i dont understand what im supposed to target
when it ask for shortcut info i dont get what the launcher is
can any one help?
I sent it to virus total. look to the result
Complete scanning result of "=?iso-8859-1?Q?Portable_App_Creator_0=B797=B72_beta.zip?=", processed in VirusTotal at 02/24/2010 20:21:09 (CET).
[ scan result ]
a-squared 126.96.36.199/20100224 found nothing
AhnLab-V3 188.8.131.52/20100224 found nothing
AntiVir 184.108.40.206/20100224 found nothing
Antiy-AVL 220.127.116.11/20100224 found nothing
Authentium 18.104.22.168/20100224 found nothing
Avast 4.8.1351.0/20100224 found nothing
Avast5 5.0.332.0/20100224 found nothing
AVG 22.214.171.1240/20100224 found nothing
BitDefender 7.2/20100224 found nothing
CAT-QuickHeal 10.00/20100224 found nothing
ClamAV 0.96.0.0-git/20100224 found nothing
Comodo 4049/20100224 found nothing
DrWeb 126.96.36.19922/20100224 found nothing
eSafe 188.8.131.52/20100224 found [Win32.Banker]
eTrust-Vet 35.2.7326/20100224 found nothing
F-Prot 184.108.40.206/20100224 found nothing
F-Secure 9.0.15370.0/20100224 found nothing
Fortinet 220.127.116.11/20100221 found nothing
GData 19/20100224 found nothing
Ikarus T18.104.22.168.0/20100224 found nothing
Jiangmin 13.0.900/20100224 found nothing
K7AntiVirus 7.10.981/20100223 found nothing
Kaspersky 22.214.171.124/20100224 found nothing
McAfee 5902/20100224 found nothing
McAfee+Artemis 5902/20100224 found nothing
McAfee-GW-Edition 6.8.5/20100224 found nothing
Microsoft 1.5406/20100224 found nothing
NOD32 4893/20100224 found nothing
Norman 6.04.08/20100224 found nothing
nProtect 2009.1.8.0/20100224 found nothing
Panda 10.0.2.2/20100224 found nothing
PCTools 126.96.36.199/20100224 found nothing
Rising 22.34.01.03/20100211 found nothing
Sophos 4.50.0/20100224 found nothing
Sunbelt 5696/20100224 found nothing
Symantec 20091.2.0.41/20100224 found [Reser.Reputation.1]
TheHacker 188.8.131.52.208/20100224 found nothing
TrendMicro 184.108.40.2064/20100224 found nothing
VBA32 220.127.116.11/20100224 found nothing
ViRobot 2010.2.24.2200/20100224 found nothing
VirusBuster 18.104.22.168/20100224 found nothing
Only two found anything; it's a false positive, very common with AutoIt applications.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Does It really portabilize programs? Make an portable version of Easy PHP and post the download link! :>
Prevx---3.0---2010.02.27---Medium Risk Malware
False positive. Because it is made in AutoIT and compressed with UPX, it will always show up as virus/malware.
@maroesjk - I tried emailing you about some changes I made, but I guess you are busy. I would like to share my changes, so I have put my changes here, in case anyone here is interested in them. I would very much like to contribute to this project and keep it moving forward.
For those that are interested, I have a link here: Portable_App_Creator_0_97_3_beta.zip
Here are some of the changes I have made:
1. PAC Launcher can be run with command line arguments. These are send directly to the application being run in AppName folder.
2. Output from PAC is now compliant with Portable Apps.com Format 1.0.
3. Added au3 file to allow custom scripting before and after the portable app has been run. This can be used to do 'things' that may have been missed by the PAC wizard.
4. Brought all au3 files upto AutoIt v22.214.171.124.
5. Allow PAC to update Appinfo.ini file.
6. Made some PAC Wizard text easier to understand.
7. Allow PAC Wizard to suggest an installation folder and portable launcher name.
8. PAC Launcher will load default app data if the data folder is empty.
9. PAC Launcher now defaults to the drive/folder containing the script, not the drive/folder in which the program was installed.
Just tested the new beta from PAC and I have a small question: when the applicationPortable.exe is launched, does it check the CustomLauncherEvents.au3 script? 'Cause if it does, then, my friend, you just made my day :-D. Nonetheless, this is a very nice program.
It will run CustomLauncherEvents.exe if you have compiled CustomLauncherEvents.au3. It will be run once before the real program is run and once after the real program has finished.
Thank you. I managed and figured out by myself that i had to compile it in order to work. Nice script, as now I can totally control what files are copied or not by my portable apps.
By the way, if I may suggest... you might want to remove that restriction about the regshot and the x64 based operating systems... I mean, I knew how to modify it, but for someone who doesn't might be a real pain... Regshot works just fine on my x64 OS, so I figure it'll work just as fain on other x64 based OS's too.
Please share the x64 fix - I run Win7 x64 and I'd need the work around and I have no idea where to even begin with that...
As far as I know, the 32-64 problem is not really a problem anymore, but the code hasn't been updated since. Which means that if you just turn off the warning, it should work.
Turn off the warning as follows:
1. Go into (Portable App Creator folder)\Other\Source and open Portable App Creator.au3 in Notepad.
2. Save as 'Portable App Creator.au3.bak'
2. Search for "64-bit."
3. Nearby, you'll find a line that says
'EnableLUA') = '1') Or StringRight(@OSArch, 2) = '64' Then RegShotError()
Delete Or StringRight(@OSArch,2) = '64'
4. Save as 'Portable App Creator.au3', overwriting if necessary.
5. Compile PAC.
Or StringRight(@OSArch,2) = '64'
If you've already compiled it, delete it and re-unpack it before following the above.
Thanks so much. I have had a lot of luck with it, and I appreciate how everything is made in PortableApps.com official format. I also like how it copies everything into the new portable directory. That's sick.
The new beta 0.97.3 is awesome.
The best feature is the shorcut to "script folder" instead the "PA Drive",this makes really Portable apps that you can put anywhere.
I ported Google earth with no mess.All the files,includig G.E. cache ,are stored in the portable app folder.
Recreated the portable apps.com Folder structure and i have a pretty Google Earth Portable with my own kml places,etc that i'm using on diferent computers.
Thanks a lot.
Google Earth saves its settings in different locations depending on what OS your on (XP or Vista/7)
If you switch between XP and a new OS, your going to lose your settings and leave behind the settings on the host.
Saving cache will make Google Earth Portable HUGE! Just run it 10 times and your folder will get to be over 200 MB!
I'm not sure if you've heard, but there is a Google Earth Portable already:
The only bug is that it leaves empty folders behind on Vista/7 (which will be taken care of in my next release, this Sunday)
Ok I have used the new PAC and it's grate in almost all ways, now here it gos the problem.
When the installation of the program is done I use the main .exe of the program to be usede as the shortcut to launch the program so that it looks more presentable but when I do that the PCA makes a folder in the App Folder withe the name of the main .exe that I have choosen to be the shortcut the with all the files of the installed program.
Example: here is a list of the folders that I made to make Spybot Portable
Spybot – Search & DestroyPortable
Appname-> Spybot – Search & Destroy
This is what PCA dose to the folders when copying the shortcut information
Spybot – Search & DestroyPortable
Appname-> Spybot – Search & Destroy
SDMain (it copys the program with all files here, it also creates a nother data folder for shortcut info)
Also in the USB drive it saves shortcut info in a seperated folder.
When you select the location to create the launcher, are you using the path that you used to install the app, or a totally different path? Ideally, to separate the install folder from the portable folder, they should be different.
Yes I am using the same path that I used to install the app, I am doing the setup as I would with the PCA v2 nothing different.
With my changed version, you should use a different path (like the default 'PAC_Installer' folder. The reasoning behind this is that you can then uninstall the program you installed to get rid of the shortcuts, registry info, etc., but leave the portable program in the other location.
Ok I just don't see why would the program PCA 3 make a new folder with the same software that has just bin made portable.
Remember that this version creates a PAT compatible folder structure. I wanted to keep this separate from the app that was installed. I also like that fact that I can uninstall the original app so that I can properly test the PAC version. For example, the app may have made some changes that could not be picked up by PAC (like registering files, etc).
Okay, that's grate and all but, PCA 3 it also dose the same thing when just creating a shortcut by it self. What I mean is that when I skip the installation proses it dose the same as if I just installed it. It copy's the program to a new folder with the name of the new shortcut with no difference to the registry.
For better help I suggest that you try to make a portable program that has multiple tools that you want to show in the PortableApps.com menu by creating other shortcuts to those tools (programs) withing the new portable app. This way you can see exactly what I mean. like I did with Spybot that has the (Single File Scanner) and (File Shreder)
I would like to thank you for your help and your time on this matter
iam makeing a new portable app for snowblobe go to this webpage its my project!
Thanks pyromaniac.You made a great portable ,but im agree with my own version.Maybe not fully portable as you said,but aim using with same os's and it's OK.
That portable is for Personal use only ,not to be published on web or shared.
PAC+Sandboxie is perfect for making my own portables for personal use quickly.
A simple vbscrit works to clean cache when i need.
I'm using diferent map overlays on Google Earth and the cache works well on it.
Yourversion is pretty good including the cache thing.
My objective is to buid my own portable apps ,so i'm woking on how to include an option or a switch better than the vbscript,maybe some auto-it code is needed for me.
You solved using the ini file.
Will PAC work with an application that requires activation after the install. I have two such apps (I have paid for these apps) that I use regularly and would like to put them on a usb stick, so I don't have to lug my notebook around. any help greatly appreciated.
Then, this app, will be updated to an Format Specification 2.0?
And... can, someone, put more explainations in the code?
The PortableApps.com Launcher is what you should use now. This is obsolete.
I know, but I don't know how to see the files activity... where are important files copyed... And FileMon is not working...
Why you don't make an tirth program (something like PortableApps.com Analyser) who to scan before and after the install and to save two files:
An .reg with all modifyed and/or created registry, and an .txt in who to be all files changes (add,delete,modify,rename,etc.), to help us to be sure we set all files we have need to that (in-future portable) software.
That will be great!
This is a 3 year old thread and a lot has changed since then.
Besides that, there is no way to make such a tool as lots of keys are created but only a few matter. The same goes for files.
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
This isn't obsolete at all. PortableApps.com Launcher will only create a launcher for an already-portablized app, which means you have to spend several hours coding for that specific program. This quickly and efficiently portablizes the app in the first place, without any need of advanced computer knowledge. Frankly I'm disappointed there isn't an official version of this after three years.
This has never made PAF apps. Nor does it do a perfect job even of keeping settings (there are major flaws with how it does some things, and you can't even properly fix them afterwards due to the method it works) - you can't even implement things like language switching in it. The PortableApps.com Launcher does currently require a bit more work and understanding, but what it produces is actually worth while having. From a couple of use cases I've seen of this, it gives a little bit of portability and lots of false confidence.
Perhaps the application is obsolete but the idea is great. Given the chance in the hands of the dev team, this app posses great potential.
I am still hoping that someday the dev team will launch something like this app.
As Chris stated, this app simply doesn't work to produce proper PortableApps.com Format apps. There is no method to automatically produce a proper portable app in existence other than a virtualization engine which costs thousand of dollars and may require admin rights to run on a given machine.
Sometimes, the impossible can become possible, if you're awesome!
I am not referring to the software but the idea that the software has.
The main idea is to make something that will package the software after it went through the process of checking what files are being copied on the host and registry entries.
Perhaps I am not understanding the core it PAC but from narrow perspective I think that is the idea.
I myself wanted to try portablizing but I can't get my self into the foundation of how it is done. That is why I thought the idea of this software is handy and great at the same time.
The idea seems tempting at first. But portablizing apps is not easily standardized (i consider that impossible). It may work on some apps that are nearly portable from the start. Or if only a few registry entries and files are to be taken care of. But even that differs with every app. And is neither much to learn nor much work but requires an estimation of the methods to use. That cannot be automatized without producing faulty results. So someone has to check if the process came out clean, what requires a comparable know-how as manually editing the inis for the launcher.
For more complicated apps where not so obvious things have to be taken into account - think of dependencies on dlls or libraries like gtk - an automated process is bound to fail. I did only package three apps for now and they were rather easy to do but in all three cases an automatic process might have failed as some issues were not obvious at first.
A semi-automatic utility to ease up the process would be really handy but is a complete other story. Chris Deveolpment Toolkit is a step towards that. Integrating some kind of regshot and generating entries based on user decision would at least prevent typos, but I doubt thats's worth the effort.
Thanks for that nice point.
actually, that is what I am trying to find since I join the community. But the lack or resources how to "really" start portabllizing is what's missing. Please don't get me wrong, I am not complaining nor criticizing the team or the community because both are wonderful. I am simply stating what "I wish" is available so I can hook up easily.
I went to guerilla guide before and revisiting every now and then when I have time but I think (personally) it doesn't lift you off the ground of portablizing apps. It simply give you instruments of how to make portable apps but instruction on how to do it the right isn't there.
Let say for example audacity, it was one of the example there in the guerilla guide (the old version) it states that audacity is naturally a portable app. but then, there is no steps on how do you repack audacity into a portable apps.
That is something that will lift you off the ground. To see how basic app is being made portable.
That is why I found this app creator a potential tool to start with.
Again thanks for the good point you mentioned. I starting to understand the core of it.
You found a kind of sore point - documentation. The manual of the launcher is a very good reference, but lacks a real tutorial. The beginners guides (there are two) are both outdated at best as they don't cover newer developments like the launcher.
At the moment, the devs are occupied with, hum, development. John, f.i., is finishing the platform update.
I though about writing a beginners guide myself, but don't feel competent enough to do so (yet?). But as I know some basics, maybe I find some time to write a 1st-timers tutorial for some newbie (like me a few months ago) to get the idea.
The creator would be a good start, if it produced a package that was compatible to the specifications an using the launcher.
This app creator as far as I remember is PAF compatible. The package ends up as paf and When you run the package it integrates the apps on PAC launcher.
But I agree with most of the people not liking this app creator because it indeed have lots of flaws. That is why like I said, I like the idea not the app creator.
I will be waiting for your beginners guide from now
Although this app DOES create a *.paf.exe, that does not mean it meets the current PortableApps.comFormat. It is outdated, and the PortableApps.com Launcher & PortableApps.com Development Toolkit should be used instead. More work, yes, but they give a cleaner package that meets PAF specifications if used properly.
Guys, if this app is outdated or bla-bla-bla WHO can make a "step-by-step manual of portapps creation for dummies" using the PortableApps.com Launcher & PortableApps.com Development Toolkit etc.
You can’t please everybody, but then again, that’s not my goal.
That is the point.
Hope now they get it.
I know... It has been ages since I've posted an update. As I state in my opening post:
I won't be able to work a lot on PAC nor will take a look at this forum on a daily/weekly basis. I accepted a quite demanding job and have 2 little children. So I am very busy with other things right now.
Nevertheless, I've been working to update PAC now and then for my own use in the last two years. As I lost an USB-stick in the last month, I needed to rebuild some "Closed Source" PortableApps, which forced me to update PAC again. After that update - which overcame some troubles I faced before - I decided to upload the newest beta.
Portable App Creator does not follow the current PortableApps.com Format™ Specification, nor creates a normal PortableApps.com Launcher… However, many people think it's useful to some extent. Listed are all changes for version 0·98 and 0·98·1 beta:
You can now download Portable App Creator 0·98·1 beta at RapidShare (MD5: CD801A381289548BDA30420C5879AC2D, only 372 kB). Please see the readme-file supplied with this package to find out what you need to do before you can use "Portable App Creator", the limitations of PAC and instructions on its usage. You may also want to watch the video demo I created using an older version of PAC at RapidShare (4.180 MB) or YouTube.
There are 10 types of people in the world. Those who understand Binary and those who don't.
I'm getting an error line 408: Array variable has incorrect number of subscripts or subscript dimension range exceeded.
yes, I try the program yesterday and got the same error...
error line 408: Array variable has incorrect number of subscripts or subscript dimension range exceeded.
Strange, that's a line that has been in the script forever... Haven't modified that and it didn't give me any errors when testing the script after the last few changes (using a VirtualBox 32-bit Windows XP configuration).
I have re-tested but cannot seem to reproduce your problem(s). But, I will see if I can find out what goes wrong for you! Would it be possible for you to e-mail to Portable App Creator [at] Gmail [dot] com (without spaces):
- the OS you are using (Windows version and if it's 32 or 64 bit)
- the app you're trying to make portable
- the ~res.txt file that is in c:\windows\temp\pac when the error occurs
Please stop editing your comment needlessly. It shows up as a new post in the tracker, and send out a new notification email every time you do so.
Conveniently, by replying to your comment, it is no longer possible to edit.
I was trying to get to the most optimal solution on how to find the bug reported and posted some first info. After trying some things, I needed to edit the post as some things were found already. Next, I made an error in the e-mail address. IMHO, it's useless to create new posts for that: this is why they invited the edit button.
However, I agree that editing of posts should be limited as much as possible. Sorry for the inconvenience!
I'm using Windows 7 32 bits. I'm trying to create a portable app for Qlikview 10 personal edition (can download free from qlikview). pac 0.98.1b gives the error at startup, b4 any tmpfile is made.
The 0.97.3b version also works, somewhat. Often it hangs during creation, but sometimes it produces a portable app. Although it does work with some fiddling, I havnt yet created a version that starts without errors.
Nevertheless, great tool! Thanks!
I tried the program in windows vista home basic 32 and windows xp 32 service pack 3
and I ran PAC compiler, but when it finished this .exe didn`t delete, then when I ran PORTABLE APP CREATOR the other .exe was deleted, and finaly I opended PORTABLE APP CREATOR, appear the principal window (portable app creator -welcome) and the error appear.
I can´t select the drive (D: or F: ....) because the error don´d leave to continue...
in the folder %temp%\pac doesn´t exist the file res.txt ~
because I don´t select the program to do portable...
maybe this help
maybe the error ocurr in AUTOit, I installed the latest version v126.96.36.199...
when I do clik in ACEPTAR, the program close.
All, I think I found the error that caused the problems for PAC version 0·98·1 beta. Hope this newer version indeed works for you!
Portable App Creator does not follow the current PortableApps.com Format™ Specification, nor creates a normal PortableApps.com Launcher… However, many people think it's useful to some extent. Listed are all changes for version 0·98 beta, 0·98·1 beta and 0·98·2 beta:
You can now download Portable App Creator 0·98·2 beta at RapidShare (MD5: 9470DA61A4B415CA168E2EB36C0BBCBD, only 381 kB). Please see the readme-file supplied with this package to find out what you need to do before you can use "Portable App Creator", the limitations of PAC and instructions on its usage. You may also want to watch the video demo I created using an older version of PAC at RapidShare (4.180 MB) or YouTube.
This appears to be self-promotional posting.
PortableApps.com Forum guidelines (#)No Self-Promotional Posting - Promoting your own software is not currently permitted here (though it will be soon). If you make a self-promotional post, it will be edited and your account may be disabled. The exception is if someone asks a question directly related to your product. In addition, if you are releasing a free, portable, open source (OSI-approved license) individual application in PortableApps.com Format that is not a fork or clone of an app hosted here, you may make a post when you do a release.
I'm not sure if this is to be seen as "self-promotional". PAC itself is "a free, portable, open source (OSI-approved license) individual application [..] that is not a fork or clone of an app hosted here". The fact that AutoIt itself is not open source is exactly why it isn't embedded: that way PAC conforms to GPL3. You're correct it's not in the current PortableApps.com Format™ Specification (it follows an older version of that Format Specification): I'll need to change that, and will do in the next release.
If the moderators decide to edit the post and/or disable my account, that will be their decision, and I can currently do nothing to change that!
The requirement is that all software which is submitted must be in PortableApps.com Format, of which an important part is—and always has been—using the PortableApps.com Installer. Your app does not thus comply to any version of the PortableApps.com Format specification. You will need to fix this.
I detected a error, when the program create the laucher
I try this version with the same program,
I try FCleaner with the version 0.97 beta 2 and now
I try FClenaer with this version 0.98 beta 2 and appear this error (see the pic).
in the after version (0.97 beta 1) the error doesn´t appear.
in beta 0.98 beta 2 if I do clik in ACEPTAR, the program continue an finish
but, doesn´t create the launcher.
the error only occur when I select same icon of the aplication, for example in this case the icon of fCleaner, but when I select the default icon of the app creator the program don´t have this problem.
the file % temp%\PAC ~ res.txt don´t have a error or similar, I think.
Well, at least this post confirms that PAC 0·98·2 beta takes you further than the previous version did. That's good news.
On the extraction of the icon: I have observed once that the extraction of the icons doesn't work correctly if the executable or dll doesn't fully meet the Windows specifications in respect to how the icon is stored. Some other programs were also unable to extract the icon in those cases.
However, I'll try to find out if the thing you ran into when trying to make FCleaner portable is because of a programming error in PAC and report back. Thanks for the bug-notification!
I got the same error about the invalid icon. Up to that point it runs smoothly. I don't get the icon error with any of the previous pac versions though. hth.
is there any way to use the icons extracted with a previous version to bypass this error?
Thanks a lot, PAC totally worked for me!
I bypassed the icon error by extracting an icon with another freeware tool, and pointing to that in the wizard. Although the upx compressions hangs (as it often does in the end), version 0.98.2b did create a launcher and that totally works error free :).
Few tips: when you have to rebuild again and again you'll want to clean the registry of all left behinds, and the directory where the installed app stores it's user data. In my case I chose to install from the extracted .msi as the previous versions of PAC saw the extracting of the .msi file as a change in the system, resulting in more data being copied.
I'm starting using it now, hopefully it will be bugfree all the way.
I think the error is in the PAC compiler
because if you observed the pic of the error...
Error Changin icon: unable to read icon or icon was.......
and the previus versions when the PAC compiler finish, it was deleted automatic.
but in the version 0.98 beta 2 this not occur. I think the PAC compliler don´t finish succesful at all.
I made all changes necessary to have Portable App Creator conform to the PortableApps.com Format™ Specification now. Listed are the changes for version 0·99 beta:
You can now download Portable App Creator 0·99 beta at RapidShare (MD5: 01ADB45828B71ECAE951619799E5DCF0, only 613 kB). Please see the readme-file supplied with this package to find out what you need to do before you can use "Portable App Creator", the limitations of PAC and instructions on its usage. You may also want to watch the video demo I created using an older version of PAC at RapidShare (4.180 MB) or YouTube.
first error: i cant see how downloading autoit , when i press continue he say that autoit not found. but the exe file autoit is in thgat category .
second error: error is with the icons at the end of creation (after process shots)
it says that icon is unsupport,.
I was able to reproduce and fix the first error: wasn't revealed in earlier tests I did, somehow!
However, I'd like to fix the second error as well before I release an update. The problem is that I cannot reproduce that error: every "Portable App Shortcut" / icon is created for me just fine. I recognize, though, that more people seem to suffer it (see some earlier posts on a previous version).
May I ask people that get this error to look if, when the second error pops up, there is an icon file in the "data" folder for the App you're trying to make portable? Please e-mail me the information (e-mail address in the help file).
I faced the same problem as in v.0.97.3_beta in Win7 64-bit, but in this 0·99 beta version the 64-bit error wouldn't resolve despite the recommendations given at https://portableapps.com/node/9909?page=5 (x64 Fix by linkhyrule5 - February 22, 2011 - 5:34pm).
Could you please share again a NEW x64 FIX without that trouble changing the code in "Portable App Creator.au3" as the code itsef has been changed (as far as I understood). May be it's reasonable to include a new version of Regshot (eg. 188.8.131.52 unicode x64 which works in x32 either) in the compiled distributive of Portable App Creator?
Thanx a lot!
try this creates portable app
I´m think that Portable App Creator is better, and I preffer this program, is too easy to use and works well.
I use a old version of this nice program
but now i can t take it because is on rapidshare
i don t now why i can receive activated mail (push lot of time)
can someone put last version 0.99 on other place? mediafire or other
I have been maded an mirror, on uploading.com - PortableAppCreator_0__99_beta_English.paf.exe.
Have a good day!
I have a problem
Next time i use the PAC 0.97.3b
When i install my software, i put the laucnhe in PAC_Launcher\%app% and it create me all folders
APP, DATA, Other and the launcher
with the last PAC0.99b, i can t put PAC_Launcher, il must select the folder in my application.
But at the end il don t have APP, DATA, Other folders ???
i don t understand how the new version works.
thanks a lot for BIG help for a noob
I have Portable App Creator 0·97·2 beta
it works until the last box,it just says working and it says
there for ever,i even waited for an hour for just a small app
i had to use the ctrl+alt+del keys to exit...what is going on?
can someone help me out?
What happens when the app doesn't ask yu for the directory to put the program into and it goes by default into ProgramFiles?
I just discovered this promising software (version 0.99_beta),
but in the last step (process Shots)an error message pops up: "Error: error opening the destination file".
Which file is meant, and what can I do ?
thanks & regards
Yeah, same version, same error happened here.
Thx for share, this awesome, really!
But it isn't working yet fully.
I have a few wishes, if it is possible to make changes at this stage:
- add %windir% to start, because many programs use this directory after installation of the system, but when moving usb to another computer modules aren't available in the system root ...
- why PAC can not running as well on virtual machines like VirtualPC, errors: "Array variable has incorrect number of subscripts or subscript dimension range exceeded"
- permanent error line 369 - "Array variable has incorrect number of subscripts or subscript dimension range exceeded" on last step
- upgrade regshot and autoit
Anyway, many thx for PAC!