CompuServe Thread

#PAR/MCI … (Razor)

13 messages in this thread
#160286From: Christophe Van OyenMar 22, 1995 4:59 PM
I just downloaded the PAR MCI drivers and have the following inquiries: I am in PAL land and I have for PAR startup: PARDRVP.EXE loaded, however MCI driver does not recognise this specific PAL driver. I then changed my startup and started with the regular PARDRV.EXE so not the PAL specific version. Well everything seemed normal animations still play perfectly will this driver work without a hitch for PAR PAL version (1.50). With this driver MCI works perfectly under Windows and WOW even this is great already. However in MCI configuration I can only select NTSC playback options????? Do I need other MCI drivers for PAL????? If so who has them could they not be uploaded here as well in case this is so. I'm still waiting to acquire Razor Pro due to the many bugs I hear about on the forum. Is there anyone that has Razor Pro working flawlessly at this time and witch version is it. And if Jamie Carr is listening when do you think Razor Pro is going to be 100% stable. For the moment I'm not in the mooth for solving conflicts I have enough trouble with Memory eating AutoCAD13 for Windows. Christophe Van Oyen
#160783From: Jamie CarrMar 24, 1995 9:19 PM
Christophe, In order to use the PAR in PAL you need to run the PARDRVP program not the PARDRV file. The P denotes PAL. It can cause problems if you run without the NTSC version. The new MCI drivers (version 1.1) work great and do work with PAL, I was demonstrating this in CEBIT last week and it worked flawlessly. Today we released RAZOR PRO 1.0d. I believe it to be extremely stable. After demonstrating it at CEBIT for a week without any problems I feel very confident saying that. There are many users on this forum who are using RAZOR PRO without any hitches. I believe we have solved every problem that we have been told about. Most of these have been due to configuration problems which we have almost eliminated due to improved installation and the ability to set up PAR parameters from within RAZOR PRO. I encourage those users who have RAZOR PRO to download the latest version from the BBS. The BBS is now working at 57600, protocol N 8 1 Full duplex, hardware compression. The download takes 4 minutes. With 1.0d we have added improved STL support and we have fixed a problem with reversed field order on the iris transition. At NAB, you will see samples of projects done with the RAZOR PRO including a 1 1/2 hour movie complete with sophisticated RP effects ! Jamie Carr in:sync
#160815From: Christophe Van OyenMar 25, 1995 7:08 AM
If I have the PARDRVP for PAL active Windows does not see the MCI drivers uploaded here this week???? If I however use the PARDRV for NTSCS with my PAL board everything uptil now seems to work even the MCI drivers under windows???? Do I need specific PAL MCI drivers????? Christophe
#161004From: Jamie CarrMar 26, 1995 5:41 PM
Christophe, Just for the record, PARDRVP and the MCI drivers were created by DPS. I will try and help you to sort out the problems you've experienced based on my knowledge of how these programs work. PARDRVP and the MCI drivers are compatible – I was using them in Germany at CEBIT without a hitch. The reason why the MCI drivers are not coming up must be related to your setup. Check that the PARINIT line in your AUTOEXEC says the following: C:\DPS_PAR\PARINIT /P=C:\DPS_PAR /WIN=C:\WINDOWS The forward slash before WIN is very important. It is not recommended using the PARDRV file with PAL because there are differences (I can't remember them right now but it can cause you to save the files to the wrong size.) There are no specific PAL MCI drivers. The regular MCI drivers work fine. Also check the size of your virtual memory swap file in Windows – (Control Panels>386 Enhanced>Virtual Memory) and make sure your virtual memory is no larger than the size of your physical RAM. Jamie Carr in:sync Jamie Carr in:sync
#161136From: Christophe Van OyenMar 27, 1995 11:26 AM
I have got the PARDRVP running with MCI drivers. I reinstalled the PAR software, it seems probably something in the PAR.INI was wrong???? Because batch file and windows where all OK. One problem however we keep getting NTSC speeds in PAR configure under windows although it runs with PARDRVP and plays back and 25FPS it is only selectable as 30FPS??? I'm hoping to acquire Razor soon, I just let other people deal with the bugs this time, I needed a break and it seems razor is getting up to speed, although I know had to tackle with Acadr13 bugs, although it is starting to get solved??? Christophe
#161230From: Jamie CarrMar 27, 1995 8:07 PM
Christophe, I am not sure about your problem being only able to select 30fps, that sounds like a problem for DPS. I haven't seen anything like that. Jamie Carr in:sync
#161285From: Christophe Van OyenMar 28, 1995 9:14 AM
Well I am not the only one seeing this, although it is not an operational problem evrything works ok. It has to be somewhere in the MCI drivers, because the PARDRVP works. So if Brick Eksten moves along maybe he has something to say about that. Christophe
#161602From: Fremer HuijgenMar 29, 1995 6:19 PM
Christoper, i'm also in Pal land and stumbled over the same problems. The new MCI drivers wouldn't work at all (didn't try pardrvP; never saw it, we do have the 1.50 upgrade) but I can see the Windows Parsetup with NTSC frame rates.
#161685From: Christophe Van OyenMar 30, 1995 5:48 AM
You should use PARDRVP, the 1.50 install does let you choose between PAL and NTSC so the right driver is automatically installed. However the NTSC MCI showing seems to be just avisual bug because everything works and plays OK under windows. I will E-mail Brick Eksten about this myself, I think it would be very easy to change this, because it only seems to be something with the visual interface showing wrong Video Type, but playing OK. Also do a couple of reinstealls, also first time MCI is installed then Windows gives an error in module krnel386, you have to quit and restart windows then it all works fine. Christophe Van Oyen,
#162603From: Fremer HuijgenApr 3, 1995 6:55 PM
Thanks, will try.
#161261From: Mar 27, 1995 11:29 PM
Jamie: >> Just for the record, PARDRVP and the MCI drivers were created by DPS. Just for the record, PARDRV (both NTSC and PAL) we created by Pyros Pictures, specifically by Gus Grubba, for DPS. :^) Greg Pyros
#162063From: Jamie CarrApr 1, 1995 12:51 AM
Greg, sorry for the misrep… Jamie Carr in:sync
#162269From: Apr 2, 1995 2:48 AM
Jamie: No problem! Just keeping you honest! <bg> Greg Pyros