Follow Slashdot stories on Twitter


Forgot your password?
Slashdot Deals: Deal of the Day - 6 month subscription of Pandora One at 46% off. ×

Comment Re:Hardware or driver's issues? (Score 1) 289

Option #2 does exist--it's called a subvendor ID and is part of the baseline spec for PCI (ie it's not an optional extension). To prevent the generic driver Samsung would need to provide a driver that matches the PCI device and subvendor IDs and Windows will opt to use this driver over the generic OS driver since it's a closer match for the device's IDs. Windows doesn't have a good model for blacklisting device IDs for use with generic drivers--the cases I can think of is where MSFT was aware of broken hardware prior to an OS release (and either blacklists in the inf file or puts a workaround in the generic driver).

With USB&USB2 the drivers were shipped earlier (in terms of common availability of driver vs hardware) compared to USB3 so right or wrong the hardware was designed/implemented to work with the Windows OS driver. MSFT was much more tardy on USB3 so vendors had to create & ship their own drivers and later could play with MSFT's driver. Having said that MSFT's driver has been out for awhile now so I don't know what is Samsung's excuse if this is newish hardware (rather than a new discovery of a hack being used on older hardware).

Comment Re:Heh (Score 2) 134

On Windows using MSFT's compilers you'll never get the same binary twice. There's timestamps and GUIDs (the latter for uniquely associating a pdb with an executable file). Different file paths to the source tree can also cause differences. Sometimes it's straightforward to pick out & ignore the GUID, timestamp, and checksum bytes that changed, but often not.

Comment So much feedback and yet Microsoft ignores it all (Score 1, Insightful) 112

The amount of feedback isn't surprising, but I would be surprised if anyone in the Redmond bubble ever made any changes (even slight) in response to any of that feedback. By the time they have a public release they're too far along in their big-company release process to accomodate changes.

Submission + - Several new OpenSSL vulnerabilities announced

revmoo writes: According to this security advisory, several new vulnerabilities have been discovered in OpenSSL across several versions. Hopefully admins have caught up on their sleep after the Heartbleed vulnerability.

Comment Re:Only "discovered" someone's discover, nothing m (Score 1) 357

I certainly agree that a redesign isn't a smoking gun. This does have the potential to also work against the public's best interest. E.g., an engineer could propose a change to improve reliability of a part or that might potentially increase safety. Management then refuses the change because someone else might later "discover" the change and use it in litigation against the company as "proof" that it was a known defect.

Comment Windows 8 support ends in 2 years (Score 2) 470

MSFT must agree Win 8 is shit, which is why its support is ending in just 2 years in January 2016. The preinstall aspect must explain why its market share grew despite the pending doom.

This is being handled differently than Vista SP1, which was really a disguised upgrade of Vista to Server 2008's codebase but it didn't involve an actual heavyweight OS upgrade & software reinstall (which seems to be the case for going from Win 8 to 8.1).

Comment RSA is poor quality, as VMware learned (Score 2) 128

There's the proverb about not attributing to maliciousness that which can be explained by stupidity.

VMware (also an EMC subsidiary) used an RSA implementation for their SSO product. It had a ton of problems and bugs, and each new patch release introduced more bugs. Applying pressure to RSA via EMC didn't help, so VMware ripped out the RSA implementation with a band new in-house implementation.

Comment Re:not surprising (Score 2, Informative) 280

There's a big difference between Windows where problems are a corner case, vs. Linux where success is a corner case. But the point still remains that I've used sleep and hibernate on most of my Windows machines without really fearing problems or data loss (I'll still save any progress before initiating it, though thanks to Office 97 I'm in the habit of saving regularly regardless), but I can't think of even bothering to try such a thing on Linux (nor can even of the people I know who love Linux enough to actually enjoy updating to a new distro every few months/years). I probably won't even think of trying to use sleep or hibernate on a Linux box until I see that the Linux kernel has developed drivers models that have some hint of being designed with power management in mind. Heck even the PCI driver model in Linux doesn't fit the spec well. Most Linux drivers I've had to deal with need to mess with the device's PCI configuration space themselves, whereas on Windows that's pretty rare because it's usually handled by the core kernel (which was the intent of the PCI spec based on how it's written).

Use the Force, Luke.