CompuServe Messages

>> The drawback is that a redirector cannot be "redirected" again. << Right, so what can be done to make this thing work? How about this? The renderer's feed the file server, which has a local hard drive with C:\IMAGES and C:\DPS_PAR directories, and the PAR with its native HD on a drive D:\. A DOS program is initiated on C:\ of the file server which checks the images in C:\IMAGE while the networked renders feed that directory. The DOS programs function is to continually looks for the next sequential file in the image directory, and when it finds it, send it to the PAR. What kinds of problems do you forsee in this approach? Would this constant checking interfere with the networks ability to pass the rendered images to the C:\IMAGES directory? Is there a way to specify a time out to release control of the program so that rendered images could be transferred from the network to the directory? Would this be necessary? It would be nice to keep the PAR busy while the network is rendering, and I get the impression that if 3DS is not installed on the file server, N_DUMP won't work for me.