Hardware & Devices

Jochen Arndt10-Jul-12 23:20

Jochen Arndt

10-Jul-12 23:20

Starting with Vista, drivers must be signed. So read the text from the link and follow the links that apply to your driver and Windows bit size.

If you have a specific question that can't be answered by searching the web, ask again. I have not much experience with driver signing. But others here may help you.

Brandon-X1200010-Jul-12 23:47

10-Jul-12 23:47

Thanks

Simple Thanks and Regards,
Brandon T. H.

Programming in C and C++ now, now developing applications, services and drivers (and maybe some kernel modules...psst kernel-mode drivers...psst).

Many of life's failures are people who did not realize how close they were to success when they gave up. - Thomas Edison

WebMaster11-Jul-12 0:10

WebMaster

11-Jul-12 0:10

You can turn off driver signing checking, or if you are in debug mode on the target it is disabled anyway. Have a google for how to do this.

Brandon-X1200011-Jul-12 0:55

11-Jul-12 0:55

Thanks, I'll give it a try.

Brandon-X1200022-Jul-12 20:02

Driver questions [solved]

22-Jul-12 20:02

Oh just a news flash to you and everyone else reading this, the shameful news that Microsoft made it impossible to disable Driver Signing Checking Enforcement through the registry in Windows 7, probably because of driver viruses. Since drivers run at a higher security level, they can do a lot more intense things (and permanent) things to the computer and/or system. Just throwing out a guess here.

The only ways to disable Driver Signing Checking Enforcement in Windows 7 is by doing this:

1. Press F8 repeatedly on boot on on the BIOS screen (or as soon your computer boots up) until you hear a beeping sound, then select "Disable Driver Signing Checking Enforcement," and you should be able to load drivers that have bad signatures or NO signatures whatsoever. Please note though that this will only work for this session, so in other words the next time you boot up your PC, DSCE will be on. Quite a pain you have to do this every time by hand.

2. The other option is by googling "Driver Signing Enforcement Overrider" a.k.a. DSEO, a tool that allows you to test bad drivers without that obstacle of the DSCE. (here I've done it for you'll non-googlers out there, just click the link how easy is that Smile | :)

, now don't complain about the searching part)

modified 23-Jul-12 2:16am.

Brandon-X1200010-Jul-12 9:17

10-Jul-12 9:17

Hello all,

OK, I have a few simple questions with you'll that expertise with driver development out there...

(1.) What's a binary driver?

(2.) Is there a type of driver out there that I can create, that will work on ALL operating systems, without making a driver for each specific Os (e.g., Windows Vista, 7, Xp, 2000, 98; Apple Macintosh; Linux)?

(3.) Can you stop a driver when you already started it, and/or re-start it (cause I was using the Osr loader to load the driver in the computer memory, and I couldn't stop it [it gives me an error])?

modified 10-Jul-12 15:45pm.

Richard MacCutchan10-Jul-12 9:31

Richard MacCutchan

10-Jul-12 9:31

I already answered these questions here[^]. I meant you to post your supplementary here about the actual problem with trying to run your driver.

speaking as ...

Brandon-X1200010-Jul-12 9:34

10-Jul-12 9:34

Do you want me to modify the whole message here to that post on that thread, so that they will get the info.

Richard MacCutchan10-Jul-12 9:40

Richard MacCutchan

10-Jul-12 9:40

Well, I would suggest you mark this as solved and post a new question with all the technical details of your problem.

speaking as ...

Brandon-X1200010-Jul-12 9:45

Are Hardware Specs Irrelevant? (software for Windows)

10-Jul-12 9:45

kmoorevs28-Jun-12 4:39

kmoorevs

28-Jun-12 4:39

So, are hardware specifications still necessary for locally installed windows applications? Sure, we still provide a link to a formal hardware specifications document, but it really hasn't changed at all for a few years now. Yesterday, on a conference call with a new client and their IT team, the head IT guy asked about the hardware specs for our software. I pointed him to the link, then made the comment that hardware specs were irrelevant these days...you would have thought I had insulted the guy!

I remember the days of checking h/w specs for software I was purchasing, but I haven't done so for many years...but then again, I guess it depends on what type of software you want to run. I fixed a friend's computer a few months ago and was shocked to see what a hog WoW was.

"Go forth into the source" - Neal Morse

Re: Are Hardware Specs Irrelevant? (software for Windows)

Luc Pattyn28-Jun-12 5:04

Luc Pattyn

28-Jun-12 5:04

Your app may require a minimum screen size below which it becomes almost useless.
Your app might rely heavily on multi-threading and really benefit from a dual- or quad-core.
Your app might rely on special hardware or interfaces; e.g. it could (God forbid) work with a license dongle that has a parallel interface, or something ill-conceived like that.

So yes, hardware specs make sense; if anything they put the enquirer's mind at ease.

Smile | :)

Luc Pattyn [My Articles] Nil Volentibus Arduum

Re: Are Hardware Specs Irrelevant? (software for Windows)

lewax0028-Jun-12 8:31

lewax00

28-Jun-12 8:31

They're still relevant for graphics intensive applications (e.g. video games). Those are applications. But for most applications probably not (beyond what Luc mentioned anyways).

How to start learning Assembly?

atoi_powered20-Jun-12 11:18

20-Jun-12 11:18

Hi, I worked a little with C#, C and C++. I've googled a lot but I got different ideas and suggestions on my topic. What do you suggest to start from to learn Assembly? And what is/are the good ebook(s) to begin with? I should add I'm exclusively looking for the ebooks.
Thanks Smile | :)

SoMad20-Jun-12 12:28

SoMad

20-Jun-12 12:28

What kind of hardware platform are you planning on targeting?

Soren Madsen

atoi_powered21-Jun-12 0:00

21-Jun-12 0:00

It's an Intel Sandy Bridge x64 PC.

fat_boy21-Jun-12 3:51

fat_boy

21-Jun-12 3:51

Interesting register usage on the 64. The first 4 params are passed through registers and not the stack.

Dave Kreskowiak21-Jun-12 1:26

Dave Kreskowiak

21-Jun-12 1:26

You can start by going through this[^].

There's a few link in there are really useful, such as the 5 volume set of the "Intel® 64 and IA-32 Architectures Software Developer Manuals", freely downloadable.

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

atoi_powered21-Jun-12 1:40

21-Jun-12 1:40

I liked the info inside, thanks a lot Smile | :)

Dave Kreskowiak21-Jun-12 3:37

Dave Kreskowiak

21-Jun-12 3:37

Congratulations on leaping into the world of extreme tedium, otherwise known as Assemly Language!

A guide to posting questions on CodeProject[^]

Dave Kreskowiak

atoi_powered21-Jun-12 12:10

21-Jun-12 12:10

What a world I desireably got stuck with Big Grin | :-D

Thanks man Smile | :)

fat_boy21-Jun-12 5:38

fat_boy

21-Jun-12 5:38

Online books will help, but what you really need is a primer a compiler and to start writing code.

The only way is to really get stuck in and using it. Gotta say, I can follow assembler pretty well, but I never write in it, I just have to debug into it quite often. But its a pig. It takes minutes of concentration just to follow variables through the stack and into a func.

Why anyone would really want to learn it and program in it is odd these days. C/C++ gives you all the power and none of the hassle of assembly.

atoi_powered21-Jun-12 12:30

21-Jun-12 12:30

You're right but I'm one of the guys who have their own reasons(even unusual-to-the-public one) to get their hands dirty with asm! The world is full of these kinds of reason Sniff | :^)

Roger Wright21-Jun-12 12:45

Roger Wright

21-Jun-12 12:45

Good for you! I learned Assembly programming hands on, reading the Intel documentation (4004) and breadboarding the CPU with a few registers and DIP switches. Moving up to the MITS Altair8800, I used what I learned to write an OS for it, then an assembler to save having to enter binary opcodes with toggle switches. It's a great way to really understand how the software and hardware interact and depend on each other, but I don't recommend it as an efficient way to write apps. Smile | :)

Of course, if you're writing real-time control code for small MCUs with tiny memories, nothing is better - not even C. It's fun, educational, and sometimes useful to program at this level, but it's never easy. Enjoy! Big Grin | :-D

Will Rogers never met me.

atoi_powered21-Jun-12 20:08