What's your vid/pod id?
To sign 64 bit drivers you need to do the following, do not miss any steps out or change order as it probably won't work!
1) Download and install the Windows 8 SDK kit
2) Download and install the Windows 8 WDK kit
3) Download the drivers I used from ftp://support.archos.com/Archos%209/...00115_Beta.zip Please note these drivers only work if your USB VID id is 0EEF and your PID id is 0001. In theory you can change this to match yours!
4) Extract drivers and copy the x64 folder to you driver root (this is only to make command line stuff simpler)
5) Working from the x64 folder you copied remove all cat files, files that start combus,ps2mini and serial mini. This should just leave usbmini and egxbus files also leave devcon.exe and DPInst.exe as you will need them to install the drivers once signed.
6) Using the Windows 7 signing guide I found on the Microsoft site (ignore all the information and what operating system its for) Steps for Signing a Device Driver Package FOLLOW EACH STEP TO THE LETTER
7) For the self-sign certificate I used: makecert -r -n "CN=eGalax - Driver signing" -ss eGalax -sr LocalMachine
8) The command I used to create the cat files: inf2cat /driver:c:\x64 /os:XP_X86,XP_X64,Server2003_X86,Server2003_X64,Vista_X86,Vista_X64,Server2008_X86,Server2008_X64,7_X 86,7_X64,8_X86,8_X64
9) You need to sign each of the cat files the were created here are my commands:
A) signtool sign -s eGalax -n "eGalax - Driver signing" /t http://timestamp.verisign.com/scripts/timestamp.dll c:\x64\egxbus.cat
B) signtool sign -s eGalax -n "eGalax - Driver signing" /t http://timestamp.verisign.com/scripts/timestamp.dll c:\x64\usbmini.cat
10) As long as you have followed all the steps as detailed and NO errors were produced you can now install the drivers by running DPInst.exe as an Administrator.
11) Remove the original x64 folder and copy this one in to the set up location and then run the setup.exe as normal. Just ignore the stuff about PS2 and COM ports. Once installed reboot!
12) If all went well you should now be able to use the touch screen as I can.
Please note I give this as a guide and not a definitive source and cannot answer technical questions.
PS You will need to find the markcert, inf2cat and signtool in the program files (x86)\Windows kits\8.0 folders. I used the 64 bit folders where possible but I am guessing its the same tool for 32/64 bits
I gave up and installed Win8 CP x86 instead, drivers install fine, but calibration is a total mess, calibrated my display and it's just random flailing all over the place what ever I do.
I finally gave up on getting one of these drivers to work, so instead I took an alternate route; since my touch screen works in 8 with no drivers but with a horizontal mirroring of input and really bad calibration I figured I could get around the calibration problem somehow, and I was right:
This guy had a similar issue but with other hardware and OS: Memo for Problems and Solutions: The Touchscreen Problem on my Laptop but his solution applies.
The TabletPC touch calibration utility normally only has very few calibration spots and the result on my cheap chinese touch screen is really bad, my best guess would be that the touch screen isn't perfectly linear in input over the surface, or uneven, anyway with a whole lot more calibration points it's much better, that utility accepts command line arguments it turns out:
Here is the command that gave me the best results thus far:
tabcal lincal novalidate XGridPts=4,207,410,613,816,1020 YGridPts=4,155,306,457,608,760
(cmd needs to be run as administrator, default path of c:\windows\system32 is the one you want)
Note that if your resolution isn't 1024x768 you need your own numbers, I'd suggest 4-6 at the extremes and one fairly close to those and then evenly spaced total of 6 points per axis, you'll need a bit of basic math to get your points, but it's not a difficult job.
I've tried a bunch, I even tried giving it an insane amount of points, but for some reason that has diminishing returns, above 6 per axis seems to break it somehow, I'll look into this further but that command gives me a very solid performance all over the screen, it occasionally goes weird on me but I think that's because I haven't yet fixated the cables involved and I'm using fairly thin double sided tape to attach the touch panel to the screen, it might be touching the screen slightly or the cables might be flexing not sure, I'm confident when I've replaced the electrical tape with screws and hard plastic around the edges and managed the cables better it will be consistent.
If you need to reset the calibration to try again you need to go into the registry to delete the reference to "LinearityData" for the device in addition to the place he talks about, searching for "LinearityData" is enough to find all entries you need to delete, the TabletPC panel can't delete values made this way it seems, rebooting and re-plugging the device might also help in some way to reset the calibration it seems, don't try to re-calibrate while the display is still acting like it did before you reset, it will just compound the offset you're trying to get rid of, it needs to act like it did before any calibration. The old calibration even after a reset seems to linger at times, helps to do the stuff I mentioned just now, restart, replug, use the calibration utility on TabletPC settings and reset it in there etc.
You still won't be able install them as they are self-signed. I'm not sure if you can install the certificate I created and this would be a security risk. Microsoft have just made the release candidate available and I'll be installing this over the British long weekend!