Subtitles of the Movie

And once the initial scan has taken place, you're presented with this screen to run the application install. And again, just like the Install Shield repackaging process, if there's any modifications you want to make after the application installs, if it requires a reboot, if you just want to reboot, you can do any of that at this point. In this case we're just going to run Install, which you can just run the executable directly. You don't necessarily have to click that button, although I did because this is what most people do in my experience. Obviously, like most Windows applications, it defaults to the directory it was run out of. In this case we'll look on Drive C in the Data Software and we'll run the Audacity Win 126.exe, just like before. So we'll just take all the defaults here, install to the default location. We'll choose not to create a Desktop icon with this. So we will choose not to launch Audacity. Now we're done. Again, very straightforward install. When the setup program is completely finished, press the Next Button. It hits Next. You're not prompted for the application's install directory. You can point out this directory at this point in the SnAppShot creation. If you leave it blank, just like it says there on the screen, it will not set a target distribution directory and you'll have to set that manually in the application object. We'll humor it this time and we'll choose C, Program Files, Audacity. And choose Next. This looks exactly like the pre-scan except now it is scanning again and comparing it to that pre-scan and again, since you probably don't want to sit and watch numbers increment for two and a half minutes, we'll just skip to the end of this whole process. And when it's complete, it says here's what I've done. I've created a new AOT, I've created new FIL Files, which are renamed copies of the newly-installed files, I've created a text version of the information captured in the application template and put it in the same directory and then it tells you to go into Console 1 and install the application object into Console 1 so it can then be distributed. And of course, we'll cover that elsewhere in this tutorial. But for now we'll hit Finish and we'll look at the directory that we got from running the SnAppShot. Now, for people that have uses in works previous to Version 7, you know exactly what you're looking at. For those that don't, we're going to go through what each of these files are. You'll see these numbered files, 1.fil, 2.fil, et cetera. These are the application files that were installed in the application directory. They're not changed, they're not compressed, they're not encrypted, they are simply renamed. If you happen to know which file was the main executable, you could take that fil file and rename it Start.exe and run it and it would work. So how do you know which files are which? By looking at this filedef.text file. If you open filedef.text, it tells you 1.fil is that help file. 2.fil is Audacity.exe, et cetera, et cetera. You can see all of the files that were installed in the application directory, all 64 of them. You can also look in this Audacity Win32.axt file and this gives you all of the options that were captured inside that aot file in a human readable format. See, I kind of fibbed earlier when I said that the aot file is not human readable. The aot file is not human readable; however you do have this axt that is and with a little bit of clever scripting or clever programming, you could pull a lot of information out of these axt files. Now, it's a generally-accepted good practice to keep this axt file around even though it's not really necessary. You can create an application object in Console 1 from either the axt or the aot. The Console 1 snap-ins prefer the aot but again, you can force it to use the axt if you really only have that file around. So now we have a legacy application object that we can manipulate elsewhere in this tutorial and now you know how to create these legacy application objects plus you know exactly what it is if you happen to run across a directory that looks like this as you're implementing ZENworks on your local network and with all of that said, this concludes our discussion on using ZENworks SnAppShot.