CompuServe Thread

#PAR access on WIN95

15 messages in this thread
#190062From: Don NellSep 9, 1995 8:25 PM
Jack, I came up with a temporary fix that you might try until this problem with Win 95 and the PAR is solved. The following is a copy of the thread "PAR + Win 95 Working" that I started a short while ago. ******************* To all, I'm not sure how many PAR users will benefit from this information, but I'll post it anyway. Like many of you, I installed Win ' 95 only to find that I couldn't use it with with the PAR drive and PARVCR.EXE. Well , there is way. I found that if you edit the PARVCR.INI file located in the Windows directory and manually write in the files you want to use under the [Recent File List] section, you can then open PARVCR while in Windows 95 and click on the files directly (dont use 'Open'). For example, my PARVCR.INI file looks like this. [Last Window Pos] Left=167 Top=274 Width=320 [Preferences] Rec Frames=300 Rec Prj=D:\DPS_PAR\REC_AD.PRJ Rec Ani=G:\REC_AB.ANI Rec Wav=D:\DPS_PAR\REC_AD.WAV Rec Name=recd_AAB [Recent File List] File1=G:\FIRST\PROJECT1.ANI File1=G:\FIRST\PROJECT2.ANI When I run PARVCR.EXE and click on 'File', I can click on either 'project1.ani' or 'project2.ani'. If you don't see the section [Recent File List], simply add it in. I have only tried this on one single computer, but I would be interested to know if this works for anyone else or if there is a better way. Let me know. Also, I don't have Razor Pro yet, but maybe a similar solution could be implemented using this technique as well. Thanks Don ( And I thought computers were going to make things easier ) *******************
#190130From: Jack WalshSep 10, 1995 12:11 PM
Thanks Don I'll give it a try. Though I'm considering moving back to WFWG3.11 just because most of my graphics software works! Jack
#190201From: A. CarrerasSep 10, 1995 10:36 PM
Don, I have both the PAR and PARVCR working fine in Win 95. I'm curious to know how your setup is different than mine. This is what I did to install it and it was quite straightforward. I had it setup for DOS, so that it would run in DOS just like it does, then when I got into Win 95 I used the PAR install through RUN. I got a little blurb about something, can't remember what it was, from Win 95 asking if it should correct the problem, I answered yes, and it brought the PAR up full screen. Works fine. Then I installed the PARVCR drivers the same way. Win 95 created a new folder and everything seems to be working. The only trouble I've had, was at one point when I was intergrating networking, it was listing the C: drive directory as the Master Drive when I clicked on F: which is my master drive. This seems to have been resolved once I got the network straightened out. Hope this helps and if nothing else maybe you can give it a try… Alex
#190260From: Jack WalshSep 11, 1995 10:05 AM
Alex, Are you able to have sound play when triggering the PAR with Media Player in Win95? Do you use Razor Pro w/ Win95 and does it access your PAR drive files? These are a couple of problems I haven't been able to solve. Any help would be appreciated. Jack
#190400From: A. CarrerasSep 12, 1995 3:42 AM
Hi Jack, Sorry to say I don't have a solution as I have neither. Just a straight PAR. One interesting thing I ran across that may help you track down some unresolved problems is Win 95 on my system allocates an IRQ and host drive for an IDE/ESDI standard controller. This is on a Neptune P90. I thought about that for quite awhile before I realised it had to be the PAR drive that it was logging in. Caused problems with my network endlessly. Other than that I don't know what to tell you. The full screen PAR interface works fine. The PARVCR seems to work o.k. except that I don't know about storing ANI files as it doesn't seem to want to store them to the Master drive. The other oddity I've noticed is that Explorer registers both the Root C: and the Master drive of the PAR with the same directories. In the PAR interface this is not a problem but its kinda odd in Explorer. Theoretically you should be able to click on an ANI file and have the PAR interface come up ready to play. Maybe in the next revision. Alex
#190569From: Jamie CarrSep 12, 1995 11:26 PM
Jack, Sorry Razor PRO can not access the PAR under Win95 for the same reason that it couldn't access the PAR when 32 bit file access was turned on in Win 3.11. Although there is a switch to turn off 32 bit file access in Win 95, it doesn't seem to fix the problem. Jamie Carr in:sync
#190920From: Mike Langieri/CT&MASep 14, 1995 9:40 PM
Jamie… Can you give us a little details about Speed Razor and it's relationship to Razor Pro… as well as it's ability to operate under W95 with a PVR? I haven't bought the deal yet, but will in a week or so. \\\. ========================= >-==<MIKE(>=– >-==*- /
#191407From: Jamie CarrSep 18, 1995 11:14 AM
Mike, There are no drivers for the PVR or the PAR for Win 95, and DPS have not and my understanding is that DPS have not announced that they will support Win 95. The most basic difference between Razor PRO and Speed Razor is that Razor PRO has to render all projects into a single final file before it can be played back on the NTSC monitor. Speed Razor works in a different way it doesn't need to render a single file in order to be able to play back the project on the NTSC monitor, it can do straight cut editing in real time, and can render transitions and effects at three times the speed of Razor PRO on the same hardware, and some transitions are sped up by a factor of 44 times. There are a lot of new features in Speed Razor, it can work with thumb nails and not have to use the final files, it has machine control which works with professional decks, it can do batch capture and can recapture, it has a lot of features which allow it to work with the PVR directly, ie it supports its PVD file format. There are a lot of other features which are listed on our web site: http://www.in-sync.com/in-sync Jamie Carr in:sync
#190277From: Don NellSep 11, 1995 11:10 AM
Alex, Yours is the first instance I've heard of getting PARVCR.EXE to work under Win 95. Everyone including myself that I'm aware of has had problems. Every time I click on my PAR drive, I see my C: drive. I'm pretty sure it has something to do with the network setup but I'm just not sure what. Since my computer is not physically on a network, I don't understand why I'm having this trouble. I have no trouble running PAR.EXE under DOS. I am using Win 95's TCP/IP dial up networking to call into the Internet by modem. Maybe that's where the problem lies. If you have any ideas, please let me know. Thanks Don
#190401From: A. CarrerasSep 12, 1995 3:42 AM
Don,
#190402From: A. CarrerasSep 12, 1995 3:42 AM
Don, PARVCR.EXE does not fully work on my system but PAR.EXE does. The problem with PARVCR is that it can't write to the Master drive. The problem is also apparent in Explorer where both the root and master directories appear identical. In PAR.EXE I can see the correct directory and I can access the Slave as well. Everything plays fine in PAR and the PAR Initializer module works as well. I haven't tried pulling in frames. Win 95 assigns an IRQ and an IDE controller drive to the PAR which I believe is causing the problem. Mine is assigned an IRQ of 15 which did cause problems for the network card. Sorry about the confusion on this. I thought your main interest was in being able to play back ANI's which you can do with the PAR.EXE Alex
#190462From: Don NellSep 12, 1995 12:32 PM
Alex, I use PAR.EXE in DOS to construct and playback the .ANI files without audio, but use PARVCR.EXE in Win 95 along with the media player to play them back with wave files or CD audio for recording to video. Fortunately, I don't have to rely on Win 95 to write to my master drive. I sure hope DPS or MicroSoft come up with a fix pretty soon. Don
#190602From: A. CarrerasSep 13, 1995 8:43 AM
Don, >> I hope DPS or MicroSoft come up with a fix pretty soon. << I was able to disengage the PAR from the Plug and Play Bios by unchecking the Configuration box which effectively disabled the IRQ and base address setting which Win 95 assigned the PAR. This freed up the interrupt but had no effect on PARVCR's ability to read the PAR's directory. Which means its probably a PAR driver problem. This doesn't help but thought you might be interested to know. Alex
#190867From: Don NellSep 14, 1995 3:23 PM
Alex, Thanks. I've got more bad news. I talked to the people at In:Sync yesterday and they haven't been able to get it to work with Win 95 yet either. I haven't tried DPS yet. Don
#191166From: A. CarrerasSep 16, 1995 5:02 PM
Don, >> more bad news. << I saw some comments to that effect mentioned here as well. NT will hopefully work. I'm discovering that certain apps run better in Win 95 and NT etc. so I guess its the shape of things for the present. Hope they find a solution for you soon. Alex