Kommentare

sdmoore schrieb am 15.09.2003 um 19:24 Uhr
Hi Cook,

Open up regedit and have a look at the key

HKEY_CLASSES_ROOT\CLSID\{8efd2490-1362-4ee2-90f1-158ed2ea24ac}

Hopefully, the (Default) value on the right-hand side pane should help in identifying the plugin.

Cheers,

Scott
c00k schrieb am 15.09.2003 um 22:39 Uhr
thank you, but i don't have the plugin installed at all hence it can't be located in the registery.
sdmoore schrieb am 16.09.2003 um 14:39 Uhr
Ah ok. I wondered whether just the .dll had been deleted but if you've uninstalled it or rebuilt your system then you're right - the registry entries won't be there. Anyway, I found out what it is ... it's Satish's Plugin Pac.

Download it from here

Cheers,

Scott
MarkWWWW schrieb am 16.09.2003 um 14:47 Uhr
In that case you'll need to look through the .veg file with a hex editor and see what plugins are referenced there - fortunately they are listed by name.

If you find a reference to one that you don't have installed then you may have found the one causing the problem. Re-install the plugin and you may be able to open the .veg file successfully.

Actually, for this particular exercise, a tool that can locate just the text strings in a binary file is better than a hex editor - you might like to have a look at the free BinText utility from http://www.foundstone.com/resources/termsofuse.htm?file=bintext.zip
I've found it very useful for this sort of thing in the past.

Mark


c00k schrieb am 17.09.2003 um 05:02 Uhr
Thanks a lot guys i got it working all sweetly :D