Problem with Delta

RedawgTS · February 18th, 2003

Whenever i make a new config or edit an existing one i get two error messages. the first is 'error opening parent key' and the second is 'error obtaining subkey names'. It sounds like a registry problem, it only started recently since i re-installed windows xp sp-1. does anybody have a clue what's going on?

__________________
"...if you drink much from a bottle marked 'poison,' it is almost certain to disagree with you, sooner or later."
-Alice, Alice's Adventures In Wonderland

OS: Windows XP Profesional SP-3 CPU: Intel Core 2 Duo E7300 OC'd @ 3.0GHz RAM: OCZ 2GB DDR2 Video: NVIDIA GeForce 9600 GT Sound: On-Board

**Betamax** · February 19th, 2003

That's a registry problem all right. Basically your missing the plugin registry keys. This is most likely because you haven't ever configured any plugins since the reinstall. The easiest way to fix this is to configure epsxe from it's own gui once. That will restore the missing keys.

__________________

Superior marketing of an inferior product will always win over inferior marketing of a superior product.

RedawgTS · February 19th, 2003

That's the first thing I tried. It didn't help. But i did find the problem. It seems Delta is reading settings from the ePSXeCutor registry settings. Since i didn't use it, the registry settings wern't there to be read. I created a new config for it and now Delta works fine. It worked before the reinstall of windows because i just recently switched to delta from epsxecutor. Thanks for the help though.

__________________
"...if you drink much from a bottle marked 'poison,' it is almost certain to disagree with you, sooner or later."
-Alice, Alice's Adventures In Wonderland

OS: Windows XP Profesional SP-3 CPU: Intel Core 2 Duo E7300 OC'd @ 3.0GHz RAM: OCZ 2GB DDR2 Video: NVIDIA GeForce 9600 GT Sound: On-Board

**Betamax** · February 20th, 2003

Actually that's incorrect, but I can see why you would come to that conclusion.

Explaination:

In the current release, whenever you create a new config/edit config, it generates the dta file then enumerates over the SPU, GPU, CDR keys contained within HKEY_CURRENT_USER/Software/Vision thing/ can copies any keys/values stored within them into the dta file. The "cannot locate primary key" message basically means that these keys do not exist on your system.

Now depending on the plugin, the missing keys will be created whenever the plugin is either loaded or configured.

I'm assuming that when you tried the above you didn't press the config button when you tried the above, as some of the missing keys still weren't generated.

Now epsxecutor also stores it's setting's in HKEY_CURRENT_USER/Software/Vision thing, under a sub key called ePSXeCutorCFG/X, where X is the name of the config. Now AFAIK when ever you run a setting using this frontend, it basically copies the contents of X into the vision thing key. Hence, by running epsxecutor once, you have re created the missing keys that Delta was looking for in the first place

.

Anyways, you've spotted a pretty nasty bug there. I only figured this stuff out after testing what you posted here. I've fixed the problem now and I'll be uploading a new version shortly.

__________________

Superior marketing of an inferior product will always win over inferior marketing of a superior product.

February 18th, 2003	#1 (permalink)
RedawgTS Royal Pain in the A** Join Date: Aug 2001 Location: Magrathea Posts: 31	Problem with Delta Whenever i make a new config or edit an existing one i get two error messages. the first is 'error opening parent key' and the second is 'error obtaining subkey names'. It sounds like a registry problem, it only started recently since i re-installed windows xp sp-1. does anybody have a clue what's going on? __________________ "...if you drink much from a bottle marked 'poison,' it is almost certain to disagree with you, sooner or later." -Alice, Alice's Adventures In Wonderland OS: Windows XP Profesional SP-3 CPU: Intel Core 2 Duo E7300 OC'd @ 3.0GHz RAM: OCZ 2GB DDR2 Video: NVIDIA GeForce 9600 GT Sound: On-Board

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

February 19th, 2003	#2 (permalink)
Betamax Resident Movie Critic Join Date: Apr 2001 Location: Belfast, Northern Ireland Posts: 9,508	That's a registry problem all right. Basically your missing the plugin registry keys. This is most likely because you haven't ever configured any plugins since the reinstall. The easiest way to fix this is to configure epsxe from it's own gui once. That will restore the missing keys. __________________ Superior marketing of an inferior product will always win over inferior marketing of a superior product.

February 19th, 2003	#3 (permalink)
RedawgTS Royal Pain in the A** Join Date: Aug 2001 Location: Magrathea Posts: 31	That's the first thing I tried. It didn't help. But i did find the problem. It seems Delta is reading settings from the ePSXeCutor registry settings. Since i didn't use it, the registry settings wern't there to be read. I created a new config for it and now Delta works fine. It worked before the reinstall of windows because i just recently switched to delta from epsxecutor. Thanks for the help though. __________________ "...if you drink much from a bottle marked 'poison,' it is almost certain to disagree with you, sooner or later." -Alice, Alice's Adventures In Wonderland OS: Windows XP Profesional SP-3 CPU: Intel Core 2 Duo E7300 OC'd @ 3.0GHz RAM: OCZ 2GB DDR2 Video: NVIDIA GeForce 9600 GT Sound: On-Board

February 20th, 2003	#4 (permalink)
Betamax Resident Movie Critic Join Date: Apr 2001 Location: Belfast, Northern Ireland Posts: 9,508	Actually that's incorrect, but I can see why you would come to that conclusion. Explaination: In the current release, whenever you create a new config/edit config, it generates the dta file then enumerates over the SPU, GPU, CDR keys contained within HKEY_CURRENT_USER/Software/Vision thing/ can copies any keys/values stored within them into the dta file. The "cannot locate primary key" message basically means that these keys do not exist on your system. Now depending on the plugin, the missing keys will be created whenever the plugin is either loaded or configured. I'm assuming that when you tried the above you didn't press the config button when you tried the above, as some of the missing keys still weren't generated. Now epsxecutor also stores it's setting's in HKEY_CURRENT_USER/Software/Vision thing, under a sub key called ePSXeCutorCFG/X, where X is the name of the config. Now AFAIK when ever you run a setting using this frontend, it basically copies the contents of X into the vision thing key. Hence, by running epsxecutor once, you have re created the missing keys that Delta was looking for in the first place . Anyways, you've spotted a pretty nasty bug there. I only figured this stuff out after testing what you posted here. I've fixed the problem now and I'll be uploading a new version shortly. __________________ Superior marketing of an inferior product will always win over inferior marketing of a superior product.