Portable Apps On CD (UnWritable Environment)

Hi Lancelot,

Following meerschaum (reply 18),
  and following Starla idea to create vhd at startup (imdisk not required) (reply 26),
   plugin attached, (put to Components)

Thanks gizmoshq keep attention on this   

I followed  the post and thought this might also be helpful for PortableApps.com.
It seems as if the portable apps are mounted to CD or a virtual CD they have problems,
because they need to expand some files and there is no space.  If the apps where opened
in a virtual hard drive there would not be this problem.  You may have already a work around
for this problem, but I'm still a little new to this application.    Thanks for the help.

Hi Mark,

Split topic since very out of discussion,

yes, not born portable apps have such problems,
on plugins we make precautions for such apps, but on personal ....

First

If the apps where opened
in a virtual hard drive there would not be this problem.

Well, we made it on Gena  and it was working, I don't know how it goes on SE..

Try this:
Create a .vhd (Mark.vhd) and put files in it,
put this Mark.vhd at cd, (Create ISO - RootCD option)
Build and run project (on emulator)
mount Mark.vhd (writable),
see if you can mount ? and your portable app work 

ps:
also let me know your results for http://theoven.org/index.php?topic=1167 

Hi Lancelot

Try this:
Create a .vhd (Mark.vhd) and put files in it,
put this Mark.vhd at cd, (Create ISO - RootCD option)
Build and run project (on emulator)
mount Mark.vhd (writable),
see if you can mount ? and your portable app work 

ps:
also let me know your results for http://theoven.org/index.php?topic=1167 

I did as you said. I created a .vhd in Windows 8, formatted to ntfs copied the apps into the drive.
Copied to RootCD and ran winbuilder program. Started PE and I found the .vhd in the root of the CD drive.
I could open it with Win7 and all programs where inside, but not accessible to use.  Tried to load
as Virtual Drive but after it asked me to format the drive.

Interesting ...

Well, let's use conventional way than 

Use a starter for utilities that needs writable environment,

When you build with  (or green play button)
Apps\HD Tasks\Active@ Partition Manager 1
(just updated to v7 for this topic ;))

you will find PartManFree_Starter.cmd inside Program Files\ folder,

copy PartManFree_Starter.cmd to your other program that you have trouble with
change first 2 lines
Set ProgramExe=PartManFree.exe
Set ProgramTempFolder=ActivePartitionManager1
to your program .exe and Folder

and rename PartManFree_Starter.cmd for your needs

double click inside .iso (rootcd, or whatever method you like)


--->
What it does, it checks if environment is writable,
 if yes only starts ProgramExe,
 if no than copy to Temp\subfolder and starts ProgramExe there



See if solves your trouble ?

Hi Lancelot,

Use a starter for utilities that needs writable environment,

When you build with  (or green play button)
Apps\HD Tasks\Active@ Partition Manager 1
(just updated to v7 for this topic ;))

you will find PartManFree_Starter.cmd inside Program Files\ folder,

copy PartManFree_Starter.cmd to your other program that you have trouble with
change first 2 lines
Set ProgramExe=PartManFree.exe
Set ProgramTempFolder=ActivePartitionManager1
to your program .exe and Folder

and rename PartManFree_Starter.cmd for your needs

double click inside .iso (rootcd, or whatever method you like)

--->
What it does, it checks if environment is writable,
 if yes only starts ProgramExe,
 if no than copy to Temp\subfolder and starts ProgramExe there

So what you are telling me is if say one of the Portable Apps need additional environment
then it will create it for that program only?  Will it work for all apps if I place it will PortableApps.com
folder. How do I start the program using the cmd? Can it start a ram drive or is this out?

Hi Mark,

no need to quote 

I don't much know PortableApps.com , I don't use ;)
 (I have very little apps from them , most of them already are out of box portable that does not require a starter/loader ...)


Above is a verrry General Solution that you will easly figure out when you practice 




Let's continue with Active Partition Manager 1 example:

get green play button, take
ActivePartitionManager1
folder out of Program Files,

put ActivePartitionManager1 folder to root cd,

see what happens when you double click PartManFree.exe
and see what happens when you double click PartManFree_Starter.cmd
->
tip: after doubleclick PartManFree_Starter.cmd , check %temp% folder ...



another trial,
put ActivePartitionManager1 folder to your usb (ufd) or disk, desktop etc.
and see what happens when you double click PartManFree_Starter.cmd

observe the difference between root cd (unwritable environment) and desktop (writable environment)


after observation, you will quickly figure out method 


**
some more words about PortableApps.com,
 as far as I remember, they also had discovered that in past, but did not update all their applications with their new loader etc. ,
   if possible, it would be easy to add PartManFree_Starter.cmd to their menu !?! (or any other .cmd you will create ...)
    well I only had used PStart in very past, today I only go to folder and doubleclick .exe 

See You

Hi Lancelot,

some more words about PortableApps.com,
 as far as I remember, they also had discovered that in past, but did not update all their applications with their new loader etc. ,
   if possible, it would be easy to add PartManFree_Starter.cmd to their menu !?! (or any other .cmd you will create ...)
    well I only had used PStart in very past, today I only go to folder and doubleclick .exe 

I see how the cmd works. I tried it on a single portable program and it worked great.  If you use it for the entire
PortableApps folder it files up all the x: drive with the temp programs. I played around with the vhd and it only
loads properly if you have it on a hard drive (not CD) and you load it through the disk management tool (attach vhd). Needless to
say no quick fix. I have put as many programs on the Y: drive as possible, except the programs that are 32 bit and 64 bit.
They work but when you duell boot the y:\Programs have to be the same operating system.  So those I put in ram. I also put
all the portableapps that work on the y: drive.  For now this is the best possible option. I also renamed any script
that was just x86 to show only x86 and any that were both x86/x64 as most all script already indicated.  Thanks for all your
help with all these programs.  I am also wondering if there can be a server like Gena that the SE programs will all be compliant?
Being new I really didn't realize that Gena had so many good programs.  You have keep up with all the demands on Gena. If there
is anything I can do just let me know as far a testing scripts on Win8.1SE.

Another idea,

put Mark.vhd inside Mark.wim
boot SE, mount Mark.wim, Attach Mark.vhd

only an idea 

except the programs that are 32 bit and 64 bit.
They work but when you duell boot the y:\Programs have to be the same operating system.

I don't understand,

Current organisation is:  when you use same set of Apps, and build projects (say: Win81SE x86 , Win81SE x64) same Programs folder serves both.

This is valid for all projects, theorically you can build all SE projects x86 and x64, and Gena x86 and x64,
 and use same programs folder easly ...

I am also wondering if there can be a server like Gena that the SE programs will all be compliant?

There is also Yomi http://theoven.org/index.php?topic=175.0
Apps not up to date, but it is nice to see things

and rest is at plugin section http://theoven.org/index.php?board=9.0

As long as common syntax used, all plugins work on current and future projects 

If there is anything I can do just let me know as far a testing scripts on Win8.1SE.

Share the plugins of apps you like 
http://theoven.org/index.php?board=9.0
There are lots of interesting, fun apps out there, we can't know all 

and further, when you notice something, let us know 

See You

Hi Lancelot,

except the programs that are 32 bit and 64 bit.
They work but when you duell boot the y:\Programs have to be the same operating system.

I don't understand,

Current organisation is:  when you use same set of Apps, and build projects (say: Win81SE x86 , Win81SE x64) same Programs folder serves both.

This is valid for all projects, theorically you can build all SE projects x86 and x64, and Gena x86 and x64,
 and use same programs folder easly ...

You are right except when the let say (y:\programs\Paragon\Manager\explauncher.exe) has the 64bit name explauncher.exe and the 32 bit the same name.
I know that in many scripts it changes the programs name to _64 but that does create another folder but what I like
is when the x64 and x86 uses the same shared programs folder to eliminate space. It is normally always about trying
to save space and make every program work at it absolutely highest efficiency. So when I install Opera in run CD it works
in 64 and 32 environment in duel boot. This is not a programming problem, it is just being aware of what each program does
and put it in the correct environment at build time. Just take getting used to. All the apps are great and fully functional.
I know you are looking at advanced portions of the program and I look at the simple build process.  Thanks for all your expert help.

Well, what I say is valid for plugins on servers 

It will gain you (and all) time and space


*
We don't only use seperate folders, for such cases we also use same folder,
(PC Provide Files --> MultiArch - MultiExe - Same Folders)
like Total Commander plugin 

only shortcut inside pe changes .... etc...

I see your only exception is Paragon,
If it is ok changing name explauncher.exe to explauncher_64.exe  (if all rest files are same ;) , like Total Commander),
 than there would be no trouble 

Let us have a
PC Provide Files --> MultiArch - MultiExe - Same Folders
Paragon PM plugin around
Paragon_Partition_Manager_14.script ? (15 16 17 ..)