ejost@unix.cis.pitt.edu (Ernest J. Obusek) (06/02/90)
I've been using JPI TopSpeed v2 for about 3 weeks now and really like it. It's definitely worth upgrading to. However, I've discovered a couple problems and wondered if anyone else may have solved them already. 1) The PMD module in the Extended Edition is missing its central routine. The documentation describes a routine to call to generate a program image dump, but that routine isn't in the PMD module. And when I try to recompile the PMD module the compiler complains that I'm missing some files. Did JPI screw up or did I? 2) I wrote a routine with the JPI assembler to switch to the VGA 50 line mode. It compiles fine and I made a .DEF file for it and declared the routine as public in the asm file, but when I try to call it from a M2 file (into which it is imported) the compiler complains that it can't find the assembler module. It even ASSEMBLES it when I make the M2 part and then says it can't FIND it!!! I greatly appreciate any help with these problems. And I sure would like to hear about any problems others are having. Thanks! Ernest ejost@unix.cis.pitt.edu ejost@cisunx.UUCP
GRANGERG@VTVM1.BITNET (Greg Granger) (06/04/90)
On Sat, 2 Jun 90 00:39:37 GMT Ernest J. Obusek said: >I've been using JPI TopSpeed v2 for about 3 weeks now and really ... > ditto >1) The PMD module in the Extended Edition is missing its central ... > >2) I wrote a routine with the JPI assembler to switch to the ... On the first one check you *.prj file to make sure that 'include %O_PMD' is in it. This is from the manual so most likely you've already tried it, but... Speaking of the manual what do you think of the PMD section where they continue to talk about C, even though it's clear they mean M2 (I personally think that inside JPI there is a evil C cult plotting to take over and ruin everything ;-). On number two, check your redirection file. These are of course guesses (likely bad ones), but... Greg
Peter.M..Perchansky@f101.n273.z1.fidonet.org (Peter M. Perchansky) (06/05/90)
Hello Ernest: You and I are both having problems tying in our assembly code with 2.00. Although they do not explicitly state so in the manuals, you have to use pragmas in the defintion module to define calling conventions, register usage, etc. JPI will be comming out with new manuals for 2.00 in the near future; hopefully it will be soon. -- uucp: uunet!m2xenix!puddle!273!101!Peter.M..Perchansky Internet: Peter.M..Perchansky@f101.n273.z1.fidonet.org