Actually, Intergraph has a long history of chip and hardware design. They started out as a contractor on the Apollo program and by the 1980's were producing their own VERY power Unix workstations and servers running on their CLIPPER chip.
They did their own Chip design and even did some work on the SPARC for Sun.
Unfortunately, they were also run by a bunch of geeks that didn't know squat about business. That, coupled with them giving up on the Unix market for Windows NT back in 1993 (about 2 years too early) caused them to take quite a fall.
In the process of moving to a Wintel platform, they worked closely with Intel and that is where they got entangled. Intergraph needed Pentiums (and lots of them) to power their workstations and Intel tried to strong arm them into turning over some of their technology. I can assure you that the cache/MMU in the current Intel chip line did in fact come from Intergraph.
You need to do a bit more reading. Sport Pilot will NOT effect part 103. It will mean then end of some of the Part 103 tandem exemptions, but not the USHGA exemption. Why? Well, read the rule and you will see that LSA's are defined as having fixed landing gear - foot launched aircraft (hang gliders and paragliders) can't be registered as LSA. The EAA/USUA/ASC exemptions to part 103 will be phased out while the USHGA will keep its tandem exemption. The USPPA (US Powered Paraglider Association) has also petitioned for an exemption for foot launched tandem PPG instruction, since the USHGA exemption specificly excluded powered flying. This will also be a BIG help to the aero-tow operations that were previously flying fat UL's for towing. They can now fly LSA's and be legal.
I bought one - I got a discount through work and I really like the small form factor. Well, it turns out there are bugs in it and they freeze up or hang on a regular baisis. Just check out the post on the Apple support forums or any other iPod forums.
Mine arrived last week and has yet to work - waiting on the return box from Apple to ship it back for a replacement.
My advice to potential buyers is to wait for the 1.01 release or buy it at the Apple Store without getting it engraved - then you can exchange it there instead of sending it in for repair (= replacement).
Should have know better to buy a v1.0 Apple product - at least other companys give nice little gifts to their beta testers.
Red-lining documents is what they do... although most use a third-party tool called Redliner to do it, so the other parties can't change their comments.
I ordered a new powerbook ($3k+) in December and it arrived on Jan 3. Since my order was placed 2 weeks earlier, I'm not eligible for the upgrade price, and if I would have waited a month, the PB would have shipped with iLife 4.
Just another screwover by the boys in Cupertino. Just ask the guy that lives next door to me that bought a 1.8gz G5 in October - now you can get the same box BUT DUAL G5's for 100 bucks more!
Sucks, but having just switched from a dual boot linux/w2k laptop, I must say I am way impressed with the PB.
Most real software companies but their code in escrow, since many big businesses require it. If the software company goes out of business, the code them goes to whoever is designated in the escrow agreement, usually the customers. The customers are give the code, but not the IP, for the purpose of maintaining the application themselves.
Working as a consultant, I've seen quite a few companies that are supporting an application using code aquired from escrow when the vendor folded.
As a consultant, I've seen MORE than my share of crappy code written by client IT staff over the years. And after a couple of stints working on commerical projects, its often the case as well (but not quite as bad). One execption was code for a CAD application I happen to get a change to review at a previous employeer - very clean.
Of course, the biggest example of this can be see by reviewing the first release of the Netscape code.:)
Ok, now you are just showing off. Should I really embarass you and let the world know about all the REXX and LU6.2 code floating around a certain state university you had a hand in. Nah, that wouldn't be nice.
I know the principal author, John Bashab, and he is every bit the techie. He may have an MBA, but he was (at one time) very much a geek.
How much of a geek was he? He wrote a disk de-fragger for the TRS-80 model 3 in z80 assembler in the 10th grade - 3 years before Norton Utilities came up with the same thing for the PC.
He may have succumbed to the dark side (management) but he does have the background to evaluate technology.
The only people that really belive that techies loose touch with the technology when they become managers are the ones with no talent for management.
Intergraph used to make its own chips - the CLIPPER line that they used in its workstations. They went to Intel based workstations back in the early ninties and have sold off most of their HW business. The problem with hardware is that the margin is small enough as it is, but Intergraph insisted on making it all in the US, not in Tawian like most.
Some ag prof probably head about all this wireless technology and is trying to apply it to an electric fence.
Roll Tide.
Social Engineering is still the biggest threat
on
Network Hacking
·
· Score: 2, Informative
I mean it. I'm a consultant and its surprising how much I can get a sys admin to do for me over the phone, from across the country.
Recent example - we were converting 17 years of production data from a mainframe into a the replacement system. With the volume, we needed an uninterrupted 40 hour window, but the client performed a cold backup of the database nightly.
The process in place says we call the production DBA's (who know us, and are employees, not contractors like us) and they pass official word to the operators in the datacenter.
Well, after 9 hours of loading, the database goes down at 5:00am. We call the prod dba's, and the on-call guy doesn't answer. So I call the ops center. The story I get is that a contractor on another project requested a backup of some critial files stored on the db box. He did this directly with the operator at 11:00 the night before, and the operator didn't even remember his name.
If a simple phone call to ops is all it takes to take the system down, why bother with the standard exploits?
Yes, but you pay for it up front and it's usually probided my a third party. So instead of a local, smart, motivated tech that probably put your machine together in the first place, you get the lastest round of ITT Techincal Institute graduates from Unisys or Pomeroy.
The second link is entirely more interesting than the initial story. The process that this Russian developed for color photographs back in the early 1900's and the fact that we can now view them is increditable.
Beat's the hell out of Ted Turner's colorization of old movies.
I've been given counter offers at least three times during my working life, and I never took them. Of course, money was not the root cause in 2 of those departures and in each case I was dumb enought to accept the outside offer before approaching management. Once I've accepted an offer, I go with it - no matter what.
As for the reasons listed on the link, the ones that are the most accurate are the ones that deal with the effect of your about-face on your working relationship with co-workers. As a manager, on the 4 occasions when I have offered counters to my employees, I did it as a sincere gesture to get them to stay - all 4 decided to leave anyway. Lots of times money isn't the real issue. But a 50% raise is hard to counter unless you know you are screwing the employee over.
Actually, Oracle's support stance on Red Hat is based on technical issues, and has nothing to do with the release of the Red Hat Database (PostgresQL). Oracle does not consider PostgresQL a competitor - people that are paying for Oracle are going to pay for Oracle.
Zoward wrote:
"If a business is going to offer a linux version of an existing product, it needs a stable, recognized, widely-used Linux platform to develop for. "
The problem is that RedHat is none of the above. Each.1 upgrade introduces new, beta code that breaks something. Look at a the product support matrix for Oracle on Linux - every new version of Red Hat takes months to be certifed for support and the older versions are dropped from support as soon as the newest is available. On the other hand, SuSE usually isn't on the cutting edge and their distributions are based on mature, stable code - just what businesses are looking for.
Slashdot Mirror
Oracle is a US company based in Redwood Shores, CA.
Siebel is a US company based in San Mateo, CA.
SAP is the German player in the ERP/CRM market.
it will probably work for BSD
syncs my calendar and contacts via bluetooth with my Powerbook (iSync).
I also use the GPRS connections via bluetooth for network access when I'm away from a wifi hot spot. Nice phone.
The fastest way to kill a good product is to let CA buy it.
Actually, Intergraph has a long history of chip and hardware design. They started out as a contractor on the Apollo program and by the 1980's were producing their own VERY power Unix workstations and servers running on their CLIPPER chip.
They did their own Chip design and even did some work on the SPARC for Sun.
Unfortunately, they were also run by a bunch of geeks that didn't know squat about business. That, coupled with them giving up on the Unix market for Windows NT back in 1993 (about 2 years too early) caused them to take quite a fall.
In the process of moving to a Wintel platform, they worked closely with Intel and that is where they got entangled. Intergraph needed Pentiums (and lots of them) to power their workstations and Intel tried to strong arm them into turning over some of their technology. I can assure you that the cache/MMU in the current Intel chip line did in fact come from Intergraph.
You need to do a bit more reading. Sport Pilot will NOT effect part 103. It will mean then end of some of the Part 103 tandem exemptions, but not the USHGA exemption. Why? Well, read the rule and you will see that LSA's are defined as having fixed landing gear - foot launched aircraft (hang gliders and paragliders) can't be registered as LSA. The EAA/USUA/ASC exemptions to part 103 will be phased out while the USHGA will keep its tandem exemption. The USPPA (US Powered Paraglider Association) has also petitioned for an exemption for foot launched tandem PPG instruction, since the USHGA exemption specificly excluded powered flying. This will also be a BIG help to the aero-tow operations that were previously flying fat UL's for towing. They can now fly LSA's and be legal.
If you restate earnings, it automaticly triggers a 10K review by the SEC. Just SOP for the regulators.
I bought one - I got a discount through work and I really like the small form factor. Well, it turns out there are bugs in it and they freeze up or hang on a regular baisis. Just check out the post on the Apple support forums or any other iPod forums.
Mine arrived last week and has yet to work - waiting on the return box from Apple to ship it back for a replacement.
My advice to potential buyers is to wait for the 1.01 release or buy it at the Apple Store without getting it engraved - then you can exchange it there instead of sending it in for repair (= replacement).
Should have know better to buy a v1.0 Apple product - at least other companys give nice little gifts to their beta testers.
Red-lining documents is what they do... although most use a third-party tool called Redliner to do it, so the other parties can't change their comments.
I ordered a new powerbook ($3k+) in December and it arrived on Jan 3. Since my order was placed 2 weeks earlier, I'm not eligible for the upgrade price, and if I would have waited a month, the PB would have shipped with iLife 4.
Just another screwover by the boys in Cupertino. Just ask the guy that lives next door to me that bought a 1.8gz G5 in October - now you can get the same box BUT DUAL G5's for 100 bucks more!
Sucks, but having just switched from a dual boot linux/w2k laptop, I must say I am way impressed with the PB.
Most real software companies but their code in escrow, since many big businesses require it. If the software company goes out of business, the code them goes to whoever is designated in the escrow agreement, usually the customers. The customers are give the code, but not the IP, for the purpose of maintaining the application themselves.
Working as a consultant, I've seen quite a few companies that are supporting an application using code aquired from escrow when the vendor folded.
As a consultant, I've seen MORE than my share of crappy code written by client IT staff over the years. And after a couple of stints working on commerical projects, its often the case as well (but not quite as bad). One execption was code for a CAD application I happen to get a change to review at a previous employeer - very clean.
:)
Of course, the biggest example of this can be see by reviewing the first release of the Netscape code.
Ok, now you are just showing off. Should I really embarass you and let the world know about all the REXX and LU6.2 code floating around a certain state university you had a hand in. Nah, that wouldn't be nice.
I know the principal author, John Bashab, and he is every bit the techie. He may have an MBA, but he was (at one time) very much a geek.
How much of a geek was he? He wrote a disk de-fragger for the TRS-80 model 3 in z80 assembler in the 10th grade - 3 years before Norton Utilities came up with the same thing for the PC.
He may have succumbed to the dark side (management) but he does have the background to evaluate technology.
The only people that really belive that techies loose touch with the technology when they become managers are the ones with no talent for management.
oh my achin' arse
Intergraph used to make its own chips - the CLIPPER line that they used in its workstations. They went to Intel based workstations back in the early ninties and have sold off most of their HW business. The problem with hardware is that the margin is small enough as it is, but Intergraph insisted on making it all in the US, not in Tawian like most.
Some ag prof probably head about all this wireless technology and is trying to apply it to an electric fence.
Roll Tide.
I mean it. I'm a consultant and its surprising how much I can get a sys admin to do for me over the phone, from across the country.
Recent example - we were converting 17 years of production data from a mainframe into a the replacement system. With the volume, we needed an uninterrupted 40 hour window, but the client performed a cold backup of the database nightly.
The process in place says we call the production DBA's (who know us, and are employees, not contractors like us) and they pass official word to the operators in the datacenter.
Well, after 9 hours of loading, the database goes down at 5:00am. We call the prod dba's, and the on-call guy doesn't answer. So I call the ops center. The story I get is that a contractor on another project requested a backup of some critial files stored on the db box. He did this directly with the operator at 11:00 the night before, and the operator didn't even remember his name.
If a simple phone call to ops is all it takes to take the system down, why bother with the standard exploits?
But this approach is VERY profitable. The shareholders could care less about the quality of service, just what it adds to the bottom line. :)
How many times does this have to come up? How many more "Best Books" threads are we going to have?
Yes, but you pay for it up front and it's usually probided my a third party. So instead of a local, smart, motivated tech that probably put your machine together in the first place, you get the lastest round of ITT Techincal Institute graduates from Unisys or Pomeroy.
The second link is entirely more interesting than the initial story. The process that this Russian developed for color photographs back in the early 1900's and the fact that we can now view them is increditable.
Beat's the hell out of Ted Turner's colorization of old movies.
I've been given counter offers at least three times during my working life, and I never took them. Of course, money was not the root cause in 2 of those departures and in each case I was dumb enought to accept the outside offer before approaching management. Once I've accepted an offer, I go with it - no matter what.
As for the reasons listed on the link, the ones that are the most accurate are the ones that deal with the effect of your about-face on your working relationship with co-workers. As a manager, on the 4 occasions when I have offered counters to my employees, I did it as a sincere gesture to get them to stay - all 4 decided to leave anyway. Lots of times money isn't the real issue. But a 50% raise is hard to counter unless you know you are screwing the employee over.
Actually, Oracle's support stance on Red Hat is based on technical issues, and has nothing to do with the release of the Red Hat Database (PostgresQL). Oracle does not consider PostgresQL a competitor - people that are paying for Oracle are going to pay for Oracle.
The problem is that RedHat is none of the above. Each .1 upgrade introduces new, beta code that breaks something. Look at a the product support matrix for Oracle on Linux - every new version of Red Hat takes months to be certifed for support and the older versions are dropped from support as soon as the newest is available. On the other hand, SuSE usually isn't on the cutting edge and their distributions are based on mature, stable code - just what businesses are looking for.