Check here

Next the player carries out a series of exercises wearing a force-recording insole called a pedar. A template is then produced for the sole and stud arrangement around which the rest of the boot is based.

The blueprint is then converted into the finished boot using a technique developed by University College London researcher Siavash Mahdavi. The 3-D design is replicated by laser printer.

For geeks, here’s how the click tracking script works: The script loops through all of the IFRAME on the page, and if the IFRAME source includes a google or chitika or yahoo ad server address, it will attach the corresponding function as an onfocus handler. When the ad unit obtains focus, urchinTracker() is called, with a goal identifier.

You will also have to create individual goals in Google Analytics for your website profile. Google lets you define only 4 goal, so choose wisely. You can always add new goal and delete the older ones.

…to a spider-friendly format:
http://www.zend.com/myscript.php/myvalue/Hello

Notice that the spider-friendly format contains no indication that there are any parameters being passed at all. Rather, it simply looks like we are trying to access the directory on the zend.com site /myscript.php/myvalue/Hello, and any search engine spider that accesses the page won’t have any trouble following the URL. Yet in reality we are executing the script myscript.php.

But what happened to your parameters?
How to GET your hidden data

Now that you have successfully hidden your parameters within what appears to be a directory structure, how do you get them out? Whenever a PHP script is executed with extra path data appended to the end of the filename (as we did in the spider-friendly example above), the Web server creates an environment variable $PATH_INFO containing this information. You can then access this environment variable through PHP automatically, and parse it to retrieve our data. So our earlier URL…

http://www.zend.com/myscript.php/myvalue/Hello

…would populate the $PATH_INFO variable with:

/myvalue/Hello

…from which you can then parse and retrieve the passed information.
Deciphering your data

Now that you know where your parameters are, the next step is to decipher them into a format that PHP can use. Although there is no required method for doing this, I’ll assume that you have formatted your data in the following way:

/var_name/var_data/var2_name/var2_data/…

Using this method, all that is left is to:

* break the provided string every time we encounter a slash (’/')
* create variables to associate the given names (var_name, var2_name, etc.) with their respective values (var_data, var2_data, etc.)

With all of this in mind, let’s look at some real code.
The script

As with many powerful techniques, the code required to create this ability in your scripts is not difficult to develop. The process consists of traversing an array based on the $PATH_INFO, and creating variables based on that data. In the end, the object is to take the URL…

http://www.zend.com/myscript.php/myvalue/Hello

…then use the data provided in the $PATH_INFO variable to construct corresponding variables:

$myvalue = “Hello”
Code flow

* Check for the existence of $PATH_INFO
* Split $PATH_INFO into an array
* If the total number of parameters is even, add an extra empty element at the end to simplify the traversal in the next step
* Traverse array and create variables based on the $PATH_INFO data

< ?php

if(isset($PATH_INFO)) {

$vardata = explode('/', $PATH_INFO);

$num_param = count($vardata);

if($num_param % 2 == 0) {

$vardata[] = '';
$num_param ;
}

for(var $i = 1; $i < $num_param; $i = 2) {

$$vardata[$i] = $vardata[$i 1];
}
}

?>

If Windows finds a (plain text) file called AUTORUN.INF in the root directory of a CD then it follows the instructions in this file to run a program. This example AUTORUN.INF file tells Windows to run program setup.exe (from the root directory of the CD):

[autorun]
open=setup.exe
icon=snazzie.ico

Use the Windows Notepad application to edit plain text files (it is in the Start All Programs Accessories menu).

Your CD users may have switched off AutoRun. This might be because they are concerned about viruses. Also, if they press the Shift key down while inserting the CD, AutoRun is disabled. In Windows NT4, 2000 and XP systems, only Administrators and Power Users can use AutoRun.

There is no way to force your users to use AutoRun. It is therefore good practice to provide instructions so that users know how to start your CD, eg tell them to open file index.htm in their browser. These instructions are also required if your CD might be viewed by non-Windows users.

So why is ShellRun needed?

Until recently, it was not possible for Windows to AutoRun a file rather than a program.
OK, that’s not strictly true: you could use the following AUTORUN.INF to show web page index.htm

[autorun]
open=start index.htm

However, if you do this, Windows displays a DOS box briefly, which looks nasty. (And start might not be available on some systems.)

If you are only targeting recent Windows systems, then you can use the shellexecute command to open a file without a flickering DOS box:

[autorun]
shellexecute=index.htm

What does ShellRun do then?

ShellRun overcomes the above problems. It shows your file and displays a neat popup window. The popup appears straight away so that the user knows that something is happening. ShellRun works in all Windows systems.

This example AUTORUN.INF tells ShellRun to show web page index.htm while displaying message “Starting CD now…” in the ShellRun popup window.

[autorun]
open=ShellRun.exe index.htm Starting CD now…

Do not forget to put ShellRun.exe in the root directory of your CD along with AUTORUN.INF.

Viewer Technicalities

All the above AutoRun examples, including ShellRun, use the same core technique to display a file.

Windows associates a viewer program with each file type. For .HTM and .HTML web pages, the viewer program will be your default browser.

If a user does not have a viewer for your file type then it cannot be displayed until a viewer is installed. For example, if you are trying to show a PDF file, the user must have Adobeâ„¢ Acrobat Reader or equivalent installed.

If a viewer is not available, the freeware version of ShellRun just displays a message. In retail version you can prompt the user to run a viewer installation program. See the Viewers page for more details.

If you have a viewer program available then put its installation program on your CD - if you are allowed to distribute it. To distribute Adobeâ„¢ Acrobat Reader, see here: Adobe Acrobat Reader - Download Adobe Acrobat Reader for distribution.

Enabling AutoRun on your computer

To test AutoRun you need to have it enabled on your computer. A registry setting can be used to disable AutoRun. Click Start Run then type in regedit. Select Edit Find and type in NoDriveTypeAutoRun. This value should be found in this key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer .

The NoDriveTypeAutoRun value should be hexadecimal 95 if AutoRun is enabled on all CDs, or B5 if disabled for CDs. (If you want to test AutoRun on a floppy disk, set this value to 91.) You may need to change more than one instance of NoDriveTypeAutoRun in the registry. You usually need to reboot for a new value to take effect.

In Windows 95/98/Me the NoDriveTypeAutoRun value is displayed as 95 00 00 00. In Windows NT4, 2000 and XP this value is displayed as 0×00000095 or hexadecimal 95. If you modify the NoDriveTypeAutoRun value make sure it is still in the correct format.

Bart’s PE Builder helps you build a “BartPE” (Bart Preinstalled Environment) bootable Windows CD-Rom or DVD from the original Windows XP or Windows Server 2003 installation/setup CD, very suitable for PC maintenance tasks.

It will give you a complete Win32 environment with network support, a graphical user interface (800×600) and FAT/NTFS/CDFS filesystem support. Very handy for burn-in testing systems with no OS, rescuing files to a network share, virus scan and so on.
This will replace any Dos bootdisk in no time!

PE Builder is not a Microsoft product and does not create Microsoft Windows Preinstallation Environment (”Windows PE”). Using PE Builder does not grant you a license to Microsoft Windows PE or to use the Windows XP or Server 2003 binaries in a manner other than stated in the End-User License Agreement included in your version of Microsoft Windows XP or Windows Server 2003. Microsoft has not reviewed or tested PE Builder and does not endorse its use.