El_Pescador

*KISS* principle (keep it simple stupid!)--purchase one copy of Ghost--any flavor--use it any way that is available on one system--be it installing it on the system, booting from the installation CD, placing it on BartPE or Reatogo-X-PE CD, creating your own custom boot utility CD disc--you name it!  

If Symantec tosses in a second Ghost program with the purchase of Ghost 10--i.e. Ghost 2003 installation CD--I'm betting they would technically say you still have purchased only one license--and you choose which version of Ghost you wish to use legally on one system--if you have a second system--purchase a second copy of Ghost so you have a license for each system!

I think every other permutation of the options is just making excuses!

Rama

Quote:


But....he already did respond!--How Many PCs can I Install Ghost on?

Quote:

So, you have two computers--you use your *uninstalled* Ghost 10 installation CD to create images of computer A.  But now you want to use it on computer B.  I know what you are trying to weasel out of what he said--you're going to say because it's not installed, it's only being used on one computer at a time.

Well, I will agree--but, only if you destroy all images made of computer A first--because those images constitute continued use of that first copy of Ghost--so until you destroy those, if you now use that same single licensed copy of Ghost on the second system--that's a violation of your single license agreement!

The math remains the same--one license--one computer!

El_Pescador wrote on Mar 31^st, 2007 at 7:59pm:

It's in there, since the corporate version needs the same basic facility - in the console tasks you can specify a cloning operation using Windows drive letters and tries very very hard to make sure that it resolves the Windows volumes to the right thing in DOS. It's not the identifier of first resort any more, but it's still floating around in the code.

Taking out anything from a software product is always hard, because even if it's actively harmful it's hard to prove that you have found everything that depends on the thing you're removing. Case in point being the legacy Ghost.env registration system - we all hate that code with a passion because it's overly complex, it was never particularly secure anyway, it's a nightmare for installation, it serves no useful purpose for licensing any more, and with Ghost32 it was interfering with logo requirements to use code signing.

But, it turns out the original Ghost license key code (created in the 4.x timeframe from memory, which attaches some stuff to the executable) years ago had an extra function added to it; to allow people to stuff additional Ghost parameters into the .ENV files used for licensing, and that capability eventually grew into the OEM customization kit. So, it lives on... because as annoying as it is, it's deeply entangled with a documented feature we know people use.

Hey thanks a Million! for your tip I have been trying for 2-3 days now to get ghost 10 to do a simple image creation and restore with one road block after another. It would restore just fine, only it refused to resize. My staff had an older copy (2003) so I tried that and all looked good until about 10 min ago but I never could get the boot cd to load the DOS USB drives (ver 1 or 2) as it would lock up everytime. I just stumbled on your message and VOL LA! For the first time it appears to be restoring and resizing..I won't know for sure for another hour or so far so good.

regards,
Fletch

fletch wrote on Apr 4^th, 2007 at 5:10pm:


Thanks to El_Pescador and his tip in message #5 our system is now up and the drive is resized to the full 300mb .

regards, Fletch