MJ>We are considering converting the system to OS/2 in order to take
MJ>advantage of features such as 32-bit and multitasking.  However I am
MJ>wondering how suitable it is for this and have received a number of
MJ>suggestions that it would not be for the following reasons:

MJ>*  OS/2 is fragile compared with DOS and important data can become
MJ>corrupted if the plug is accidentally pulled without going through the
MJ>proper shutdown procedure.  (This is likely to happen in a retail
MJ>envirionment!)

   No.  OS/2 will take some time to run CHKDSK on a HPFS volume, but your
data is safer than it is on a DOS system.  The time componant is a problem
though.....  If you have access to a network on those machines then RIPL
over a network would be much better, pulling the plug will never lose data,
and CHKDSK will never slow the boot time.

MJ>*  OS/2 takes a lot longer to load than DOS when powering up the
MJ>system and can be a nuisance in retail where you are likely to have a
MJ>queue of customers waiting to be served.

    That depends.  For my usage a DOS system and an OS/2 system take about
the same time to boot (30-40 seconds).  If the OS/2 system has to CHKDSK a
large HPFS volume then it'll take longer to boot.  However OS/2 doesn't
have to use HPFS.

MJ>*  The user interface of OS/2 is more complex than DOS and can cause
MJ>problems if for example the user hits Ctrl-Esc or Alt-Esc and ends up
MJ>in some window other than the POS application.  (It is unlikely that
MJ>we would want to use a mouse for an application which is designed to
MJ>give the look and fell of a cash register.)

   2 solutions.  1 is to use software to disable CTRL-ESC.  Another (one
that I might use) is to simply remove the ESC key from the keyboard.
    If you're running in plain text mode (as might be a good idea for a POS
system then locking out CTRL-ESC etc is simple.


   cya
___
 X MR/2 2.0 NR X After we pull the pin, Mr. Grenade is NOT our friend!

--- Maximus/2 2.01wb