Office 2016 De 32 Bits Mega
Katja Gains
Butch, is this a 'new' install of the IDE/Mega 2560 BOARD or just a working IDE installation (in my case a Uno R3) not working on the new Iteaduino board??? the issue I have is similar although I tried as per instructions (for a new install) to "Re-Install" the driver with no success. I did go into the device manager and remove the non-working instance of the USB Port (the one with the yellow ! label. Did I do it wrong??? I don't know what is the issue here but the mega 2560 chip is working and reports "The Right Stuff" as evidenced by Mr Gammons help and sketch (Thank you Nick again for your kind help especially after my display of bad manners) So I am at a loss until I can replace the defective part (s) or connect a regular serial port to the Mega. I own both FTDI232R's and a couple of PL23XX USB adapters and mainly I am hoping someone will point out any faulty reasoning I might have applied in attempting a 'fix' for the issue in that manner. an external cable for programming the Mega in that fashion is good to go for me. The Mega has a wealth of hardware UART's and dedicating one just for programming is not an issue for me at all, preferable too, as I have the parts in my "Junk Box". I can either solder a PL23XX cable directly to the board or make a connector using bread board connector pins. IMO
I have had this problem sporadically over the past two years. Very frustrating indeed. Seems it's just arbitrary when I unplug the Mega from the USB sometimes, it just looses the Port when I replug. Restarting windows 7 (32) does nothing, reinstalling the drivers does nothing. Only found one solution, the obvious one noted on oh so many USB devices - "Plug the USB device directly into a computer USB port - do not plug into a USB multi-port expander" My expander is a USB 3.0 expander and has never had a problem. But when the Arduino hangs and does not show a serial port, I plug it directly into one of the computer USB's and it works perfectly. Please be sure to try plugging the device directly into one of the computer USB ports.
what if this doesn't work? drivers are updated, programs are updated, computer software and hardware is all up to date, but the device accepts usb power, can be written to with a tinyusb programmer, (the one that bypasses the usbport) but doesn't impact the board. The board is a rumba. I've tried 3 seperate cables , two operating systems, four programs, three rumbas, and nothing sees the rumba.
I'm experiencing the "USB not recognised" error when I power the arduino mega externally with a power adapter followed by connecting the arduino to my laptop using usb. However, if I don't power the mega externally and i just connect the arduino to my laptop using usb then I don't get the error, and it is appearing correct with no error/warning in control panel->device manager. Strangely this happened only in a shopping mall environment but in office it works without any issue. I tried it out in a shopping mall on separate days and 90% of the time the "USB not recognised error" showed up, but back in office there is no such issue. I do have connections from my own pcb to the digital and analog pins on the arduino, and the pcb is receiving power from the same power adapter. Can anyone tell me what's wrong and how to resolve the issue? Thanks.
How to Fix Bad Chinese Arduino Clones: Have you ever wondered if a cheap Chinese Arduino clone will actually work?You pay only a few bucks and get the same product. Sounds to good to be true right? The truth is that some work and some won't. Follow...
Were we losing touch or were we trying to do bigger and better things that would naturally and unfortunately alienate our best fans? Were we growing our ability to create strategic enterprise products or were we over-reaching on what we could (or even should) deliver? Was disruptive innovation happening in real time like it should, or were we just being disruptive?
Nevertheless Sun continued to use Office in finance, presentations, and more. Sun was still a strong company, though that would change in due time, coincidently as their use of Office declined. McNealy held an influential position, particularly when it came to internet technologies. Like Microsoft, Linux also took its toll on Sun.
Highlighting Star Office as an alternative to Office was one way enterprise customers expressed increasing frustration with bloat. Depending on who you asked the products indeed had many flaws. What we began to consider was that we were now being evaluated on and held to an absolute scale. It was no longer enough to be better than a competitor we vanquished or a new competitor like Star. We needed to be great on our own, an absolute standard.
A really (really) big problem brewing was that Windows XP was struggling in the market, having received muted reviews it often proved difficult for enthusiasts to upgrade and required a significant uptick in PC hardware from OEMs. More alarming though, the virus and malware criminals and troublemakers that attacked Office moved their focus to Windows XP and Windows Server. Those products with significantly more surface area were under assault. The Windows team was scrambling to patch a relentless onslaught of bugs. There was ample consternation over the rationalization that the product was behaving as was intended while also deep concerns about breaking third-party software. If this challenge sounds familiar it is because it is exactly the situation Office was in years earlier.
Windows developed a plan to implement a fast-turnaround service pack that addressed the major holes in the product and to complete it in six to nine months. From my vantage point, having a 50 percent error rate on the estimated schedule completion of a short-term project was already a sign of a team that was not operating in control. The scope of the work, the resources, and the schedule were not aligned. The update to Windows XP was going to need more time, more people, and more work.
There was some good news in how the update progressed. Windows XP as it released was outfitted with Watson technology from Office. For the first time a Windows release was getting real-time information on crashes. The Office team continued to run the Watson service while Windows was able to isolate and fix a very large number of common crashes, as Office did while shipping Office XP.
A favorite saying in the Office hallways was that it is not enough for the leading product to drop the proverbial ball, but someone had to be there to pick it up and run with it. While there were many challenges in market with Windows XP, the real concern was that it was increasingly apparent that the network computer and browser were there to pick up the dropped ball.
Unfortunately executing the product changes to secure Windows XP turned into a 36-month journey (including an interim Service Pack 1), releasing Windows XP Service Pack 2, XP SP2, on August 24, 2004, three years after RTM and much longer than a quick turnaround. There were several major security incidents over the course of this, which either motivated more changes or slowed down releasing broad product changes, depending on perspective. When people say the regulatory climate distracted Microsoft and slowed execution, all I can think about is how much more responding to security did. While not everyone was working on compliance, every single group with code in Windows, Server, Office was making changes, fixing bugs, or investigating potentially risky areas to improve security of products while continuing to function correctly with the changes Windows was making. PC OEMs and independent hardware vendors (IHVs) contributed immensely by updating all the software installed on new PCs and required by hardware devices.
While the first couple of years were rather difficult with Windows XP, it emerged to become a deeply loved and fixture of a PC operating system. When I was working on Windows, we ended up extending official support for the product to nearly 13 years, three years longer than any other product.
Office was in a different place. We did not face the security challenges to the same degree but faced the needling of Scott McNealy, softening demand for new Office features, and high-friction upgrades from enterprise customers, and the ever-present risks of browser-computing.
WinXP was the first OS with Watson. As such, a lot of low-lying fruit was there to be picked; many bugs (in Windows itself) got reported and fixed. But alas, the fixes were being held up, because Win management really really wanted to simul-ship the Windows XP Service Pack with Windows Server. Lots of good reasons for this, but there's a limit!
Watson has a feature where we can tag buckets with a link; if you hit Send on that bucket, we bring up the browser, typically saying "we fixed this, go for the update". But since the SP hadn't shipped, the page (for a zillion buckets) was authored to say (in effect) "hey we've fixed this bug, really we have, and you'll get the fix really soon, but not just yet". Needless to say, this made not a lick of sense to our customers.
Win XP probably ran on 1000x as many machines as Server. No one was clamoring for the Server release, but all my XP peeps were being denied their fixes, and it just kept dragging on. So I wrote to whatever Windows Veep ran the thing, and told him to get off the pot, sever the connection, ditch the simship, deliver my SP. To his credit, they did so, and I was happy.
And then, twenty years later at a party, somehow the subject came up, and some guy I'd never met before said "that was you?", and was ready to punch me out over it. I guess he'd been square in the simship clan, and I'd shoved him aside.
The turn of a new century and survival of \u201CY2K\u201D begins a massive expansion of the Office product line, a dramatic change in the products we built, and a reinvention of how we market Office, while simultaneously tripling and quadrupling down on enterprise customers. The result of this transformation sets the stage for the most formative years culturally for the Microsoft that takes us to today\u2019s products (365, Azure), but unknowingly constrained us going forward.
d3342ee215