Portable Tabs. Now tabs can be made fully portable by pointing them to a portable path that is resolved depending on the context, for example %userprofile%. Portable Tabs smartly adapt their contents to the current host system.

Here are some examples for portable paths:

These portable paths are remembered as such (unresolved) between sessions. So, for example, if you have a tab pointing to %userprofile%, it will always be resolved to the current user profile folder, no matter where it is located in the system you are currently working on, no matter where you plug your stick! This revolutionary concept is called Portable Tabs.

To point a tab to a portable path you use the Relocate Tab command in the tab header's context menu:

Tip: To increase the usability of such a portable tab it is recommend to set its home (Set Home) to the portable path and then apply Lock Home Zone. That way you can browse the whole portable branch without ever losing the portability of the tab.

Go to Last Target. Now the copied or moved items found in the target location are auto-selected when you go there using the "Go to Last Target" command. A surprisingly useful little service.

The command is found in menu Go, and can be triggered via keyboard shortcut Ctrl+Alt+F7.

History Retains Selections. Now (optionally) if you return to a previous location, any previous selections in this location are restored.

To enable this feature tick Configuration | Advanced | History retains selections:

Portable File Associations. Now you can define associations for files without extension. (Pro Edition Only)

The pattern to use is *. (asterisk-dot). For example, to open all files without extension with UltraEdit:

"No extension" *.>UEdit32

Note that the pattern does not match folders.

To add this definition to your Portable File Associations use menu Tool | Customize File Associations:

Now a double-click will open files without extension with UltraEdit.

Tree. Now tooltips of junctions display the Junction Target.

Scripting. This new version comes with a couple of powerful new or improved scripting commands like inputselect(), tab(), listfolder(), and report(). (Pro Edition Only)

Imagine you have a customer 5,000 miles away and you need to find out which version of a specific DLL he has on his system. But this customer does not really know how to find out. Here's the solution: The report() function now supports to directly pass the items that you want a report about. Here's a small script the generates a report on a single specific item, shell32.dll:

text report("{Name}, {Size B} bytes, 
  {Modified yyyy-mm-dd hh:nn:ss}, 
  ver {FileVersion}", "%winsysdir%\shell32.dll");

Send it to your customer by email, and let him paste it into the Run Script box (menu Scripting | Run Script). He will get the desired version information in a blink and ready to copy and paste into the reply email:

Of course, just the same easy and fool-proof way you can collect file information of any number of files on your own or a foreign system with a single click (once you have written the script, which is a no-brainer as well).

Address Bar. Now right-clicking the dropdown arrow pops the breadcrumb menu for the current path.

Ctrl+RightClick pops the virtual folders and drives: