CompuServe Thread

Razor Upgrade Problems

11 messages in this thread
#158497From: alec jasonMar 12, 1995 9:14 AM
Jamie, I downloaded the 1.0c version and since there were no instructions nor readme file with the zip file I just unzipped it into a subdirectory, went into windows, and did a "run;install". The process appeared to run correctly (although it is very confusing to start the process with a message which states: "Welcome to the RAZOR professional 1.0a upgrade" — when this is actually the 1.0 _c_ upgrade.) When I started Razor, I noticed two things: * In the transitions and effects menus, I now have two copies of everything. * The Razor Player does not work properly. The player image is pixelated and although the preview window works fine, the player will only play a few frames of the entire preview. I read your earlier message about manually installing the new par_mci driver (how is anyone supposed to know about this requirement? Shouldn't there be a message about this in the install process?). I tried to follow your instructions but I found that I do NOT have a "par_mci" subdirectory. I then added the driver from the subdirectory where I had unzipped the upgrade file and it appeared to install correctly but the Player still does not work correctly. I would appreciate any advice. Thanks, Alec Jason
#158803From: Mike MorganMar 14, 1995 12:08 AM
Alac, The new upgrade should put the effects and transitions into there proper sub-directories, check their dates, then delete the files in the main Razor directory (these should be the old ones), you might and should recreate your new libraries with the current trans/effects. The problem in Razor player is that the compression is set way too high!, go into the preview settings and change the compression until you get a decent picture and a fast playback, mine is a 100% and it drops frames as needed (I think that's how it works <G>).
#158830From: alec jasonMar 14, 1995 4:13 AM
Hi Mike, I realize that the Razor upgrade should do all you suggested but the reason why I posted my message is because none of those things did occur. That is the problem. Alec Jason
#158904From: Mike MorganMar 14, 1995 1:59 PM
Alac, I thought that you were having a problem with the Player, there is a report on the problems/bugs you described and they are being worked on for the next release,when, I don't know. Mike Morgan, CAd Forms Inc.
#158932From: david W. mennenohMar 14, 1995 4:34 PM
Alec, I just jumped on this because I'm having similar problems. I found the new MCI drivers to be in the "C" directory. My preview window sometimes works and sometimes doesn't. Sometimes it gets all pixelated and green and doesn't play. There seems to be no apparent rationale either. Also, If I set my final output to DPS .PRJ and then press make final my system locks up tight. Though this seems to only happen if I'm trying to incorporate WAV files. If you figure anything out, or hear anything from Jamie let me know if you would. DM
#159011From: alec jasonMar 14, 1995 11:24 PM
Hi David, Yes, I believe we are having identical problems — except that I haven't had any lockups. I'm surprised Jamie hasn't responded to my first message, he's usually pretty fast. I just got the official update disk and I may try re-installing the upgrade from it. I'll let you know if I learn anything. Alec Jaon
#159441From: Jamie CarrMar 17, 1995 4:29 AM
Alec, Yes, I have been a bit slow to respond, as I'm in England today and Germany earlier this week at the CEBIT show. Anyhow – please let me know if you have any other problems I will be back in the office on Monday. Jamie Carr in:sync
#159023From: James M. MurphyMar 15, 1995 1:20 AM
David, We talked after you posted this so I'll jump in to let everyone know that there's going to be a new copy of the RazorPro files available to registered users on their BBS in about 24 hours with the missing .DLL files that are causeing these problems as well as a couple new "features". <G> At least that's my understanding from todays phone conversation with tech support at in:sync. Hang in there kids, it ain't perfect Yet….Pretty Soon! Though! <BG> Murph'
#159440From: Jamie CarrMar 17, 1995 4:27 AM
David, We have discovered the following: The new DPS software when installed seems to change the AUTOEXEC.BAT incorrectly. I think that you will find if you look in it that the DPS PAR line has changed and that a crucial slash is missing: C:\DPS_PAR\PARINIT /P=C:\DPS_PAR /WIN=C:\WINDOWS This is the correct line and the slash that you may find to be missing is the one that appears immediately before the WIN parameter. Secondly – you may find that there are two copies of the PARDRR.DLL on your system. Search your hard drive for PARDRR.DLL and if you find more than one copy, then find the latest (2/10/95) and delete the others. Put the one dated 2/10/95 in the RAZOR directory. I have contacted DPS about these problems and hopefully this will prevent these problems from turning up with anybody else. Thanks for your message. Jamie Carr in:sync
#160124From: Jamie CarrMar 21, 1995 9:50 PM
David, Have you checked whether you have more than one PARDRR.DLL on your system ? If you have more than one, make sure you delete the others and then leave the latest version in the RAZOR directory. Also how much RAM do you have ? The new requirements with the latest DLL are 24 MB. The green problem sounds interesting – I have not been able to repeat this problem – is it still happening ? Jamie Carr in:sync
#159438From: Jamie CarrMar 17, 1995 4:18 AM
Alec, We have changed the installation program and we have added doumentation to the upgrade so that it gives you all the instructions necessary for a proper installation. If you still experiencing difficulties please get the revised upgrade from the BBS. Jamie Carr in:sync