CompuServe Messages

Well (ptoey, ptoey [feathers drifty to floor]) I have the double dipleasure of crow all over my face – I'm a vegetarian, you see. It seems the 68040.library is a CBM supplied module, not a GVP module. GVP's tech support is of the opinion that the problem is really with lightwave. They say that since the CPU has to "throttle back" (my term) to 68030 and '882 emulation, the resultant demands on the '040 are such that the slowdown I am witnessing in muli-taksing with LW rendering (which works nicely with an '030 but not with the '040) occurs. I asked them about the claims I've seen in print of like the PPS and RCS '040s speeding up LW by 4 to 10 fold over a similar clock speed '030. They maintain it is because the other manufactures MAY NOT (emphasis mine) be using the CBM 68040.library. (This is reasonable as I noticed a 25% speed increase if I removed that library. The problem is that you can't get the '040 into burst mode without that library, or apparently some other home-grown library). Is this a subtle hint that CBM has a lot of optimization left to do in that library? Does anyone know, short of having a beta copy of LW 3.0, how these people that have written to/for various magazines have been able to get such radical speed improvements of LW with a 68040? Some other information I gathered that is helpful but not in the document for the '040 combo board: The J22 jumper should be as in the table on p7 not as in the text on p13 (this enables/disables burst mode). The "GVPCPUCtrl MoveSSP FastROM" needs to be bracketted by "cpu nocache nocopyback" and "cpu cache copyback" statements. This sequence should go at the beginning of s:User-Startup. Note that I found that without the MoveSSP option of the GVPCPUCtrl command, the FastROM option will slow the machine down remarkably. The correct GVPScsiCtrl command sequence if you have a tape drive and a removable on the SCSI bus is -r , -s, DCOFF rather than the -r, DCOFF, -s sequence in the document. This sequence should appear at the end of the s:User-Startup sequence. On the serial port, they claim that it works just fine with at least JRComm, latest rev. It is possible that my problems really lie with AutoPilot and the older MSS terminal programs, but until I can get the latest JRComm to test it I won't know. I've been told that anyone following BM standards will allwo Autopilot to run using alternate serial device drivers. The 2.4 MFC rev works with Autopilot, so I know it is not impossible. Am I a happy camper now? Not yet. Aside from the crow eating exerise, I am still trying to figure out (short of waiting for LW 3) how to get better performance in rendering and how to dump the multi-face card by getting the GVP serial port working.