Microsoft sounds support warning bell for customers running Windows 7, Windows Server 2008, Windows Server 2003, and more
-
@Carnival-Boy said:
If you think programming your own software under Solaris is the answer I'm not sure you have much experience of the realities of small manufacturing.
Maybe small manufacturing just isn't looking at the best tools for itself. That's a general factor in all SMBs. They often overlook what is cheap and good for what is well marketed.
Has anyone thought of assembling a market consortium to deal with this? 200 hours isn't that much programming. It's a lot for a single piece of equipment at a single shop, of course. But just five weeks of work. How much is that machine worth to protect? Would it lengthen the life of the machine? Could it protect against down time? Could you reduce support costs, licensing costs, etc? Could the consortium sell the result to recoup the investment? Get two shops together and it is just 6.000 Euro. Get one hundred shops together and it is just 120 Euro each. If there are any number of these out there and everyone is facing the same issues, there is likely a market for fixing things.
-
Do you know other companies that have these?
-
I've helped support drill shops in Spiceworks who have Solaris control systems. Single drill shops, very small. Solaris is, or at least was, the standard for drill systems.
-
Great out of the box thinking there Scott.
Here's my situation:
We have a Toshiba CT scanner that's running on XP. Toshiba does not have an option for replacing the control workstations for this equipment with another OS. Simply does not exist. Unless we wanted to hire a company to completely rewrite a whole new interface on a new OS we have no options. Additionally once we do that Toshiba will no longer provide support/maintenance on the machine, which means it will no longer qualify as a certified piece of medical equipment, and the insurance companies won't pay for its use.I'm sure there were other CT machines that would could have looked at, but running them on Windows seems to be standard practice. I'm guessing that anyone who runs their machine on something else would be considerably more expensive and probably outside our price range (programming for windows is for some reason considered much cheaper than for say Solaris - at least that's my guess why someone like Toshiba would use it as a base instead of something else).
-
@scottalanmiller said:
200 hours isn't that much programming. It's a lot for a single piece of equipment at a single shop, of course. But just five weeks of work.
Seven weeks. This is Europe not America
I'm sure there's ways and means. I just took umbrage at you suggesting that buying hardware controlled by Windows OS was silly, really bad or lacking due diligence.
-
@Carnival-Boy said:
@scottalanmiller said:
200 hours isn't that much programming. It's a lot for a single piece of equipment at a single shop, of course. But just five weeks of work.
Seven weeks. This is Europe not America
I'm sure there's ways and means. I just took umbrage at you suggesting that buying hardware controlled by Windows OS was silly, really bad or lacking due diligence.
Ha ha. Actually in the US that is only four weeks. A professional day is 10+ in the US (that's a real term.) So normal professional weeks are 50 hours minimum and 60-72 hours not that uncommonly. Probably 55 hours is most common. So in the US it could be as little as three weeks. When I was on Wall St. normal weeks were 65-75 hours not including being on call 24x7.
-
@Carnival-Boy said:
I'm sure there's ways and means. I just took umbrage at you suggesting that buying hardware controlled by Windows OS was silly, really bad or lacking due diligence.
Is there no way to require vendors to support the products in an updated way? No market pressure, contractual obligations, etc? Not that they have been taken, but is there no means to take them? All they would have to do is follow extremely basic standards and even being on Windows they would not have these compatibility problems. As a vendor that makes this kind of software it's extremely easy not to get into these situations (we make not entirely different software for hospitals.)
-
@scottalanmiller said:
A professional day is 10+ in the US (that's a real term.)
Wow. Really? As far as I can tell no-one at NTG does any work at all, you all just hang out on ML all day long? I don't think over 50 hours of work a week is productive over the long term - it just leads to burn-out and low productivity. I have no evidence to back this claim up though.
-
@Carnival-Boy said:
@scottalanmiller said:
A professional day is 10+ in the US (that's a real term.)
Wow. Really? As far as I can tell no-one at NTG does any work at all, you all just hang out on ML all day long? I don't think over 50 hours of work a week is productive over the long term - it just leads to burn-out and low productivity. I have no evidence to back this claim up though.
That's odd because it is a constant issue that the NTG team is never on ML. Hmmm.... where are they posting?
Over 50 hours a week might not be productive, agreed. But the entire US operates this way. Even when I was a sixteen year old blue collar restaurant worker I was doing more than 50 hours. I've worked in factories doing over 70 hours a week. Even fast food, grocery storage, hotels, etc. All that "low end" manual labour, pretty commonly did over 50 hours a week. It is extremely common here and once you get into a "professional" job the numbers go way up as far as what people expect.
It's horrible for "engineering" jobs where you have to be creative. But it is very good for "administration" job where your primary value is in being available.
It's shocking how any European desires to move to the US given our horrible laws, terrible employee protection, high taxes, worthless healthcare and insane working conditions. Although to be fair, I've spent nearly a decade working for London and in big business financial IT, they worked many more hours than the Americans often in the 80+ hours per day category starting early in the morning and working through the US evenings.
-
@scottalanmiller said:
Although to be fair, I've spent nearly a decade working for London and in big business financial IT, they worked many more hours than the Americans
It never used to be like that. Life in the City of London was pretty cushy until the mid-80s when the Americans arrived and introduced American banking culture.
-
It's Called working in a world market.
-
@Carnival-Boy said:
It never used to be like that. Life in the City of London was pretty cushy until the mid-80s when the Americans arrived and introduced American banking culture.
That's actually what they say on Wall St. Everyone in NY works super long hours because of the London culture. Didn't used to be like that here either. Now that London works longer hours than us, we have to work super long to look like we are working as hard.
-
@Dashrender said:
It's Called working in a world market.
I think everyone works longer hours now. The region of the world working before you seems like they work harder because they are "in earlier" so you want to stay late to try to look like you are working more. It's a game of constant "hours escalation."
-
@scottalanmiller said:
@Dashrender said:
It's Called working in a world market.
I think everyone works longer hours now. The region of the world working before you seems like they work harder because they are "in earlier" so you want to stay late to try to look like you are working more. It's a game of constant "hours escalation."
So are you saying the only way to solve the problem is to go to a single world timezone?
-
@Dashrender that doesn't do much. People work their local daylight regardless of the time. There is no good answer. The new world is simply one where sleep must be enforced.
