🚀 go-pugleaf

In article <1990Dec26.175746.24208@panix.uucp>, schuster@panix.uucp (Michael Schuster) writes:
%% In article <7366@chorus.fr> mir@opera.chorus.fr (Adam Mirowski) writes:
%% >Wrong! :-)  MS-DOS has IO.SYS, MSDOS.SYS and COMMAND.COM.
%% >IBMBIO.COM and IBMDOS.COM are for PC-DOS.
%% 
%% Wrong again. The names of the MS-DOS hidden files seem to vary among OEM's.
%% Some use IO.SYS and MSDOS>SYS; others, perhaps for aping IBM more completely,
%% use IBMBIO.COM and IBMDOS.COM. Take a look, for instance, at EPSON MS-DOS;
%% they use the IBM conventions for hidden files.

I know this. That's why I've put the smiley. In fact, on most DOS I have used
there were IBM*.COM files, although only MicroSoft was mentionned in the
copyrights besides the OEM.
I have once found a program, named PCLAN.COM (on a Toshiba) which only purpose
(after a disassembly) was to create those IBM*.COM files in the root directory
of the A disk. But IBM PC-LAN program doesn't need to see those files to run,
as I have check later. Could some programs be allergical to non IBM*.COM
hidden files?

The general question is how is an OEM DOS version eleborated. Which part
is doing this? Who is choosing the names and the code repartition between
IBMBIO/IO and IBMDOS.COM/MSDOS.SYS (IO.SYS is much smaller than IBMBIO,
MSDOS.SYS much bigger than IBMDOS.COM)? And the last but not the least,
how much does it cost for an OEM to have "it's own" DOS?
-- 
Adam Mirowski,  mir@chorus.fr (FRANCE),  tel. +33 (1) 30-64-82-00 or 74
Chorus systemes, 6, av.Gustave Eiffel, 78182 Saint-Quentin-en-Yvelines CEDEX