CDBurnerXP compile/test-write question/problem

I am exploring the use of CDBurnerXP for backup of nonrecreational
data (not music/images/movies) onto CD-R's.

From reading the help, it seems that assembling a compilation merely
creates a plan of the file hierarchy to be burned onto disc. Since it
took a long time for the dragging of a file tree to the compilation
area to finish, I looked around my hard drive to see if there might be
an temporary storage area that the files are being copied to --
perhaps the copying was keeping the program busy. I couldn't find an
area on the hard drive that the files are copied to, at least while
assembling the compilation; so I assumed that such copying is not
done. Is this correct?

Assuming it is, then it is possible that files to be burned might
change in between the time that it is put into the layout and the time
that the CD is burned. So there should be a phase in CD write process
that checks all the files in the compilation to ensure that they are
still present on the hard drive, and of the size specified in the
compilation. I guessed that this was part of the function of the
test-write setting. Indeed, a test-write reported a file that was
named in the compilation, but which I had removed from the hard drive.
The test-write then removed the filename from the compilation. This
behaviour is what I would consider desirable.

I tried to check what test-write would do if the file on the hard
drive was present, but merely changed sizes. When I started a
test-write, under this condition, CDBurnerXP terminated. This happens
repeatedly if I start up CDBurnerXP again. After termination, there
was no hint of a CDBurnerXP process in the task manager. However, a
process "nmsaccess" did exist. According to google, this allows
nonadministrators to access the CD drive. The presence of nmsaccess
seems to be sane because I had set the CDBurnerXP options to allow
nonadministrators to burn CDs.

I am puzzled, however, by the repeated and unexpected termination of
CDBurnerXP when a file in the compilation differs from the
corresponding file on the hard disk. Thanks for any suggestions on
how to resolve this problem that I'm encountering in test-write (for
the purpose of checking the files before writing).

"Dubious Dude" wrote in message
...
I am exploring the use of CDBurnerXP for backup of nonrecreational
data (not music/images/movies) onto CD-R's.

From reading the help, it seems that assembling a compilation merely
creates a plan of the file hierarchy to be burned onto disc. Since it
took a long time for the dragging of a file tree to the compilation
area to finish, I looked around my hard drive to see if there might be
an temporary storage area that the files are being copied to --
perhaps the copying was keeping the program busy. I couldn't find an
area on the hard drive that the files are copied to, at least while
assembling the compilation; so I assumed that such copying is not
done. Is this correct?

Assuming it is, then it is possible that files to be burned might
change in between the time that it is put into the layout and the time
that the CD is burned. So there should be a phase in CD write process
that checks all the files in the compilation to ensure that they are
still present on the hard drive, and of the size specified in the
compilation. I guessed that this was part of the function of the
test-write setting. Indeed, a test-write reported a file that was
named in the compilation, but which I had removed from the hard drive.
The test-write then removed the filename from the compilation. This
behaviour is what I would consider desirable.

I tried to check what test-write would do if the file on the hard
drive was present, but merely changed sizes. When I started a
test-write, under this condition, CDBurnerXP terminated. This happens
repeatedly if I start up CDBurnerXP again. After termination, there
was no hint of a CDBurnerXP process in the task manager. However, a
process "nmsaccess" did exist. According to google, this allows
nonadministrators to access the CD drive. The presence of nmsaccess
seems to be sane because I had set the CDBurnerXP options to allow
nonadministrators to burn CDs.

I am puzzled, however, by the repeated and unexpected termination of
CDBurnerXP when a file in the compilation differs from the
corresponding file on the hard disk. Thanks for any suggestions on
how to resolve this problem that I'm encountering in test-write (for
the purpose of checking the files before writing).

If you're puzzled now, wait till you try to uninstall the thing. In my case
it kept coming back, I never got rid of it until I rebuilt the system. Not
recommended.
Get burn4free does a nice job. BurnAtOnce is good but I had trouble with
multi-session, but apparently others don't have problem I had so it's worth
a try.
Dave Cohen

Dave Cohen (****wart) whined:

snip whining

Shut the **** up, ****wart!