New Driver install prob.
26 messages in this thread
Dave- I d/l'd your new drivers, unzipped them and ran the install program. My
problem is that while in install, after the ? about where the TBC is located
and answering P for par I get an error from pkzip that the "file at line No is
not found. I guess I've got a bad zip file. I'll try d/l'ing again. Has
anyone else had this problem? I can manually unzip Par_all.zip and everything
checks out, but when I copy those file into my DPS_Par dir and run par.exe I
get some really weird things happening (ie. can't delete files, can't make new
projects, etc.) so I assume something else needed to be setup in the install
program. If there is a manual workaround, please let me know. The new stuff
looks exciting and I'm anxious to try it.
Thanks, -Mark
Several people have commented that they downloaded it successfully and it is
working fine.
Dave DPS
Well, this guy's not alone because I'm have the exact same problem! I have
tried to do it manually and got nowhere. I'm wondering if the install software
requires the presence of the TBCIV. I don't. Please help. I'm really looking
forward to using the new software. BTW, why were there no installation doc's
included?
-Mitch
Mitch, I have found that the new PAR software can be easily installed *without*
the Install routine by simply un-zipping the files in the appropriate
directory. I reccomend this method to anyone having problems with the Install
routine.
As it is still beta software, you should back up your old PAR directory first.
-Alan
Alan- I tried doing that and then running the program but I get dumped out with
a "Fatal Error: Communications timeout". I assume that means that the
software is not finding the par or the tbciv. Is there a manual way that I can
tell the software that I have both the TBC and the par? I'm sure one of the
init files has it but I'm not sure where or what to change. Any insight?
Thanks, -Mark
IS this the DOS software or the Windows software, Mark?
If it's the DOS program, then it sounds like it's not in a directory that the
environment expects. Are you running PARINIT, PARDRV, and PAR.exe all from the
same directory? Are the Path statements correct? I believe that, once you find
the PAR (and PARINIT should be doing that), the PAR finds the TBCIV through the
connector cable. Run PARTEST and see if any of the initialization tests there
fail.
-Alan
Alan- I have all of the software in c:\dps_par. I've tried removing parinit
and pardrv from autoexec.bat and running them manually. I run parinit, pardrv,
and par.exe in that order. Everything is fine until Par.exe is run. I get the
Pharlap screen, a pause, and then Fatal Error:Communication time out. I've run
all of the Partest test and everything test fine. I'm beginning to suspect
something with Pharlap mainly because I'm at a loss as to what else it could
be. I noted in an earlier message that you said you were going to contact DPS
on Monday… Is there a tech support # for them or do you just have a
connection? I've been unable to find a # in my manuals. If you do talk to
them, I would appreciate it if you might mention this problem and see if they
have any ideas. The line that craters in the Install program is immediatly
after the question about whether the TBC is connected to Com1, Com2 or Par. I
select P for par and it obliterates. I'm wondering if that needs to set
something in one of the INI files to tell it where everything is. Oh well,
back to the old version. Thanks, Mark
Hmmm…
DPS's number is 606/371/5533, and they'd be glad to help you out, I'm sure.
Dave White is a good person to talk to.
I suspect at this point (from the number of folks that couldn't run it) that
the Install program is not quite right yet.
In the mean-time, what memory manager are you running? I know that they are
reccomending DOS 6.2/MemMaker, but it is running great with my QEMM setup, and
it might be worth it to try a few different memory manager configurations, as
the new software *does* use a Phar Lap DOS extender.
Best of luck, and sorry I wasn't of more help to you, Mark.
-Alan
Alan- Thanks for trying. I'll give them a call Tues. I'm sure that it is
something simple that I just don't have set up right on my end. The strange
thing was, the first time I installed it I forgot to reboot my system and so I
was running the 1.14 driver. The software ran, but there were some quirks like
I couldn't delete files, etc. So then I rebooted and that's when I've been
getting tossed out. Thanks again for trying. I'll let you know what I find
out. -M
Mark:
I too had problems with the new PAR install. What I finally ended up doing is
creating a temp directory on drive D: and unzipping _everything_ there. Then
do the install to dps_par on drive C:. Then copy over to drive C: all the
files that the install didn't copy over for me.
This worked great, everything saw everything else, it all works great! I
tested out the GPI trigger, right on the money, except that the readme.doc
states that it is calibrated in minutes:seconds, it is actually seconds:frames.
Greg Pyros
Greg,
I just put in the PAR and went through the usual inane, incomplete, and flawed
software installation crap. After all the hoopla about the PAR, I guess I
expected the installation process to be better what you usually get with cheap
hardware. I was wrong.
I get the same "Fata Error: Communication Time Out" message as Mark reported
everytime I try to start par.exe. I've been through all the tests and
formatted the drive, etc, etc many times.
DPS might also properly label the new software: it is NOT new version; it is an
UPDATE. After a long time spent trying to just use the new software, I finally
realize that you must first install the old software. No mention is made of
this fact anywhere.
Any ideas?
Alec Jason
Alec- Im' sorry your having trouble, but at least now I know I'm not crazy. I
was beginning to think I had really botched something up. I'll keep messing
with this and if I get something to work, I'll be sure to post you. -Mark
Mark,
Thanks but I tried your technique but its still dead. I've tried everything
there there is but par.exe still won't load.
Alec Jason
I have found a possible workaround to this problem. See post entitled
"PAR FIX Comm Timeout!!"
— James — MAP —
Alec:
I'm getting different results: I renamed my old PAR directory and just
installed the new version I downloaded here, no problems after I realized that
I just need to unzip the files, no reformatting, it just worked!
Is PARINIT.EXE working correctly? What about PARDRIVE.EXE? Do not load these
automatically, go to DOS and run them by hand one at a time to let us know
where exactly your problem is. If these two work PAR.EXE should run OK, too.
Since this is a new installation for you, maybe also try PARTEST to check out
communications, addresses, etc.
Greg Pyros (and I thought I got out of the hardware/software support biz!)
Greg,
Yes, everything loads fine and the partest goes smoothly with EVERY test and
reset and download and format feature appears to check out OK.
I've tried loading the drivers manually and they show no problem. Its just with
the Par.exe that I have the problem: "Fatal Error: Communications Timeout."
I've tried every permutation of installing, unzipping, starting with the old
software to new software, no software to new, etc.
Thanks anyway,
Alec Jason
P.S. Yes, it sure it good that you got out of the hardware business —
otherwise you'ld be having to read desperate messages with unsolvable problems.
I saw that too but [GPI] but noticed the timing of the last two digits only
went to 29 before starting over at 00. Who ever heard of 30 seconds per
minute? <BG>
Seems like you used a similar install method as I. It was dumb luck for me. I
just unziped everything in the DPSPAR dir and didn't have any problems. Is is
possible that when using DPS' install program one MUST be starting from
scratch, like a virgin install with unformatted HD and all? But if one just
wants to upgrade the install won't work. ???
I would suggest those having problems reinstall the older software and verify
everythings back to normal, then, pkunzip the update in the DPSPAR directory
allowing the PKUNZIP to overwrite all duplicate files. It worked for me.
PS: I won that bid to take perfectly superb crisp betacam SP shot with a
studio camera and make it look like an old time movie. I ordered the IPAS from
Digimation on Friday. I will never figure out this industry! I originally
suggested shooting the scenes with an old Kodak 8mm movie camera and videoing
the projected screen after winding the film through a pile of dirt from a
vacuun cleaner bag but everybody just looked at me kind of dumb struck. <BG>
Don
Check out the "The Stand" by Steven King. There are sections, every now and
then, which appear to me to be taped . The difference in the look is
incredible. The tape is very hard and contrasty while the film is much softer.
Interesting effect. Good luck on the project.
TedB
!^NavFont01F0007MGHHGE4FA4D
Don:
Congrats on getting the project! Let me know how OLDMOVIE.IXP works for you!
The next one to try would be our FILMGRAIN.IXP to fuzz it up even more!
Greg Pyros
Greg- I'll keep working on it. I'm going to try some different base addresses
and stuff today… really just grasping at straws, but hey it's a holiday and I
doubt if DPS is open til tomorrow. What I really need to know now is what
triggers a Fatal Errror: Communication time out. Whatever that is is what's
wrong with my setup. Thanks for the advice. -Mark
RE:
This worked great, everything saw everything else, it all works great! I
tested out the GPI trigger, right on the money, except that the readme.doc
states that it is calibrated in minutes:seconds, it is actually seconds:frames.
———————————————————–
Oops, youre right, the GPI should be labeled Seconds:Frames, not
Minutes:Seconds.. Thanks Greg.
I did try to copy the new unzipped files to a new directory ( the install seems
to be for TBC users only) but still had complications. I took your advice and
backed up my PAR anims (needed to anyway) and did a format of the drive. Now
the new software runs fine. This should be ammended to the docs. Thanks for
your help.
-Mitch
Great, Mitch. I'm glad it's working for you.
-Alan
Mitch and all:
I saw your original message and though you might have overcomplicated your
installation of the upgrade.
I was the second person to download it and the installation went smoothly.
This is the way I did it.
I took the zip file and unzipped it in its own directory. Then I took the
second zip file that appears and moved it to my DPSPAR dir.
I then unzipped it and allowed it to replace any common files from the previous
ver. I did do a tape backup of the directory first should I need to start over.
After that I rebooted the computer and loaded my driver and then the par
software with the same startup batch file as before and everything loaded
correctly. I did NOT use any "install" command. Maybe this is not the correct
procedure but I'm operational with no problems.
Hope this helps.
I'm having the same problems as you described. Please let me know if you
figure it out.
-Mitch
Mitch- I'll let you know if I get it working.
-Mark