CompuServe Messages

Jamie, >> 99% of problems that people have when using RAZOR PRO >> and the PAR are related to the system's memory configuration. Very clever wording. At first I thought NO WAY!, but you're not really talking about all the bugs. I was really hoping that this software would be tested before it was released. It would be so nice to spend my hours working on my projects, instead of testing the reliability of software. >> When Windows is set up on a machine it automatically sets the >> virtual memory to be 2 or 3 times the amount of physical memory. >> This is a bug. It should be set to be the same size as the >> physical memory or a smaller size. Can you explain why all of a sudden this is a bug? I've never heard of the requirement that the virtual memory must be the same size or smaller than the physical memory in Windows. I been using larger virtual memory for years now with no problems. Also, can you explain to me why I cannot use QEMM in my system anymore. I have many applications that recommend using QEMM, at one time Microsoft sent out MAX386 with their development system, so I'm wondering why the PAR and RP cannot use anything but EMM386. Here's a feature I can't explain. I copied the example CAMERA.BMP file several times with the program manager (CAMERA2.BMP, CAMERA3.BMP, CAMERA4.BMP). Whenever I load these files (stills) into the Library, the total times are different; and when I place them into the Composition window, I can stretch out the original (CAMERA.BMP) and last copy (CAMERA4.BMP), but not the middle ones. Is there no way to display the filenames of the objects in the Composition window? If the library is empty, how do you know where the files are located? Would it be difficult to drag (or copy) an item from the Composition window to the Library window? When are you planning on releasing the next version? What is your return policy? Thanks in advance, byron engineering arts