RegNamespace Forum Rss Feed

New Post: RegPH sample program do not create any entry in the index

fpiette — Mon, 25 Oct 2010 16:11:13 GMT

Hello,

Using VS2008, I have compiled the protocol handler "RegPH" (The version which is in Windows Search SDK). It seems to work but do not create any entry in the index (Running on Windows Vista French, latest updates installed). Compilation went 100% OK. The protocol handler and shell folder are installed and apparently working fine.

I have looked at the eventlog and found a warning saying the content source <reg://{s-1-5-21-1259595494-1951413687-3429671250-1000}/> is not accessible (Exact message is in french because I use a localized Windows Vista). Event ID is 3036. Error code is 0x80040d07.

Maybe it is a permission problem. I have no idea about solving that issue.

Any help appreciated.

New Post: Computer windows problem

Pammachio — Sun, 31 Jan 2010 23:15:00 GMT

I all,
I have a problem on my Windows Vista that began afetr the purchase of an external Hard Disk Freecom.
A few days afetr the purchase I disconnected it while it was writing and, since that moment, every time I connect and disconnect it, the PC go to freeze mode for 5 minutes.
The same thing happen even if the hard disk is disconnected: every time I start windows it go to freeze a little after the password, and every time I connect and disconnect a usb device.
I have looked for the solution everywhere, updated windows, unistalled and installed the hard disk from the device manager but I solved the problem only when I restored a recent backup.
Yesterday the Hard disk was writing a backup while Vista was installing the updates; at the end of the proceure windows restarted automatically and the problem began again!!!
The Pc go to freeze when it starts, every time I connect or disconnect the hard disk, an usb earphone that has always worked switch on but there is no audio and I don't know how many others usb devices will have problems.
Has anyone an idea to solve this problem before I throw out of the window Vista or the the hard disk?
Thank you

__________________
Never seen gift like these! (geschenkideen fur on german or ideas para regalos originales on espanol), fotografie matrimoni

New Post: Address Bar/Direct Path Option - One step to perfection?

jonusc — Tue, 13 Oct 2009 08:58:20 GMT

Hello :)

This is a great extension and it's great for browsing the registry. However, the main reason I am greatly interested in this is a quick ability to browse to a specific key - short of manually opening the folder namespace and pasting the Key Path after.

For tinkerers and testers like myself, i'm sure you understand where I'm coming from - when trying to diagnose or inspect any sort of software (via Process Explorer for example) we come across a specific key we need to inspect. For the average tinkerer trying to tweak or fix a windows problem, a support person may query the user on a Registry value to check on and mention the path. It'd be great if there was a super quick way of getting there.

What my point is, how good would it be if I could whack Winkey+R and just paste/type in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\IDE and a new Explorer process would jump straight there? I understand the security concerns of such a thing of course, but it'd be very useful.

I don't know much at all about this kind of programming, but I am reading up on Namespace Extensions to try and achieve exactly this. At first I thought - maybe I could map a drive letter to the Registry Extension....

Browsing the source, I notice references to a reg:// protocol. Trying to fiddle with that via Run command either gives me a catastrophic failure or "No program is registered with this protocol" prompt. Is this related?

Hope someone can give some insight on this one! Until then i'll keep doing my research to see if I can get anywhere with my limited skill.

Definately the best explorer Extension since PowerMenu. Where's the donate link? Someone deserves a beer or two!

New Post: Windows Vista x64

jonusc — Tue, 13 Oct 2009 08:18:37 GMT

Hi Juraj,

The solution converted to VS2008 fine and built successfully after switching the active config from Debug to Release. I recieved an error from WixSetup but of course that was not a critical error, and the built RegNamespace.dll in your copy requires elevation before registering. But both DLL's regsvr32'd fine and I now have the icon successfully visible on my desktop :)

Thanks very much for sharing Juraj! Have you (or the developers) considered making a commit to provide x64 support out of the box? It'd be a good thing to do sometime in the future. Thanks again!

New Post: Windows Vista x64

juraj — Tue, 13 Oct 2009 07:22:49 GMT

Hi,

try my version of the project which is working fine under Vista x64.

You will find the project files here:

http://rapidshare.com/files/292340133/RegNamespace_x64.zip.html

However, in this project I hardcoded the processor architecture in the manifest file and I didn't use pragmas.
But for you just in order to verify whether it's working or not, it should be sufficient that way.

Juraj

New Post: Windows Vista x64

jonusc — Mon, 12 Oct 2009 18:38:41 GMT

Hi guys,

I noticed this thread is over a year old, but I am trying to compile from source for Windows 7 x64 and not having a great amount of luck. Bear with me, i'm only a web developer and scripter and don't have a lot of experience in C(++/#) coding but I can recognize syntax and have a very basic understanding of pointers and methods and whatnot.

I have compiled things in Visual Studio before, although this is the first time I've tried to compile for a 64-bit machine. The last post by juraj seems to cover everything, I have also read articles on 64-bit porting such as the CodeProject C++ 64-bit article here however I encounter errors when trying to register the RegNameSpace DLL.

I am running Visual Studio 2008 with the Windows SDK v7.0 (for Windows 7 x64) integrated. That may be part of the issue. Anywho, in reference to the guide I mentioned above, I have did not find any issues with pointer length and 32>64-bit compatibility (via a recursive Find Text In Files command in UltraEdit) apart from that single size_t variable, so I'm sure it's the architecture setting that I can't figure out. If I simply change my Configuration by copying the Win32 to x64 architecture as outlined on this MSDN article I get the same 'This DLL is not for 64-bit architecture' message or whatever it is when trying to register it. Fair enough, I take it that changing the "processorArchitecture attribute" is more than that. So taking that code you posted juraj and inserting it after (and I tried before) the #pragma once line in stdpch.h under the RegLib project, seems to build a correct x64 DLL. However, I get this error in Event Log:

Activation context generation failed for "S:\Storage\Software - Windows 7\Registry Shell Namespace Extension\RegNamespace_x64\RegNamespace\x64\Release\RegNamespace.dll".
Error in manifest or policy file "" on line . 
A component version required by the application conflicts with another component version already active. Conflicting components are:. 
Component 1: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_fa645303170382f6.manifest. 
Component 2: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7600.16385_none_421189da2b7fabfc.manifest.

I understand that it's basically conflicting between the 32-bit and 64-bit comctl32.dll but I have no idea how to resolve it =( My not-so-educated guess is that these "preprocessor pragmas" should be put somewhere else instead...? If someone could give me a tip or has any ideas, I'd be very grateful - I have missed using this extension since moving from Vista 32-bit to 7 64-bit very much. I have subscribed to this thread via E-Mail and look forward to replies.

Thank you for the great explorer extension you've created.

New Post: How search in NSE works

lsag — Thu, 17 Sep 2009 14:33:35 GMT

Can you please explain to me how Windows search searches NSE? I was unable to figure out when search protocol is invoked when I search for any data in Windows registry NSE. I though Windows search would use properties and PKEY_Search_Content particularly to perform deep search inside NSE. Does it search recursively?

Also when I go into Vista main search it does not seem to include NSE in search.

New Post: Vista Sync Handler and IShellItem2

pete0815 — Tue, 21 Apr 2009 05:48:37 GMT

hi
Sorry but it seems i cannot help you cause i used the interfaces in c++ but i think if you should be able to connect via c#. there should be no reason why you cannot connect from c# cause mobsync would connect via com. do you have registered your sync handler and handler collection and updated thoses infos in HKLM\Software\Microsoft\Windows\CurrentVersion\SyncMgr? as far as i know you don't need the collection handler but you need to register the info in the apporp. registry key.

gl and cya
pete

New Post: Vista Sync Handler and IShellItem2

masique — Fri, 17 Apr 2009 05:48:53 GMT

Helo, It is kind of off-topic, but I also was playing with ISyncMgrHandler and legacy ISyncMgrSynchronize. Do you using this interfaces from C# ? I have trouble to connect throught new ISyncMgrHandler with C# on Vista. But old ISyncMgrSynchronize works well on both Windows XP and Vista.

New Post: IPropertyStore vs. IFilter

rlrcstr — Sat, 03 Jan 2009 06:50:02 GMT

Matt, Jerry -

Hopefully you guys are still monitoring this thread... I've got a project where I'm building an IFilter for a file format based on the Microsoft Exchange journaling feature which, in turn, is based on the .eml file format. So I register a new file extension (.jeml) and created an IFilter for it. The filter emits a series of properties specific to the journal envelope and then feeds the rest of the document through the standard .eml IFilter (mimefilt.dll). Everything seems to run just fine when I test with FiltDump.exe. But getting the filter to run in the context of Explorer.exe or general desktop indexing seems to be an issue.

As far as I can tell, I've got all the proper registry entries, but the system never loads my filter.

For standard indexing for WDS, I don't have to implement IPropertyStore or create a separate property handler if I've got the fill IFilter interface implemented, do I. What's the point of IFilter::GetValue, if I still have to implement the other interface?

Any clarification you can lend here would be much appreciated. I feel like I'm so close to getting this thing up and running, but I'm missing one tiny bit...

Thanks.

J

New Post: Can We access the Document details, and preview windows in vista explorer window

Javed — Wed, 08 Oct 2008 12:12:00 GMT

I want to adds some tab pages on to the explorer in vista to show metadat categorically in the bottom document detials view. Is this possible to do? If yes, how?

My another question is is it possible to get the client area of the windows explore somehow. I know IShellBrowser is the container who holds the explorer window but not able to find a way.
My requirement is I will create a window with a splitter. In one pane I want to show some data and in another pane I want to host the whole windows explorer (just without the caption). It is either Xp or vista. Is this also doable.

Thanks,
Javed

NEW POST: Location of the Registry Icon

vprimachenko — Sun, 27 Apr 2008 12:31:21 GMT

Is it possible to locate the icon under "Computer" instead of "Desktop"? It is possible to move the icon manually?

NEW POST: Vista Sync Handler and IShellItem2

pete0815 — Thu, 10 Apr 2008 11:47:41 GMT

Hi
I'm using the the Sync Handler to synchronize our company applications. For this I implemented the ISyncMgrHandler Interface but now I would like to extend the application with the conflict store. Every conflict during a synchronization is stored in a db and is displayed in the sonfict store. When a user would like to resolve the conflict i have to pass a IShellItem2 in the Strucuture CONFIRMCONFLICTITEM which in my case i have no clue if i should implement this interface in a class or if there is a way that i retrieve a IShellItem by calling the methode SHCreateItemFromIDList.

Do I have to register a shell item so that i can use the methode call? If so do i have still to implement the Interface IShellItem2 or can i link a class with this shell item that is wrapped in a IShellItem2 Object? Or is there only the hard way and implement my own class with the interface?

Please keep in mind that this is the first time i get in touche with this Interface and any information would help me.

Best regards,
pete

NEW POST: Windows Vista x64

juraj — Mon, 24 Mar 2008 10:38:59 GMT

For those who intend to get it working under x64 I discovered two issues which must be fixed
1) The manifest is composed to use the 32-bit version of comctl32.dll. You must either change the processorArchitecture attribute to "amd64" or you may use the preprocessor pragmas to use the right version of the DLL, like this

#if defined _M_IX86
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='x86' publicKeyToken='6595b64144ccf1df' language='*'\"")
#elif defined _M_IA64
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='ia64' publicKeyToken='6595b64144ccf1df' language='*'\"")
#elif defined _M_X64
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='amd64' publicKeyToken='6595b64144ccf1df' language='*'\"")
#else
#pragma comment(linker,"/manifestdependency:\"type='win32' name='Microsoft.Windows.Common-Controls' version='6.0.0.0' processorArchitecture='*' publicKeyToken='6595b64144ccf1df' language='*'\"")
#endif

2) In the XMLDocument::Load method, there's a small pointer compatibility problem, causing passing a pointer to a 64bit value where a pointer to a 32bit value is expected. All you need to do is change the type of the local variabla "cch" from size_t to DWORD.

That's it. May be there are some other 64/32bit pointer compatibility issues, but I've not been confronted with them yet.

NEW POST: Windows Vista x64

JamesFinnigan — Tue, 11 Dec 2007 18:40:48 GMT

I don't believe we tested it for 64-bit, but it might work. It would need to be recompiled for 64-bit, though.

NEW POST: Windows Vista x64

snaky — Tue, 11 Dec 2007 13:15:43 GMT

Does it work under Windows Vista x64? I've installed it but an icon of the extension didn't show up.

NEW POST: Windows Vista Sync Center Style Control Panel Extension

JamesFinnigan — Tue, 25 Sep 2007 17:37:20 GMT

We weren't sure exactly what you were trying to do - here's a couple guesses and the answers that go with them.

If you want to write an in-frame Control Panel with the same look and feel as windows. Since the display technology is not public, you can't do this using the display technology we're using. You can make a shell namespace extension which looks like our CPLs, but you'll have to draw the contents on your own, with the display technology of your choice (except that managed code is not yet a good choice for shell extensions). Here are some design guidelines: http://msdn2.microsoft.com/en-us/library/Aa511272.aspx

If you want to write a Sync handler. The interface is ISyncMgrHandler, and there should be a sample in the sdk.

Hope that helps.

Thanks,
James

NEW POST: Windows Vista Sync Center Style Control Panel Extension

sajid — Fri, 21 Sep 2007 17:42:08 GMT

Hi Guys,

I'm developing a control panel application and I was wondering how do I go about developing a Vista Style Sync Center control panel.

I've already CPlApplet based panel so that is not an issue and I'm pretty sure I can register a Tasks.xml file for common task.

The sync center is unique in that it opens up in place and is navigated like pages.

I could'nt find any reference or documentation for doing something like it. Although I did get to Shell namespace extensions. Is Sync center a regular namespace extension? or is this new kind of extension supported on Vista, Would be great if I could get some sample code.

regards

Sajid

NEW POST: Registry not showing up in Explorer

AR — Thu, 30 Aug 2007 23:56:35 GMT

Thanks for that.

Yep, that did it!

Minor point for the record, in case others run into the same problem:

The /f in the command line needs to go at the end, or it will fail with "key not found":

reg delete HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\CLSID\{E48ABDCD-0DE7-4C5A-91EB-13D6E81506F0} /f

NEW POST: Registry not showing up in Explorer

JamesFinnigan — Thu, 30 Aug 2007 21:34:13 GMT

This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.