3 ms·

Problem is, it doesn't work right: http://support.microsoft.com/kb/262265 http://support.microsoft.com/kb/262265

by quoderat 17y ago

deleted 17y ago
[deleted]
- deleted 17y ago
  [deleted]
jodrellblank 17y ago
And if I picked a Linux distro from 8 years ago I'd find some bugs in it too. Use the current version of Windows, it has fewer bugs.
- quoderat 17y ago
  Sorry, I have to use what the company provides, not what I wish the company provided. That's the real world.
  - jodrellblank 17y ago
    By that logic, if your company provided Windows 3.1 you would go around saying Windows has no multiuser support. Windows has an interface for doing what you asked. It had a bug / didn't work as described so they fixed it. Your company wont buy the fix, but that doesn't mean the fix doesn't exist. It means you can't take advantage of it, sure. But saying Windows doesn't support it is deliberately misrepresenting Windows to make it look bad. It's spreading FUD, and it's wrong. Plus, why did you bring WMI into this? You can't seem to do it with WMI: http://msdn.microsoft.com/en-us/library/aa394595(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa394595(VS.85).aspx "If you are not using DHCP, you cannot use WMI to disable a network connection". Were you just bringing WMI into it because it sounds scary and complicated and so would help shore up your FUD, or is there a way and this MSDN article is wrong? (But you can do it by scripting the shell: http://mcpmag.com/columns/article.asp?EditorialsID=619 http://mcpmag.com/columns/article.asp?EditorialsID=619 or by using Devcon to disable a hardware device from the command line: http://support.microsoft.com/kb/311272/en-us http://support.microsoft.com/kb/311272/en-us )
    - deleted 17y ago
      [deleted]
    - quoderat 17y ago
      It's not FUD, and it's not wrong. It took me hours of research to do a simple down/up in Windows -- something that took me 30 seconds of research in Linux. And you yourself illustrate all the odd and very long things you have to do in Windows to do a simple down/up of the NIC, and to get it to work correctly. While in Linux, I can just do "sudo ifdown eth0" All in all, I prefer the 30 second way, versus the five hour way. By your very use of evidence, you proved my point. Cool. But didn't know about DevCon. Thanks.
      - jodrellblank 17y ago
        You're still claiming that it took you hours of research to do in windows without acknowledging that you're using an ancient version and that it is a one line command in current versions. I could counter that in the scope of all possible operating systems there's no reason disabling a network adapter should be a simple thing and that you're picking on it because you considered it an easy thing in Linux' favour. I could counter how much better it is to type "tracert" on windows than "traceroute" on linux, or that windows PPTP setup wizard blows Linux out of the water, or that there are uncountable things I've spent hours reaearching on bob platforms because they aren't as simple as I want them to be. Or I could say "yoruban wax potato parachute"; I suspect any of the preceeding would result in further argument about how I'm proving your point. I set out to counter your claim that x is too difficult in windows, but this further back and forth - it's not going anywhere, is it?
    - oomkiller 17y ago
      You just said something monumental "Your company wont buy the fix, but that doesn't mean the fix doesn't exist. It means you can't take advantage of it, sure." Thats one of the biggest things that Linux has going for it, if something breaks, YOU DON'T HAVE TO BUY THE FIX! You can A. Fix it yourself; B. Get the latest source which probably has the fix (if it's a problem anyone else is having); or C. Filing a bug report and have the community fix it usually within a day, or even hours or minutes for really simple fixes. Sure, Linux isn't for everyone, but for corporations and small businesses looking to save money, it looks better every day!
- mace 17y ago
  >And if I picked a Linux distro from 8 years ago I'd find some bugs in it too. Use the current version of Windows, it has fewer bugs. Perhaps that last bit should read "Use the current version of Windows, it has fewer known bugs." As software gets larger and more complex the tendency is for more bugs to be introduced. Open Source mitigates this problem by allowing everyone to inspect and fix it.

Problem is, it doesn't work right: http://support.microsoft.com/kb/262265 http://support.microsoft.com/kb/262265

deleted 17y ago

[deleted]

deleted 17y ago
[deleted]

jodrellblank 17y ago

And if I picked a Linux distro from 8 years ago I'd find some bugs in it too. Use the current version of Windows, it has fewer bugs.

quoderat 17y ago
Sorry, I have to use what the company provides, not what I wish the company provided. That's the real world.
- jodrellblank 17y ago
  By that logic, if your company provided Windows 3.1 you would go around saying Windows has no multiuser support. Windows has an interface for doing what you asked. It had a bug / didn't work as described so they fixed it. Your company wont buy the fix, but that doesn't mean the fix doesn't exist. It means you can't take advantage of it, sure. But saying Windows doesn't support it is deliberately misrepresenting Windows to make it look bad. It's spreading FUD, and it's wrong. Plus, why did you bring WMI into this? You can't seem to do it with WMI: http://msdn.microsoft.com/en-us/library/aa394595(VS.85).aspx http://msdn.microsoft.com/en-us/library/aa394595(VS.85).aspx "If you are not using DHCP, you cannot use WMI to disable a network connection". Were you just bringing WMI into it because it sounds scary and complicated and so would help shore up your FUD, or is there a way and this MSDN article is wrong? (But you can do it by scripting the shell: http://mcpmag.com/columns/article.asp?EditorialsID=619 http://mcpmag.com/columns/article.asp?EditorialsID=619 or by using Devcon to disable a hardware device from the command line: http://support.microsoft.com/kb/311272/en-us http://support.microsoft.com/kb/311272/en-us )
  - deleted 17y ago
    [deleted]
  - quoderat 17y ago
    It's not FUD, and it's not wrong. It took me hours of research to do a simple down/up in Windows -- something that took me 30 seconds of research in Linux. And you yourself illustrate all the odd and very long things you have to do in Windows to do a simple down/up of the NIC, and to get it to work correctly. While in Linux, I can just do "sudo ifdown eth0" All in all, I prefer the 30 second way, versus the five hour way. By your very use of evidence, you proved my point. Cool. But didn't know about DevCon. Thanks.
    - jodrellblank 17y ago
      You're still claiming that it took you hours of research to do in windows without acknowledging that you're using an ancient version and that it is a one line command in current versions. I could counter that in the scope of all possible operating systems there's no reason disabling a network adapter should be a simple thing and that you're picking on it because you considered it an easy thing in Linux' favour. I could counter how much better it is to type "tracert" on windows than "traceroute" on linux, or that windows PPTP setup wizard blows Linux out of the water, or that there are uncountable things I've spent hours reaearching on bob platforms because they aren't as simple as I want them to be. Or I could say "yoruban wax potato parachute"; I suspect any of the preceeding would result in further argument about how I'm proving your point. I set out to counter your claim that x is too difficult in windows, but this further back and forth - it's not going anywhere, is it?
  - oomkiller 17y ago
    You just said something monumental "Your company wont buy the fix, but that doesn't mean the fix doesn't exist. It means you can't take advantage of it, sure." Thats one of the biggest things that Linux has going for it, if something breaks, YOU DON'T HAVE TO BUY THE FIX! You can A. Fix it yourself; B. Get the latest source which probably has the fix (if it's a problem anyone else is having); or C. Filing a bug report and have the community fix it usually within a day, or even hours or minutes for really simple fixes. Sure, Linux isn't for everyone, but for corporations and small businesses looking to save money, it looks better every day!
mace 17y ago
>And if I picked a Linux distro from 8 years ago I'd find some bugs in it too. Use the current version of Windows, it has fewer bugs. Perhaps that last bit should read "Use the current version of Windows, it has fewer known bugs." As software gets larger and more complex the tendency is for more bugs to be introduced. Open Source mitigates this problem by allowing everyone to inspect and fix it.