Samsung Software Upgrade? (part 2)?

As said, call Samsung. It is likely your TV does not have the hardware to decode video files, or may even use a different CPU system. The Series 9 firmware, at best will be rejected by the firmware upgrade routine, and at worst hose your set.

1. Can software licenses be resold? [duplicate]

Forget about selling your autodesk software, or buying used one.We bought autocad 2010 upgrade, and the activation failed because i registered the previous editions with a different name!I had to do several long calls to SWISS (of course, a money-making house like them, can be located somewhere else?) and mail them a copy of all the previous versions CD and boxes, with the invoices!!!! You can imagine what trouble can be finding the invoice of Autocad R14!!! (1998!!!)

2. What is it like to be a software engineer with a PhD?

There was no difference in general as most people did not know I had one. I did not actually think it was relevant. I took the degree because I wanted to enter teaching. When company started printing it in my calling card, the differences started to emerge. Most people started using the title and started asking for advice. Whenever I visited customers, the sales folk would start by introducing me as Doctor. Personally, I have always made decisions scientifically and like to measure and experiment. That I presume was a product of academic training

3. How do you make software?

First of all, you wo not be making any iPhone apps in the first couple years. With that said, I would advise learning an easy language, like BASIC or Pascal. There are lots of books on this subject

4. Are US software patents enforceable in the UK?

There are three main provision of the laws that might cause you problem and they all involve exporting to the US or encouraging others to do so. The primary statute on point is 35 U.S.C. 271(a)-(c).Thus, if you import an infringing product into the US or induce someone to import the infringing product into the US, then you can be held fully liable as an infringer. Even if you are selling through a third party distributor, you likely be seen as inducing the importation depending upon the facts. There is nothing illegal about selling to US customers when they are in the UK so long as that sale is not part of an import scheme.Now, there are some procedural issues that a patentee would need to overcome: (1) can a court get jurisdiction over you as a non-US entity; and (2) can they collect money damages since you are in the UK. These are big questions. If the case is brought in the US International Trade Commission (USITC) rather than in court then the court automatically claims jurisdiction based upon the imported products. The nice thing (for you) about USITC cases is that USITC never awards money damages (only awards exclusion orders to block further imports). If you lost a money judgment in court, the patentee could seize your US assets. There is no particular treaty between the US and UK on enforcing foreign money judgments. However, it is usually relatively simple for a US judgment winner to go to the UK and collect the money

5. Illegal wiretapping software available to the public?

because america is f*cked up and it seems invading privacy is "ok" when it involves some one you know. i say f*ck it all

6. Most SEO friendly ecommerce software?

Magento is the most SEO friendly, user friendly and customer friendly eCommerce solution. More than 40% of merchants are using magento for their ecommerce stores. There is no doubts magento is the best.

7. What are some DVD Unprotecting software?

I am a big fan of handbrake. DVD to MP4 in one easy step

8. Regarding antivirus software such as AVG and Avast?

AVG is just anti virus i think but theres free firewalls as well. the zone alarm one is good and maybe comodo. you might want some spyware software like windows defender as well.

9. What do software architects do?

I think the best (most practical and most accurate) definition of "architecture" is "what you think about when you think about your current problem in a usefully more abstract way". Or to put it another way, it can be an analogous to the old saying about winning the battle but losing the war. Programmers win the battles, architects win the war. Talking about software architecture is slippery, because the definition of software architecture itself is slippery and changes depending on who you ask, and when. One descriptor most people would agree with is "architects look at the bigger picture."At one end of the spectrum is a CTO or CIO to whom architecture is about which technologies and platforms the company should invest in. At the other end, even a regular Joe/Jane programmer thinks about how the pieces of the system they're working on go together.In between, that programmer's team might have an architect who spends his or her day making sure:that the team is taking the right general approach to solving the problem;that the different subsystems the programmers are working on will mesh well when they put them together;that the team is solving the right problem (depending on the culture and size of the organization this might be broken out into a different role).This might involve a lot of UML diagramming, or it might be more hands on and involve more discussions and whiteboarding, depending again on the culture and size of the organization. If it's a good software development group, I'd expect those discussions to involve project team members at all levels, but in more average groups there might be more formality and stricter lines of division, and the architect might spend most of their time with project managers, project planners, team leads, etc.In larger organizational contexts, frequently there's a lot of emphasis on formalisms to protect the rank and file workers from distractions. In smaller organizations, or sharper dev groups in larger organizations, it's easier to keep teamwork collaboration from becoming distraction (and sometimes easier to convince management that you know which is which). There might be an architect at the next level up who thinks about how the different enterprise systems work together.There's a term that sometimes comes up in software discussions, but surprisingly I don't think I've ever seen it in a discussion of architecture: cross-cutting concerns.Cross-cutting concerns are issues that cut across the entire application, like logging, security, how data gets around (message queues vs event listeners vs, etc), and sof orth. Programmers certainly think about these things and how they relate to the parts of the project they're working on. But it'd also be reasonable to say that cross-cutting concerns are (or are a good part of) the meat and drink of the architect.Also, as a slightly more obscure military saying goes, "privates study tactics, generals study logistics":The nature of the architect's role is such that he or she spends a lot of time dealing with all members and levels of the team, including the project planner, and the project manager (if they're not the same person). As I mentioned above, while I wouldn't be at all surprised if a given organization is very formal about the lines between areas of responsibility, I also wouldn't be at all surprised if it's the opposite - if the project manager and project architect and whoever else spent a lot of time not just liasing, but collaborating and kibbitzing. Hence the architect might also end up doing a lot of hands on stuff with project planning and software development methodology.(Note, where I write "programmer", insert your favorite title: developer, engineer, etc. Some people (and a few organizations) try to invent a hierarchy around these titles, but nobody seems to have the same definitions so the distinction is meaningless.)