#PVR under WinNT
5 messages in this thread
Mike,
Have you (or anyone else) actually installed/used a PVR with the WinNT s/w?
I got a set of early beta NT s/w (v0.01), but still can't get the system
running on my PCI bus NT machine. The "dpspvr service" fails with an Event Log
error "microcode write failure" followed by an "incorrect parameter" error.
I've also had an error stating "can't create a file when that file already
exists".
To check the rest of the system I pulled another machine apart (one without a
PCI bus) and fitted its HD containing Win3.11. Everything worked fine with the
standard Win3.1 PVR s/w, so I know the MB, PCI slots, etc are OK.
Any idea what the "late Beta" PVR version number is up to? Any other testers,
please contact me…
– Martin Kay, ZEN Computer Services
>I got a set of early beta NT s/w (v0.01), but still can't get the system
running on my PCI bus NT machine. The "dpspvr service" fails with an Event Log
error "microcode write failure" followed by an "incorrect parameter" error.
I've also had an error stating "can't create a file when that file already
exists".<
I haven't received my PVR yet so I can't say what is causing your problem, but
did you install the PVR NT software while logged in as administrator? Some NT
software I have, especially software that can run as a service, needs to be
installed under the administrator account.
Hi Tim. I have installed the NT PVR software at least 25 times now, and I am
becoming an expert on it <<GRIN>>. We had Perception machines all over our
booth at SIGGRAPH (in:sync) There are a few things you need to check out.
First of all, the latest version of the software I know of for NT is 1.38. You
should try to get the latest version from where ever you got the last one.
There are a few things that could be wrong. An incompatible HAL or BIOS or BUS
speed (which since it works under 3.1 this !probably! isn't the case.)
Misinstalled drivers could also be the culprit (they misinstall themselves!).
In your WINNT35/SYSTEM32 directory there is a program called "regedit32.exe".
Run it. It brings up the equiv. of the WIN.INI in windows 3.1. (but much more
complex and more organized). Click on the hkey_local_machine window. Now
select current_user (I am doing this from memory so I could be missing a level
here) and then choose services, and then find DPSPVR. Check through the lists
and look for
path's that are incorrect. If you find something that looks wrong, double
click it to change it. It will mostly look like gobbledy gook, but just look
for the path's. This is generally where the trouble is.
If all else fails, you can try deleting the entire "folder" and re-installing
the PVR software.
Hope this helps.
Eron
in:sync technical support
Eron,
Thanks for the advice about the Registry path settings. I'm already familiar
with the Registry Editor after I accidentally created an unwanted WGPO and had
to remove it. The only path name under services/dpspvr correctly pointed to the
DPS_PVR directory, so I suspect I'll be better off just trying to get v1.38.
This whole kit has been supplied direct from DPS UK, and whilst they're as
helpful as they can be, they don't always seem to be kept up to date from HQ.
(Coupled with which, the two main staff members are both away at present.)
Knowing which version to ask for means that I'm less likely to be fobbed off
with another earlier version 8-).
Meanwhile, I'm looking forward to seeing your new model Razor s/w which takes
advantage of the PVR. I have a passing aquaintance with Razor Pro (even sold a
couple with PAR systems), but it couldn't hide the fact that the PAR was never
intended as an editing system. The PVR is another matter, and with a good front
end looks like the basis for an excellent edit system. Where are you up to with
it?
Regards,
Martin Kay, ZEN Computer Services
Martin,
>> I got a set of early beta NT s/w (v0.01) <<
Not sure where you got this version, there have been a few updates since then.
The software is still in beta and the final version will be released soon.
When, I'm not sure. I can say that it will be worth the wait!
-Mike