Delbridge.Org

A Musician's Guide to QR Code

2010-06-25T05:06:00Z

For DIY musicians, Quick Response Code, or "QR Code," may represent the biggest thing to hit guerilla music marketing since the vuvuzela. And by "hit," I mean a right sucker punch to the mouth. Already the rage in Japan, passers-by can scan a band's gig poster into their smartphone and download a free music sample on the spot, or be transported to a special web page with discounted ticket and merchandise offers. Engaging stuff.

But elsewhere - I'm looking at you, America - QR Code is only just catching on. Many camera-equipped smart phones still cannot scan the curious pictograms with any reliability. Those that do may fail to launch the phone's native web browser or refuse to download an MP3 audio file. Welcome to the bleeding edge. What's more, American consumers are only just becoming familiar with the crossword-like squares and how they can open gateways to free music and discounted goodies.

But wait! That's good news for ambitious bands looking to capitalize on emerging trends. Bleeding edge, be damned! Let's put these codes to work for us now, while the novelty is hot and before the competition catches up.

What Is QR Code?

Technically speaking, QR Code is an improved, two-dimensional bar code. Whereas traditional barcodes provide one line of information with limited error correction - this is evidenced by the number of times your checkout clerk scans and rescans your deli meat - QR Codes provide multiple lines of information and much greater error correction. In fact, with as much as 30% of a QR code smudged or missing, a quality scanner can still read and interpret the code's meaning. Try that with your meat.

QR Code Error Correction Levels	Capability
Level L	~ 7%
Level M	~ 15%
Level Q	~ 25%
Level H	~ 30%

To be specific, the QR Code technical specification defines four selectable levels of error correction (see table), employing the same Reed-Solomon error correction algorithm used by music CDs. Greater levels of error correction capability require more data redundancy and, consequently, will increase the size ("symbol version") of the symbol accordingly.

QR Code is free to use. Japanese corporation, Denso-Wave, invented the technology in 1994, but chose to share, rather than capitalize on its patents.

Though designed for commercial parts and shipment tracking, QR Code has become synonymous with mobile tagging, or hardlinking, whereby physical objects are linked to virtual content. When printed in a magazine ad or on a billboard, for example, consumers may scan the real-world advertisements with a camera-equipped smart phone and immediately view the linked virtual content.

To that end, mobile tagging appears to be purpose-built for musicians. How many industries market a product that can be beamed freely to its customers? Just as the Internet and MP3 file formats equalized music distribution in the 90's, mobile tagging takes an equivalent leap forward in the field of music marketing. Other businesses can deliver offers and incentives, but only media makers can deliver the goods. Anywhere. On the spot.

It's also worth noting that indies and DIY musicians who already offer free music downloads can make the most of QR Code right away, while traditional record labels continue their struggle with digital music, downloads, and generally, the 21st century. In other words, those who give the most can gain the most from QR Code.

How To Make Your Own QR Code

The Internet is chok full o' free QR Code applications you can use to create your own code images. My personal favorite is Kerem Erkan's QR Code and 2D Code Generator (http://keremerkan.net/qr-code-and-2d-code-generator/), by virtue of its features. Of the code generators I tested, some were prettier, but Kerem's was the only one that allowed for the selection of error correction level.

Another QR Code generator worth checking out is offered by i-nigma.com (http://www.i-nigma.com/CreateBarcodes.html). Though fixed at Level M error correction, it displays and updates your QR Code image in real-time, as you type. This novelty demonstrates nicely the relationship between coded message size and code version (image complexity).

Not enough online code generators fer ya? Check out the list of QR Code Generators Online, at 2D Code.

WhERE Should My QR Codes Link To?

When choosing a link destination, consider the longevity of the marketing campaign. Shorter and experimental campaigns pose few concerns. However, if you'll tattoo your code on your forehead (see "Where To Display Your QR Code," below) or otherwise publish your code forever and ever, it's critical that you maintain 100% control of the destination content. Do not link to Facebook, Twitter, MySpace, YouTube or any other third-party destination because, quite simply, they might not be popular, accessible or alive in ten years. Instead, be sure to link to a domain name that you own, that is free from any potential trademark, business or partnership conflicts and that holds content you can readily modify at any time - that is to say, the content is not built upon a particular programming language or other technology that will limit your options.

Long-term campaigns should probably link to a standard HTML web page rather than a music, movie or other media file (e.g., http://mywebsite.com/mymusic.mp3). While you might be able to replace the "mymusic.mp3" content, you will be limited to that file format and, again, the format might be incompatible with future media players. By contrast, a standard web page is largely future-proof and can either incorporate, link to or automatically redirect visitors to your content du jour, including said MP3 audio file.

To further protect yourself from digital obsolescence, I recommend using a directory URL (e.g., http://mywebsite.com/mysub/) rather than a document URL (e.g., http://mywebsite.com/mysub/index.html). This way, you can specify the default filename to deliver in the web server's settings and, more importantly, change it later. So, for example, your web server could deliver a default document of index.html today, index.php tomorrow (when you launch that new interactive webpage design), mysong.mp3 next month, and mysong.mp6 when the audio file format is invented in ten years.

A directory URL also has the advantage of being shorter. Shorter URLs in your QR Codes have two benefits. First, if you choose to display the unencoded URLs aside your QR Code pictograms (many advertisers do this for the benefit of those without a compatible phone), shorter URLs are easier to remember and much easier to type into a Blackberry or other "thumby" device. Another advantage of short URLs is that they produce smaller, simpler QR Code images that are easier to scan at small sizes and greater distances. When embroidered on a hat, for example, the code image produced by a lengthy URL may be too complex for sewing machines to render properly and the results too choppy for scanners to read.

To demonstrate the importance of small webpage address URLs, the three QR Code blocks displayed below resolve to addresses with twenty-nine characters, 60 characters, and 90 characters, respectively. Which one would you feel safest stitching on your band's 2010 world tour apparel?

And while we are on the subject of image optimization, we should discuss error correction, being that higher correction levels produce larger, more complex code images. Fortunately, error correction Level L (the lowest error correction level) is sufficient for most print applications and affords the smallest, simplest code images. Anything above Level M is discouraged, except for mission-critical applications that are likely to generate damage to the code image, such as inventory tracking and shipping. That said, know that higher error correction levels afford greater artistic freedom, should you wish to incorporate overlapping graphics, non-uniform backgrounds and low-contrast colors, for example, into your design. Irregular surfaces, such as T-shirts might also demand Level M. But there's no one-size-fits-all rule here. Use your own judgement and, most importantly, test thoroughly before committing to a high-production run.

As already suggested, musicians will be tempted to link their QR Code directly to an MP3 audio file. However, my experiments revealed a few caveats. First, American cell phone technology isn't quite ready for this application. In my attempts with Blackberry and iPhone 3GS smart phones, only one out of four code reader applications succeeded in cueing up the destination audio file. Not surprisingly, the commercial ($0.99) QuickMark iPhone app - it is recommended by Google - succeeded while all of the free code readers failed.

Another thing to consider when linking to MP3 files is that many cell phones operate on limited data plans. As such, when you push a multi-megabyte file to somebody's phone without warning, it could be regarded as a frivolous, self-serving consumption of the subscriber's resources. While it remains to be seen how public opinion will judge such promotional activities, a safer alternative would be to offer an opt-in landing page instead. On it, you can clarify the song title, file size, and a bold "download now" button, linking to the opt-in MP3 file.

Have fun with your links! Those who scan your code want to be surprised and rewarded, so give them a gift - free music, free tickets, a discount, a laugh, or some other surprise. Hold a contest or scavenger hunt, incorporating QR codes pasted around town. Whatever you do, do not punish your visitors with a heartless sales pitch. Deflate them and they might not bother to scan your next poster. Or worse, they might not bother to scan anybody's poster.

Where To Display Your QR Code

For guerilla music marketers, QR Code pops the top on a whole new can of opportunities. Anywhere you would display a promotional piece, you can hang or incorporate a custom QR Code. And if graphic design is your weak point, you can take advantage of QR Code's novelty right now by pasting unmodified printouts around town.

Give your QR Code legs! Branded T-shirts and hats have longevity over posters while adding a social component. Artists can wear their own codes and invite prospective fans to "scan me" (wink, wink). And speaking of sex - you knew I'd get there eventually - silkscreen your code in a tantalizing spot (e.g., butt shorts) for laughs and flirtatious scans. How 'bout a tattoo? If that's too bold (or too "big brother") for you, know that custom temporary tattoos are also available and make terrific give-aways.

Nevermind that QR Codes will appear in national and international advertising campaigns. For indie bands, QR Code returns our attention to the local market, or wherever you have a street presence. In other words, the worldwide Internet, though heralded as the "great equalizer" for struggling musicians, has become a crowded, difficult environment in which to gain fans. But place a QR Code on your gig posters and watch your website buzz with new fans. What's more, you'll generate local fans who might otherwise never attend a live show.

Last, but certainly not least, be sure to create a separate QR Code for each of your advertising campaigns. Record the name and description of the campaign (e.g., "Sacramento Gig Posters"), the publication date and destination link (e.g., http://myband.com/qrcode/sac_gig_2010/). This way, you can track the success of each campaign in Google's WebSense or other web stats application and tweak your promotional efforts accordingly.

That's it, my minions of self-construction. I sincerely hope you find this information helpful. Now, go perpetrate some mobile tagging and be quick about it, before I beat ya to it.

Mouse Trouble in Microsoft Word After Windows Update

2010-03-31T11:03:00Z

It must be Wednesday. My Windows desktop is blissfully clean where three-hundred Firefox windows once were, and Microsoft Word 2007 has gone funky - the mouse doesn't work, except for opening menus. Yup, it's Wednesday, when Microsoft pushes out its Windows updates. I've seen this four times now and, though it has been documented elsewhere, I'm composing this blog post - a note to myself, really - so that I may never again need to Google the solution.

To clarify the problem, after a Windows Update, the mouse pointer in Microsoft Word 2007 refuses to select most application controls, including document components, window sliders, and more. Menu items will function, if only enough to close the application, but then Word throws an application failure message with the option to restart Word and to notify Microsoft of the trouble. When Word restarts, the problem recurs. Likewise, restarting the system doesn't remedy the situation.

The solution, it turns out, is to remove (or, more prudently, rename) a particular Windows registry key. Here's the steps:

Close Microsoft Word 2007
Launch Windows Registry Editor (regedit.exe)
Rename the following registry key to "Data_Backup," for example:
```
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Word\Data
```
Close Registry Editor

The trouble should be gone. Launch Microsoft Word 2007 and resume your document-editing goodness.

I hope you find this information helpful.

How to Install ColdFusion 9 on Windows 2000 / IIS 5

2010-03-06T11:03:00Z

With the release of Coldfusion 9, Adobe has officially discontinued CF support for Windows 2000, this just prior to the operating system's official EOL. For what it's worth, it appears that the policy change was not by design. According to the blog post, "Coldfusion 9 Initial Reactions: Installer Woes," Adobe's official list of system requirements included Windows 2000 until problems were reported. Then, rather than produce a fix or publish a workaround in the Adobe Knowledgebase as would be typical, the company simply removed the OS from the list. This is evidenced by so many VARs still showing the original, uncorrected compatibility list. In another article (which I can't seem to locate), an Adobe support rep offered suggestions for circumventing the installer, but with the caveat that any such installation, even if successful, would be "unsupported" by Adobe. That's scary if you plan to go live with CF9 on a Windows 2000 server. What might the next service pack do to your installation? But then, if you're reading this article, you're more scared by the expense of upgrading your OS and, no doubt, your "old-skool" server hardware. In this economy, non-essential upgrades are a luxury some of us simply can't afford.

I'm happy to report that ColdFusion 9 can indeed be installed on Windows 2000 with IIS. Success was the product of two separate Adobe TechNotes (and a little experience with prior CF versions):

Understand, however, that these TechNotes predate ColdFusion 9 and do not address this challenge directly. For clarity, I have parsed out the relevant bits and traced my exact steps below.

Needless to say, it is merely apparent at this time that my installation was successful - the ColdFusion Administrator has launched and no errors are apparent in any server logs or web pages. Still, there may yet be gremlins to discover. I will post any such discoveries here and encourage others to do the same. It's worth repeating that Adobe has declared installations of Coldfusion 9 on Windows 2000 to be "not supported." Likewise, I offer no guarantees. Proceed at your own risk.

Part 1: ColdFusion 9 Command-Line Installation

Coldfusion 9's GUI installer fails on Windows 2000, getting itself stuck in a loop while trying to install the Microsoft VC++ 2008 Runtime. You can break out of this loop by closing the window, but then the installation fails nonetheless. The workaround is a command-line, or "silent" installation. Follow these steps to perform a silent Coldfusion 9 installation:

With Notepad, create a new text file, with the following content. [For an explanation of these and other allowed parameters and acceptable values, visit the aforementioned Adobe TechNote, "Install ColdFusion 8 Silently" and perhaps also "Installing ColdFusion MX 7 Silently."] These are the values I used for installation on Windows 2000 w/ IIS 5.

INSTALLER_UI=SILENT
SILENT_LICENSE_MODE=trial
SILENT_SERIAL_NUMBER=
SILENT_PREV_SERIAL_NUMBER=
SILENT_INSTALLER_TYPE=standalone
SILENT_INSTALL_ODBC=true
SILENT_INSTALL_VERITY=true
SILENT_INSTALL_SAMPLES=false
SILENT_INSTALL_JNBRIDGE=true
SILENT_INSTALL_FOLDER=C:\\ColdFusion9
SILENT_WEBROOT_FOLDER=C:\\Inetpub\\wwwroot
SILENT_ADMIN_PASSWORD=password
SILENT_ENABLE_RDS=false

Save the file as "CF.PROPERTIES" and close.
Copy the ColdFusion 9 installer (ColdFusion_9_WWE_win.exe) and CF.PROPERTIES file to C:\Temp.
From the Command Prompt, navigate to C:\Temp and launch the installer with the following command:
```
COLDFUSION_9_WWE_WIN -f CF.PROPERTIES
```
Give the installer plenty of time to finish. In silent mode, one might be tempted to restart the server before installation completes. If you'd like to verify that your installation was successfully completed, check out C:\Coldfusion9\Adobe_ColdFusion_9_InstallLog.log.

Part 2: Install ColdFusion 9's ISAPI Connector

Having completed basic installation, we must now connect Coldfusion to IIS. Unfortunately, ColdFusion 9's Web Server Configuration Tool also does not work on Windows 2000. What's more, the command-line installer has not generated the necessary JRun files and directories necessary for manual configuration, making the next steps tedious, even if you're familiar with this exercise from prior versions of CF. Here goes:

In Notepad, open C:\ColdFusion9\runtime\servers\coldfusion\SERVER-INF\jrun.xml.
Locate the entry labeled "ProxyService".
A few lines down, locate and modify the "deactivated" attribute to read "false," as follows. [Be careful - there are three separate instances of "deactivated" in this file. Make sure you modify the correct one.]
```
<attribute name="deactivated">false</attribute>
```
A few more lines down, locate and modify the "port" attribute to read "51800," as follows.
```
<attribute name="port">51800</attribute>
```
Save and close the jrun.xml file.
Create the following directory:
```
C:\ColdFusion9\runtime\lib\wsconfig\1
```

With Notepad, create a new text file, with the following content:

1=IIS,1,false,""
1.srv=localhost,"coldfusion"
1.cfmx=true,C:/inetpub/wwwroot

Save the file as C:\ColdFusion9\runtime\lib\wsconfig\wsconfig.properties

Extract jrun.dll and jrunwin32.dll from C:\ColdFusion9\runtime\lib\wsconfig.jar

To extract JAR files, you can use Java's JDK. Download from http://java.sun.com/javase/downloads/index.jsp and install.
Locate JAR.EXE. On my server, it's in C:\Program Files\Java\jdk1.6.0_18\bin.

In a Command Prompt window, navigate to C:\Temp and enter the following commands (adjusting for the actual location of your JAR.EXE file):

"C:\Program Files\Java\jdk1.6.0_18\bin\jar.exe" xf C:\ColdFusion9\runtime\lib\wsconfig.jar connectors/installers/intel-win/prebuilt/jrunwin32.dll
"C:\Program Files\Java\jdk1.6.0_18\bin\jar.exe" xf C:\ColdFusion9\runtime\lib\wsconfig.jar connectors/isapi/intel-win/prebuilt/jrun.dll
copy connectors\installers\intel-win\prebuilt\jrunwin32.dll C:\ColdFusion9\runtime\lib\wsconfig
copy connectors\isapi\intel-win\prebuilt\jrun.dll C:\ColdFusion9\runtime\lib\wsconfig\1

With Notepad, create a new text file, with the following content:
```
proxyservers=127.0.0.1:51800
```
Save the file as C:\ColdFusion9\runtime\lib\wsconfig\1\jrunserver.store.

With Notepad, create a new text file, with the following content:

verbose=false
scriptpath=/JRunScripts/jrun.dll
serverstore=C:/ColdFusion9/runtime/lib/wsconfig/1/jrunserver.store
bootstrap=127.0.0.1:51800
apialloc=false
ssl=false
ignoresuffixmap=false
#errorurl=<optionally redirect to this URL on errors>

Save the file as C:\ColdFusion9\runtime\lib\wsconfig\1\jrun.ini.
Using the IIS Management Console, add the JRun Connector Filter to the IIS Master Properties.
1. Launch the IIS Management Console, at Start > Programs > Administrative Tools > Internet Services Manager
2. Select (right-click) the web server > Properties > Master Properties > WWW Service > Edit...
3. Select the "ISAPI Filter" tab and press the "Add" button.
  - Filter Name: JRun Connector Filter
  - Executable: C:\ColdFusion9\runtime\lib\wsconfig\1\jrun.dll
4. Select the "Home Directory" tab and press the "Configuration..." button.
5. Add extensions for .jsp, .jws, .cfm, .cfml, .cfc, .cfr, and .cfswf, with the following parameters:
  - Executable: C:\ColdFusion9\runtime\lib\wsconfig\1\jrun.dll
  - Verbs: All verbs
  - Script engine: yes
  - Check that file exists: yes [Necessary if you specify site-specific 404 handlers in IIS. Otherwise, if you use CF's server-wide Missing Template Handler, no.]
6. For each IIS Web Site with ColdFusion templates, add a JRunScripts virtual directory.
  1. Select (right-click) an IIS Web Site > New > Virtual Directory
    - Alias: JRunScripts
    - Directory: C:\ColdFusion9\runtime\lib\wsconfig\1\
    - Read: yes
    - Run Scripts: yes
    - Execute: yes
    - Write: no
    - Browse: no
  2. Repeat for each IIS Web Site
Restart your server.

That should do it. Point your web browser to the IIS server's default website (e.g., http://localhost/cfide/administrator/index.cfm) to complete the ColdFusion 9 installation wizard and access the ColdFusion Administrator.

If you found this article helpful, please check out Circa 3000 for your ColdFusion hosting needs. Since 1998 (that is, ColdFusion 3.1), Circa 3000 has held the honor of "original ColdFusion specialty host." My company is uniquely service- and relationship-driven, and serves only as many customers as I can personally manage. If you've been burned by budget, volume-driven hosts who don't know what a "datasource" is, please give me a call, at 800-CIRCA3K (800-247-2235). I look forward to hearing from you!

Install Kai's Power Tools (KTP) 3, 5 and 6 on Windows Vista

2008-04-19T11:04:00Z

If you've tried to install your old-school (e.g., MetaTools, MetaCreations) Kai's Power Tools on Microsoft Windows Vista, you've certainly discovered that the installers, like so, so many others of their generation, are incompatible with Vista. Don't even bother with Vista's "Compatibility Mode;" it won't help. Sure, you could purchase the newer KPT suite from Corel, but this collection doesn't include all of the tools from KPT 3, 5 and 6. Whatever will you do without Spheroid Designer?! Furthermore, you've probably just emptied your bank account on Adobe suite upgrades for Vista compatibility. Now, do you really want to purchase a "best of" collection of KPT when you already own the complete works?

Thankfully, there's a solution. Kai's power tools aren't themselves executables but Photoshop plug-ins and, as such, you need only extract the contents of your KPT 3, 5 and 6 CD-ROMs in order to install the respective files into your imaging apps. Here's how:

Install KPT 3, 5 or 6 on a pre-Vista computer (e.g., Windows 95, NT, 2000, XP). Of course, if your prior installation of KPT is still available, you can retrieve the files from that PC without reinstallation.
By default, the KPT 3 installer places the KPT files in C:\Win32App\KPT. Later versions prompt for your Photoshop Plug-Ins directory, but note that you needn't have Photoshop installed on the target computer in order to proceed with the installation. For this article, I've installed KPT 5 and 6 to C:\Win32App\KPT5 and C:\Win32App\KPT6, respectively. Can't find the files? Mixed 'em together? A complete file listing for KPT versions 3, 5 and 6 is supplied below.
KPT 3 also installs KPT3HUB.DLL and KPT3HELP.HLP in C:\<windows root>.
KPT 6 also installs KPTW600.TXT in C:\<windows root>\MetaCreations.
In accordance with the License Agreement, backup the directory (and subs) and any files from steps #3 and #4 to CD-R so that future installations won't require the older OS. While you're at it, you might as well paste a copy of these instructions in there.
Copy the directory (and subs) to your Vista PC's Photoshop plug-ins directory. For example, in Photoshop CS3 on Windows Vista, the default plug-ins directory is C:\Program Files\Adobe\Adobe Photoshop CS3\Plug-Ins. Copy each KPT installation to a separate subdirectory of the aforementioned Plug-Ins folder. For example, I've copied each KPT version to the following directories, respectively:
- C:\Program Files\Adobe\Adobe Photoshop CS3\Plug-Ins\KPT 3
- C:\Program Files\Adobe\Adobe Photoshop CS3\Plug-Ins\KPT 5
- C:\Program Files\Adobe\Adobe Photoshop CS3\Plug-Ins\KPT 6
Copy any files from steps #3 and #4 to their respective locations in Vista.

That should do it. Fire up Photoshop and get weird with your ol' KPT faves. Enjoy!

KPT 3 Installed Files

C:\Win32App\KPT\DeIsL1.isu
C:\Win32App\KPT\EREG1_32.DLL
C:\Win32App\KPT\EREGLB32.DLL
C:\Win32App\KPT\KPT3READ.WRI
C:\Win32App\KPT\KPT3_DR.8BF
C:\Win32App\KPT\KPT3_GD.8BF
C:\Win32App\KPT\KPT3_GD.PRS
C:\Win32App\KPT\KPT3_GL.8BF
C:\Win32App\KPT\KPT3_IF.8BF
C:\Win32App\KPT\KPT3_IF.PRS
C:\Win32App\KPT\KPT3_KS.8BF
C:\Win32App\KPT\KPT3_PC.8BF
C:\Win32App\KPT\KPT3_PQ.8BF
C:\Win32App\KPT\KPT3_SD.8BF
C:\Win32App\KPT\KPT3_SD.PRS
C:\Win32App\KPT\KPT3_SN.8BF
C:\Win32App\KPT\KPT3_TC.8BF
C:\Win32App\KPT\KPT3_TE.8BF
C:\Win32App\KPT\KPT3_TE.PRS
C:\Win32App\KPT\KPT3_VT.8BF
C:\Win32App\KPT\KPT3_WL.8BF
C:\Win32App\KPT\REGISTER.EXE
C:\<windows root>\KPT3HUB.DLL
C:\<windows root>\KPT3HELP.HLP

KPT 5 Installed Files

C:\Win32App\KPT5\DeIsL1.isu
C:\Win32App\KPT5\KPT5
C:\Win32App\KPT5\KPT5 ReadMe.WRI
C:\Win32App\KPT5\regkpt5.exe
C:\Win32App\KPT5\KPT5\FPXLIB.DLL
C:\Win32App\KPT5\KPT5\JPEGLIB.DLL
C:\Win32App\KPT5\KPT5\KPT5 Blurrrr.8bf
C:\Win32App\KPT5\KPT5\KPT5 Blurrrr_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 Blurrrr_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 FiberOptix.8bf
C:\Win32App\KPT5\KPT5\KPT5 FiberOptix_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 FiberOptix_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 Frax4D.8bf
C:\Win32App\KPT5\KPT5\KPT5 Frax4D_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 Frax4D_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 FraxFlame.8bf
C:\Win32App\KPT5\KPT5\KPT5 FraxFlame_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 FraxFlame_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 Fraxplorer.8bf
C:\Win32App\KPT5\KPT5\KPT5 Fraxplorer_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 Fraxplorer_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 Noize.8bf
C:\Win32App\KPT5\KPT5\KPT5 Noize_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 Noize_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 Orb-it.8bf
C:\Win32App\KPT5\KPT5\KPT5 Orb-it_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 Orb-it_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 RadWarp.8bf
C:\Win32App\KPT5\KPT5\KPT5 RadWarp_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 RadWarp_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 ShapeShifter.8bf
C:\Win32App\KPT5\KPT5\KPT5 ShapeShifter_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 ShapeShifter_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5 Smoothie.8bf
C:\Win32App\KPT5\KPT5\KPT5 Smoothie_c.mcm
C:\Win32App\KPT5\KPT5\KPT5 Smoothie_ce.mcm
C:\Win32App\KPT5\KPT5\KPT5Hub.dll
C:\Win32App\KPT5\KPT5\kptaxiom.dll
C:\Win32App\KPT5\KPT5\kptaxiomui.dll
C:\Win32App\KPT5\KPT5\kptimageio.mcm
C:\Win32App\KPT5\KPT5\mCComponent.dll
C:\Win32App\KPT5\KPT5\mCEffect.dll
C:\Win32App\KPT5\KPT5\mCParmServer.dll
C:\Win32App\KPT5\KPT5\mCPresetManager.mcm
C:\Win32App\KPT5\KPT5\mCPSFilterSys.dll
C:\Win32App\KPT5\KPT5\metaos
C:\Win32App\KPT5\KPT5\mPlatformUtils.dll
C:\Win32App\KPT5\KPT5\mPSUtils.dll
C:\Win32App\KPT5\KPT5\prefs
C:\Win32App\KPT5\KPT5\presets
C:\Win32App\KPT5\KPT5\uisys.dll
C:\Win32App\KPT5\KPT5\metaos\data
C:\Win32App\KPT5\KPT5\metaos\plugins
C:\Win32App\KPT5\KPT5\metaos\User Guide
C:\Win32App\KPT5\KPT5\metaos\data\background.dat
C:\Win32App\KPT5\KPT5\metaos\data\basepanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\bumppanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\chopsitem.dat
C:\Win32App\KPT5\KPT5\metaos\data\colorpicker.dat
C:\Win32App\KPT5\KPT5\metaos\data\defaults.dat
C:\Win32App\KPT5\KPT5\metaos\data\environpanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\filmstrip.dat
C:\Win32App\KPT5\KPT5\metaos\data\fraxpanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\glowpanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\gradientitem.dat
C:\Win32App\KPT5\KPT5\metaos\data\imageio.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 Blurrrr.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 FiberOptix.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 Frax4D.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 FraxFlame.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 FraxPlorer.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 Noize.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 Orb-It.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 RadWarp.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 ShapeShifter.dat
C:\Win32App\KPT5\KPT5\metaos\data\KPT5 Smoothie.dat
C:\Win32App\KPT5\KPT5\metaos\data\layeritem.dat
C:\Win32App\KPT5\KPT5\metaos\data\lightpanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\memdots.dat
C:\Win32App\KPT5\KPT5\metaos\data\modaldialog.dat
C:\Win32App\KPT5\KPT5\metaos\data\popupmenu.dat
C:\Win32App\KPT5\KPT5\metaos\data\PresetManager.dat
C:\Win32App\KPT5\KPT5\metaos\data\previewitem.dat
C:\Win32App\KPT5\KPT5\metaos\data\shadowpanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\shapepanel.dat
C:\Win32App\KPT5\KPT5\metaos\data\splash.dat
C:\Win32App\KPT5\KPT5\metaos\data\system.dat
C:\Win32App\KPT5\KPT5\metaos\data\topmaskpanel.dat
C:\Win32App\KPT5\KPT5\metaos\plugins\Gif.8bi
C:\Win32App\KPT5\KPT5\metaos\plugins\psplugindata.dat
C:\Win32App\KPT5\KPT5\metaos\plugins\pspluginexceptionswindows.txt
C:\Win32App\KPT5\KPT5\metaos\User Guide\Blurs.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\Fiber.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\Frax4D.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\FraxFlame.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\FraxPlorer.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\KPT 5 User Guide.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\KPT Basics.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\KPT Tutorials.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\Noise.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\RadWarp.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\ShapeShift.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\Smoothie.pdf
C:\Win32App\KPT5\KPT5\metaos\User Guide\Sphere.pdf
C:\Win32App\KPT5\KPT5\prefs\Blurrrr.last
C:\Win32App\KPT5\KPT5\prefs\Frax4D.last
C:\Win32App\KPT5\KPT5\prefs\FraxFlame.last
C:\Win32App\KPT5\KPT5\prefs\FraxPlorer.last
C:\Win32App\KPT5\KPT5\prefs\Noize.last
C:\Win32App\KPT5\KPT5\prefs\Orb-It.last
C:\Win32App\KPT5\KPT5\prefs\RadWarp.last
C:\Win32App\KPT5\KPT5\prefs\ShapeShifter.last
C:\Win32App\KPT5\KPT5\prefs\Smoothie.last
C:\Win32App\KPT5\KPT5\presets\Blurrrr
C:\Win32App\KPT5\KPT5\presets\EnvMaps
C:\Win32App\KPT5\KPT5\presets\FiberOptix
C:\Win32App\KPT5\KPT5\presets\Frax4D
C:\Win32App\KPT5\KPT5\presets\FraxFlame
C:\Win32App\KPT5\KPT5\presets\FraxPlorer
C:\Win32App\KPT5\KPT5\presets\Gradients
C:\Win32App\KPT5\KPT5\presets\Lights
C:\Win32App\KPT5\KPT5\presets\Noize
C:\Win32App\KPT5\KPT5\presets\Orb-It
C:\Win32App\KPT5\KPT5\presets\RadWarp
C:\Win32App\KPT5\KPT5\presets\ShapeShifter
C:\Win32App\KPT5\KPT5\presets\Smoothie
C:\Win32App\KPT5\KPT5\presets\Blurrrr\Blurrrr Basics
C:\Win32App\KPT5\KPT5\presets\EnvMaps\basic enviro
C:\Win32App\KPT5\KPT5\presets\FiberOptix\basic fur
C:\Win32App\KPT5\KPT5\presets\Frax4D\Frax4dbasic
C:\Win32App\KPT5\KPT5\presets\FraxFlame\Flame Basic
C:\Win32App\KPT5\KPT5\presets\FraxPlorer\Frax basic
C:\Win32App\KPT5\KPT5\presets\FraxPlorer\Frax basic 2
C:\Win32App\KPT5\KPT5\presets\Gradients\Grads 1
C:\Win32App\KPT5\KPT5\presets\Gradients\Grads 2
C:\Win32App\KPT5\KPT5\presets\Gradients\Grads 3
C:\Win32App\KPT5\KPT5\presets\Lights\basic lights
C:\Win32App\KPT5\KPT5\presets\Noize\noise examples
C:\Win32App\KPT5\KPT5\presets\RadWarp\Basic warps

KPT 6 Installed Files

C:\Win32App\KPT6\KPT6
C:\Win32App\KPT6\KPT6\FPXLIB.DLL
C:\Win32App\KPT6\KPT6\JPEGLIB.DLL
C:\Win32App\KPT6\KPT6\KPT Equalizer.8bf
C:\Win32App\KPT6\KPT6\KPT Equalizer_c.mcm
C:\Win32App\KPT6\KPT6\KPT Equalizer_ce.mcm
C:\Win32App\KPT6\KPT6\KPT Gel.8bf
C:\Win32App\KPT6\KPT6\KPT Gel_c.mcm
C:\Win32App\KPT6\KPT6\KPT Gel_ce.mcm
C:\Win32App\KPT6\KPT6\KPT Goo.8bf
C:\Win32App\KPT6\KPT6\KPT Goo_c.mcm
C:\Win32App\KPT6\KPT6\KPT Goo_ce.mcm
C:\Win32App\KPT6\KPT6\KPT LensFlare.8bf
C:\Win32App\KPT6\KPT6\KPT LensFlare_c.mcm
C:\Win32App\KPT6\KPT6\KPT LensFlare_ce.mcm
C:\Win32App\KPT6\KPT6\KPT Materializer.8bf
C:\Win32App\KPT6\KPT6\KPT Materializer_c.mcm
C:\Win32App\KPT6\KPT6\KPT Materializer_ce.mcm
C:\Win32App\KPT6\KPT6\KPT Projector.8bf
C:\Win32App\KPT6\KPT6\KPT Projector_c.mcm
C:\Win32App\KPT6\KPT6\KPT Projector_ce.mcm
C:\Win32App\KPT6\KPT6\KPT Reaction.8bf
C:\Win32App\KPT6\KPT6\KPT Reaction_c.mcm
C:\Win32App\KPT6\KPT6\KPT Reaction_ce.mcm
C:\Win32App\KPT6\KPT6\KPT SceneBuilder.8bf
C:\Win32App\KPT6\KPT6\KPT SkyEffects.8bf
C:\Win32App\KPT6\KPT6\KPT Turbulence.8bf
C:\Win32App\KPT6\KPT6\KPT Turbulence_c.mcm
C:\Win32App\KPT6\KPT6\KPT Turbulence_ce.mcm
C:\Win32App\KPT6\KPT6\KPT6.dta
C:\Win32App\KPT6\KPT6\KPT6Hub.dll
C:\Win32App\KPT6\KPT6\KPT6Unin.isu
C:\Win32App\KPT6\KPT6\kptaxiom.dll
C:\Win32App\KPT6\KPT6\kptaxiomui.dll
C:\Win32App\KPT6\KPT6\kptimageio.mcm
C:\Win32App\KPT6\KPT6\KPTSCBLD
C:\Win32App\KPT6\KPT6\KPTSKYE
C:\Win32App\KPT6\KPT6\mCComponent.dll
C:\Win32App\KPT6\KPT6\mCEffect.dll
C:\Win32App\KPT6\KPT6\mCParmServer.dll
C:\Win32App\KPT6\KPT6\mCPresetManager.mcm
C:\Win32App\KPT6\KPT6\mCPSFilterSys.dll
C:\Win32App\KPT6\KPT6\metaos
C:\Win32App\KPT6\KPT6\mPlatformUtils.dll
C:\Win32App\KPT6\KPT6\mPSUtils.dll
C:\Win32App\KPT6\KPT6\Objects
C:\Win32App\KPT6\KPT6\Prefs
C:\Win32App\KPT6\KPT6\Presets
C:\Win32App\KPT6\KPT6\ReadMes
C:\Win32App\KPT6\KPT6\RegKPT6.exe
C:\Win32App\KPT6\KPT6\uisys.dll
C:\Win32App\KPT6\KPT6\KPTSCBLD\KPTSCBLDX.DTA
C:\Win32App\KPT6\KPT6\KPTSKYE\Bank1.sdx
C:\Win32App\KPT6\KPT6\KPTSKYE\Bank2.sdx
C:\Win32App\KPT6\KPT6\KPTSKYE\Bank3.sdx
C:\Win32App\KPT6\KPT6\KPTSKYE\Bank4.sdx
C:\Win32App\KPT6\KPT6\KPTSKYE\Bank5.sdx
C:\Win32App\KPT6\KPT6\KPTSKYE\KPTSKYEX.dta
C:\Win32App\KPT6\KPT6\KPTSKYE\user.sdx
C:\Win32App\KPT6\KPT6\metaos\Data
C:\Win32App\KPT6\KPT6\metaos\Defaults
C:\Win32App\KPT6\KPT6\metaos\Plugins
C:\Win32App\KPT6\KPT6\metaos\User Guide
C:\Win32App\KPT6\KPT6\metaos\Data\backgroundX.dat
C:\Win32App\KPT6\KPT6\metaos\Data\basepanel.dat
C:\Win32App\KPT6\KPT6\metaos\Data\colorpicker.dat
C:\Win32App\KPT6\KPT6\metaos\Data\filmstrip.dat
C:\Win32App\KPT6\KPT6\metaos\Data\gradientitem.dat
C:\Win32App\KPT6\KPT6\metaos\Data\imageio.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Equalizer.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Gel_.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Goo_.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT LensFlare.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Materializer.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Projector.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Reaction.dat
C:\Win32App\KPT6\KPT6\metaos\Data\KPT Turbulence.dat
C:\Win32App\KPT6\KPT6\metaos\Data\lightpanel.dat
C:\Win32App\KPT6\KPT6\metaos\Data\makemovie.dat
C:\Win32App\KPT6\KPT6\metaos\Data\memdots.dat
C:\Win32App\KPT6\KPT6\metaos\Data\modaldialog.dat
C:\Win32App\KPT6\KPT6\metaos\Data\popupmenu.dat
C:\Win32App\KPT6\KPT6\metaos\Data\PresetManager.dat
C:\Win32App\KPT6\KPT6\metaos\Data\previewitem.dat
C:\Win32App\KPT6\KPT6\metaos\Data\splashX.dat
C:\Win32App\KPT6\KPT6\metaos\Data\system.dat
C:\Win32App\KPT6\KPT6\metaos\Defaults\Equalizer.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\Gel.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\Goo.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\LensFlare.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\Materializer.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\Projector.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\Reaction.def
C:\Win32App\KPT6\KPT6\metaos\Defaults\Turbulence.def
C:\Win32App\KPT6\KPT6\metaos\Plugins\Gif.8bi
C:\Win32App\KPT6\KPT6\metaos\Plugins\kptAVIExport.brm
C:\Win32App\KPT6\KPT6\metaos\Plugins\kptBMPSeqExport.brm
C:\Win32App\KPT6\KPT6\metaos\Plugins\kptQTExport.brm
C:\Win32App\KPT6\KPT6\metaos\Plugins\pspluginexceptionsmac.txt
C:\Win32App\KPT6\KPT6\metaos\Plugins\pspluginexceptionswindows.txt
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Basics.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Equalizer.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Gel.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Goo.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT LensFlare.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Materializer.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Projector.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Reaction.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT SceneBuilder.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT SkyEffects.pdf
C:\Win32App\KPT6\KPT6\metaos\User Guide\KPT Turbulence.pdf
C:\Win32App\KPT6\KPT6\Objects\apple.PTC
C:\Win32App\KPT6\KPT6\Objects\cube.PTC
C:\Win32App\KPT6\KPT6\Objects\flying saucer.PTC
C:\Win32App\KPT6\KPT6\Objects\Objects ReadMe.txt
C:\Win32App\KPT6\KPT6\Objects\pin.PTC
C:\Win32App\KPT6\KPT6\Objects\sphere1.PTC
C:\Win32App\KPT6\KPT6\Objects\torus.PTC
C:\Win32App\KPT6\KPT6\Presets\EnvMaps
C:\Win32App\KPT6\KPT6\Presets\Equalizer
C:\Win32App\KPT6\KPT6\Presets\Gel
C:\Win32App\KPT6\KPT6\Presets\Gradients
C:\Win32App\KPT6\KPT6\Presets\LensFlare
C:\Win32App\KPT6\KPT6\Presets\Lights
C:\Win32App\KPT6\KPT6\Presets\Materializer
C:\Win32App\KPT6\KPT6\Presets\Projector
C:\Win32App\KPT6\KPT6\Presets\Reaction
C:\Win32App\KPT6\KPT6\Presets\Turbulence
C:\Win32App\KPT6\KPT6\Presets\EnvMaps\Maps 1.envm
C:\Win32App\KPT6\KPT6\Presets\EnvMaps\Maps 2.envm
C:\Win32App\KPT6\KPT6\Presets\EnvMaps\Maps 3.envm
C:\Win32App\KPT6\KPT6\Presets\Equalizer\Eq. Basics
C:\Win32App\KPT6\KPT6\Presets\Gel\Gel Basics
C:\Win32App\KPT6\KPT6\Presets\Gel\More Gel
C:\Win32App\KPT6\KPT6\Presets\Gradients\Grads 1
C:\Win32App\KPT6\KPT6\Presets\Gradients\Grads 2
C:\Win32App\KPT6\KPT6\Presets\Gradients\Grads 3
C:\Win32App\KPT6\KPT6\Presets\Gradients\Subtle Grads
C:\Win32App\KPT6\KPT6\Presets\LensFlare\Flare Basics
C:\Win32App\KPT6\KPT6\Presets\Lights\Basic Lights
C:\Win32App\KPT6\KPT6\Presets\Lights\More Lights
C:\Win32App\KPT6\KPT6\Presets\Materializer\Material Basics
C:\Win32App\KPT6\KPT6\Presets\Projector\Projector Basics
C:\Win32App\KPT6\KPT6\Presets\Reaction\Reaction Basics
C:\Win32App\KPT6\KPT6\Presets\Turbulence\Turb. Basics
C:\Win32App\KPT6\KPT6\ReadMes\KPT6ReadMe.txt
C:\Win32App\KPT6\KPT6\ReadMes\MetaSupport.pdf
C:\Win32App\KPT6\KPT6\ReadMes\TechTips.txt
C:\<windows root>\MetaCreations\KPTW600.TXT