Hi Paul



 PE> /* ttrial - time trial.  How does your environment shape up?

 PE>    Note that this test does not reflect real-life applications,

 PE>    it is only meant to let you know which ballpark to start at.



 PE> RESULTS:

 PE> time     configuration

 PE> (secs)



 PE>    4     9121-260e with sas/c optimized

 PE>    5.2   9121-260e with cobol optimized

 PE>    5.2   9121-260e with sas/c unoptimized

 PE>    6.6   9121-260e with cobol unoptimized

 PE>   24     486-33 in Microsoft C



       14.5   486-66 in Borland C 4 (should translate to 29 secs on

                a 486-33, correct? )



 PE>   31     486-33 in Microsoft C under OS/2 2.1

 PE>   33     486-33 in Watcom C 10.0 under OS/2 2.1

 PE>   34     486-33 in Watcom C 10.0 DOS 16-bit under DOS

 PE>   36     486-33 in Watcom C 10.0 DOS 16-bit under OS/2 2.1

 PE>   48     486-33 in Borland C



Which Borland was this? (I'll try my copy of 3.0 later - I have to

reconfigure a bit)



I tried a few options, and oddly enough, when I told it to use 486

opcodes instead of 286, it *slowed down* by 1.5 seconds...



Cheers



--- PPoint 1.86