File association is handled by the operating system, it has no effect on the burning software other than open it to use the configured defaults associated 'in the program' for use with the file type.
Giving it permission to become a default program that executes a file extension in windows, is irrelevant to the software's function. Even being 'not the default' the software still gets full hardware access to the IDE controller and locks the drive to burn the disc. There's no overhead, there's no PowerISO interference. The only reason I can see this happening in your case, is improperly configured DJ software. (for the burn image function) Or bad hardware/media.


Reply With Quote

