Datel suing Microsoft over Max Memory card lockout


Recommended Posts

3rdpartymu580pxheaderimg.jpg

Datel announced that it has filed an antitrust lawsuit against Microsoft, in response to Microsoft's lockout (via Xbox 360 firmware update) of the company's Max Memory Cards. We doubt this is the "remedy" for the lockout issue to which the company previously referred, but it's certainly one way to address it.

"Microsoft has taken steps to render inoperable the competing Datel memory card for no visible purpose other than to have that market entirely to themselves," Datel attorney Marty Glick explained in a press release. "They accomplished their recent update by making a system change that will not recognize or allow operation of a memory card with greater capacity than their own. We believe that with the power Microsoft enjoys in the market for Xbox accessories this conduct is unlawful."

In the press release, Datel goes on to say that the lawsuit is intended to "restore competition" which, the company suggests, is beneficial to consumers. It's now up to a federal court in San Francisco to determine whether the Max Memory-crippling Xbox update constitutes unlawful anti-competitive behavior on the part of Microsoft.

The last time Datel went to court, it viewed the experience from the other side. Sony filed suit against the peripheral maker over the "Lite Blue Tool," which would have enabled users to run unsigned code on PSP hardware.

Source: http://www.joystiq.com/2009/11/23/datel-su...y-card-lockout/

I hope that microsoft gets sued for blood right out of their ass on this one. I wanted to purchase a cheap 120Gb HDD for 65$ ( in india ) , but i must hold on as it may be useless in near future. The effect of this was seen directly on GTA : Gay Tony & Lost & damned , as without a HDD there was texture popping all over the place.

So microsoft very well managed to spoil the look & feel of the legendary GTA for me.

GRRRRRR, death to this Hetro Hating, Major Nelson & all his morons.

Datel could win this, I remember another case involving car door openers, somebody made a universal one, so one door company built in a lock against the universal ones, remote company sued and won.

I also remember something similar with 3rd party ink cartridges.

Edited by The_Decryptor

Yeah there is no reason that Datel should lose this, it is purely Microsoft trying to monopolise the 360 peripheral market. Same as I believe they don't licence out the wireless technology either so companies cannot make controllers etc? (That might have changed now, I know it was the case in the start)

Im lost here

Why would datel win this battle?

If M$ want you to only use there licences equipment with thier own 360, how can a company come a long and sue because M$ has stopped thier equipment from working on it?

Im not saying its good for M$ to do this but i don't get why they will win a case when its M$ own machine?

Yeah there is no reason that Datel should lose this, it is purely Microsoft trying to monopolise the 360 peripheral market. Same as I believe they don't licence out the wireless technology either so companies cannot make controllers etc? (That might have changed now, I know it was the case in the start)

It's still the case, but tbh there's no real reason to want to buy a 3rd party controller over official... not that that makes it any better. I guess it does affect some things negatively though, like the logitech G25/G27, two of the most popular steering wheels, can only be used on the PC/PS3.

It's not the 90s any more, nearly every electrical goods device that supports addons is allowed official and 3rd party now... Can you imagine if Apple didn't allow any 3rd party iPhone/iPod addons? :|

If there's one thing MS did wrong with the 360 this generation in amongst everything they've done right, it's rape people with accessories.

imo Microsoft can lock out any hardware they want to. It's their platform, and if they don't want people making money out of it, that's up to them. However, it's a stupid move to block these things four years into the 360s life cycle when a lot of customers have already bought one of these and now find its useless. They should get recompensed at least.

imo Microsoft can lock out any hardware they want to. It's their platform, and if they don't want people making money out of it, that's up to them. However, it's a stupid move to block these things four years into the 360s life cycle when a lot of customers have already bought one of these and now find its useless. They should get recompensed at least.

But you are not meant to connect unlicenced equipment to the 360 right?

imo Microsoft can lock out any hardware they want to. It's their platform, and if they don't want people making money out of it, that's up to them. However, it's a stupid move to block these things four years into the 360s life cycle when a lot of customers have already bought one of these and now find its useless. They should get recompensed at least.

This really is no different that Apple and the iPod ecosystem. Xbox is a closed platform owned by MS and they are free to control what products are compatible with it. It all comes back down to licensing. If MS is denying Datel a chance to get a license but has offered others a similar license, then this case just might have some water. But as it seems, like most third party accessories, they are not licensed by the OEM simply because licenses are not freely offered in the hardware gaming industry as they are with computer peripherals.

Maybe, but it's still a pretty big '**** you' after 4 years.

True and im not saying M$ are right but is there a law that could over turn this?

Are M$ by law meant to allow any tom dick and harry access there equipement?

This really is no different that Apple and the iPod ecosystem. Xbox is a closed platform owned by MS and they are free to control what products are compatible with it. It all comes back down to licensing. If MS is denying Datel a chance to get a license but has offered others a similar license, then this case just might have some water. But as it seems, like most third party accessories, they are not licensed by the OEM simply because licenses are not freely offered in the hardware gaming industry as they are with computer peripherals.

So does M$ by law have to allow Datel to buy the License needed to connect there equipment to the 360?

Im lost here

Why would datel win this battle?

If M$ want you to only use there licences equipment with thier own 360, how can a company come a long and sue because M$ has stopped thier equipment from working on it?

Im not saying its good for M$ to do this but i don't get why they will win a case when its M$ own machine?

Well your clever swapping of the S with a $ has convinced me you know exactly what you are talking about :rolleyes:

That said, I agree with your point, it just got lost in your attempt at 1998's Internet humor.

quick question, but do you really think writing MS with a $ makes you cool or something ?

Why should it?

I do it becuase i am lazy, I could use MS instead or even Microsoft, but that is to long and I always find my fingers go straight for the $ so i use that instead.

Well your clever swapping of the S with a $ has convinced me you know exactly what you are talking about :rolleyes:

That said, I agree with your point, it just got lost in your attempt at 1998's Internet humor.

Thanks bob

I think

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!