for more info about signing of drivers, see following link.http://msdn2.microsoft.com/en-us/library/aa906341.aspxI find it confusing even after reading it several times.Jan

So, is tileproxy.sys aPnP Kernel-Mode Boot Driver or aNon-PnP Kernel-Mode Boot Driver or aPnP Kernel-Mode Driver That Is not a Boot Driver or aNon-PnP Kernel-Mode Driver That Is not a Boot Driver?Could Christian create a signed driver and make it easier for all of us?George

Well, a pity it's not Open Source ... :(---------------------------------------Freeware A380 Load Editor coming soon !

So far I thought the driver needed to be signed by Microsoft or at least be signed by a trusted authority. Wouldn't self-signing with a random key kind of defeat the purpose of providing some level of trust to the driver?Anyway, the 64 bit version will be part of the next installer package, but the next version (Beta 2) will likely not be signed yet.Christian

>My understanding is that you need to have signed drivers for>windows x64.>I think you are referring to Microsoft certified drivers. In>that case, you can indeed choose to install uncertified>drivers "at your own risk".>There is a difference between the two.>>Tileproxy.sys will not load under Vista x64 if you do not sign>them yourself (see one of my previous posts) or if you do not>disable the checking before booting into windows. >(there is a third option, but I consider that one dangerous,>as it had me reinstall Vista twice. Of course each time my own>fault).>>JanAs i stated in my post, and you can see my sig, I'm talking NVidia display drivers and NVidia's 680a chipset driver. MS don't write em.I just installed an HP wireless mouse and keyboard driver, same deal, no problems, and unsigned.If they were signed by MS, why the dialog box.Makes no sense.I see no difference from XP,"This driver has not passed MS WHQL","Do you still want to install"?I get "Yes","NO" buttons.I run Vista-64 now.

I believe I have a Kernel Mode driver which is not a boot driver, meaning I would have to sign the "catalog" file. I believe with that they mean the INI file.Don't know if it's Plug and Play or not. It's a MiniFilter driver. That's all I know ;)

Did you use the process called "test signing" the drivers? The .doc file (walkthrough) in the archive warns that test signed drivers are not to be released to end users as part of a software release.It means that the end user manually has to install a trusted root certificate (well, I could make that part of the installer). But I don't think shipping a test signed driver is legally OK.Christian

even worse: the commandbcdedit.exe /set TESTSIGNING ONdisables checking for a trusted root authority and your desktop will state "Test Mode" in all 4 corners of the screen.That is kind of bad to ship to end users in this way.

Have you been able to solve this problem yet?How much does it load before it stops? only a few URLs? thousands?

I don't know. I think it depends who signs them : - WHQL drivers are tested by Microsoft and approved by them : installs without problems (warning messages).- nvidia beta drivers are none WHQL : not tested (signed ?) by Microsoft : the warning you see- there are some drivers you can not start/install without signature on vista x64, luckily you can bypass this by F8 during boot or by signing the drivers yourself, or disable the checking altogether ( again , NOT recommended, and I am not going to tell how to do that here ).I think in this case, that it is indeed enough to create and sign a cat file for tileproxy.sys, but I am not sure. I am not sure either if I can do it, or if one need acces to the source, in that case it is up to Christian. Will look into it next week.Jan

This works on XP x64 ?---------------------------------------Freeware A380 Load Editor coming soon !

I should have used the Windows Server 2003 x64 build target because that one might also execute on XP 64 bit., but I used the Vista x64 target. Well I guess it's a hit or miss if this actually executes on Windows XP 64 bit (I didn't even know such a thing existed, hehe). Actually I thought 64 bit support only started to really become mainstream with Vista (and before that with Linux, hehe)Christian

Hallo,it might be wise to offer a Vista x64 and XP x64 version of the sys file. Should be quite easy with the WinDDK ... (I code C++ myself)I run Windows 2003 x64 SP2 and it does not work.Always between 20-30% of the FSX loading screen FSX hangs and no tiles get downloaded. Tested with various map services and different big airports.I tried to compile the TileProxy opensource stuff to x64 but sadly the SimConnect SDK offer no 64-bit libs ... :(---------------------------------------Freeware A380 Load Editor coming soon !

Have you tried enquiring Microsoft about the state of a 64bit simconnect interface?

No, not yet. And as I'm not inside the beta my voice might not be so important like yours :)---------------------------------------Freeware A380 Load Editor coming soon !