253 replies to this topic

[pscEx]

I use this script for all my builds, without any problems up to now
with this version of PowerISO script!?

Yes, a quick view across your script tells that it is rather propably not the 'bad boy' generating the troubles.

But to be sure:
Can you replace it by the standard 'CreateISO' script?

Maybe we have to do series of step by step tests. From the past I know that you are patient enough for that!

Peter

BTW: Can you also post the PowerISO script. If inside there are confidental infos, PM me.

[pscEx]

@Phox!

Before doing all these test I mentioned above:

Maybe in your system there is an old remainder of something wrong.

Can you either:

• Try the same project in a brand new installed WinBuilder folder
  
• Delete the Temp folder completely and delete the Workbench\<your project>\Cache folder.

And rebuild the project.

Peter

[phox]

@Pedro
@Peter

Thank you for all your help!

I have found what is wrong with Pedro's version of PowerISO script.

This is final VistaPE version:  VistaISO.zip   1.36K   156 downloads

This is Pedro's LiveXP version:  PowerISO.7z   1.31K   150 downloadsError: one Hive is not unloaded!

This is my final LiveXP version:  PowerISO.zip   1.31K   148 downloads

It concludes my quest for excellence of application scripts (for now!).

Thank you for your time and attention.

[phox]

Just for the kick, I have tested final LiveXP version of PowerISO script
with VistaPE and guess what: IT WORKS!

So this is universal version for VistaPE and LiveXP:  PowerISO.zip   1.31K   154 downloads

[pscEx]

I have found what is wrong with Pedro's version of PowerISO script.
Error: one Hive is not unloaded!

That means that Pedro can fix the Make Script?

Peter

[pedrole15]

That means that Pedro can fix the Make Script?

Peter

Peter
I have simply convert phox'script by hand not by MakeScript
He wanting just have registry convert to app script model

MakeScript can't do all ,but i hope it can help people to start scripting

Pedro

Note: there is probably some little bug

[phox]

Peter
I have simply convert phox'script by hand not by MakeScript
He wanting just have registry convert to app script model

MakeScript can't do all ,but i hope it can help people to start scripting

Pedro

Note: there is probably some little bug

@Pedro.

MakeScript is the great tool!

It has helped me in early stages to learn application scripting
and kept me active on the Forum.

This is my list of Forum's seven wonders:

1. WinBuilder.
2. nativeEx_Core.
3. API
4. PENetwork.script.
5. MakeScript.
6. BootLoaderISO.Script.
7. qEmu.Script.

After this recent experience I think you could safely adopt
%ProgramFolder%=%TBoxFolder% and adapt registry setting
function to produce from this Reg file:  _Register.zip   678bytes   147 downloads
this result:  RegSettings.zip   685bytes   94 downloads

I would like to thank you again, for your patience with me!

[phox]

I have tested MakeScript 15.5: you are almost there!

This is generated version:
 GeneratedPF.zip   378bytes   144 downloads
 GenShortcuts.zip   915bytes   143 downloads
 GenGhost.zip   758bytes   140 downloads

And this is wanted version:
 WantedPF.zip   524bytes   139 downloads
 WantedShortcuts.zip   920bytes   139 downloads
 WantedGhost.zip   758bytes   135 downloads

If you put %ProgramFolder%=%TBoxFolder% everything will be OK!
What is the problem to accept it?

I also suggest changing:
CheckBoxRAM="Run from ram (boot.wim)",1,3,30,23,168,18,False
to be in line with other check boxes.

[pedrole15]

I have tested MakeScript 15.5: you are almost there!

If you put %ProgramFolder%=%TBoxFolder% everything will be OK!
What is the problem to accept it?

I also suggest changing:
CheckBoxRAM="Run from ram (boot.wim)",1,3,30,23,168,18,False
to be in line with other check boxes.

Phox
Will see
but can you try if if work with the other methode : encoded in script and 7z encoded

[phox]

Phox
Will see
but can you try if if work with the other methode : encoded in script and 7z encoded

I could try, but problem is that I could make that change,
AFTER generating the script not before and then it will be too late!

Better solution is that you make test version with %ProgramFolder%=%TBoxFolder%
and I will test it several situation.

[pedrole15]

I could try, but problem is that I could make that change,
AFTER generating the script not before and then it will be too late!

Better solution is that you make test version with %ProgramFolder%=%TBoxFolder%
and I will test it several situation.

OK
Replace MakeScript.exe by this  MakeScript.7z   607.38K   172 downloads
Just added a CheckBox, no test

Pedro

[phox]

OK
Replace MakeScript.exe by this  MakeScript.7z   607.38K   172 downloads
Just added a CheckBox, no test

Pedro

That's it! Thank you!

I will test it very carefully.

[amalux]

Hi Pedro,

As promised, I'm testing MakeScript 15.5 (stand-alone) and love the concept but I'm running into lots of little annoyances. I want to be fair to you and honest (not just tell you what sounds nice), so here's my first impressions:

1) Should either include WBzip with download or at least inform people they need it in the same folder as MakeScript and provide link or info. where to get it.

2) When starting program, should go (open) directly to 'New' window; not to 'About' (credits) window and have to choose Files - New.

3) Program should save last settings; Program Source, Target Folder, Auto Name By... etc. Even though these settings and directories may change with the next run, at least you know how you set it up last time and start in the same directory rather than having to browse again (in my case) to another partition and down 3-4 sub directories back to my source files (in same directory as last use).

4) Odd glitch (?) where icon file names have first letter cut off when selecting shortcut .ico files in Customize - Shortcuts. I assume this is why all my shortcuts were 'icon-less', Desktop and Start Menu (but still worked). Strangely, this was not the case when choosing the Logo file which worked fine.

5) It seems your still using the 'old' scripting style; is this scheduled for change to reflect the new API?

Some spelling/grammar stuff (if interested)...


More cosmetic but still important...

In 'New' window, you list Click on 3 above Click on 2, seems odd to me (and underlined descriptives look to much like links).

I like the smaller, centered UI but when going back and forth between larger 'Preview' window, leaves smaller window 'off to the left'; can this be re-centered automatically? (OK, I'm getting really picky now, I'll stop here).

Thank you again for your great efforts, please take these 'criticisms' as constructive and well meaning; I just want your program to be the best it can be!

p.s. If still wanted , I'll look at the script version as well...

[pedrole15]

Hi Pedro,

As promised, I'm testing MakeScript 15.5 (stand-alone) and love the concept but I'm running into lots of little annoyances. I want to be fair to you and honest (not just tell you what sounds nice), so here's my first impressions:

Thank you for testing ,Amalux

1) Should either include WBzip with download or at least inform people they need it in the same folder as MakeScript and provide link or info. where to get it.

It is included in MakeScript package

2) When starting program, should go (open) directly to 'New' window; not to 'About' (credits) window and have to choose Files - New.

When you start from Winbuilder it do ,will also do it for standalone mode

3) Program should save last settings; Program Source, Target Folder, Auto Name By... etc. Even though these settings and directories may change with the next run, at least you know how you set it up last time and start in the same directory rather than having to browse again (in my case) to another partition and down 3-4 sub directories back to my source files (in same directory as last use).

All change you make are saved in an ini file, in menu select "Open last"

4) Odd glitch (?) where icon file names have first letter cut off when selecting shortcut .ico files in Customize - Shortcuts. I assume this is why all my shortcuts were 'icon-less', Desktop and Start Menu (but still worked). Strangely, this was not the case when choosing the Logo file which worked fine.

No it's intented the ico file must be in same folder as program

5) It seems your still using the 'old' scripting style; is this scheduled for change to reflect the new API?

Depend of how you have set Project type, full support for Api
For Api you must choose "App Script" all other use conventional scripting
It seem you have set it to LiveXP, Does the script work fine ?

Some spelling/grammar stuff (if interested)...

Thanks, sorry for my poor english


Pedro

[phox]

That's it! Thank you!

I will test it very carefully.

Tested with XPProSP3 (first time) and everything is OK with:

- Copy files from source,
- Encode files in script and
- 7zip encoded in script.

Great work!

PS: I will let you breathe freely for some time and come back with minor comments!

[amalux]

It is included in MakeScript package

You're right, it is

When you start from Winbuilder it do ,will also do it for standalone mode

This is what I see when I dbl-click MakeScript.exe (stand-alone)


...maybe better to start in 'Open last' by default?

No it's intented the ico file must be in same folder as program

Understood.

Thanks, sorry for my poor english

No reason to be sorry, just thought you might want to correct for next release


Thanks again Pedro for your awesome program! I'll probably have more questions but for now I just want to learn and have fun with it

[ispy]

Hi all ,

When I get time, I want to have a dabble with this program but I do not know the first thing about script writing so in a sense it might be better to read Nuno's script writing tutorials first or would it confuse issues in respect of MakeScript?

I have read somewhere that there is an api thingy that is supposed to make any scripts written with this conformity, forwards compatible with future versions of Winbuilder. So scripts written today will work equally with WinBuilders in the future? So what is the api convention, so if scripts are written they will not eventually become obsolete?

Questions

• Will this program write a script for any program or are there limitations in its usage.

• What is classified as a source file, is it the unpacked file before it is installed program on the PC, does it have to be installed & what about registry entries etc.

• Is it better to use a portable program to write scripts as some programs have more files than grains of sand in a large bucket & distribute files etc like shrapnel like a bomb exploding. I think program manufacturers should provide a log file so that when a program installs it lists path & files so the user has a fighting chance at removal.

• I have read that it is better to use SFX format to pack the files how is this done?

• What about programs like anti-Virus software, Anti-spyware utils that want to downloads def's etc
  
• where do these go if the media is read only are they hard coded to certain folders/dirs?

• what happens if the program goes looking for updates will it stall

• what about commercial programs with there passwords and activation what nots etc how is this embedded within the script?

• Is the standalone Makescript the best varient to use to start with?

Sorry about the amount of questions but these things have crossed my mind!

Regards & Best Wishes,

ispy

[pedrole15]

Hi all ,

When I get time, I want to have a dabble with this program but I do not know the first thing about script writing so in a sense it might be better to read Nuno's script writing tutorials first or would it confuse issues in respect of MakeScript?

Yes ,It's better to have some base before

I have read somewhere that there is an api thingy that is supposed to make any scripts written with this conformity, forwards compatible with future versions of Winbuilder. So scripts written today will work equally with WinBuilders in the future? So what is the api convention, so if scripts are written they will not eventually become obsolete?

Yes, MakeScript can build script with api or the old methode ,then you can learn more winbuilder language

Will this program write a script for any program or are there limitations in its usage.

It write simple script with or without interface
with or without shortcut for desktop,startmenu,sendto,quicklauch and autostart
with or without association
with or without registry (using the program reg2wbs of psc)
possibility to add 5 other program (shortcut in startmenu) from the same or a different folder of the 1st program
possiblity to add file in any folder (Window or I386,System32,etc..)

What is classified as a source file, is it the unpacked file before it is installed program on the PC, does it have to be installed & what about registry entries etc.

The source is the program.exe for which you want make a script (example for AutoIt, the program.exe is AutoIt3.exe)
MakeScript don't import automatic registry you must export registry entry by your hand, it simply convert it (with psc program) for winbuilder

I have read that it is better to use SFX format to pack the files how is this done?

MakeScript don't buid the SFX it only make 7z file but result is exactly the same

Is the standalone Makescript the best varient to use to start with?

It's same

I am not a good doc writer
When i got more time i will make a video tutorial
If someone have an idea which free program to use as example
The program must have multi folder, multi app or batch file , some association ,need registry entry,need some file in system32 or I386 folder
and i build the script and demo with MakeScript

[ispy]

Hi pedrole15 ,

Many thanks for the reply, I think I need to do some homework on script writing first it's just I didn't want to use your program, if it contradicted Nuno's script tutorials in any way. I can easily be confused, it comes naturally to me LOL!

Also when you decide a tutorial and you want someone to proof read from an english perspective I will offer my services if you would like?

First though, must complete the tables in the tutorials section.

Many thanks

ispy

[pedrole15]

Hi pedrole15 ,

Many thanks for the reply, I think I need to do some homework on script writing first it's just I didn't want to use your program, if it contradicted Nuno's script tutorials in any way. I can easily be confused, it comes naturally to me LOL!

MakeScript don't contradict Nuno's script tutorials, we are both promoting the api script
In the begenning i have wrote MakeScript for simplify the write scripting and promote the "Run from cd" of @Proton
After we have develop the api scripting with Nuno and Galapo and let fall down MakeScript because scripting begun so easy
And now restart MakeScript because it seem the api is not so easy
Perhaps I can't make thing simple
MakeScript is just a little tools for learn the api scripting

Also when you decide a tutorial and you want someone to proof read from an english perspective I will offer my services if you would like?

First though, must complete the tables in the tutorials section.

Many thanks

ispy

Many thanks ispy
Pedro

[pedrole15]

Updated to version 16.0
(Delete previous MakeScript.cfg before)
In section Lang in MakeScript.cfg
To have interface in french uncomment Default = FR
To use an other language uncomment File and set a filename
filename will be created in folder Lang based on the default Lang (FR or EN) and translate it


Pedro

Tutorial comming soon ...

[Nuno Brito]

What the heck, this tools keeps getting better and better!


Tested on a somewhat big sized app of the google earth program.


The UI changes are excellent when compared to my previous test, it's so simple to learn and understand quickly how it works.

Congratulations!

---

Now for the review:

- There is no stop button when creating the app script (google earth is big sized so I wanted to cease encoding and no option was available)
- Elapsed time and overall progress are a good indicator to know that the program is still working on the app script generation
- Full API support was a good decision to keep it as universal as possible
- Missing an option to change the shortcut title on the customizations tab
- Option to directly encode subfolders from the program folder is simply excellent and is working well.
- Once the script was done in background, by mistake I pressed the space key (or was it enter) and it began creating the script again
- Maybe an option to open the folder where the script is located would be a good idea (or open in notepad once it was completed) since it was a bit confusing to know where to find the script later (I found the button on the first panel but I didn't even read it when starting up the program - or perhaps a button there to open the target script folder?)
- Tool tips on buttons - the help you included next to each menu is excellent, only missing a few tool tips to hover around the buttons to allow users read a bit more about what they should do.


In overall, very happy with this new version - thank you for making it available.

[TheHive]

Thanks for the update. Havent tested yet. Borrowing somes net access for a few minutes. So will download it right now.

[jsgage]

MakeScript.script and MakeScript_16.7z has a Win32/Packed.Autoit.Gen Threat was detected

BUT MakeScript.7z is clean . reported to pedrole15

http://pedrole15.boo...keScript.script Win32/Packed.Autoit.Gen application connection terminated - quarantined Threat was detected upon access to web by the application: C:\Program Files\Mozilla Firefox\firefox.exe.

http://pedrole15.boo...akeScript_16.7z Win32/Packed.Autoit.Gen application connection terminated - quarantined Threat was detected upon access to web by the application: C:\Program Files\Mozilla Firefox\firefox.exe.

[pedrole15]

Thank you
Updated MakeScript.script with version 16.1
Removed MakeScript_16.7z