Vista compatibility

My x64 port of InpOut32
Post Reply
User avatar
phil
Site Admin
Posts: 5158
Joined: Sun Apr 06, 2003 11:12 pm

Vista compatibility

Post by phil » Wed Feb 14, 2007 12:23 am

OK, I have uploaded v1.0.0.8 to my website.

This is NOT a 64bit update, it is an update that includes an InstallDriver.EXE file which simply runs with elevated privileges to allow the driver to be installed in Windows Vista 32bit.

If the driver was not installed (fresh install) then you need administrator privileges to install it because the installation involves writing to the System32\\Drivers folder.

This would have been (and probably still is) a problem in earlier OS's also if you do not have administrator access.


Note:
InpOut32(x64) does NOT have a signed driver and as such, it will NOT work with Vista 64bit.

Unfortunately neither I or Logix4u have the ability to sign the driver because you need a specific VeriSign certificate that a) I don't think I can get as an individual and b) I cant afford anyway!

Maybe someone can find a work around to signed drivers in 64bit vista - I sure hope so - its the only thing stopping me running in 64bit :(

Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, Intel i5-6600k, Asus 170-A, 16GB DDR4,
nVidia GeForce GTX 970, 2xEvo 850 (RAID 0), 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 5158
Joined: Sun Apr 06, 2003 11:12 pm

Post by phil » Wed Aug 01, 2007 12:38 am

Well, contrary to all that, I managed to install and use InpOut32 on Vista x64.
Also, I managed to install other unsigned x64 drivers :)

I did this by following the procedure outlined by Chris123NT here:
http://chris123nt.com/2007/04/28/driver-signing-in-x64/

I've reproduced the steps here in case that link dies:
  • 1. Open an elevated command prompt
  • 2. Type “bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS” without the quotes (and no the DD is not a typo).
  • 3. Reboot and enjoy being able to use unsigned drivers in Vista x64.
[/color]
However, someone has just leaked some much anticipated Vista beta hot fixes onto the net. Be aware, that they stop this from working and once again, disable unsigned drivers in x64 event with the BCDEdit fix (above).

The [beta] updates that break the BCDEdit fix are: KB938979-x64 and KB938194_x64 (I'm not sure which one specifically).
Anyway, until MS release these hot fixes, (rumours suggest next patch Tuesday - but maybe not until SP1 - who knows) you can run my unsigned x64 port of InpOut32 in Vista :)

Phil.
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, Intel i5-6600k, Asus 170-A, 16GB DDR4,
nVidia GeForce GTX 970, 2xEvo 850 (RAID 0), 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 5158
Joined: Sun Apr 06, 2003 11:12 pm

Post by phil » Wed Aug 01, 2007 1:33 am

Wow, things moving swiftly along in unsigned x64 land.

No sooner than the MS beta hotfixes break unsigned driver usage, do Linchpin Labs relase a tool to load unsigned drivers into any version of windows, including Vista x64 - even with the latest hot fixes.

This new tool, Atsiv allows drivers to be loaded in unsigned Vista x64 without using the BCDEdit mod I mentioned above.

And it works. All you need to do, is type
atsiv -f hwinterfacex64.sys

Of course, this assumes you have atsiv.exe and hwinterfacex64.sys. Normally, hwinterfacex64.sys is installed to the \\windows\\System32\\Drivers folder when InstallDriver.exe is run (or when you call the InpOut32 DLL the first time).

Thanks for that linchpin - you just made lots of people very happy.

NOTE: I haven't tested this thoroughly yet, just that it will load the InpOut32x64 driver and allow it to be used in Vista x64. I don't know if this will have to be done every time you boot tp, of if it remembers the driver list (I hope so).

Phil.
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, Intel i5-6600k, Asus 170-A, 16GB DDR4,
nVidia GeForce GTX 970, 2xEvo 850 (RAID 0), 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 5158
Joined: Sun Apr 06, 2003 11:12 pm

Post by phil » Sun Aug 12, 2007 1:45 am

Grrr, it seems MS have revoked Atsiv's certificate (And symantec is treating it as malware too FFS!). Well that's monopolistic behaviour if ever I saw it.. Hey that company is doing something we don't agree with. Its not illegal but I think we should stop them anyway, because we have the power.

Oh well, I guess it is their OS.. And maybe its our fault for choosing to use it. Clearly MS don't want us as users. Maybe we should choose something else, that is less aggressive towards its users?! (I never thought I'd say that heh)...

As I don't actually have to use Inpout x64 on my vista box, its not a huge deal for me, but I am still pissed off about it... :(

So, I guess if you have the latest updates, you cant use the bcdedit fix AND now you cant use Atsiv.. so we are back to not working on Vista x64.

Sorry!
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, Intel i5-6600k, Asus 170-A, 16GB DDR4,
nVidia GeForce GTX 970, 2xEvo 850 (RAID 0), 2x2TB WD Black (RAID1)

User avatar
phil
Site Admin
Posts: 5158
Joined: Sun Apr 06, 2003 11:12 pm

Post by phil » Sun Aug 19, 2007 5:20 pm

OK, I've had some positive feedback for one Vista x64 user.
By disabling the driver signing requirement at boot time (by pressing F8 ), inpout32 (x64 version) will run on Vista and will work with programs like LCD Smartie.

So at least there is a way to get it working, even if it does involve manual intervention for EVERY boot :(.

I've been looking at how to sign the driver, and it looks like the cheapest certificate is $229 for one year. That is still too expensive for a package that is free - I guess I could setup a donation link, and if enough people were to donate, I could by a certificate and sign my x64 port of InpOut32. But I wont bother doing that unless there is enough interest.

Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]--
Logitech G9, Logitech MX518, Microsoft Intellimouse, Trust 16341 BT Mouse
Windows 10 x64, Intel i5-6600k, Asus 170-A, 16GB DDR4,
nVidia GeForce GTX 970, 2xEvo 850 (RAID 0), 2x2TB WD Black (RAID1)

dalangalma
New User
Posts: 1
Joined: Wed Jan 02, 2008 2:47 am

Post by dalangalma » Wed Jan 02, 2008 2:50 am

I'd toss in about $80, since that's the cost of the Phidget I'd have to buy to replace what I'm using inpout32 for...

Diek
New User
Posts: 1
Joined: Wed Jan 02, 2008 4:16 pm

Another Donation

Post by Diek » Wed Jan 02, 2008 4:39 pm

Hi,

Am also willing to donate for getting signed this driver for the amount of 80 dollar !

Let me know when you found enough people !

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest