Discussion in 'Windows 7' started by secr9tos, Nov 24, 2009.
You need to login to view this posts content.
Interesting. Thank you. I will look at this when I get home. I am always interested in learning more......
Btw.. if anybody has ideas to improve my code or if I made a mistake in it don't be afraid to post it.
I think we should ask M$ to have an "official" WHQL for this kind of drivers... and maybe have them through WU.
anyone got a link on how to do the post install config of wddk, the inc and
lib directories are not found by cl.exe
So, is this how the Paradox royal.sys driver was created?
Yes I assume so, but now I'm working on a new version of my driver ( just for fun ) to fix some little bugs and make it more "intelligent"
i looked at this and i thought it was good could you do a port to the 32bit machines?
Sure, but for now I concentrate on the x64 version 'cause I use a 64bit version of Win7. After that I'll try to convert it to x86. But hey, everyone can try to port the source code and post the result here.
id try it but im only good with C# and VB.NET
Well I think only the ram addresses will cause trouble but hey the windows nt kernel api is very well documented at msdn
interesting.... come on share the knowledge..
how to install/use it?
Is there any Way To sign Unsigned Drivers in 32-Bit System....
Bcoz My Modem Driver Is Un-signed,So it Creates Many Problems.........
Well you have likely three options.
1. Use atsiv.exe
2. rename the driver to ex. beep.sys copy it to System32\drivers and press F8 on startup ( don't forget to backup the orginal file )
3. create and .inf which installs the driver on your system
Oh and this beta version searches for a slic.bin file on C:\
But I've to say that I strongly recommend to use it an any VMware and not on your real pc.
As far as I know x86 does not require driver signing
Uploaded a new version I mention it just in case if someone is interested in
1) what is the driver?
I have two files:
sd64.c and sd64.h.
2) can you create .inf file for me?
3) why not make a simple program (exe file) with UI that install/uninstall the driver.
4) you can also make randomization of the driver (so it install the driver
in a different name/size for each user.
also you can make encryption of the slic.
so microsoft will not blacklist it.
I think the best advantage of using this is that it's 100% software solution without longer boot time (like loaders).
the disadvantage is that microsoft can blacklist it easily.
5) what about x86 support?
1. sd64 is the old version but well..
non of them is the driver .c & .h is the source code of the driver itself
you need the compile it with WinDDK 7600 ( slic64.7z contains a compiled version + makefile )
2. yes you can see msdn for a sample
3. good idea but the driver is not intended to be used as a "replacement" for loaders/bios mods. so maybe in the future or if someone else wants to make it
4. yes it possible but as I said, it just proof-of-concept
5. I'll add x86 support as soon as x64 version is 99.9% finished ( very close )
If there are any other question feel free to ask