|
That's what the subject read in an email I received from AliExpress.
I didn't know they frequented Code Project nor that they knew me that well.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Maybe a question for @Brisingr_Aerowing.
I have a FreeNAS box running at home that I have setup with NFS shares. I chose this over SMB as NFS is quicker and I access them from Linux and OpenELEC on a Raspberry Pi.
I have been accessing it with no issues from my Windows 7 boxes for sges and didn't run in to a problem till I put Windows 10 on the Missus's computer.
Seems that since I was running Windows 7 Enterprise from my old TechNet subscription I had access. From what I have read Microsoft are not going to give any Windows 10 version NFS access.
Can anyone point me to a 3rd Party NFS Client they have used or that will work. Google has helped mr find 1 that doesn't seemed to have been maintained for ages and I don't want to rebuild FreeNAS to use SMB.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible."
- Mr.Prakash One Fine Saturday. 24/04/2004
|
|
|
|
|
Networking is so totally inconvenient on Win 10 at home.
My choices are:
see my NAS in File Explorer and treat it like another drive, but not see the rest of the computers on the network
or
not see the NAS except via a web interface, but have access to shares on other systems.
It wouldn't be so bad, if I could switch back and forth without having to reboot.
|
|
|
|
|
I only have to use it for testing, I wouldn't go anywhere near it as a work station, but our msi, that installs drivers, doesnt work on win10.
The problem is the win10 pnp manager, it uses the system driver in preference to our driver. Naturally previous windows OSs work correctly.
Windows 10, piece of crap.
modified 17-Mar-16 3:56am.
|
|
|
|
|
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....  
|
|
|
|
|
No, previous windows versions all work correctly, it is windows 10 that is junk.
|
|
|
|
|
|
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
|
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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?
|
|
|
|
|
|
|
|
Help?
How the hell would you help when your only suggestion is 'its better like this'. 
|
|
|
|
|
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!
|
|
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
|
|
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....
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
