Jump to content

Search the Community

Showing results for tags 'support'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 17 results

  1. Microsoft to support new Edge browser until July 15, 2021 on Windows 7 Microsoft released the first stable version of the company's new Chromium-based Microsoft Edge web browser one day after it ended support for its Windows 7 operating system. Support for Windows 7 ended on January 14, 2020 for Home customers. Business and Enterprise customers have options to extend support by up to three years if they pay Microsoft for Extended Security Updates. The release of the new Microsoft Edge web browser for Windows 7 raised some questions. One of the main questions concerned support for the browser under Windows 7. For how long would Microsoft support the Chromium-based Edge browser on Windows 7? Microsoft has now provided an answer to that question. According to the company, the new Microsoft Edge web browser will be supported on Windows 7 and Windows Server 2008 R2 until July 15, 2021. We will continue to support Microsoft Edge on Windows 7 and Windows Server 2008 R2 until July 15, 2021. These operating systems are out of support and Microsoft recommends you move to a supported operating system such as Windows 10. While Microsoft Edge helps keep you more secure on the web, your PC may still be vulnerable to security risks. In order for IE mode to be supported on these operating systems the devices will need to have the Extended Security Updates for Windows 7. Without the Windows 7 Extended Security updates Internet Explorer functionality will be vulnerable to security risks. Additionally, IE mode functionality may cease to work without the continued servicing through the extended security updates. The browser's IE Mode (Internet Explorer mode) is only available on systems that have joined the Extended Security Updates program because of security risks involved. One question that has not been answered in the context is whether the new Microsoft Edge browser will remain supported for customers with Extended Security Updates functionality beyond July 15, 2021. These may get support until early 2023 for Windows 7 and Windows Server 2008 R2, and ending Edge support early may not sit well with some of these customers. Source: Microsoft to support new Edge browser until July 15, 2021 on Windows 7 (gHacks - Martin Brinkmann)
  2. Microsoft quietly extends support for Windows 10 Mobile Image Courtesy: PhoneDog.com Windows 10 Mobile has been a dead platform for years now and Microsoft themselves recommended users to try Android iOS where its services are regularly updated. On December 10, Microsoft shipped the final cumulative update for Windows 10 Mobile and confirmed the end of support. Windows 10 Mobile has officially reached its end of life and is no longer supported, but in a surprising move, the software maker has decided to extend the life of Windows 10 Mobile by one month. Microsoft on Friday quietly announced it had extended Windows 10 Mobile’s end-of-support date by about 30 days. Microsoft’s mobile OS was originally scheduled to fall out of “security support” on December 10, 2019. According to updated documentation, Microsoft is now planning to end support for Windows 10 Mobile on January 14, 2020. After January, Microsoft will no longer deliver security patches for Windows 10 Mobile, which could lead to security issues and other problems for users who continue to run the OS after the end date. “Windows 10 Mobile, version 1709 will reach end of service on January 14, 2020. Devices running Windows 10 Mobile and Windows 10 Mobile Enterprise will no longer receive monthly security and quality updates that contain protection from the latest security threats,” the updated document reads. We don’t know why Microsoft has extended the support, but this move aligns Windows 10 Mobile end-of-life with Windows 7 SP1 EOL date. One month extension is some good news for users running Windows 10 Mobile, but it’s not clear if another cumulative update will be released in January. Source: https://www.windowslatest.com/2019/12/15/microsoft-quietly-extends-support-for-windows-10-mobile/
  3. Firefox users won't be able to sideload extensions starting March 2020, with Firefox 74. Mozilla has announced today plans to discontinue one of the three methods through which extensions can be installed in Firefox. Starting next year, Firefox users won't be able to install extensions by placing an XPI extension file inside a special folder inside a user's Firefox directory. The method, known as sideloading, was initially created to aid developers of desktop apps. In case they wanted to distribute a Firefox extension with their desktop app, the developers could configure the app's installer to drop a Firefox XPI extension file inside the Firefox browser's folder. SIDELOADING REMOVED BECAUSE OF ABUSE This method has been available to Firefox extension developers since the browser's early days. However, today, Mozilla announced plans to discontinue supporting sideloaded extensions, citing security risks. "Sideloaded extensions frequently cause issues for users since they did not explicitly choose to install them and are unable to remove them from the Add-ons Manager," said Caitlin Neiman, Add-ons Community Manager at Mozilla. "This mechanism has also been employed in the past to install malware into Firefox," Neiman said. TWO-PHASE REMOVAL PLAN As a result, Mozilla plans to stop supporting this feature next year in a two-phase plan. The first will take place with the release of Firefox 73 in February 2020. Neiman says Firefox will continue to read sideloaded extensions, but they'll be slowly converted into normal add-ons inside a user's Firefox profile, and made available in the browser's Add-ons section. By March 2020, with the release of Firefox 74, Mozilla plans to completely remove the ability to sideload an extension. By that point, Mozilla hopes that all sideloaded extensions will be moved inside users' Add-ons section. Through the move, Mozilla also hopes to help clean up some Firefox installations where malware authors were secretly sideloading extensions behind users' backs. Since these extensions will now show up in the Add-ons sections, users will be able to remove any extensions they don't need or don't remember installing. TWO METHODS OF LOADING EXTENSIONS REMAIN Further, Mozilla's blog post on the matter today also serves as a notice for extension developers, who will have to update their extensions and make them available through another installation mechanism. There are currently two other ways through which developers can distribute extensions, and through which users can install them. The first and the most widely known is by installing extensions from the official addons.mozilla.org (AMO) portal. Extensions listed here are verified by Mozilla, so most are relatively safe, albeit the security checks aren't 100% sure to catch all malicious code. The second involves using the "Install Add-on From File" option in Firefox's Add-ons section. Users have to manually download a Firefox XPI extension file, visit the Add-ons section, and then use the "Install Add-on From File" option to load the extension in their browser. This option is usually employed for loading extensions that have to handle sensitive corporate data inside enterprise environments, and can't be distributed via the AMO portal. There was also a fourth method of loading extensions inside Firefox, but this was removed in September 2018, with the release of Firefox 62. This involved modifying Windows Registry keys to load custom extensions with Firefox installations. This, too, was abused by malware devs, and Mozilla decided to remove it. Source: Mozilla to stop supporting sideloaded extensions in Firefox (via ZDNet)
  4. Gaming on Android has usually meant gaming on the touchscreen of your smartphone. While Android does boast of a very large collection of touch-optimized games, some titles just work out better when the player uses a gamepad and real hardware buttons and keys. For the same purpose, you can find a whole host of generic gaming accessories, including controllers, that will easily allow you to upgrade your gaming experience. For example, if you have a PlayStation 4, you can connect the DualShock 4 controller to your smartphone to play. Unfortunately, this doesn’t work on every device, and the reason usually boils down to missing key layout files. If you are looking to reuse one of your existing game controllers, Android has been gradually adding in support for various popular controllers, such as the Xbox One S wireless controller, and the Xbox Elite Series 1 Controller. A study of the AOSP commits revealed that Android 10 also brought along the ability to connect and properly play on Android using the Nintendo Switch Pro Controller. A commit in the AOSP Gerrit had added in the key layout file for the Nintendo Switch Pro Controller. The key layout file enables Android to properly recognize the button presses on the controller, and map it to the appropriate Android action that games can listen for. Without this key layout file, the game either will not be able to recognize hardware presses or it will initiate wrong actions. The Nintendo Switch Pro Controller was launched alongside the Nintendo Switch and served as a better alternative to the Joy-Cons. This commit was added back in June 2019, so Android 10 updates on your phone are likely to have the same already incorporated. If you have a Nintendo Switch Pro Controller around, you can check and confirm if the same works seamlessly on your Android 10 device. Source: Android 10 brings controller mapping support for the Nintendo Switch Pro Controller (via XDA Developers)
  5. Dear Members, Post your ACTIVATION Backup, ACTIVATION Restore and Re-Activation problems Here. Hope you may get 100% support by the members. Keep in mind that DESCRIBE your problem clearly and elaborately. Description of your problem details will be important for your resolution. Points to be mentioned: - 1. The Method you used to Activate your Office (Online OR Phone). 2. Last 5 digit (for example -3DY5T) of the key you are trying to restore or re-activate. 3. Version of your office you want to Restore or Re-activate. 4. Method of restoration you are trying - Software or Manual. If Software, then name of the Software you are using to backup and restore. 5. Changes you have made (Hardware OR Software) to your system before your activation error.
  6. These daily price charts show the possible support and resistance levels for key, widely followed, heavily-mentioned in the business media "FANG" stocks: Facebook, Amazon, Netflix and Google. Let's start with Mark Zuckerberg's publicly traded business: Facebook daily price chart You can see that once Facebook peaked at just above 215 back in July, the stock has steadily and relentlessly tanked. It took out that previous 149 support level (from March), attempted a small bounce and then continued to the recent deeper low down near 130. That July gap down area is an eventual target to overcome should Facebook ever begin to recover from this remarkable down trend. The price has been unable to close above that Ichimoku cloud since that time -- six months ago. That's getting to be a long time for a formerly hot Internet sensation. Here is the daily price chart for Jeff Bezos' big enterprise: Amazon daily price chart. Amazon made it to late August before establishing a significant top at 2050. Although the stock did not suddenly gap down like Facebook, the steady descent to lower prices is similar: remaining below the Ichimoku cloud even with a decent sized bounce in November before continuing to sell-off to a lower than the October low. You can make out clearly that Amazon remains above the 1275 support level of the February low price. Here is the Netflix chart: This one peaked earlier than the others -- the top of 420 came in June with a retest the following month. After that, you can see the steady decline that's become so representative of this Internet-related sector since June. At the most recent price of 250, it looks as if Netflix is about to at least re-test the previous low -- and support level -- of about 238 from February. This chart has established an ersatz type of head and shoulders top, possibly. Also, while Netflix continued downward for months, one of its competitors, Disney, has continued higher to establish new highs. And this is the Google (legal name: Alphabet, Inc.) chart: Another monster Internet stock makes a summertime high and then takes a dive. The Google peak price is 1270 and now we're all the way down to 1000 -- almost all the way back to the March 980 low which represents some kind of support level. Each of these FANG price charts is unique in structure and yet they all show the same kind of general, overall pattern where a summer peak gives way to extensive selling as fall approaches and kicks in. Google is no different judging from the appearance of this chart. Just for comparison's sake, here is a non-Internet stock you could have owned instead: Clorox daily price chart. You don't hear Clorox mentioned much on the business channels or in the financial media -- certainly not even close to the number of times the FANG stocks are referenced. Nonetheless, Clorox continues to make new highs. Maybe it's better not to be the focus of so much attention. I do not hold positions in these investments. No recommendations are made one way or the other. If you're an investor, you'd want to look much deeper into each of these situations. You can lose money trading or investing in stocks and other instruments. Always do your own independent research, due diligence and seek professional advice from a licensed investment advisor. Source
  7. More information to come in November. During today’s Inside Xbox livestream, Phil Spencer announced that mouse and keyboard support is coming to Xbox One. It will be on Xbox Preview in October, and will be initially tested on Warframe. The idea behind mouse and keyboard support will be as a tool for developers, so they can choose how they want the control style integrated, if they want it integrated at all. “If you’re a dominant FPS player right now on controller and you’re worried that all the sudden you’re gonna get swamped because a bunch of mouse and keyboard players are gonna get flooded into your game, that’s not what we’re doing,” said Spencer. “We’re putting choice into the hands of the developers about the games that they want to bring." More information on mouse and keyboard support will be coming during the returning XO18 fan event in Mexico City on November 10. There is currently no news when this feature will be rolling out for all developers and gamers, but expect news along these lines during XO18, and for more on the exclusive Microsoft and Razer partnership for mouse and keyboard support. Source
  8. Julian Assange’s lawyers fear his extradition to the U.S. where they believe a sealed indictment in Virginia is awaiting him. In a rare move by a U.S. politician, a state senator in Virginia has come out in support of Assange. By State Senator Richard Black As a military officer, I was trained to strictly observe security protocols. So when I first heard of WikiLeaks and Julian Assange, I was instinctively critical. But upon reading his released documents, I saw how Julian gave people accurate insights into the inner workings of their own government. Government “of the People” cannot flourish beneath a suffocating cloak of secrecy. And secrecy is often aimed, not at protecting us from enemies abroad, but at deceiving us about the dark machinations of our own government. The most consequential secrets are those used to conceal steps taken to establish predicates for future wars—unwarranted conflicts that seem to roll off an endless assembly line. No-fly zones, bombings, sanctions, false flags, blockades, mercenaries, bloodthirsty terrorists have all become stock in trade. Sanctions destabilize our targets through hunger and suffering. We terrorize and blow body parts into the streets like calling cards. Regime change is the end game; coups and assassinations are fair play. Before Assange, those who “broke the code” and detected the Deep State’s patterns of misbehavior were labeled “conspiracy theorists” or worse. But with the advent of WikiLeaks, original, unchallenged source documents have proven our arguments, and revealed the truth to citizens. Donald Trump’s election sent violent shock waves through the Deep State. People had been warned they could not elect this person—but they had ignored the instructions. That was not supposed to happen—and could not be permitted to happen again. The People demonstrated that the mainstream media had lost its tight grip on the national conversation. National intelligence was being revealed and shared. Generations of subtle censorship had folded under an onslaught of uncensored communications among families, friends, and interest groups. Social media, a new and frightening paradigm, challenged the elite’s grip on the levers of power. After Trump, restoring barriers to free speech and communications became a global imperative. Today, we see intense, coordinated efforts to reimpose effective information control in America and globally. Facebook, Twitter, Google, YouTube, PayPal and other high-tech titans rush to hire censors and adopt restrictive policies that block controversial voices from reaching global audiences. Big Brother is back in town. Julian Assange and WikiLeaks are among the censors’ prized targets. They have disrupted Big Media censorship. Assassinating Assange is not out of the question. He is that important. I realize that Julian Assange is controversial, but I’d be pleased if some courageous nation granted him permanent asylum. Let him continue giving citizens an honest peek at the inner workings of their governments. That seems to be our best hope for peace. Source
  9. The company faces an inherent contradiction it has yet to resolve: It says Windows 10 is the last Windows ever, but has also set time limits on support. DobaKung (Creative Commons BY or BY-SA) Microsoft has backed off a possible confrontation with customers who had been told their two-to-four-year-old PCs were unfit for Windows 10, a sign, said one analyst, that the company remains unsure of its support strategy for the OS. Earlier this year, Microsoft blocked a class of low-end personal computers - those equipped with Intel's Atom system-on-a-chip (SoC) processors, dubbed "Clover Trail," part of the "Cloverview" architecture - from receiving the Windows 10 Creators Update. Also known as 1703 in Microsoft's year/month parlance, Creators was the first feature upgrade of the year, and the third since the operating system's launch. Those Clover Trail-powered devices were made and sold between 2012 and 2015 - the latter the same year Windows 10 debuted - and many if not most were eligible for the free upgrade to 10 that Microsoft offered. But the company balked at serving those machines 1703, telling users in April that because Intel dropped support for four models of the Clover Trail SoC, the PCs "may be incapable of moving to the Windows 10 Creators Update without a potential performance impact." (Intel calls this state, "End of interactive support (EOIS), which means it no longer offers phone-, chat- or email-based support. Microsoft cited a lack of "necessary drive support" on Intel's part as well, hinting that the issue was largely due to the SoCs' integrated graphics.) "They're still vague about the constraints to Windows 10 support," said Stephen Kleynhans, an analyst with Gartner. "They're still trying to figure out [support] themselves." The background: A built-in support contradiction Some background is required to put Microsoft's decision, or indecision, into context. Windows 10 suffers from a support contradiction. On the one hand, Microsoft has said that the OS will be the last version of Windows, ever, implying that it will be updated and maintained - "serviced" in the company's vernacular - for all time. Yet Microsoft has also set the usual 10-year limit on Windows 10 support, setting the end of its "product lifecycle" as Oct. 14, 2025, for almost all versions of the operating system. (The exception: Windows 10 LTSB, for "Long-term Servicing Branch," a change-free SKU available only to enterprise customers, which currently has an end-of-support date of Oct. 13, 2026, or 10 years after the appearance of the last approved LTSB build, mid-2016's Anniversary Update.) But Microsoft has stuck a different kind of monkey wrench into the works, one that raised questions when it was announced two years ago and was the cause of the recent consternation over Clover Trail. According to company statements of the past, Windows 10 was to be "supported for the life of the device," a timespan it never defined. In its own documentation, Microsoft gets more specific: "A device may not be able to receive updates if the device hardware is incompatible, lacking current drivers, or otherwise outside of the Original Equipment Manufacturer's ('OEM') support period," that documentation reads. This was the out Microsoft gave itself when it explained why it denied the Clover Trail SoC-powered machines the right to upgrade to Creators Update, aka 1703. "They require additional hardware support to provide the best possible experience when updating to the latest Windows 10 feature update, the Windows 10 Creators Update," Microsoft said. "However, these systems are no longer supported by Intel, and without the necessary driver support, they may be incapable of moving to the Windows 10 Creators Update without a potential performance impact." Later, Microsoft threw more fuel on the fire when it nailed down the support timetable for each feature upgrade. Its original plan - 12 months of support - was clearly too short, relying on a three-times-a-year release cadence. So, Microsoft extended the support lifespan to 18 months, that period defined by a twice-a-year release tempo. According to Microsoft, once the 18 months was up, a Windows 10 device would no longer receive security updates and other bug fixes. The only way to continue receiving those updates and fixes was to upgrade to a new feature upgrade. And that was a problem for Clover Trail. The systems would be stuck on the Anniversary Update, or 1607, which by Microsoft's schedule, would drop off support in March 2018. Microsoft capitulates Last month, after the Clover Trail Catch-22 again cropped up -- ZDNet's Ed Bott led the way on July 17 - Microsoft gave in. While the company kept the door to upgrades beyond 1607 closed, it reprieved the devices from the execution of its usual no-security-updates order. "To keep our customers secure, we will provide security updates to these specific devices running the Windows 10 Anniversary Update until January of 2023, which aligns with the original Windows 8.1 extended support period," Microsoft said in an addendum to the April support document. That solution was easy for Microsoft to implement, as it was already committed to coming up with vulnerability patches for 1607 because that feature upgrade was designated a "Long-term servicing branch" (LTSB) edition, the no-change version aimed at enterprises. Windows 10 1607 LTSB is to receive security fixes until Oct. 13, 2026, so Microsoft was going to quash bugs in any case. Does Microsoft know what it's doing? Microsoft has struggled to clarify Windows 10 support since before the Redmond, Wash. giant got it out the door, taking months, for example, to confirm that it would maintain the OS for the usual 10 years. And it's still grappling with defining policy, argued Gartner's Kleynhans. "They're being hit by the unexpected implications of things they hadn't considered," Kleynhans said when asked about the turn-about on Clover Trail. Under that explanation, Microsoft hewed to its promise to push hardware off the Windows 10 train when it decided that hardware was too old to run the OS. But it did not anticipate the blow-back, whether from users of the Clover Trail devices or the media, when people realized it meant an end to security updates, and thus a forced obsolescence of systems purchased as few as three years earlier. But Kleynhans contends that the Clover Trail snafu is a blessing in disguise. "This was a good wake-up call. It could be something bigger that runs into the same problem [in the future], Skylake or Haswell," he said, referring to Intel processor architectures that populate many times the devices of Clover Trail. Better to have an issue that affected millions of systems rather than hundreds of millions, Kleynhans said. Where Microsoft has stumbled has been in communicating how Windows 10 support works, why and how it's been changed when events superseded stated policy, and what new rules have been put into place. "Microsoft will come up with an answer in cases like this, but it must be communicated," Kleynhans said, implying that the firm has been less than stellar on the latter. "That's going to be the challenge for them." Although Kleynhans envisions Microsoft taking each instance of inadequate support as it comes along, "The goal would be to formalize that," he said. In cases like Clover Trail, however, Microsoft may not be able to set policies alone. "I imagine there will need to be coordination with Microsoft's partners," said Kleynhans, talking about chip makers such as Intel and AMD, as well as major OEMs (original equipment manufacturers) like Hewlett-Packard, Dell, Lenovo and others. It remains unclear how Microsoft will handle similar situations in the future if they arise. The company may not be able to rely on Windows 10 LTSB to provide the security updates that would cover systems Microsoft decides can't upgrade, as it did the Clover Trail devices; the next LTSB won't appear until 2019, Microsoft has said. (Windows 10 1607 remains the current LTSB version.) "This is definitely an area that [Microsoft] has to clean up," Kleynhans said of Windows 10's support policies. "It's still fuzzy." Source: Microsoft's still trying to figure out Windows 10 support (Computerworld - Gregg Keizer)
  10. Microsoft confirmed today it will support HTTPS Strict Transport Protocol (HSTS) in Internet Explorer 12, bringing its browser in line with other major vendors in its support of the protocol. Browsers supporting HSTS force any sessions sent over HTTP to be sent instead over HTTPS, encrypting communication to and from a website. According to OWASP, HSTS protects users from a number of threats, in particular man-in-the-middle attacks by not only forcing encrypted sessions, but also stopping attackers who use invalid digital certificates. The protocol denies users the ability to override invalid certificate messages. HSTS also protects users from HTTPS websites that also may include HTTP links or serve content unencrypted. IE 12 is expected to be released this year; IE 11 was introduced in October 2013 and is the default browser in Windows 8.1. IE 12’s support of HSTS puts it on an even keel with other browsers, some such as Chrome and Firefox have supported the protocol since 2011. Apple added HSTS support on Safari upon the release of Mavericks 10.9. According to the Electronic Frontier Foundation’s Encrypt the Web report, a few leading technology companies already support HSTS on their websites, including Dropbox, Foursquare, SpiderOak and Twitter. Others such as Facebook, LinkedIn, Tumblr, and Yahoo also plan to do so this year; Google too for select domains. EFF staff technologist Jeremy Gillula said today that developers either are unaware of the availability of HSTS, or have been stymied by incomplete support in browsers. “This is changing though: we noticed that Apple quietly added HSTS support to Safari in OS X 10.9,” Gillula said. “For now, Internet Explorer doesn’t support HSTS—which means that there’s basically no such thing as a secure website in IE.” Until that happens, much of the security burden falls on the user to either rely on a browser that supports HSTS, or use something such as the HTTPS Everywhere browser extension. “For now all a savvy user can do is to always carefully examine the address of the site you’ve loaded, and verify that it’s secure by checking to make sure it has “https” in the front and is the precise address you want to visit,” Gillula said. “Unfortunately this assumes that you know ahead of time (and remember) whether or not a site should be secure, and are meticulous with every website you visit.” Secure protocols such as HTTPS, HSTS and Perfect Forward Secrecy have been given greater priority now that the depths of NSA and government surveillance have been exposed. Experts urge developers to consider encryption technologies such as these a minimum standard for web-based services such as email. Just this week, Yahoo caught up to many of its contemporaries when it announced that it had encrypted traffic moving between its data centers; Snowden documents revealed that the NSA and Britain’s GCHQ were able to tap into overseas fiber optic cables and copy data as it moved to the company’s data centers. Yahoo also announced its intention to support HSTS, Perfect Forward Secrecy and Certificate Transparency this year. Source
  11. By MANNY FERNANDEZJAN. 24, 2014 Erick Munoz, the husband of Marlise Munoz, at the Tarrant County courthouse in Fort Worth on Friday. Larry W. Smith/European Pressphoto Agency FORT WORTH — A Texas judge ruled Friday that a Fort Worth hospital may not keep a brain-dead pregnant woman on life support against her family’s wishes, and ordered doctors to take her off the machines by 5 p.m. on Monday. The ruling gives the family of the woman, Marlise Muñoz, their first legal victory in a two-month battle over the fate of her body that has raised an emotionally charged national debate over end-of-life care, abortion and a Texas law that prohibits medical officials from withdrawing life support from a pregnant patient. The judge, R. H. Wallace Jr. of 96th District Court in Tarrant County, ruled that Ms. Muñoz, 33, who has been on life support at John Peter Smith Hospital since November and is now 22 weeks pregnant, was legally dead, agreeing with the family’s lawyers that the hospital had erred in its decision to keep her on life support. The hospital had said the Texas law addressing life support for pregnant women prevented it from granting the family’s wish, but the judge said the law did not apply to Ms. Muñoz because she is dead. Judge Wallace set the 5 p.m. Monday deadline, saying he wanted to give the hospital time to file an appeal. A spokeswoman for the county-owned hospital, which was represented by the Tarrant County district attorney’s office, said it would be consulting with its lawyers. The hospital appeared to be considering an appeal. Lawyers for Ms. Muñoz’s husband, Erick Muñoz, said they were provided with medical records that showed the fetus was “distinctly abnormal” and suffered from hydrocephalus — an accumulation of fluid in the cavities of the brain — as well as a possible heart problem. The hospital acknowledged in court documents that the fetus was not viable. The hearing Friday, at a courthouse three miles from the hospital, touched on the larger political issues that have underscored her case. In legal filings and in the courtroom, the lawyer for the hospital, Larry M. Thompson, said that Ms. Muñoz met the clinical criteria for brain death two days after she arrived there. But he argued that the law still applied to her, and that the Texas Legislature’s passage of the law showed that the state had a compelling interest in protecting unborn children. Mr. Thompson wrote in court papers that the Texas Penal Code’s definition of an individual stated that an unborn child was alive at every stage of gestation, from fertilization until birth. And he pointed to a bill backed by Gov. Rick Perry that lawmakers passed last year that banned abortions after 20 weeks of pregnancy, based on the theory that the fetus can feel pain at that stage. “Given the strong interest of the Texas Legislature in protecting the life of unborn children, it is unlikely the Legislature contemplated only the welfare of the mother” when it enacted the law prohibiting the withdrawal of life support for pregnant patients, Mr. Thompson wrote. He added that it was reasonable to infer that the law was meant to “protect the unborn child against the wishes of a decision maker who would terminate the child’s life along with the mother’s.” But a lawyer for Mr. Muñoz said Mr. Thompson’s argument amounted to a sweeping public policy declaration with broad implications. The lawyer, Heather L. King, said that if the state indeed had such an interest, paramedics who arrived at crash scenes would be required to give dying women pregnancy tests to ensure they were following the law. Ms. King apologized in the courtroom for putting it so crudely, but told the judge that pregnant women “die every day,” adding: “When they die, their fetus dies with them. That is the way it’s always been, and the way it should be.” Moments after Judge Wallace made his ruling, Mr. Muñoz, 26, who had been sitting in a bench behind his lawyers, slumped in his seat and began weeping. He was embraced by his relatives. “There’s nothing happy about today,” Ms. King said outside the courtroom. “This was a sad situation all the way around. We are relieved that Erick Muñoz can now move forward with the process of burying his wife.” The hearing dealt largely with the blunt issue of Ms. Muñoz’s death. Brain death — the total loss of all brain functions — amounts to a legal state of death. As part of his ruling, the judge ordered the hospital to pronounce Ms. Muñoz dead. Though Mr. Muñoz did not speak at the hearing, he said in court papers that it has been painful to watch his wife deteriorate from the woman he knew to what he described as a corpse being kept alive against his wishes. “Over these past two months, nothing about my wife indicates she is alive,” he said in an affidavit. “When I bend down to kiss her forehead, her usual scent is gone, replaced instead with what I can only describe as the smell of death. As a paramedic, I am very familiar with this smell, and I now recognize it when I kiss my wife. In addition, Marlise’s hands no longer naturally grip mine for an embrace. Her limbs have become so stiff and rigid due to her deteriorating condition that now, when I move her hands, her bones crack, and her legs are nothing more than dead weight.” Mr. Muñoz’s lawyers had asked the judge to declare the Texas law unconstitutional, arguing that it violated Ms. Muñoz’s rights under the 14th Amendment to make medical decisions about her own body. The judge said since the law did not apply to Ms. Muñoz, he would make no ruling on its constitutionality. Ms. Muñoz, who was trained as a paramedic, lived with her husband and their 15-month-old son, Mateo, in nearby Haltom City. She was at home in the middle of the night on Nov. 26 when she collapsed from an apparent blood clot in her lungs. She had gone to the kitchen to prepare a bottle for Mateo. Her husband later found her on the kitchen floor. She had stopped breathing, but was alive when she arrived at the hospital, according to court documents. Her parents and her husband’s lawyers said she was not breathing for an unknown length of time, possibly as long as an hour or more, which severely harmed the fetus by depriving it of oxygen. http://www.nytimes.com/2014/01/25/us/judge-orders-hospital-to-remove-life-support-from-pregnant-woman.html?hp Comment: Brain dead already occurred, no point keep going, right legal decision as hospital can not remove support by itself w/o court order
  12. By Chandrika Narayan, CNN January 24, 2014 -- Updated 0733 GMT (1533 HKT) Court: Sperm donor to pay child support A Kansas sperm donor caught in the middle of a child support case says he wanted to help a lesbian couple when he made the donation nearly five years ago. Instead, he may end up paying for his action. A judge ruled that William Marotta must pay child support, even though he says he signed documents waiving his parental rights. Shawnee County District Court Judge Mary Mattivi said on Wednesday that Marotta failed to conform to Kansas law, which says a licensed physician must be involved in an artificial insemination process, court documents show. The documents show that the lesbian couple whom Marotta helped conceive a child say they performed the artificial insemination procedure at home. 'I donated genetic material, and that was it' This story begins on Craigslist in March 2009. That was when Marotta noticed an advertisement from the Topeka couple, seeking donated sperm. "Intrigued" by the ad, he says, he delivered three cupfuls of his sperm -- gratis -- to the women. One of the women gave birth to a daughter in December 2009, according to court documents. "I donated genetic material, and that was it for me," he told CNN affiliate WIBW. Or so he thought. That changed when the parents separated and one of the women stopped working because of illness and applied to the state for help, he said. The state contacted Marotta for child support. Kansas officials were not persuaded by what Marotta says were agreements he signed, before making his donations, that he would assume no financial responsibility for the child, who is now 4 years old. The Kansas Department for Children and Families said any agreement would not apply because a physician did not perform the insemination. Marotta said that was news to him. "I didn't know that there was no doctor involved," he said. Lawyer blames political motivations His lawyer, Ben Swinnen, accused the state, where same-sex marriage is not legal, of being politically motivated in its pursuit of his client. "The cost to the state to bring this case far outweighs any benefit the state would get," said Swinnen, adding his client has no other children. Swinnen said the state is asking for $4,000 to recoup the money it has spent. It is also asking Marotta to pay child support, which could run into tens of thousands of dollars, he said. Swinnen said the Kansas court has failed to address many of the challenges brought forward by Marotta, under the guise of statutory interpretation of the law requiring the donor sperm to be provided to a licensed physician. "From a very narrowly crafted statute, the court has made a very broad rule -- that is the issue," Swinnen said. Swinnen said he planned to appeal the decision. Marotta: "I'm not her parent" Marotta said he met the child once -- a few months ago -- when he and his wife by chance crossed paths with one of the girl's parents at an area carnival. He said he had no intention of assuming a paternal role. "I'm not her parent," he said. But under Kansas law, he is her father. Had a physician carried out the insemination, that would not be the case, because Marotta would be able to document that he was a sperm donor and not the lover of the girl's mother, CNN senior medical correspondent Elizabeth Cohen said. "For all they know, they were lovers," she said. "They need that documentation. He's the dad; he ought to be paying up." Though a physician would have tested the sperm for sexually transmitted diseases and certain genetic disorders, there are disincentives associated with going through a physician. A single attempt at artificial insemination costs about $3,000, and sometimes several tries are needed. "It's a lot cheaper to get someone to come on over with their donation, and then do it yourself at home," Cohen said. Meanwhile, Marotta owes legal fees and has taken his story to the news media. "If enough noise gets made about it, at this point, maybe things will change for the better," he said. Asked whether, knowing what he now knows, he would answer the advertisement again, Marotta said, "Probably not." A different kind of fatherhood CNN's Justin Lear contributed to this report. http://edition.cnn.com/2014/01/23/justice/kansas-sperm-donation
  13. Microsoft has just announced that it is extending the support for Anti-Malware protection on Windows XP till July 2015. With this, Microsoft wants to bid more migration time to the existing Windows XP users. The decade old operating system Windows XP is set to go off support by April this year. This originally implied that Microsoft won’t be pushing any security patches to the operating system as and when we hit the deadline. In a blogpost, Microsoft writes, Microsoft has announced the Windows XP end of support date of April 8, 2014. After this date, Windows XP will no longer be a supported operating system. To help organizations complete their migrations, Microsoft will continue to provide updates to our antimalware signatures and engine for Windows XP users through July 14, 2015. To make things clear, Microsoft is not extending the deadline. Windows XP will still be unsupported after April 2014. But this Anti-Malware protection will make the operating system a bit more secure. This does not affect the end-of-support date of Windows XP, or the supportability of Windows XP for other Microsoft products, which deliver and apply those signatures. So what does this change mean to consumers? The enterprise users will continue getting the following security protection: System Center Endpoint Protection, Forefront Client Security, Forefront Endpoint Protection and Windows Intune running on Windows XP. Whereas for normal users, Microsoft Security Essentials will get you covered till July 2015 Although Anti-Malware protection itself won’t make the operating system fully protected, since there’s a limited number of things it can do, it will come handy to tackle with a wide range of malware and help in trying to secure Windows XP, against the many dangers it may face. This is a welcoming change from Microsoft and shows how much it cares about its users. Source
  14. You may have just bought that new Surface 2 or Surface Pro 2 tablet earlier this week, but the clock is already ticking to the day that Microsoft's official support for their newest hardware devices will end. According to Microsoft's Product Lifecycle page, mainstream support for both the Surface 2 and Surface Pro 2 will end on April 10th, 2018. That's nearly four and a half years from now, which is pretty much an eternity when it comes to new hardware. Microsoft had previously indicated it will end mainstream support for its Surface RT (now known just as Surface) tablet on April 11th, 2017. The original Surface Pro will find its support clock reaching its final second on July 10th, 2017. Microsoft is still not offering any information on when it will end mainstream support for Windows RT itself, which is installed in a number of tablets from OEMs that were released in 2012. The Windows RT 8.1 version will also be installed on the upcoming Nokia Lumia 2520. Microsoft will end support for Windows 8 on October 18th, 2015, while mainstream support for Windows 8.1 will stop on January 9th, 2018, with extended support continuing until January 10th, 2023. source: neowin
  15. Windows 8.1 is set for release as a free update to current Windows 8 users on October 17th. Windows 8.1 is set to hit general availability on October 18th. But did you know that mainstream support for Windows 8.1 ends in 2018? Those on Windows 8 will have two years to update to Windows 8.1, if they wish to be under the support lifecycle. Windows 8.1 users, on the other hand, will have Mainstream Support until 2018. For those who like to be 'in the know,' Mainstream Support for Windows 8 ends January 9th of 2018. Mainstream Support covers paid support (per-incident, per hour, and others), security update support, non-security hotfix support, no-charge incident support, warranty claims, design changes and feature requests, product-specific information that is available by using the online Microsoft Knowledge Base, and product-specific information that is available by using the Support site at Microsoft Help and Support to find answers to technical questions. Extended Support, which ends January 10 of 2023, covers everything listed above except you will not receive non-security hotfix support, no-charge incident support, warranty claims, or design changes and feature requests. Of course, those wishing to extend the "non-security hotfix support" can do so by purchasing an extended hotfix agreement, which must be purchased within 90 days of mainstream support ending. On a side note, Surface Pro, which runs Windows 8 Pro, will receive the Windows 8.1 update on October 17th and will see Mainstream Support until July of 2017. If you want more details on the support lifecycle, head over to the policy page. SOURCE
  16. I have HP Pavilion DV6-2174-TX Notebook PC which has no official support for Windows 8 from HP.But i downloaded drivers from here and it worked for Windows 8.After i clean installed Windows 8.1 Pro with WMC,i tried the driver for Nvidia GeForce 105M Graphics card from Windows update as well as from Nvidia website.I experience random BSODs Even if i don't install/update the driver i get BSOD?I tried Driver Magician but resulted in BSOD.BSOD is always related to Nvidia driver. Do you suggest any reliable software for updating my driver? Does anyone the way to install Win 8 driver on WIn 8.1?
  17. smallhagrid

    An XP-centered query...?

    I asked this before - someplace, sometime - and then I had to move, changed PCs - and lost the great replies that came to me before I could use them...so forgive me for asking here, again, please. I know there are forums devoted to XP users. Searching for them is not easy because 'XP' and 'forum' are such general terms... My query: If anyone here knows of them - please point me to any forums you know of that are specifically centered around XP ?!? Thanks for helping me out here.
×
×
  • Create New...