jharper@euroies.uucp (Jerry Harper) (11/18/88)
I am working on a project where one of our industrial partners has just purchased MSC 5.1. The project's objective (crudely stated) is the development of a production scheduling system using IKBS principles (in so far as there are any). It is obviously crucial that we create runtime "give away" copies that can be beta-tested. I am not very familiar with micro-based Cs'; mainly using UNIX 4.3 C in the past. Using the SETUP facility we have chosen the medium memory model purely by way of getting used to the micro-environment (we are not using Quick C, incidentally). This seems ideally suited to data blocks which are no larger than 64K (correct?), however, Isuspect in down- loading our existing code (those pieces which are down-loadable, that is) we may have to move to the large memory model or the compact model - as is obvious, I haven't spent a lot of time considering these options at present. The MSC package is installed on a 286 with a 287 coprocessor. I have two questions (ideally addressed to MicroSoft or someone with experience of developing runtime systems in MSC): Firstly, what problems can we expect using the large memory model with 32-bit pointers, besides slow execution, when creating runtime versions of our system; Secondly, is it possible to state an optimum runtime configuration using the compact memory model (code no greater than 64K) which will handle the complete 8088 and 80x86 families, Finally, if we remain with the medium memory model (assuming for the moment that this is possible) I repeat the first and second question above. I realise these are fairly general questions but *at the moment* I am seeking general information. You may email replies if prefered. jharper@euroies.uucp