**Saturday, September 14th 6:45 AM**

Returned home and installed Poser 5.
Went with full installation in default directory.
Restarted Windows.

7:00 AM

Launched Poser 5 for the first time.
Entered serial number, opted for automatic registration over the 'Net.
The challenge and response codes remind me of freeform poetry. Very strange.
Registration went flawlessly.

7:15 AM

Played with some of Poser's basic functions; started rearranging everything to match my old workspace.
Set up P5 to recognize my P4 Runtime directory (thanks for the tutorial, Jelisa!)
Couldn't find the parameter dials. Set monitor to 1024x768, found them hiding on the right.
Noticed that the parameter dials are always on top; they obscure the Library. Moved them to the left side of the screen.
Confirmed a couple of bugs reported by others.
Pleased by performance; user interface seems to run about as smoothly as P4.

8:05 AM

First crash.
Loaded a Poser 4 scene file. Everything seemed fine until I attempted to render.
P5 reported "texture not found or can't be read", then crashed to the desktop several seconds later.
Relaunched P5 and repeated the process, with identical results.
Relaunched P5 and repeated the process with a different scene file, with identical results.
Decide not to try old scene files until the problem is resolved.

9:00 AM

Apparently, the floating parameter dials are not part of the UI; they don't remain where I left them on subsequent launches, and the UI dots don't affect their position. Not a life-threatening quirk, but still irritating.
Experimenting with materials.
Confirmed that we can now tile our maps in the renderer, without having to remap the prop (see above). No more tiling with UVMapper. Just like trueSpace!
Tried out a few shader nodes, including the Toon shader and Movie shader.
You can indeed create animated textures, transparencies, and bump maps. The possibilities are near-endless.
The new FireFly renderer is nothing like the P4 renderer. I expect a long learning curve ahead.