Portable Finder Startup ( TheOven_Startup.cmd )

Portable Finder Startup

Available at
\Apps\System Tools\'Portable Finder Startup'



This way following your personal portable applications on your disk (mostly usb disk, flash drive),
 You can:
  * add new applications
  * create shortcuts
  * add new drivers
  * start an application at startup
  * You can automate installing Windows to different pc (see WinNTSetup http://theoven.org/index.php?topic=1236.0 )
  *  etc. (Whatever possible with a .cmd available on PE)
without rebuilding your pe  .


When you add
TheOven_Startup.cmd
file to one of your drive at root. (most popular usb drive)
It will be executed 20 seconds after PE boots.



(20 seconds to wait all drives etc. ready)

**** Reminding ********
Plugin enabled default and probably you may forget this option available,
just put a TheOven_Startup.cmd to one of root of your drives with

Code: [Select]

nircmd.exe shortcut "%SystemRoot%\system32\cmd.exe" "~$folder.desktop$" "CMD Test"

If you see "CMD Test" at desktop after 20 seconds at boot, you have TheOven_Startup.cmd option available. 
**** Reminding ********




Example:
Extract ExtractTOUSB.7z to one of your drive
 ExtractTOUSB.7z (44.03 kB - downloaded 311 times.)

When you boot you will get 2 shortcuts at desktop and driveview application start






Idea to create such plugin
http://TheOven.org/index.php?topic=1892

Credits to laddanator "Portable Finder CMD"
http://theoven.org/index.php?topic=370.0

Ps: ExtractTOUSB.7z also attached to Plugin \Folder\ExtractTOUSB.7z



For more info see following posts

reminding:

when you prepare your own
TheOven_Startup.cmd

keep in mind you are responsible from any result following your .cmd (so called batch) skills.

Here is a tip:
to do special tasks for x64 or x86 builds
(ex: execute x86 version of an application on PEx86  AND execute x64 version of an application on PEx64)
You can use following .cmd trick:

TheOven_Startup.cmd

Code: [Select]

If "%PROCESSOR_ARCHITECTURE%" == "AMD64" Call :AMD64
If "%PROCESSOR_ARCHITECTURE%" == "x86" Call :X86

nircmd.exe sysrefresh
Exit

:AMD64
ECHO AMD64
REM Example nircmd.exe shortcut "%LaddsStu%\MyApplication\blabla.exe" "~$folder.desktop$" "TEST TEST"
REM Example Start "SH" /D "%LaddsStu%\MyApplication\BlaFolder" "%LaddsStu%\MyApplication\BlaFolder\Bla_x64.exe"
pause
GOTO:eof

:X86
ECHO X86
REM Example nircmd.exe shortcut "%LaddsStu%\MyApplication\blabla_x64.exe" "~$folder.desktop$" "TEST TEST"
REM Example Start "Bla" /D "%LaddsStu%\MyApplication\BlaFolder" "%LaddsStu%\MyApplication\BlaFolder\Bla.exe"
pause
GOTO:eof


with the possibility to add dynamic shortcuts to any portable program that you add to the USB.

You can also use the good sh.exe utility developed by nikzzzz for that exactly and with additional features: Shortcut, Add registry, Autorun, autoexit
Nice utility, maybe Nikzzzz could present it here 
Sh.exe - programmes portables Manager: http://usbtor.ru/viewtopic.php?t=298
Google Translate:

There is a demo program for testing and understand the config dile Sh.ini and the files link *.shl (eg: "link.shl") next to each apps, cmd
copy the content of ShDemo_for_Win, DemoPrograms folder included, to the root of your USB key.
and Run sh.exe or sh_x64.exe

Here is TheOven_Startup.cmd
with sh.exe and sh_x64.exe at root of usb

Drive:\TheOven_Startup.cmd
Drive:\Sh.exe
Drive:\Sh.ini
Drive:\Sh_x64.exe
Drive:\Sh_x64.ini
Drive:\ShCache.exe
Drive:\DemoPrograms\

\DemoPrograms\ from "Sh_2016_09_15.7z -> Sh_2016_09_15\ShDemo_for_Win\DemoPrograms"

TheOven_Startup.cmd

Code: [Select]

If "%PROCESSOR_ARCHITECTURE%" == "AMD64" Call :AMD64
If "%PROCESSOR_ARCHITECTURE%" == "x86" Call :X86

GOTO:eof


:AMD64
ECHO AMD64
Start "SH" /D "%LaddsStu%" "%LaddsStu%\Sh_x64.exe"
GOTO:eof

:X86
ECHO X86
Start "SH" /D "%LaddsStu%" "%LaddsStu%\Sh.exe"
GOTO:eof

Here is TheOven_Startup.cmd
with sh.exe and sh_x64.exe at subfolder of usb

Drive:\TheOven_Startup.cmd
Drive:\DemoPrograms\1Nikzzzz_SH\Sh.exe
Drive:\DemoPrograms\1Nikzzzz_SH\Sh.ini
Drive:\DemoPrograms\1Nikzzzz_SH\Sh_x64.exe
Drive:\DemoPrograms\1Nikzzzz_SH\Sh_x64.ini
Drive:\DemoPrograms\1Nikzzzz_SH\ShCache.exe
Drive:\DemoPrograms\

\DemoPrograms\ from "Sh_2016_09_15.7z -> Sh_2016_09_15\ShDemo_for_Win\DemoPrograms"

TheOven_Startup.cmd

Code: [Select]

If "%PROCESSOR_ARCHITECTURE%" == "AMD64" Call :AMD64
If "%PROCESSOR_ARCHITECTURE%" == "x86" Call :X86

Exit

:AMD64
ECHO AMD64
Start "SH" /D "%LaddsStu%\DemoPrograms\1Nikzzzz_SH" "%LaddsStu%\DemoPrograms\1Nikzzzz_SH\Sh_x64.exe"
GOTO:eof

:X86
ECHO X86
Start "SH" /D "%LaddsStu%\DemoPrograms\1Nikzzzz_SH" "%LaddsStu%\DemoPrograms\1Nikzzzz_SH\Sh.exe"
GOTO:eof

Testing on Gena, adding any \DemoPrograms\ ,
 sh.exe cause Gena taskbar unresponsive,
  probably Nikzzzz would improve in future.

Attached Nikzzzz sh Sh_2016_09_15.7z

Hmm, it does not become clear on how to use this feature.

In the corresponding Winbuilder section it is written:

"Add 'TheOven_Startup.cmd' to one of your drive"

Does that mean I have to generate at first the ISO, then open the ISO file (we.g. with UltraISO) and add the mentioned file manually?

Is there a way to add this file BEFORE generating (so that it is automatically available in ISO target file)?
if yes: Where exactly (in which subfolder) do I have to put the text file 'TheOven_Startup.cmd' ?

In the example script in WinBuilder nircmd.exe is used. Is it already available or do  I have to install it additionally?

Can I put "regedit" commands into the file as well?

Peter

In the corresponding Winbuilder section it is written:

"Add 'TheOven_Startup.cmd' to one of your drive"

I do not know such a winbuilder section .

Sorry, since Winbuilder closed source software,
 We can not add or remove something WinBuilder GUI .

 

How would call this



?

How would call this

It is written on plugin

Ok, now lets call it plugin.
But my initial questions are still unanswered

But my initial questions are still unanswered

your initial questions answered on topic post.

and even at FAQ & Tutorials http://theoven.org/index.php?board=35.0


*
From topics and posts you create,
 obviously you like to ask questions before practicing.
  and you like not to read all and follow provided information,
   instead you like to post.

With such behaviour,
 I advice Practice with projects at least 2 weeks,
   you will get your answers of your questions yourself.

Ok, so reading this thread, i was a little disappointed on the responses for this.
When someone is asking a simple question, please answer in a simple response. It will help those of us who are really new to this to understand in more details on what we need to do to get the results we are looking to achieve, and contribute back to the forum.

After performing allot of digging, as I am relatively new myself, I found that the Interface for the "Portable Finder Startup.script" is BROKEN in the Win7PESE project.

By comparing "Portable Finder CMD.script" and "Portable Finder Startup.script", I think i was able to deduce the "EDIT" button is not visible as it should be in the interface section of the script.. and since I am new to WinxPESE, I would not have known that!!

The "Edit" button uses a method for you to be allowed to edit the TheOven_Startup.cmd file, so this way, when it get's written to the ISO file, your user changes would be included in the Build process, and my ISO would contain the BAT/CMD script.

I can't just add, nor would i want to, to the ISO after the project is cooked.

Please update the Win7PESE "Portable Finder Startup.script" to include the "Edit" button to be visible and usable for all to use.
thanks

After performing allot of digging, as I am relatively new myself, I found that the Interface for the "Portable Finder Startup.script" is BROKEN in the Win7PESE project.

No it is NOT.

I was a little disappointed ,
Before someone is asking a simple question, someone should check provided plugins first,
where all have same title prefix to be found easily.
"Portable Finder CMD"
"Portable Finder Startup"
"Portable Finder Startup CD"
obviously there to serve different purposes.


There is already "Portable Finder CMD" plugin there that provides "edit" button where your user changes included in the "Build" process

"Portable Finder Startup" as well as "Portable Finder Startup CD"  only there to manually make additions AFTER having a ready cd/iso , probably after passing some time (months) , not at build time since not required. (No edit button required.)

Could you clarify some things please?
What directory should the TheOven_Startup.cmd file be in?
The description just says 'place it on one of your drives'? It does not say where!
Must it be in the root of any one of my drives?
Also, if I make an ISO using the Portable Finder Startup plugin, and boot the ISO from a USB as an ISO file, will it search all drives for the TheOven_Startup.cmd?
WHat if there is more than one cmd file on different drives?
Thanks.

Could you clarify some things please?
What directory should the TheOven_Startup.cmd file be in?
The description just says 'place it on one of your drives'? It does not say where!
Must it be in the root of any one of my drives?

Wow, hard to figure out I guess.
I put "root " to first post.

Also, if I make an ISO using the Portable Finder Startup plugin, and boot the ISO from a USB as an ISO file, will it search all drives for the TheOven_Startup.cmd?

naturally yes.

WHat if there is more than one cmd file on different drives?

Naturally first found one will be executed.
+
If you are interested feel free to add .cmd lines to detect such case and ask user to choose one.

*
As written on other topic,
Portable Finder Startup CD ( TheOven_Startup_CD.cmd ) will take your more interest,
Since TheOven_Startup_CD.cmd is available at root of cd-iso (or usb) to be customized more easily without editing wim ,
to get PEStartup or whatever operational.

Thanks! I missed the mention of 'root' in the first post - it would be more helpful if it was actually mentioned in the WinBuilder plugin itself though!

Anyway, the Win10PESE project by ChrisR has the Startup CD Finder and Startup Finder plugins already ticked.
So I built a standard, unchanged defaults, Win10 x64 WinPE.
However, when booting from Easy2Boot as an ISO, my \TheOven_Startup.cmd file does not run???
I can see both CD and USB script .cmd files in X:\windows\system32 - if I run the  Portable Finder Startup.cmd file from X:\Windows\system32 then my \TheOven_STartup.cmd is run,
So it seems that the X:\windows\system32\Portable Finder Startup.cmd script is not being called on startup?
Can you tell me where it is supposed to be called from? I can't seem to find any file in X: which mentions it or any reg entry?
Thanks

Scratch that! It seems to be working now!
It would be useful to know where it is called from though...?

Hi Steve6375,

mention 'root' at plugin itself now.

new plugins:
Portable Finder Startup
Portable Finder Startup CD
on All SE and Gena servers.


*

It would be useful to know where it is called from though...?

From your tutorial I see you already figure out. 

Plugin all opensource and should be easy to follow for an experienced user like you.