In article <759735.99156.qm at web61024.mail.yahoo.com>,
Chris M <chrism3667 at yahoo.com> writes:
Apricot PCs. They were MS-DOS compatible, but not
BIOS compatible.
What do you mean by MS-DOS compatible (specifically)?
Think about it.
I can tell you that software that talked to the system through MS-DOS
and BIOS interrupts worked properly, but software that depended on
entry points in the BIOS at specific addresses, or hardware located at
specific addresses failed.
In other words if you "stuck to the API", your application would run.
If you "accessed the hardware directly", your application would most
likely not run.
I've got an Apricot "Microsoft Pack" manual sitting right here in
front of me. It included MS-DOS, "various utilities" (edlin, etc.)
and GW-BASIC. It *is* MS-DOS from Microsoft, not from someone else.
It *isn't* an IBM PC compatible BIOS.
I don't have any detailed specifications on how the hardware differed
other than the BIOS. The earlier assertion that it was miles away
from an IBM PC just isn't true. Peripherals and
drivers from 3rd
party manufacturers worked just fine in all the configurations we
sold
at the store where I worked (the only Apricot dealer in Delaware).
It was the software that was always the problem -- software that
didn't go through the BIOS or MS-DOS software interrupts but instead
accessed BIOS routines through specific addresses.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>