> Not dir2dat is tied, the currently loaded profile is. So if you loaded a profile
> which got NES enabled and you enter Dir2Dat, NES is active. When nothing is
> loaded, no header should be active.

This seems to hold true, except for when the "clear cache" is clicked. As I described in the steps above, the header detector(s) will remain loaded in Dir2DAT.

>
> By the way...if you created new header xmls yourself (or did I misinterpret
> this?), let me know. I'd like to add them officially.

I've currently created header detectors for NSF, PSID, and PSID v2 NG. I want to perform more testing though, since I just created the PSID ones at work today ;) I'm also looking into some more, but we'll see where that goes...

>
>
> *Edit* Hmmm....I guess an option to select the currently used header xml would
> be fine within dir2dat...I will think about it.
>

What I was hoping for would be a Dir2DAT independent of any profile: adding a small subsection to select the detector(s) desired to be applied during DAT creation. Is there a particular reason for tying the Dir2DAT to a loaded profile? Perhaps some hidden functionality I could be harnessing? Or is it to prevent having to reload a profile upon closing Dir2DAT?

In any case, I am very grateful for this tool no matter what you decide to do, and the header detectors already work when the appropriate steps are taken. I recognize that this work is done in your own free time, and appreciate it.

I'll be sure to contact you when I am comfortable with the correctness of my header detectors.