Hello KCK and others.
Well, the workaround has improved things considerably, but I am still getting occassional crashes - "blue screen."
Tonight, it told me that a program called "B's CLiP" had stopped responding! Do you know what "B's CLiP" is? I did a web search using google and it appears to be some sort of Packet Writer! How did that get on my system?! Is it part of InCD or is it a part of some other program (like Windows Media Player)?
I wonder if an interaction with it is causing the problem!
It would appear that if I have two packet writer drivers that that might be the case, but I just don't know if "B's CLiP" is OEM'ed to Ahead or something. (?)
By the way, Craig at Ahead gave you (KCK) a big compliment: He said you are VERY knowledgeable.
Anyway, I apologize if I was confused when I guessed I had InCD 3.4 series, because I honestly didn't remember. I thought that that's what I had, but if it was NOT released to the general public, then I did NOT have it, as I had only updated via the nero.com website.
To answer your questions, the Nero InfoTool reports
System.ASPI. Should I have the Nero.ASPI instead and if so, how? Just copy it from the original CD or from a directory somewhere?
(When I click on Nero.ASPI it says "ASPI is not installed."
Also, it does NOT matter (for me) if Auto-Insert Notification is on or off, but I generally keep it off.
I happen to have one of those "weird" (and infamous) hp cd-writer 8230E's that appears in the Device Manager to show up as an hp cd-writer+ 8290.
I hope this info answers all of your questions.
I apologize for not responding sooner; I am not as regular as checking my email which I check VERY often and respond to much more regularly.
I'm DEFINITELY going to go back to the InCD 3.31 as you suggest to see if all problems disappear. In the meantime, if you figure out how "B's CLiP" fits into things, I'd appreciate hearing about it! I'll try poking around to see if I can figure out where it is coming from.