PAR/Lantastic 6.0
7 messages in this thread
Upgrading hassle:
Added a PAR to network and upgraded to Lantastic 6.0
Incident:
PAR operates correctly for the exception of importing .TGAs from any drive when
the network is up. It will import the same files it gave corrupt or
incompatible error messages for from it's own C: drive, when the network is not
up.
This happens with both the beta 1.27b and the shipping version 1.09.
Objective:
1. Fix the import problem with the PAR so importing can be from any network
drive using PAR software.
2. Develop a technique where files can be copied to the PAR drive from any
network drive using DOS commands, and resulting in an .ANI. This technique if
possible, will bypass having to run PAR and use IMPORT command.
Item 1 is critical, Item 2 is wishlist.
Steve Pidgeon
Pulse Productions
Tampa, FL
pidgeon@gate.net
70732,2546
813-977-8414
I saw your not over the mail list!
I'm not sure I understand all of your problems. Alan Iglesias has the same
setup you do and he could probably have more answers than I do. The DPS dude
with "all" the answers is also around. His name is Brick Eksten and he has been
a great help.
It seems to me you have a conflict among your software configuration. I don't
use Lantastic so I can't say much about it. Also make sure no two (or more)
systems are writing and/or reading to/from the PAR at the same time. The driver
is not multitasking.
Stephen,
I am currently running PAR (1.27b) along with Lantastic 6.0 and don't have any
problems reading network drives from the PAR software.
You have to be sure to load your network software *BEFORE* (yes, before) you
run the PAR drivers. Oh, and set up the PAR as an "OTHER" network drive in
your Lantastic Resources. The network access capabilities of this drive should
be "RWC-L——-".
I've even had limited success allowing slave machines reading the PAR drive for
rotoscoping. You can install your PAR as a network drive. The problem I was
having was that while the slave machines are reading the PAR, the machine where
the PAR was installed would have some sort of "lockup". I couldn't do any work
with the machine where PAR was installed, but the slave machines could continue
to read the PAR…..kinda weird.
I read another message here indicating that the PAR software is not
multitasking and so wouldn't work with multiple machines reading it. This may
be so…..and my experiment mentioned above may have worked just by fluke, that
none of the slaves attempted to read PAR at the same time.
Later,
-Jeff
Hi Steve,
My system is set up the way JeffR has described (second paragraph) in his
message to you. The PAR software sees networked drives no problem.
If you'd like to talk about this over the phone, let me know and I'll Email you
my number…
-Alan
Hi Alan,
Yes, I'd like to persue this. I haven't put much time in it so far, just set
it up and had a problem. Took no time at all to create this situation 🙂
I'm using an NE2000 clone set at IOBASE 300 and INT 5.
I'd be grateful if you could shed some light on configuring the PAR dedicated
drive as a resource. My initial attempts result in a message that says the
drive has no volume label, and the next message is one of those Abort, Retry,
Fail messages.
Other than that, it would be good to hear from you. Still thinking/saving for
LA95.
Gus suggested that I follow-up with you since we are running similiar systems.
My item 2 is also of interest to me….copying TGAs to the PAR drive using DOS
commands….are you having any success doing this?
BTW, Lee tells me you were very helpful in his initial attempts with FLAME.
Steve
Alan/All to replied,
This is like Burger King…..'I love this place'
The solution to my problem was provided by Alan …. Thanx Alan.
The solution (FYI)
In autoexec.bat launch parint, then call startnet.bat, then launch pardrv.
In Lantastic Net_mgr, set PAR drive as other
Voila! It works. I guess that it says to do this somewhere in something but I
didn't find it. Thanx for the always beneficial support we get here.
Steve Pidgeon
Pulse Productions
Tampa, FL
My pleasure, Steve…
-Alan