"The service name is invalid ............" - 64-bit Driver problem

[Typhoon]

"The service name is invalid ............" - 64-bit Driver problem

I'm trying to get a driver to work under 64-bit Windows 7 Pro but am not having any luck.

The driver is a modified version which will allow my EPROM programmer and software to access the Parallel port under 64-bit Windows (the default driver for the software only works under 32-bit Windows and works fine if I boot the same PC into 32-bit Windows 7).

The driver is called glpntdrv.sys (the guy who created this 64-bit version of the 32-bit driver says that it works on his 64-bit Win 7 installation).

I've copied this to c:\windows\system32

The above directory is in my default windows PATH (I've even tried copying it to c:\windows\system32\drivers (which is NOT in the PATH!) but that didn't of course work either)

The permissions appear to be okay (although it doesn't have a permission for trustedinstaller (does it need it?).

However, when I start up the software for the EPROM Programmer it errors saying that it's can't access the driver

If I go to the command prompt and type:

net start glpntdrv

I get the error:

"the service name is invalid"

I'ver tried rebooting and going to the menu via F8, to do this:

“Disable Driver Sign Enforcement” (which at the moment needs to be done according to the guy who revised the driver for 64-bit)

but still no luck. For some reason the driver is acting as if it's invisible.


Any ideas please anyone? This is driving me nuts.

Thanks

 

[ComputerGeek]

As I understand things, simply copying the .sys (and allow-ing unsigned drivers) is not enough to actually install a driver.

Could you point me to where you got this information on steps to modify the driver? I'd like to see what they say to do

/* EDIT */
Big and important Ooops! Just noticed I left out the word NOT in "is not enough to actually install a driver". Corrected

 

[Typhoon]

Thanks for the reply.

The modified driver can be found here:

Galep 4 und Windows 7 / 64 Bit ?? - International Device Programmers Forum

(scroll down to the last message for the .zip file link).

The guy who modified it has since got hold of a loan EPROM programmer and verified that it does work (on his system at least).

So now I'm wondering how to properly install it.


Here's his instructions for how to install the new driver (which don't work for me):

The missing 64-bit compilation of glpntdrv.sys driver is the
one-and-only reason why galep32.exe won't run on 64 bit editions of Windows.
This is a running, unsigned beta release of
64-bit glpntdrv.sys, with this installation instructions:

- Install galep32 as usual (with administrative privileges) and start once.

- Copy glpntdrv.sys to C:\windows\system32\drivers,
using the 64-bit version of Windows explorer, with administrative privileges.
(The 32-bit driver file should be at C:\windows\syswow64\drivers,
this file is useless in a 64-bit Windows and can be deleted safely.)

- Windows Vista,7: Reboot system, press F8 on startup, choose
“Disable Driver Sign Enforcement”.
This step must be done on every startup and reboot!

- Windows 8: Control Panel, Enhanced boot options, choose
“Disable Driver Sign Enforcement”, reboot.
This is complicated, see How to Disable Driver Signature Enforcement in Windows 8 - YouTube

- Check for working driver using console window (cmd.exe), enter
“net start glpntdrv”. This should emit no error message,
or possibly „Service already started“.

- Start galep32.exe, it works now.

 

[ComputerGeek]

1) Do you see your device listed in Device Manager? If yes, what category does it fall under?
> If there, right click the device->Properties->Details tab. Use pull down menu to select Hardware IDs. Copy/paste the result into your next post

2. Download/run 64 bit version of DevManView. Click Ctl-A to select all items, Ctl-S to save, before saving the file be sure to change the file Save As pull down menu to Tab Delimited Text (.txt). Save the file upload to your next post

 

[Typhoon]

Thanks, all sorted now - after a LOT of work I've managed to personally "test sign" the driver which works fine if Win 7 is set to run in test mode.