15 replies to this topic

[amalux]

Just copy into your Apps folder and run! Tested in most builds (LiveXP and NativeEX) running WinXP (Pro) on many diff. machines - Works great! Have fun
[attachment=3327:Ghost_8.script]

Pulled due to licensing concerns.

[allanf]

Just copy into your Apps folder and run! Tested in most builds (LiveXP and NativeEX) running WinXP (Pro) on many diff. machines - Works great! Have fun
[attachment=3327:Ghost_8.script]

Interesting. Can you also provide a "script" with all the Ghost 11 (Solution Suite 2.x) files attached?

[pscEx]

Just copy into your Apps folder and run! Tested in most builds (LiveXP and NativeEX) running WinXP (Pro) on many diff. machines - Works great! Have fun
[attachment=3327:Ghost_8.script]

@amalux!

You should consider whether publishing this script is legal.

I think it is not!

Peter

[phox]

@amalux!

You should consider whether publishing this script is legal.

I think it is not!

Peter

This is exactly situation I have had in mind,
when I suggested that application scripts
should not be included in the scripts.

[amalux]

Interesting. Can you also provide a "script" with all the Ghost 11 (Solution Suite 2.x) files attached?

After my experience with 9 and 10, I gave up on newer versions of this program What is 'better' about 11? Does it require an individual license and/or activation? If so, forgeta bout it!

[allanf]

After my experience with 9 and 10, I gave up on newer versions of this program What is 'better' about 11? Does it require an individual license and/or activation? If so, forgeta bout it!

DOS-based with Vista support. No "individual" license; it's enterprise (minimum of 25 licenses, I think), like the Ghost 8 files you're distributing.

You're not worried about licensing? Are you?

[amalux]

@amalux!

You should consider whether publishing this script is legal.

I think it is not!

Peter

Hi Peter!

I think it's a grey area because there is no mention of scripts in the EULA that came with this version and there is no individual license or activation required. this is not a 'crack' or keygen etc. If this thinking (@Phox!) is taken to its logical conclusion, doesn't the whole project come in to question? What would M$ think about a fully functional Windows that can boot any computer anytime without entering a product key or need for activation? I trust your opinion Peter, should I pull the link?

[pscEx]

Hi Peter!

I think it's a grey area because there is no mention of scripts in the EULA that came with this version and there is no individual license or activation required. this is not a 'crack' or keygen etc. If this thinking (@Phox!) is taken to its logical conclusion, doesn't the whole project come in to question? What would M$ think about a fully functional Windows that can boot any computer anytime without entering a product key or need for activation? I trust your opinion Peter, should I pull the link?

I currently have Ghost 2003 which really is licensed.
Before that I have had Ghost8 (unfortunatelly 'recycled', including package). But as far as I remember Ghost8 has been licensed, too.

There are some licensed software packages which do not have special register codes or activations.
My WinZip is one of them. But inspite of missing register code I'm not allowed to distribute.

Maybe Ghost8 is similar.

I suggest to remove the attachements and to add a path to 'Your Ghost8 Installation' in the GUI.

So everybody having Ghost8 (for you and for the forum it does not matter whether legally or not) can use your script.

Peter

[phox]

I think it's a grey area because there is no mention of scripts in the EULA that came with this version and there is no individual license or activation required. this is not a 'crack' or keygen etc.

It's not question of the scripting but redistribution!

[amalux]

DOS-based with Vista support. No "individual" license; it's enterprise (minimum of 25 licenses, I think), like the Ghost 8 files you're distributing.

You're not worried about licensing? Are you?

This version can boot from DOS also, I'm not sure what the advantage is Don't know about the Vista support, have you tried it? If it doesn't work, that's reason 517 I don't 'upgrade' to Vista

Actually, I tend to think more in moral terms than legal, sometimes they coincide but in this case, I can't imagine anyone is worried about losing money from the sales of their newer, "better" products. Bottom line, I don't have Ghost 11 (or Vista) and wouldn't 'distribute' the files if I did.

[allanf]

This version can boot from DOS also, I'm not sure what the advantage is Don't know about the Vista support, have you tried it? If it doesn't work, that's reason 517 I don't 'upgrade' to Vista

Actually, I tend to think more in moral terms than legal, sometimes they coincide but in this case, I can't imagine anyone is worried about losing money from the sales of their newer, "better" products. Bottom line, I don't have Ghost 11 (or Vista) and wouldn't 'distribute' the files if I did.

Thanks!

[amalux]

I currently have Ghost 2003 which really is licensed.
Before that I have had Ghost8 (unfortunatelly 'recycled', including package). But as far as I remember Ghost8 has been licensed, too.

There are some licensed software packages which do not have special register codes or activations.
My WinZip is one of them. But inspite of missing register code I'm not allowed to distribute.

Maybe Ghost8 is similar.

I suggest to remove the attachements and to add a path to 'Your Ghost8 Installation' in the GUI.

So everybody having Ghost8 (for you and for the forum it does not matter whether legally or not) can use your script.

Peter

OK, it's gone; sorry for the controversy

I'm not clear on this option "add a path to 'Your Ghost8 Installation' in the GUI". How does that work?

[pscEx]

OK, it's gone; sorry for the controversy

I'm not clear on this option "add a path to 'Your Ghost8 Installation' in the GUI". How does that work?

@Amalux:
Thanks for your reaction

How to handle the path:
As an example look into the latest CreateISO script. Here FBWF is included, only if you define the path to certain files on your PC.

If there are some technical questions about the necessary script lines: Do not worry to ask here (Look at the very bottom of this post).

Peter

[amalux]

@Amalux:
Thanks for your reaction

How to handle the path:
As an example look into the latest CreateISO script. Here FBWF is included, only if you define the path to certain files on your PC.

If there are some technical questions about the necessary script lines: Do not worry to ask here (Look at the very bottom of this post).

Peter

OK, I see how this works and I like the concept! Given enough time (trial and error) I can probably incorporate this option, as needed, into my scripts. Is the ability to include this option available in any of the script creation tools? It's not available in the tools I currently use or in the one included with WinBuilder - Will this be added at some point?

[pscEx]

Is the ability to include this option available in any of the script creation tools? It's not available in the tools I currently use or in the one included with WinBuilder - Will this be added at some point?

@amalux!
Welcome as '.script developer newbie'!

Of course, all most of your intentions are doable by WB script lines!

As told above already, do not worry to ask.

Maybe as sample for options take the OB1 script.

It has nearly only options and nearly no other startements.

Peter

[amalux]

@amalux!
Welcome as '.script developer newbie'!

Of course, all most of your intentions are doable by WB script lines!

As told above already, do not worry to ask.

Maybe as sample for options take the OB1 script.

It has nearly only options and nearly no other startements.

Peter

Thanks again Peter, this really helps!