Not sure if this is the right place to put this or if it will be read, but here goes.
Would it be possible to create a portable version of BeepComp? By portable, I mean that the settings are saved to the app folder and that (ideally) no trace is left on the computer. See this post for more details.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, you are welcome to post any questions or feedback regarding the project, so you're in the right place. I have actually just read that post and started compiling a portable package!
But before uploading this package... let me first test out this package on a few different machines to confirm that it can run perfectly from a USB drive and absolutely no trace is being left on the target computer. It'll be just a couple of days.
I appreciate your feedback! :)
Kind regards,
Hiro
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nice, thanks :) I tried to test it out in Sandboxie but it crashed whenever I tried to open it. Running it normally (Win10 x64) everything works fine. I'll make a post on the Portable Freeware forum notifying them of this great development, and they'll test it further. Keep up the awesome :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for testing this portable package! Hmm... it might have to do with the program reading the default music txt file at start up - maybe Sandboxie is blocking the program from reading the file? I will find out what is causing this crash inside Sandboxie. I appreciate your report - I'll let you know once I've made progress! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just finished working on this!
Now it is working fine inside Sandboxie.
The problem was easy to fix - I just changed all relative path references the program was using internally to absolute paths (which are determined at runtime), and voila, everything worked in Sandboxie.
One thing that I noticed is that if the program is stored in a drive other than C: and is run inside Sandboxie, the reference to that drive letter needs to be added in the "Quick Recovery" paths in the "Sandbox Settings", or any files that BeepComp saves or exports to will stay hidden. I'm guessing that this is a normal procedure for running any program from an external drive?
Thanks again! Runs just fine in Sandboxie as indicated, and testing here shows no residual files.
Regarding Sandboxie: yes it's fairly standard procedure, but only for initial portability testing. Once a program has been verified as portable or stealth, it can be run normally. Other typical testing methods are creating before/after system snapshots of the registry, running in a virtual machine that is completely clean. and using system file monitors to pick-up any changes made to the filesystem. There's a nice post here detailing all about this.
Some people use Sandboxie Portable for programs that aren't portable or otherwise leave unwanted residuals (some more instructions here).
But anyway, I'll be sure to return if any issues, bugs, etc are found. Have a good day further :)
Last edit: shnbwmn 2016-05-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for testing this further! And I am glad to know you were able to confirm that the program does not leave any residual files. I started reading the posts you linked. Those portablity testing methods they mentioned will definitely come in handy whenever I update the program.
BeepComp is registered at Softpedia, and when I let them know there is now a portable version available, they liked it and created a dedicated page for it. This lets me know that more and more people are choosing to use portable software.
I will continue to do testing on this portable package - thank you once again for making your feature suggestion! :)
Last edit: Hiro Morozumi 2016-05-05
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi there
Not sure if this is the right place to put this or if it will be read, but here goes.
Would it be possible to create a portable version of BeepComp? By portable, I mean that the settings are saved to the app folder and that (ideally) no trace is left on the computer. See this post for more details.
Hi there!
Yes, you are welcome to post any questions or feedback regarding the project, so you're in the right place. I have actually just read that post and started compiling a portable package!
But before uploading this package... let me first test out this package on a few different machines to confirm that it can run perfectly from a USB drive and absolutely no trace is being left on the target computer. It'll be just a couple of days.
I appreciate your feedback! :)
Kind regards,
Hiro
I've finished compiling and testing the portable version! You can download it from:
https://github.com/hiromorozumi/beepcomp/releases/download/v0.2.0/BeepComp_v0-2-0_portable.zip
Nice, thanks :) I tried to test it out in Sandboxie but it crashed whenever I tried to open it. Running it normally (Win10 x64) everything works fine. I'll make a post on the Portable Freeware forum notifying them of this great development, and they'll test it further. Keep up the awesome :)
Thank you for testing this portable package! Hmm... it might have to do with the program reading the default music txt file at start up - maybe Sandboxie is blocking the program from reading the file? I will find out what is causing this crash inside Sandboxie. I appreciate your report - I'll let you know once I've made progress! :)
Just finished working on this!
Now it is working fine inside Sandboxie.
The problem was easy to fix - I just changed all relative path references the program was using internally to absolute paths (which are determined at runtime), and voila, everything worked in Sandboxie.
One thing that I noticed is that if the program is stored in a drive other than C: and is run inside Sandboxie, the reference to that drive letter needs to be added in the "Quick Recovery" paths in the "Sandbox Settings", or any files that BeepComp saves or exports to will stay hidden. I'm guessing that this is a normal procedure for running any program from an external drive?
I uploaded the fixed version of BeepComp Portable on Github:
https://github.com/hiromorozumi/beepcomp/releases/download/v0.2.0/BeepComp_v0-2-0_portable.zip
Enjoy!
Please let me know if you notice any other issues :)
Last edit: Hiro Morozumi 2016-05-04
Thanks again! Runs just fine in Sandboxie as indicated, and testing here shows no residual files.
Regarding Sandboxie: yes it's fairly standard procedure, but only for initial portability testing. Once a program has been verified as portable or stealth, it can be run normally. Other typical testing methods are creating before/after system snapshots of the registry, running in a virtual machine that is completely clean. and using system file monitors to pick-up any changes made to the filesystem. There's a nice post here detailing all about this.
Some people use Sandboxie Portable for programs that aren't portable or otherwise leave unwanted residuals (some more instructions here).
But anyway, I'll be sure to return if any issues, bugs, etc are found. Have a good day further :)
Last edit: shnbwmn 2016-05-04
Hi shnbwmn,
Thank you for testing this further! And I am glad to know you were able to confirm that the program does not leave any residual files. I started reading the posts you linked. Those portablity testing methods they mentioned will definitely come in handy whenever I update the program.
BeepComp is registered at Softpedia, and when I let them know there is now a portable version available, they liked it and created a dedicated page for it. This lets me know that more and more people are choosing to use portable software.
I will continue to do testing on this portable package - thank you once again for making your feature suggestion! :)
Last edit: Hiro Morozumi 2016-05-05