dwallersv
21st April 2006, 22:19
I accidentally pointed BeSweetGUI to azidts.exe as the Azid path in the file locations popup, not realizing that Azid was called internally through a DLL.
Now I can't decode any AC3 anymore, and I can't figure out how to clear this path spec. I can change it to point to a non-existent file, but that doesn't help.
Anyone know how to fix this? Or, where these config parameters are stored? I looked in the BeSweet directory (under Gordian Knot), the Registry, and did a general search of my root volume for anything with "BeSweet" in the filename, but couldn't find anything that looked promising...
Now I can't decode any AC3 anymore, and I can't figure out how to clear this path spec. I can change it to point to a non-existent file, but that doesn't help.
Anyone know how to fix this? Or, where these config parameters are stored? I looked in the BeSweet directory (under Gordian Knot), the Registry, and did a general search of my root volume for anything with "BeSweet" in the filename, but couldn't find anything that looked promising...