phil@sci.UUCP (Phil Kaufman) (05/13/86)
[dummy line] i have a copy of microemacs 3.6 that looks very nice. i have compiled it on a vax under unix 4.2 and it runs fine. i've been trying to get it to operate properly on a pc using lattice. it is a standard ibm pc and lattice ver 3.0. to compile under this lattice i had to remove the "realloc" function defined in line.c since this new version of lattice has a realloc and it does not like two of them. it does compile correctly and i've tried using several models. under small (64k code, 64k data supposedly) it runs just fine but is limited to about 28k of data. compiling unded the D model (64k code and 1 meg data) it runs horribly slow and it will not load the emacs.rc file (runs out of room!). under Large it is slower than D and in either case can't keep up with the repeat key for arrow. so, the question is; what model REALLY works and is there one that works on large files and handles redefined keys in .rc files and is fast enough to be useful? any help would be appreciated.
las@apr.UUCP (Larry Shurr) (05/21/86)
In article <165@sci.UUCP> phil@sci.UUCP writes: >i have a copy of microemacs 3.6 that looks very nice. i have compiled >it on a vax under unix 4.2 and it runs fine. i've been trying to get >it to operate properly on a pc using lattice. it is a standard ibm pc >and lattice ver 3.0. > etc... > >so, the question is; what model REALLY works and is there one that >works on large files and handles redefined keys in .rc files and >is fast enough to be useful? > >any help would be appreciated. Phil (and all else), I haven't tried to bring up 3.6 yet, but I have brought up 3.5. The D model works great iiiiiiffffffff..... you also use the -s switch (or use -mds if you compile with lc). This tells the compiler that you don't want him to "normalize" all pointers and all results of pointer arithmetic. A normalized pointer is one in which the offset is always in the range 0x0 - 0xF and the segment is pointing at the appropriate paragraph. For example: 0900:1237 is converted to 0A23:0007 The advantages include: comparisons between arbitrary pointers are meaningful and addressing (using pointers) > 64k of data. Disadvantage is significant CPU time consumed normalizing pointers. This will cure your slowness problem. D model is probably the best choice for Microemacs. S model doesn't have enough data space. Ditto for P model. L model is unnecessary as the code space for Microemacs doesn't exceed 64k. As for your other problems. I can't help you (yet). Please let me know what you learn about them. Regards, Larry -- ------------------------------------------------------------------------------ BRITANNUS (shocked): Caesar, this is not proper. THEODOTUS (outraged): How? CAESAR (recovering his self-possession): Pardon him Theodotus: he is a barbarian, and thinks that the customs of his tribe and island are the laws of nature. (_Caesar and Cleopatra_, Act II - G. B. Shaw) Larry A. Shurr (osu-eddie!apr!las || 137c South Towne Ln; Delaware, OH 43015)