I can't really blame you for being put off by the prospect of the firmware update process. I was very wary of the process myself, given I didn't want to damage my gear. Even though I thought I was being super careful, I still connected the blaster cable to the jumper pins in reverse... I consider myself relatively capable of tinkering with the innards of electronics and still made such a simple mistake that potentially could have caused serious harm.I've been following this thread for some time...also the DAC-19 thread before it. I own a NOS 19 (primary system DAC) + DAC-19 (2ndary system). I also owned an NB 15.32 combo at one time. I'm kind of an Audio GD fanboy.
But to be honest here, I can't imagine going through what you describe to update any Audio GD DAC. It sounds like a real kludge w/real potential for harm to the DAC, or at the very least, inducing all manner of errors that weren't there before. FYI, I tried setting up a virtual Win 7/32 machine several years ago (on a Win 7/64 PC). It may or may not have worked...I'll never know because I just couldn't understand how to actually operate real-world software on the virtual machine.
Later this year I'll purchase an R2R 1, the newest one w/everything switchable from front panel (no jumpers). Then, as I've done w/my other AGD DACs, I will forget all about the possibility of updating because it's just too difficult/intimidating.
There are many things to like about Audio GD--but for this crazy method of updating to persist at a time when pretty much every other mfr allows updating via flash driver or download--it just makes no sense to me.
I'm sure more experienced tinkerers would have no problem with the process, but even for someone who has always built their own PC's and done upgrades by hand, it was daunting. In saying that, practice makes perfect, if you've ever got some cheaper/smaller gear to get your head around making a process that works for you!