Measekite would have us believe that "compatible" is a meaningless
term. He sites the early days of IBM and IBM compatibles as an
example.
Compaq was the first to offer a "compatible".
http://oldcomputers.net/compaqi.html
This was done by reverse engineering the roms in a clean environment,
mainly one group writing out the specifications, and the other group
who had no prior exposure to the roms cashing out something that would
act the same. The result was actually something 1/2 the size of IBM's
roms. To assure as close to 100% compatibility, compaq licensed basic
from Microsoft.
Phoenix did the same thing, and hired people who had NO exposure to
the 8086/8088 processors intel offered. This and a huge insurance
policy discouraged IBM from suing them to oblivion. Phoenix didn't
sell PCs, they sold ROMs to PC manufacturers, and thus put them in a
position to be the defacto PC standard.
Now the meaning of IBM compatible was not something clear cut as there
were various levels of compatibility. At the very least, you could
expect an IBM compatible to run MS-Dos. To assure something was
compatible with your application before 1988, you had to depend on
reviewers. The main benchmark was whether it ran Lotus 1-2-3, an
application developed in assembly, and MS Flight simulator.
Measekite would have us believe that because clones didn't offer IBM
basic roms and supported the IBM terminal network standard of the
time, they were not trully "compatible".
BASICA - It's true that there were "some" applications that were keyed
to the IBM roms and designed not to run on clones. I don't know This
approach was pretty much abandoned in 1987, though the last system
shipped with basic roms was 1990. However as this was Microsoft's
basic, they released GW Basic for MS-dos, so clones could run anything
written for BASICA on an IBM.
3270/5250 terminals - The IBM PC didn't ship with 3270 support except
for the 3270 PC, which was just a regular XT with 4 cards to support
the terminal network. As it turns out, you could take those cards and
put them into a clone at least according to one source. IBM terminal
emulation was supported by a number of companies.
If you bought a PC in 1987, and you were trying to decide between a
clone and an IBM, the big question you need ask was whether the clone
ran the software you wanted. You had to depend on the reviewers to do
this. After 1987, it was a moot point. Your average clone had either
a BIOS from Phoenix or AMI (Unsure when Award was formed) and was
compatible with the old IBM save ROM Basic which was abandoned by this
point. It was these machines that had the least issues running off
the shelf software. It was in fact IBMs that had more issues with off
the shelf software as
1) The PS/2 wasn't compatible with the hardware
2) The BIOS wasn't compatible
So what does this mean? IBM Compatible had a meaning. For the most
part, it meant it could run MS Dos. Software compatibility wasn't
always 100%, and there were a number of big company clones that
weren't. Before 1987 you had to depend on reviews to determine how
compatible an IBM Compatible was. After 1987, the clones set the
standard.
[Why Measekite is full of ****]
He thought that he could throw out 3270 terminal support as a defining
factor of IBM compatibility. The sad truth of the matter is the IBM
PC/XT/AT were not compatible AT ALL with 3270 terminals. The keyboard
was totally different, screen support was different. I don't know
what sort of CPU was used for 3270 terminals, but that too was
different. First generation XTs had 4 full length ISA cards to handle
3270 support. This was later cut down to 1 card.
But Measekite as always depends upon someone having no clue what he's
talking about and as such is able to prove his point. I freely admit
I know very little about 3270/5250 terminal networks. The main thing
I do know about them is if you need it, you talk to Attachmate for a
PCI card, adapt your mini/mainframe to support ethernet, or build a
controller that will take 3270/5250 telnet sessions and pipe that data
to and from the mini/mainframe.
But Measekite's point is if you needed to hookup to an IBM mini/
mainframe, you needed an IBM. That is bullshit. The service contract
might demand it, but there was a ton of 3rd party support. But this
hardly qualifies as a defining factor of compatibility because a true
blue IBM PC didn't support 3270. Whether you had a real IBM or a
clone, you had to get cards and software to emulate 3270/5250.
http://publib.boulder.ibm.com/infoce...twork_261.html
http://74.125.45.104/search?q=cache:...lnk&cd=6&gl=us
[What does this mean as far as ink goes]
Compatible ink means exactly as it states, ink that works with a given
printer. As with 1980's PCs, you do have to depend on reviewers to
determine how compatible an ink is with your printer. However, just
like the PC era, it's possible to make a superior product to OEM.
However the main point to bulk ink is the lower price, and as such
they tend to not be as light/gasfast as OEM.
There is also generic ink that is ink designed to work with a wide
range of printers. Often this stuff "works" but may not be color
matched to your model, or might not operate properly.