ML>> why did i do it this way? why should we figure out what os we're running
ML>> ea
ML>> and every time we go to slice? figure out the os during program startup
ML>> and
ML>> from there... in your above, you have to decide which slice to use on
ML>> every
ML>> invocation of the slice routine... i see that as inefficient... thus i
ML>> came
ML>> with the decision stuff during program start and just install the desired
ML>> slice then...

ugh, nasty quotes... i'm not going to straighten them out any more ;-(

 CH> Good point.  It would make for better programming.  Once
 CH> someone installs the software are they going to change
 CH> the OS it runs on?  I don't really think they will.

it doesn't matter as the application will install the interrupt vector each
time it loads and uninstall it each time it unloads... i run the same
application across a network under several different OS' with no
problems... it detects the OS and does its thing as needed...

)\/(ark