Chips in the same family are already pretty much the same. CPU's with same specifications but for clock speed are already the same chip. The difference is that some chips pass more stringent QA procedures @ higher speeds and so they are 'marked' as running @ that speed given the assumption that some number of chips out of the oven passed "x" test. Chips that don't are tested less rigorously until they do pass @ some lower speed. You see it's not a technology or chip design problem - its a manufacturing process & QA problem associated with being able to bake-off "z" numbers of chips from a die of a given size and passing a given QA threshold. There's nothing inherently difficult with producing an Intel chip or any CPU that can run at any speed you wish if you can cool it off. The problem is being able to manufacture enough of them reliably & economically on the same die without a very small number of rejects.
First of all there are many 'grades' of military communications from secure to not so secure. It's not clear what kind of communications grade they're talking about here. Could be a satellite that supports the movement of pencils from one warehouse to another. Second - gov'ts do not go public with this stuff unless it is in their interest to do so. For example if it is already known that some communications are not secure and/or then eventually it behooves them to announce that fact in lieu of having to explain which coomunications are still secure and why. By analogy in the US, stealth aviation projects were black until it became obvious that a)there was political gain in going public and, b)they probably were not the latest generation.
Well it depends what you mean. On the server side whether you're using LAN server or TCP applications only Warp & Warp server are rock solid & it's not unusual to boot them every 3 months or so. On the other hand the stability of WPS is well known. So while OS/2 as a desktop provides some great function - sometimes it doesn't work well. The other problem with OS/2 is that when it works it works great but when it breaks then things go disasterously and tragically bad. Mess up WPS and find yourself rebuilding the machine from scratch? Remember to backup all of your WPS customizations? Remember to reapply fixpacks and CSDs? remember the workarounds to patches that caused problems of their own?
Slashdot Mirror
At least Dialogic has started to develop their CTI products for SCO Unixware - can Linux be far behind?
Chips in the same family are already pretty much the same. CPU's with same specifications but for clock speed are already the same chip. The difference is that some chips pass more stringent QA procedures @ higher speeds and so they are 'marked' as running @ that speed given the assumption that some number of chips out of the oven passed "x" test. Chips that don't are tested less rigorously until they do pass @ some lower speed. You see it's not a technology or chip design problem - its a manufacturing process & QA problem associated with being able to bake-off "z" numbers of chips from a die of a given size and passing a given QA threshold. There's nothing inherently difficult with producing an Intel chip or any CPU that can run at any speed you wish if you can cool it off. The problem is being able to manufacture enough of them reliably & economically on the same die without a very small number of rejects.
First of all there are many 'grades' of military communications from secure to not so secure. It's not clear what kind of communications grade they're talking about here. Could be a satellite that supports the movement of pencils from one warehouse to another. Second - gov'ts do not go public with this stuff unless it is in their interest to do so. For example if it is already known that some communications are not secure and/or then eventually it behooves them to announce that fact in lieu of having to explain which coomunications are still secure and why. By analogy in the US, stealth aviation projects were black until it became obvious that a)there was political gain in going public and, b)they probably were not the latest generation.
Well it depends what you mean. On the server side whether you're using LAN server or TCP applications only Warp & Warp server are rock solid & it's not unusual to boot them every 3 months or so. On the other hand the stability of WPS is well known. So while OS/2 as a desktop provides some great function - sometimes it doesn't work well. The other problem with OS/2 is that when it works it works great but when it breaks then things go disasterously and tragically bad. Mess up WPS and find yourself rebuilding the machine from scratch? Remember to backup all of your WPS customizations? Remember to reapply fixpacks and CSDs? remember the workarounds to patches that caused problems of their own?
I think MS stills owns most of HPFS or at least the LAN server version of it HPFS.386