#PAR – access denied
21 messages in this thread
I'm having difficulty recording information to my PAR drive. Up until
recently, everything has been great. For the last few days when I attempt to
render to it, I get the message "Error writing to .TGA file". I've checked my
setup, reseated the card and connections, used the old software and the new.
The par passes all it's tests and yet the disk will not accept input. The disk
is recognized by the computer. As a test, I attempted to copy an ASCII file to
the PAR drive and got an "Access denied" message. I'm sure this is pilot error
but I'm out of ideas. Any help will be greatly appreciated.
Dave:
"Access denied" usually means that there is an existing 'lnadlocked' animation
of the same name previously on the drive…
What versions of everything are you using? PAR.EXE. PARDRV.EXE, PARINIT.EXE?
>> As a test, I attempted to copy an ASCII file to the PAR drive and got an
>> "Access denied" message.
I just re-read your message – the PAR software will not allow you to copy
anything except Targa files over to the PAR.
Greg Pyros
Greg:
I've written to you about this before but I've got the problem again. I'm
using 3DS r4 with PAR software 1.5. The PAR passes all tests in the PARINIT
program but when I try to record animation to it, I get a "write error on .TGA
file" message. A single frame is transferred to the PAR drive but that's all.
My Anim/Still selector is set to Anim, CHR FILTER is on, Q-Factor and Block
Limits are at default settings.
When I wrote to you before I somehow managed to get it to work. I don't have a
clue how *that* happened. If I render to a non-Par drive it is possible to
import the frames successfully to the PAR. I'm stumped.
In November I upgraded to a Pentium and installed the PAR card and HD myself.
I don't think the problem I'm experiencing is related to installation but I'm
willing to consider it. I appreciate your help.
-Dave
Dave:
Sounds like you are doing everything correctly! I can't see anything out of
the ordinary from your message. When did it stop working?
What does DPS have to say about this?
Greg Pyros
>>a "write error on .TGA file" message
I got this same error message when I accidentally left render alpha on during a
work session yesterday.
John Stetzer
JWS
John,
>> I got this same error message when I accidentally left render alpha on
during a work session yesterday. <<
Ah! This might explain a problem I had with a series of TGAs a friend gave me
on a Bernoulli. For some reason I couldn't load them into the PAR. I had to
go into VideoPost and render them to the PAR to get it to work. I know he had
been playing with alpha somewhere in that project. Maybe they were rendered
with alpha on.
Is there a way you can set up the PAR to at least be able to accept TGA with an
alpha channel, even though the alpha channel is ignored?
Alden:
>> Is there a way you can set up the PAR to at least be able to accept TGA
>> with an alpha channel, even though the alpha channel is ignored?
Of course! Just start the driver with "PARDRV -B:1800" or so to create a
buffer large enough for the alpha.
Greg Pyros
Greg,
>> Just start the driver with "PARDRV -B:1800" or so to create a buffer large
enough for the alpha. <<
Got it. Thanks for the tip!
Got another PAR question for you if you don't mind. I'm about to install a
second 2217A for the PAR. In my PAR documentation, it says that the master
drive should have J6W2 jumpered and J6W1 unjumpered, while the slave drive
should have J6W1 jumpered and J6W2 unjumpered. But the Micropolis
documentation say it's just the opposite. So … which is it?
Alden
Alden:
>> In my PAR documentation, it says that the master drive should have J6W2
>> jumpered and J6W1 unjumpered, while the slave drive should have J6W1
>> jumpered and J6W2 unjumpered. But the Micropolis documentation say it's
>> just the opposite. So … which is it?
Whichever one works! <bg> Just try one, if it doesn't work, it's the other.
Perhaps one of the friendly PAR dealers can step in here with the answer?
Greg Pyros
>> Whichever one works! <<
Well the PAR documentation worked for me!
Thanks
Alden,
Alpha On was the problem. Thanks.
-Dave
John,
Thanks. That was the problem!
-Dave
In addition to the alpha thing John mentioned, you might need to add
"/B:1500" to your "DPS_PAR\pardrv" line in your autoexec.bat. Allows you to
store larger files.
Paul S.
Paul:
>> you might need to add "/B:1500" to your "DPS_PAR\pardrv" line in your
>> autoexec.bat. Allows you to store larger files.
In the interest of PAR correctness <g>, it allows you to _process_ larger
files, the PAR always stores the files at the same resolution (752×480).
Greg (picky, picky!) Pyros
Hello Greg,
>In the interest of PAR correctness <g>, it allows you to _process_ larger
files, the PAR always stores the files at the same resolution (752×480). <
Now if only the PAR actually *stored* the alpha channel, we wouldn't need
another big drive to store alpha channel enabled files. 🙂 I don't know if
there is an easy way to split alpha to a separate drive letter, is there?
(would be a good option for the driver, no? for input and retrieval)
Another question, why does the PAR store in such a funny resolution? It'd be
nice to have it as a standard CCIR or square pixel 640×40 resolution.. oh well,
I guess I didn't pay for a Diskus.. I can't complain that much. 🙂
John (why isn't everything perfect?) N. Jordan
John:
>> Now if only the PAR actually *stored* the alpha channel, we wouldn't need
>> another big drive to store alpha channel enabled files. 🙂 I don't know
>> if there is an easy way to split alpha to a separate drive letter, is
>> there?
All we do here is to turn on alpha split and run PAROUT with the "delete files"
option on. This renders the files to the network, copies the big 24-bit files
to the PAR, and deletes them as it goes, leaving only the little 8-bit files on
the network.
Then just call up the 8-bit files as a background to the machine with the PAR
on it and render them directly to the PAR. That way you have both the full
color and the matte ready to lay off for A/B/C roll editing.
Greg Pyros
>All we do here is to turn on alpha split and run PAROUT with the "delete
files" option on. This renders the files to the network, copies the big 24-bit
files to the PAR, and deletes them as it goes, leaving only the little 8-bit
files on the network.
Then just call up the 8-bit files as a background to the machine with the PAR
on it and render them directly to the PAR. That way you have both the full
color and the matte ready to lay off for A/B/C roll editing.<
Greg. this sounds great, but what is the "parout" thing you mentioned, an IPAS
of yours? (btw- finally got a P100.. <g>)
JNJ
JNJ:
>> Greg. this sounds great, but what is the "parout" thing you mentioned, an
>> IPAS of yours? (btw- finally got a P100.)
Hey, really moving up in the world! Check your e-mail for the PAROUT info!
Greg Pyros
>Hey, really moving up in the world!
Sorta, not fast enough for my interests tho. Definately more productive.
Still mainly corporate. (would rather do gamedev/effects stuff- more creative,
more time, etc.)
Got your message, thanks.
JNJ
BTW- are you going to the E^3 expo in may? (in LA) I got info on it today,
and it sounds very interesting. Know how much hotels cost somewhat nearby? (1
person, basic) Sounds like a good tax writeoff. 🙂
JNJ:
>> are you going to the E^3 expo in may? (in LA)
Probably – I think I miss more LA shows because I don't have to plan
on them like you do for a plane/hotel trip somewhere!
It's on my calendar, not that it means anything…
Greg Pyros
>> In the interest of PAR correctness <g>, it allows you to _process_ larger
files, the PAR always stores the files at the same resolution (752×480). <<
Ah, the PAR-litically correct faction raises its head! <g>
Paul S.