burnBabyBurn

Thanks, Lightning UK! Makes sense.

Is this how verify is suppose to work? So odd, I would have expected that verification happens immediately after burning, no popping out and in. I don't recall seeing anything user message about this, so I pushed the tray in and was planning to use cygwin's diff for my own verification when ImgBurn's verification kicked in. Why the odd ritual of popping-out and popping-in?

I was not sure how well, and how uniform across machines, such UDF support was. Got bitten by that in the distance past, though I *was* using RoxIO (I know, I know). It didn't even warn me. It just silently dropped the file. I did run across one hiccup, not unexpected. If I try to copy an entire file tree from the burned CD back to the HD at a deepr location (i.e. not at the root directory) I am warned that the file path would exceed the maximum length. At least I am notified.

I am going to set the options to allow more than 8 directory levels, more than 255 characters in the path, and files without extensions. What is the consequence of that if I try to read the DVD or CD in a machine running Windows XP, Windows 7, Windows 8, or Linux? I will most likely read the disc from Windows 7, possibly XP.

OK, thanks. As far as using one of the classic backup tools go, I find them great for imaging huge swaths of things, but too heavy artillery for what I back up. I back up quite selectively, and I adapt that selection each time I do a backup. I'll forge ahead with the method in my original post. P.S. I'm not sure that buying Ghost was a good investment considering how I do things. I don't even rely on a ghost of my HD if I have to replace the HD. I do a clean install, even though it takes longer. Maybe because I haven't done that enough to get sick of it. It just seems cleaner.

I want to caution that Google Support forums uses a "Mark as Best" feature for individual posts in a thread. Unfortunately, the OP does not have the ability to unmark a post as an answer (or best answer) if he/she determines that it doesn't address the specific issue that he/she raised. This means the "mark as [best] answer" feature can be mis-used. Microsoft forums *does* allow the OP to unmark a post as an answer.

I already bought Norton Ghost. I don't see any advantage in using it for my purposes, but I was wondering if I was missing something or if there was a more direct way than what I described.

I have been browsing around and trying out ImgBurn and MagicISO to cobble together a process using freeware for backing up selected folders from multiple accounts onto disc. Since I am importing content from more than one account, I was going to create an ISO file in the Public user folder tree, then add files to it as I log into different accounts. However, the process for editing ISO files seems more involved than simply creating a Windows folder tree (in the Public user folder) for the content that is to be burned to disc. I can then user Window 7's native CD burning feature to burn to disc. Any comments on this outlook? Have I identified the most direct way to achieve my backup aim? P.S. It would be way simpler if I could use an account that had permission to access all accounts. I could then everything to be burned in one shot. But I've never seen such a thing in Windows 7 before.

Thank you, LIGHTNING UK!. Works exactly as advertised. There doesn't seem to be a way to mark a thread as resolved in this forum, nor give thumbs up.

I just installed ImgBurn 2.5.7.0. I built an ISO from a selection of files and folders. I used MagicDisc to view the ISO. The full path is not preserved. I googled and explored the ImgBurn settings. Under the General tab, there are options to "Preserve Full Pathnames" for CUE, DVD, and MDS. No such checkbox exists for ISO, though mention is made of full paths for ISO at: http://forum.imgburn.com/index.php?showtopic=7890&hl=+full%20+path%20+iso#entry77897 Is there a way to preserve full paths when building an ISO? P.S. I attached the log file. I am aware that it reveals some files that could not be added to the ISO image, and that is a separate issue (to find a way to pull in from different user accounts). In an ISO file that *is* created, the constituent files do not have their full paths. ImgBurn_usrRenamed.log