When considering where to place encrypted container files, many people recommend creating dummy files like "my_hawaii_vacation.avi" or creating deep subdirectories to hide your encrypted files. The AVI idea is nice because you can make a large container but it's easy to see it's fake since it won't play and deep directories are a hassle. Sure, Truecrypt has plausible deniability but any extra security/deniability that does not incur additional inconvenience is always a good thing.

According to the Truecrypt docs

"...TrueCrypt installer disables paging files by default when TrueCrypt is installed or updated."

That's when I thought, why not create a dummy page file and use it as an encrypted container. I'm no virtual memory expert but the contents of a page file and an encrypted container should look somewhat similar even to some computer experts.

I haven't tried this out yet but once I free up a machine to test this idea I'll update this post.

Update

Turns out this is not such a good idea. I was afraid from the start that Windows might mess with the pagefile even if virtual memory is disabled. While this may or may not be true, Truecrypt specifically recommends against using .sys as a file extension for encrypted containers.

"First, make sure that your TrueCrypt container does not have a file extension that is reserved for executable files (for example, .exe, .sys, or .dll). If it does, Windows and antivirus software may interfere with the container and adversely affect the performance of the volume."

Oh well, it would have been a cool trick if Windows and or AV didn't interfere.