#Lantastic, WFW & Mirage
7 messages in this thread
Glen –
Thanks for the info. (Been on vacation for a couple of weeks, so didn't get
back sooner).
Are you able to use WFW Add-on for DOS to render 3D Studio outside of Windows
across a network??? Sure would save me money not having to use Lantastic, etc,
since I don't need a DOS network for anything else but 3D Studio. Also, where
does one acquire the DOS client software? Do programs like Norton Backup for
DOS work across the DOS client software?
Also, do you make your DOS batch file replacement to NDUMP available to others
– or can you give me a general idea of the principles behind the process?
Thanks again. :-).
rw
Bob:
>> DOS batch file replacement to NDUMP
Actually, it is not a batch file replacement, it is a full stand-alone .EXE
file which runs basically the same as NDUMP.IXP, searching for files, making
sure they are in the proper order. The advantage of it, though, is that you
don't have to be running 3D Studio on the machine with the PAR on it, and it
will run very well in a DOS box in Windoze, so as not to take up clock cycles
from other things you are working on at the time!
Greg Pyros
Greg –
Thanks for the info. . .
two q's
– Does it have to run in a DOS window under Windows (I can't see any
benefit to running 3D Studio under Windows)?
– How does one acquire the .exe file?
Thanks. . . and how's the new biz? What was the work like that you showed at
the meeting?
rw
Bob:
>> Does it have to run in a DOS window under Windows?
No, plain DOS will do. NDUMP.EXE was only created for those people who don't
want to run 3DS on the machine with the PAR on it. If you are running 3DS on
the machine, instead run NDUMP.IXP on it.
Greg Pyros
Bob,
<<Are you able to use WFW Add-on for DOS to render 3D Studio outside of Windows
across a network???>>
Yes, you can. My setup basically is WFW running on my server – this is where I
send all of my rendering output files (your choice to send network control
files here or not) – and then all of my slaves are running WFW add-on for MSDOS
& 3D Studio to render across the network. (Note: this is a different product
than "MS Workgroup Connection for MSDOS!) The reason I use the "Add-on" vs.
"Connection" is that the former allows the slave machines to be peer servers,
unlike connection which will not allow sharing of files to a peer machine. I
like this feature because if I ever want one of the slaves to be the
Workstation renderer – holding the network files – I can allow it to do so
WITHOUT having to run Windows.
Summary:
1. Server (holds TGA outputs from slaves) running WFW
2. Workstation 3D Studio – holds network control files
3. Slaves running 3D Studio
2&3 are running WFW add-on for MSDOS.
This setup runs just fine. Hope this helps you out. If you have any other
questions, feel free to drop me a line and discuss it further.
Good Luck!
-Glen
Glen –
<<the reason I use the "Add-on" vs. "Connection" is that the former allows the
slave machines to be peer servers>>
Thx for the input – where did you order the additional DOS-based software?
rw
Bob,
You can get it just about anywhere – PC connection, MicroWarehouse, COMP-USA,
Egghead, and the like. Because the people taking orders aren't
always too great – make sure they understand you want the Add on for Msdos and
NOT the Workgroup connection. The first time I ordered – what I got and what I
had ordered were two different things! 🙂
Good luck with all of this stuff – I know it can be a hassle. Let me know how
things work out for you when you get it all up and running…
P.S. I've found that I get better results using the FULL redirector vs. the
BASIC redirector. The manual of course doesn't explain it well, but in trial
and error tests, it worked better. Also, if you run into funny things
happening (slaves reporting "failed" when then render fine, etc.) LET ME KNOW.
A few others and I have seen some weird things with the network rendering – I'd
be interested if you see some bugs occuring as well.
Talk to you soon.
-Glen