It has been about two years, since I last updated the look of my website, and with the release of WordPress, they finally offered a template that caught my eye.
Yesterday, after doing a lot of reading, and backing up files, I upgraded my website to version 3.8.
I am happy to report that I did not have any issues with the upgrade, and now I’m just fine-tuning sections with some of the new features that are now offered!
So please take a look around, and if you see anything “odd”, or have any comments, please let me know!
Back in early August, I ordered a new computer for myself, and like any personal item, it takes some time to figure out all the new nuances…
When I first started using Loong, everything was so new, that when I ran into a minor issue, I took a quick look, and moved on to the bigger on configuration issues.
One of the really cool things about the ASUS installation disk, is that it comes with Google Chrome as an option when installing the various motherboard drivers, and being a long time user, this was great!
I was able to complete my base OS install without having to launch IE once!
Fast forward a couple of days…
With the basics of installation over and done with, and really beginning to use the computer in a ‘normal’ fashion, I noticed that one day, when I tried to check my Audible.com account for a new book, I was unable to do ANYTHING once I got to the site.
I could see an image of the website, and I could refresh the site and images changed, but no matter where I clicked, nothing would happen, even in the bare-bones links in the footer!
This had never happened to me in my 32-bit environment, running the same software configuration, and why on only one website?
Immediately, added Audible.com to the Cookie Exceptions in Chrome, and still nothing…
This is very strange…
Okay, time to read the Forums, but wait, I can’t get in via Chrome…
Thankfully, I got in without issue with Firefox, and started to poke around to see if anyone else had a similar issue… Nothing…
I Google-d the internet, still nothing…
Oh well… on to the next thing, I had a workaround.
Fast forward some more, a new school year has started, and I have new credits in my Audible account. Time for a new book.
I’m already in Chrome, and after I type in the address, I am reminded of the issue from a couple of weeks ago, that I had fluffed off because I had already found a workaround.
More searching… Nothing…
I finally typed up an email report, and sent it to the Audible Help Desk.
I received a standard “Thank you for your report” email, followed by another note suggesting that I do a un-install and re-install of Chrome.
It is always a pain to move to a new computer because there are so many files and settings that need to be redone for the user to really get productive again.
With this idea in mind I offer the following tips and advice in regards to moving an Adobe Lightroom User from one machine to another.
This guide is geared towards people who are technically proficient on the Windows operating system, but should be able to serve as a guide to those working in a Macintosh environment.
If you have any other ideas or tips please feel free to send them my way!
Transferring the Data
As any User of Lightroom knows, the Catalog and Image files are the heart of your work and business, and if you are moving to a new machine, you need to consider what to do with them as you move forward.
On the “C:” drive of Old Machine –
There are several of options available to you, if your original catalogs and Images are still on the main “c:\” hard drive of your old machine.
Transfer files across the Network
If both machines are still attached to a network, you can easily transfer the catalogs across, but that is going to take time, and chew up various network resources.
Remember, depending on the number of Images you have, your catalog directory could easily reach several gigabytes worth of data,in my case: Catalog: 12.7 GBs & Images: 261 GBs
Remove the old hard drive –
If you remove the hard drive, you have two basic options, but before you begin, backup your files on the old machine in your normal manner.
Install in new computer –
By simply taking the hard drive out of the old machine, and installing it into your new machine, is most certainly the easiest of the options, and also gives you a second HD spindle when dealing with I/O operations in Lightroom.
But before you remove the hard drive, be sure to check the compatibility of data interfaces on your new machine – Can the new machine deal with the older IDE interface?
An example I can give, is my new machines, that is based on the Asus Z87-Pro motherboard, which does not have any IDE connections.
Also keep in mind, that if you connect the old “C:” drive, and it wants to reinitialize for whatever reason, and you have not backed up your data…
External case –
This is another good alternative, and does give you the flexibility to move to different environments with little issue, and also gives you the additional spindle speed during I/O, but is subject to the port speed when you plug-in, assuming that the chipset on the external drive is the faster of the two.
Backups
There are three critical areas that need to be transferred to your new machine for it to work in a fashion that you are used to: Images, Catalogs and Preferences.
Images –
Do I really need to say more?
Catalogs –
As mentioned earlier, catalogs can easily reach several gigabytes worth of data, but does all that data need to be transferred to the new computer?
Again Users of Lightroom know, and unless they have change the default settings, the program will prompt you to do backups, which are located in a sub-directory of the main catalog directory.
c:\My.Adobe.Lightroom.Catalog\Backups\
By simply looking into the backup directory, one could easily save time and the amount of data that needs to be transferred, by simply cleaning out old unnecessary files, but this is completely user based.
Just check to see which “Date – Time” named directories really need to be moved.
Preferences –
Since this is most likely a new software install, none of your preferences will be in place, so where are those files located?
Like all other User preferences, they are stored in the operating system’s Users profile directory, that is hidden through the normal interface, that can be easily accessed with a little forethought.
Once installed in the new directories, Lightroom should have no issue accessing the “.lrtemplate” files. (BTW – If you really want to be geeky, you can open up these files in a text editor and play with them to your heart’s content)
Conclusion
When I moved to my new machine, I used a combination of techniques described above.
On my old machine, the Lightroom catalogs and images were already located on an internal secondary SATA hard drive, so I just removed the old hard drive, and installed it into the new machine.
From there, I copied the images and catalogs (approx 275 GBs) to the root directory of my new machine, creating a new backup of the files.
Even across the SATA III bus, this still took several hours, and I could smell hard drive smoke. (just kidding!)
When I got to my preferences, I connected to my old machine across the network and simply copied the files into the associated directories.
From there, I reconnected the Lightroom catalogs to the local main image directory, now located on the root of my main “c:\” drive.
Finally, I rewrote my old robocopy script to include the additional external hard drive, that I added for redundancy in my backup solution.
Some may argue, that having all my data on the “c:\” will produce bottlenecks, while I would agree in theory, I also have to wonder with my usage of Intel’s RST technology, reduces this as an issue.
Used by Google Analytics to determine which links on a page are being clicked
30 seconds
_ga_
ID used to identify users
2 years
_gid
ID used to identify users for 24 hours after last activity
24 hours
_gat
Used to monitor number of Google Analytics server requests when using Google Tag Manager
1 minute
_gac_
Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together.
90 days
__utma
ID used to identify users and sessions
2 years after last activity
__utmt
Used to monitor number of Google Analytics server requests
10 minutes
__utmb
Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server.
30 minutes after last activity
__utmc
Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session.
End of session (browser)
__utmz
Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server
6 months after last activity
__utmv
Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server.
2 years after last activity
__utmx
Used to determine whether a user is included in an A / B or Multivariate test.