install problem Vista64 and Multikey 0.18.0.3

[Sharp]

Hi Guys

I have a serious problem with getting the Multikey emulator 0.18.0.3 to install on my Vista 64 bit notebook.

I have used Git’s nice tool (dmp2mkey v. 23) to do a dump of my Sentinel superpro dongle and it worked fine.

My problem is every time I try to install the multikey emulator, by using install.cmd (running as admin) I get the message “No devices were removed. Devcon failed.”

I have tried many approaches to get around this (I have admin rights in the Vista)

- I have added my multikey dir path to Vistas path.
- downloaded new devcon 64 file and put it in the windows dir
- done all the calls from a dos prompt ex.: devcon install multikey.inf root\multikey
- I have used the below link as guideline

http://www.reteam.org/board/showthread.php?t=1508&page=8&highlight=vista+64+sentinel


Can anyone come up with a clue ?

Regards to you all

Sharps

[Git]

You need to overwrite the old devcon.exe with the new devocn.exe and run install.bat from there.

Git

[Sharp]

Git,

Thank you for a quick reply

I did what you said - I searched Vista to find all devcon.cmd.
I deleted all and copyed the devcon from Chrishel’s link to the folder …. Multikeyemu-V0.18.0.3\Release\MultiKey64

and started the install.cmd as admin from the MultiKey64 folder

I still get the same error


Chrishel’s link:
http://rapidshare.com/files/215029834/devcon-x64.zip


Any new suggestions ?

Regards

Sharps

[Git]

So did you download latest 64bit devcon.exe from here?. I uploaded the latest version here - do a search. It is devcon.exe not devcon.cmd

Git

[Sharp]

Git,

Yes I did - sorry for my mistake. it is devcon.exe I use

I still get the same error by using it

I have downloaded it from rapidshare - I got the link in this forum (from Chrishel to rapidshare) - The file info is:

File and product version : 6.0.6001.18000
Size: 79.0 KB (80896 bytes)
Size on disk: 80.0 KB (81920 bytes)
date: 18th of Jan 2008

Regards

Sharps

[cadbob]

Git,

Yes I did - sorry for my mistake. it is devcon.exe I use

I still get the same error by using it

I have downloaded it from rapidshare - I got the link in this forum (from Chrishel to rapidshare) - The file info is:

File and product version : 6.0.6001.18000
Size: 79.0 KB (80896 bytes)
Size on disk: 80.0 KB (81920 bytes)
date: 18th of Jan 2008

Regards

Sharps


Correct me if I'm wrong I believe you still need ReadyDriver as the driver certificate problem still exists.

[Sharp]

@Git any further clues or ideas ?


@cadbob
Yes and it has been installed from the beginning – It is in the guidance I listed above – but thank you anyway :-)

Do you gave any additional clues ?


Regards

Sharps

[Git]

My problem is every time I try to install the multikey emulator, by using install.cmd (running as admin) I get the message “No devices were removed. Devcon failed.”

There is no install.cmd, do you mean install.bat?. I am not being pedantic, I ask because the error message you show is likely to come from remove.bat, not install.bat.

install.bat is like this :

@devcon remove root\multikey
@devcon install multikey.inf root\multikey
@pause

The first line is to remove any old version that may be running, The second line does the business of installing the new version. If you are failing on line 1 but line 2 works OK then that is fine. After all, if MK isn't installed it can't be removed. I would recommend you open a cmd shell in the installation dir and type the two lines above, one at a time and without the '@'. Copy and paste the cmd shell here afterwards.

Later... just occured to me - is multikey.cat in the same directory?

Later still... one thing that may help is to get rid of any multikey entries in the Inf directory. Uninstall multikey then use your favourite file search tool to search WIndows\Inf directory for files containing multikey. It will find something like oem73.inf. Delete oem73.inf and oem73.PNF, also delete branches.PNF and INFCACHE.1. Now run RegEdit, find HKLM\System\CurrentControlSet\Services\multikey and delete just that key. If you have not done this before don't do it. If you do not have permission to delete it, Take Ownership, then delete it. If you don't know what I am talking about don't even think about trying it, you will torch your windows installation. Reboot and try the multikey installation again.

Git

[Sharp]

Git,

First of all thank you for your inputs to my problem. Your input initiated me to start thinking in different directions which actually solved the problem :-)

I got it up running and I have listed my approach below. It can be the case that some of my points can be skipped but I will look into that later when I have some more time – Anyhow this is what I did:

First I updated to Vista SP2
I then looked for a up-to-date devcon.exe to download. The only up-to-date devcon.exe I could find was from (07-13- 2009) from MS homepage Windows Driver Developmen Kit v 7.0.0 So I had to install Windows Driver Developmen Kit. 7

Link http://www.microsoft.com/whdc/devtools/wdk/RelNotesW7.mspx

You only need to install tools in the installation menu to get the devcon which install in: C:\WinDDK\7600.16385.0\Tools\devcon\

There are 3 devcon folders : amd64, i386 and ia64, the amd version worked on my PC (Intel Core 2 duo) ? strange with a intel cpu - but it did.
Path: C:\WinDDK\7600.16385.0\Tools\devcon

I will attach all 3 files here as well as I have listed my way getting the Multikey up and run for the very beginning.

Then I put all the files from the MultiKey64 folder in the multikey folder - path: C:\MultiKey\multikey
I replaced the devcon.exe in this folder (multikey) with the one I mentioned above.

After this I started a dos prompt as administrator and “moved” to the C:\MultiKey\multikey folder. Hereafter I gave the following command: devcon install multikey.inf root\multikey
This installed the Multikey, I checked and I could see it in the Device Manager as SafeNet USB SuperPro/UltraPro under Universal Serial Bus Controllers. I tested the application and it was running like a dream :-)

For those of you who need to do this installation from the beginning I will hereby list the whole installation I did I’m quite sure that you can skip some of the steps I have done but this is to get it out to you as quick as possible – I will work on doing a batch job or a real windows installation project later when I have the time – Here it is:

Download:
- MultiKeyEmu v. 0.18.0.3
- Git tool dmp2mkey v 2.3
- PVA v 3.3


1. Plug in your Sentinel dongle SuperPro into the USB port
2. Use PVA sprodmp.exe file to dump the dongle data – It creates a .dmp file
3. Use Git Tool dmp2mKey to make a .reg file
4. Install the .reg file (by doubleclick on it and select “to reg”)
5. You can check number 4 by using regedit and follow the path in the .reg file
6. Make the following folders: C:\MultiKey\multikey
7. Copy the files from MultiKey64 folder (MultiKeyEmu) to the C:\MultiKey\multikey folder.
8. Replace the devcon.exe file with the one I have attached to this reply
9. Start a dos prompt as administrator
10. Move to multikey folder in the path: C:\MultiKey\multikey (you can use the cd command or whatever)
11. type or paste the following command: devcon remove root\multikey (to remove if any installed)
12. type or paste the following command: devcon install multikey.inf root\multikey - a text in the dos window should tell you that the installation was successful
13. Check in the Device Manager under Universal Serial Bus Controllers here you should see a SafeNet USB SuperPro/UltraPro installed.
14. You are done :-)


Regards to Git and all of You and keep up the good work

Sharps

[Sharp]

File attached are devcon.exe files remove the OS /CPU mark and change the zip to exe
SO pick the one you need and rename as listed below:

devconAMD64.zip = devcon.exe
devconI386.zip = devcon.exe
devconIA64.zip = devcon.exe

[Sharp]

The last one is to big for this forum - If you need it go and get it from MS homepage (download)

Regards

Sharps

[Git]

Nothing strange about it, IA64 is for Itanium, a completely different architecture. Basically, you did exactly what you were told to do several days ago and surprise surprise it worked.

Git

[Sharp]

Git,

Yea you are right, but I think we maybe need some more precise installation guides - or maybe I am to slow :-)

@All: By the way I forgot to state that I also installed SetupReadyDriverPlus.exe to avoid the driver sign check - I did it after number 8 in my installation guide.

Regards

Sharps



SetupReadyDriverPlus.exe link:

http://www.citadelindustries.net/readydriverplus/index.php

[Git]

Having to boot from a CD or USB drive sounds a right pain. WHy not just sign the driver and install your own certificate?. There's a link to full instructions somehwere on this site if you search.

Git

[cadbob]

Having to boot from a CD or USB drive sounds a right pain. WHy not just sign the driver and install your own certificate?. There's a link to full instructions somehwere on this site if you search.

Git


Correct me if I'm wrong but signing the driver ourselves still runs Vista 64 in TEST MODE.

SO you will need a water mark removal app to remove Test Mode from the desktop screen.

[Git]

If I try to answer that I will be guessing because I think something changed in Vistas last SP (and I don't use Vista). The observation I can make is that the subject used to arise here regularly but since that link was posted I think your post is the first time it has been mentioned since. You could conlcude that it is still working but I don't know for sure. I do see the subject discussed now and again on different boards and I don't hear about people booting from CD or USB stick.

Sorry to be so vague. If you search on Certificate and 64 you should find it.

Later... I could not find the link but I did find several links to the SetupReadyDriverPlus program so you were right on that and I was wrong. I did find two archives I had, one of which I know I downloaded from the post I am referring to.


http://rapidshare.com/files/270167795/drivercert.zip
http://rapidshare.com/files/270168252/Test.Certificate.rar

Git

[Sharp]

@ Git and cadbob

Does this small application (see link) solve the WM problem ?

http://www.mydigitallife.info/2009/01/06/remove-watermark-32-bit-and-64-bit-universal-patch-free-download-for-windows-7-vista-and-server-2008/


Sharps

[Klopschik]

@sharp
Better you make a google search for atsiv 1.02 command line tool that allows the user to load and unload signed or unsigned drivers on 32 and 64 bit versions of Windows XP, Windows 2K3 and Windows Vista. Atsiv is designed to provide compatibility for legacy drivers and to allow the hobbyist community to run unsigned drivers without rebooting with special boot options or denial of service under Vista.

Klopi

[Git]

Looked a good idea on the surface but you won't be able to load atsiv anymore as Versign have withdrawn it's own security certificate. So it is itself an unsigned driver. Therefore you will need a solution to the signing problem to load atsiv, and by the time you have that solution you don't need atsiv anymore.

http://blogs.pcmag.com/securitywatch/2007/08/microsoft_stomps_atsiv.php

Git

[Sharp]

@Git and Klopschik

What is the right approach then ?

Sharps

[cadbob]

Has anyone tried this?


http://www.osronline.com/article.cfm?article=504[/url]

[Git]

MS stopped the trick with their own BCDEDIT, or at least made it show it was in test mode. Do you think this will work?. I only have XP x64 setup at the moment so I can't test it. BTW, OSR are highly competent in the device driver world, and have even contributed toward the WDK/DDK and some of the operating system drivers, and their web site is a mine of information.

@sharp - I don't have vista 64 or Win7 64 installed at the moment so I can't make any recomendations, sorry. I guess use "BCDEDIT -set testsigning on" and one of the hacks to get rid of the Test Mode logos if they bother you, but to be honest I don't know if it still works and can't test it. One thing that comes to mind is that kernel mode drivers only need to be signed if they start at system boot time. Has anybody tried making the driver Demand or Manual start, and then starting it after boot?. Does it still ask for certificate or does it just run?. You would have to change the INF file before installing so it isn't boot start. Open MultiKey.inf in a text editor and find these lines :

;StartType = 3 ; SERVICE_DEMAND_START
StartType = 2 ; SERVICE_AUTO_START

change to

StartType = 3 ; SERVICE_DEMAND_START
;StartType = 2 ; SERVICE_AUTO_START

Then re-install. You may have to clean the Inf cache before installing.

Git

[cdraj99]

Hello Git and Sharp

Thanks very much for the help. Following your tips, I successfully emulated Hasp HL in x64 bit Win 7 Enterprise.. :) But about Sentinel Super Pro, I could emulate, but my software identifies it as wrong dongle.. :rolleyes: Any idea what went might have went wrong.:confused:

Thanks

[Git]

Sorry, I'm not psychic.

Git

[cadbob]

StartType = 3 ; SERVICE_DEMAND_START
;StartType = 2 ; SERVICE_AUTO_START


Driver installed but would not start using Vista 64 :(

Havent tested with bcedit yet

[gus]

search soft ATSIV 1.01 and test

i find but no test

[cadbob]

Hello Git and Sharp

Thanks very much for the help. Following your tips, I successfully emulated Hasp HL in x64 bit Win 7 Enterprise.. :) But about Sentinel Super Pro, I could emulate, but my software identifies it as wrong dongle.. :rolleyes: Any idea what went might have went wrong.:confused:

Thanks


I have tried everything in forum, Plus more! What did you do to get Multikey running on 64 bit box??

Thanks in advance!

[mctheRE]

Got it up and running yesterday,Multikey/redidriver/i even before install set the bcedit stuff.

[cadbob]

I have been trying easybcd. It no work!
Then tried Vistaboot Pro. It no work!
Even tried gpedit and turned off driver signing!

Guess my only option is driver ready. :(

[mctheRE]

Why are you against ready driver.....the boot sequence?

[cadbob]

Why are you against ready driver.....the boot sequence?

Yes, kind of. I was just looking for a cleaner way to do it. I liked the idea of shutting off Driver Verification inside the operating system as opposed to the boot method.

[mctheRE]

I agree.I was hoping the bcedit would have worked by itself.

[cadbob]

Bcedit would work but you have to remove some updates and I really don't want to do that. I also want to go with Windows 7 I'm sure that those updates are now built into that operating system. I wish some of the smart guys out there would find a clean work around, I mean if they can generate CDKeys and Activation codes for the operating System they can remove the Signing Verifications as well. Just keep hope'in and fingers crossed :)

[mctheRE]

I had it cranked up on win7 yesterday.No roll backs for that.

[jazzy.nl]

Iam working with windows seven x64 , i can not get it to work too. When i install the multikey it shows up in my device manager, but with an exclamation.

I created an .reg file, but when i load in in the registry, the dongle doesnt show up at the usb devices.

The ready driver tool doesn't work, i can not start up windows seven, so i had to change the startup sequence.

[Git]

Well, people develop device drivers, how do you think they manage if they haven't got a signing certificate?

Git

[cadbob]

[Moderator note : please don't quote full posts, it is completely unnecessary.]

Driver Ready will not start because i believe you probally have Windows 7 Activated with a Loader. Someone correct me if i'm wrong but I do believe that the Activation Loaders corrupt the Driver Ready installs.

[jazzy.nl]

[Moderator note : please don't quote full posts, it is completely unnecessary.]

I think youre right..

[chanvaidan]

I have install success but it software don't work. Software warnning don't write keylock to register. I need option Sentinel SuperPro Dump write to register.

[crockysam]

any updates on installing the unsigned drivers on windows 7?

I have them now installed on my windows 7, Home Premium, built 7600, using the following method:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON as stated here: http://www.killertechtips.com/2009/05/05/disable-driver-signing-windows-7/

And to remove the test-watermark I followed this:
http://deepxw.blogspot.com/2008/12/remove-watermark-v03-build-20081210.html

But I'm wondering how long this will last as I read that a service pack of Vista removed the bcdedit.exe function.

[gnerogeem]

Refer to this thread.
http://www.reteam.org/boar/showthread.php?t=2050& (http://www.reteam.org/boar/showthread.php?t=2050&highlight=multikey+x64+windows+7)
highlight=multikey+x64+windows+7 (http://www.reteam.org/boar/showthread.php?t=2050&highlight=multikey+x64+windows+7)Then download this installer.
http://www.ngohq.com/home.php?page=Files&go=cat&dwn_cat_id=34It's not hard if you know how to use the search function.
Been using this method for a year now. As for the watermark removal, just google it.

[crockysam]

I know, It all works... I was only asking if there had been any updates on installing an emulator that doesn't require turning on testsigning in Windows 7.

[gnerogeem]

installing an emulator that doesn't require turning on testsigning in Windows 7.Yes there is, by buying a signing certificate.

[plan.cao]

Hi guys, I just tried to follow the steps mentionned by sharp and Git at the beginning of this toppic and it worked on vista
-In fact, I tried hard to get a certificate but it doesn't worked
but it worked with setupreadydriverplus

many thanks to you -> this is a real deliverance :)
Thank you so much

[gus]

Please use SEARCH

http://www.reteam.org/board/showthread.php?t=2050

i use this steps today , and all ok

[mctheRE]

Make sure you use the 64 bit multikey.....version along the line of 18.02 or 3 i believe it is.Follow the steps layed out and it works

[plan.cao]

In fact, I've already tried this method on my laptop which is on vista and it doesn't work,
devcon is trying to install it, but it finally fail
don't be angry Gus I'm not lazy, I promess I've read a lot in this forum.

-I first tried to sign the *.sys myself with the certificate
-then I saw this gorgeous freeeware but it didn't work on my laptop
-then I tried readydriverplus.

I tried it on my other computer which is also on vista and it works perfectly.

both of them are vista 64bits OS
the problem is that I don't really need it on my fix computer
I need it on my laptop ...

Anyway, the good thing is that now, I know that something is turning wrong on my laptop, maybe it is because of all the manipulation I've done on it...

I'm going to repair the system and try an other time. I can only think about this solution, because readydriverplus.exe is not so good, I don't like this way of driver installation.

I'll took you aware about it

Many thanks for replies

[Git]

Are you sure you have the correct version of devcon.exe ?. The multikey archive was incorrectly distributed with the 32bit devcon in the 64bit emulator folder. I uploaded the correct one here, you will find it with search, or you can grab the latest DDK from MS>

Git

[plan.cao]

In fact the problem is that the system is unable to load the *.inf file
problem code 39 : http://barugon.wordpress.com/2008/08/01/windows-cannot-load-the-device-driver-for-this-hardware-the-driver-may-be-corrupted-or-missing-code-39/

-By the way, I mistaked, my fix computer is effectively working on a 32bits OS
-I tried all the devcon.exe on my laptop so it's because of the error code 39.

I'll try this solution and I'll keep you aware
thanks guys

[Klopschik]

"error code: Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)."

Do you have changed *.sys file and not correct the checksum?

[Git]

Uninstall MK, delete MK inf and MK PNF files, delete INFCACHE.1. Delete MK registry entries. Reboot and reinstall MK from archive.

Git

[plan.cao]

done !
it works :p
many thanks guys

just a question :
my dongle is a old flora asic with limited license (there is no time limitation)
I didn't look verry much in this forom to solve the problem because it was not my priority
anyway I've seen some posts which talk about try to modify randomly the reg file and then try to up the restriction by remove and reinstall MK ...

-> I've also seen some posts about time hasp to up the time limitation but I don't think this is for me,

can you say me which way I have to follow

Many thanks

[1933]

Hello Guys,

need help. I generated successfully the reg file from my dongle and installed sentinelporusb and multikey on two pc clients with windows 7 x64. Works great. But on one client, Windows 7 x64 every time i got devcon failed and it don´t install the devices. On this PC is an AMD CPU. Could that be the Problem? I use Multikey 18.0.3 from this Forum.

Thank´s for help

[kjms]

use this devcon 64bit (http://www.reteam.org/board/attachment.php?attachmentid=170&d=1250870518)
After,
zip file rename to devcon.exe note here (http://www.reteam.org/board/showpost.php?p=15394&postcount=10)

[1933]

Thanks kjms, but when i try to open the zip windows says, file is unknown or corrupt. know why?

[1933]

sorry, haven´t seen the message over it. have replaced old devcon with this one. same error. no device were removed.
CPU is AMD Llano A8-3870 4x3GHz

At my Intel PCs with Win7 x64 Prof it works well.. :/

[nedgraphics]

sharp

you have given a right way to solve this problem.I have also tried many solutions to fix this but nothing miracle was happend.
right emulator,right register data.many right matrial.
brrowed the thread over and over. At last I finanly found we own one same verson of named "devcon" you download here 6.0.6001.18000 (longhorn_rtm.080118-1840) it's for vista not for win764 that's why we try and try have a same relusts.

thanks for your experience.
:)