Welcome to the Lounge

Super Lloyd16-Mar-16 3:51

Super Lloyd

16-Mar-16 3:51

Let me get that right:
a critical piece of software you use don't work with Windows 1.0 to 8.
but because of fracking something it doesn't work in Windows 10 either. Is that right?

Somehow I think Windows 10 is blameless in that.... Poke tongue | ;-P

All in one Menu-Ribbon Bar
DirectX for WinRT/C# since 2013!
Taking over the world since 1371!

Munchies_Matt16-Mar-16 21:56

16-Mar-16 21:56

No, previous windows versions all work correctly, it is windows 10 that is junk.

16-Mar-16 4:29

16-Mar-16 4:29

Message Removed

#realJSOP16-Mar-16 6:23

#realJSOP

16-Mar-16 6:23

He knows exactly where the junk is. When you install a driver, the OS should use the driver you installed, not something it thinks is a better fit.

".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013

16-Mar-16 6:34

16-Mar-16 6:34

Message Removed

Munchies_Matt16-Mar-16 22:00

16-Mar-16 22:00

You are an idiot and know nothing about it.

When the system has a MORCOSOFT SIGNED DRIVER (the one I wrote) on it specifically for that piece of hardware the OS should use that and not the generic one that shipped with the system.

N_tro_P wrote:
If you don't agree find a OS that follows those rules. I doubt you will find one though that was made in this century.

Windows 2000, windows XP, windows vista, windows 7 windows 2008 windows 2012 windows 8 windows 8.1

Oh look, you are an idiot who knows nothing.

17-Mar-16 3:17

17-Mar-16 3:17

Message Removed

Munchies_Matt17-Mar-16 3:36

17-Mar-16 3:36

Yes, my arrogance comes from 20 years of writing windows kernel drivers, its justified. Whereas you know nothing about the matter, as others have pointed out. Time to shut your mouth and open your ears and learn something.

17-Mar-16 3:42

17-Mar-16 3:42

Message Removed

Munchies_Matt17-Mar-16 4:16

17-Mar-16 4:16

N_tro_P wrote:

So let me get this straight. You really think writting a driver for Windows 3.1 should be the same as for Windows 10?

Windows 3.1 was the only windows OS out 20 years ago was it?

Shows how little you know doesn't it. Ever heard of NT?

17-Mar-16 4:25

17-Mar-16 4:25

Message Removed

Munchies_Matt17-Mar-16 4:35

17-Mar-16 4:35

N_tro_P wrote:
So because someone uses an obvious example for your fallacy it is the only example. Wow, you are beyond naive and arrogant. No wonder you are struggling.

= backpedal

N_tro_P wrote:
Yep. Quite hackable system too. I recall being able to crack into it for a while no tooling even. What was your point? Should we also talk about Win 2K and the difference between it and ME?

= diversionary crap

Thanks for confirming you know jack about the kernel.

If you didn't you would have used WDM or PnP as a difference between NT and win10 instead of 3.1

17-Mar-16 4:38

17-Mar-16 4:38

Message Removed

Munchies_Matt17-Mar-16 4:46

17-Mar-16 4:46

Help?

How the hell would you help when your only suggestion is 'its better like this'. Laugh | :laugh:

Mark_Wallace16-Mar-16 9:22

Mark_Wallace

16-Mar-16 9:22

N_tro_P wrote:
of THEIR OS

When it's installed on a machine that I own, it's not THEIR OS, any more, it's mine.

The function of the OS is to allow you to use hardware and software that you own -- and "software" includes drivers.

THEIR OS is not more important than my work or my property. I shall not be using or paying MS a penny for anything new they produce until they get that perspective back into their "OUR OS IS MORE IMPORTANT THAN YOU" arrogant heads.

They should start the machine, let me see where my apps and files are, then get out of my f****** way.

I wanna be a eunuchs developer! Pass me a bread knife!

Munchies_Matt16-Mar-16 21:58

16-Mar-16 21:58

N_tro_P wrote:
your unknown driver

Tested and SIGNED for Windows 10, WITH Microsofts tools.

N_tro_P wrote:
Me thinks you do not understand where the "junk" is....

Listen you *&(4 I have been writing kernel drivers for Windows since 1997. Let me tall YOU what the junk is, and its windows 10 pnp manager.

17-Mar-16 3:18

17-Mar-16 3:18

Message Removed

Munchies_Matt17-Mar-16 3:38

17-Mar-16 3:38

An insult that's well deserved isn't an insult, its an observation.

You know nothing about the subject at all. Its time you listened to those who do, and to keep your baseless opinions to yourself.

17-Mar-16 3:47

17-Mar-16 3:47

Message Removed

Munchies_Matt17-Mar-16 4:18

17-Mar-16 4:18

N_tro_P wrote:
Have you read my resume? Have we ever had an actual technical conversation?

You know jack about the kernel, clearly.

N_tro_P wrote:
highly doubt you are even qualified to start a computer

You need qualifications where you live do you?

Explains a lot....

17-Mar-16 4:29

17-Mar-16 4:29

Message Removed

Munchies_Matt17-Mar-16 4:37

17-Mar-16 4:37

N_tro_P wrote:
Can't even get your driver installed!!!!

And now you exhibit an ignorance of the problem. It installs perfectly, if you do a manual update, the OS however should use it in preference to the system one.

N_tro_P wrote:
There are also pompous asses such as yourself claiming to have built "good" windows drivers over the decades. Definitely does not mean they are qualified to do so in the modern systems

And again you wave your ignorance like a flag. The win10 kernel hasn't changed since win2k.

17-Mar-16 4:42

17-Mar-16 4:42

Message Removed

Munchies_Matt17-Mar-16 4:49