Thought I would update my post to include some info on using Filmmaker and overall impressions so far.
Turns out that even though we had done a clean install of Windows 7 Pro and over 180 updates upon installing - Windows update still had not gotten up to SP1 installed when I attempted to install FM which was what was causing FM to through the Visual C++ library exception when trying to print.
The folks at Cadlink got back to us quickly this morning and low and behold today was the one day (out of every 90 or so it seems) that we had internet connectivity issues with our service provider. The tech at Cadlink agreed to give us a call back in a couple of hours to see if it was resolved and true to their word they did.
The techs logged in remotely and fixed the above issue. Once done with this they were having an install issue that was hanging up when trying to put the EPSON SEPARATIONS driver on the machine from their software. I don't honestly know what the fix was to this as (I only went back and forth to the machine about 40 times today to get the tech's logged in with reboots etc... - didn't get too much work done until late afternoon today

. Regardless, they finally had us up so that we could print a test file from the rip station to the one of the two printers and they built a couple of basic queues for us.
From there (it was 5pm EST at this point) I modified the queues to meet our needs and built two additional queues (so that each printer has a couple of queues). All seemed good. Then I went to our individual work stations that need to rip and started setting up the FM printer drivers in each of them so we could finally get to producing some films.
At the first workstation after installing the FM print drivers I tried to send a test file to make sure all was working - low and behold it goes across to FM fine, but when release it gets a 'HOLD ERROR'. Not much documentation in the FM Quick Start guide so I went and took at what T RIP had to say about this since it's basically the same product. From there it states to clear the error and resend -after doing this about 5 times with no progress I gave up for the day to get back to some quotes, daily invoicing and shipping etc. and thought I would come back to it after hours when I could easily reboot people's workstations without disrupting the shop workflow anymore than I already had for the day.
After hours we rebooted the rip station and the work station that had an issue and finally got a print to go to the printer (finally - after two days of dorking with this stuff). Although the print went to the 'wrong' printer....hmmmmm...... Some further investigation showed that the reboot of the rip station had caused the computer to assign LPT port #1 to printer #2 and LPT Port 2 (both USB Virtual printer ports) to Epson #1. We have two EPSON 9800 printers connected to this machine so we started looking for causes for the switch. We found that in the windows printer and devices the two Epson printers were called 'Epson Stylus Pro 9800' for what had originally been printer #1 (and was now printing as #2 through the FM queue) and 'Epson Stylus Pro 9800 (copy 1)' for what had originally been designated as printer #2 (and was now printing as #1 through the FM queue). So we went and changed the names to 'Epson Stylus Pro 9800 1' and 'Epson Stylus Pro 9800 2' through the windows devices manager. We then rebooted the rip station about 3 times to make sure it no longer switched upon reboot from one USB port to another for the specific printers - this appears to have worked as three out of three reboots did not change after this.....
Finally we ripped a four color all over through a remote workstation to the rip station (4 pages at 44 x 44 for this job). It after receiving and ripping the four pages we sent them to print - the first page printed fine, but the three behind it spooled and did not print automatically when the first page was complete. We then grabbed the next three pages under the jobs menu and told them to print - the first one went to print and within about 2 or 3 minutes FM crashed. (Error message - FM unexpected ceased working in a pop up menu). So cleared the printer and restarted FM and reprocessed the three pages that had not printed yet. When I left the office at 8pm this evening the first of the three remaining pages was printing and the other two showed a 98% and Active for spooling.... I guess I will see if they printed without error in the morning.
Some general impressions so far.....
1. There are almost no troubleshooting suggestions within the FM Quick Start guide and those listed on T Rips site are only slightly better.
2. What I thought would be a pretty straight forward install and evaluation has been anything but so far. The first issue inadvertently, and admittedly caused by me and Windows Update. I really hoped that after that most of the issues would be over, and while I think I have fairly good grasp of how to configure and operate the rip - the overall stability of the program has not been very good so far - hopefully this is just shakedown stuff but we'll see. We did, back in the day, use Fastfilms and I remember (even more clearly now) that is wasn't always the most stable program - hopefully this isn't how things will be with the FM3 version though as honestly - we must have stability in our work flow - we have too much going on to be constantly dorking with the rip once setup and need to have it be pretty much a shoot the file to the rip and go program in order to make this upgrade a serious contender for purchase. It's early yet, though and we'll give it a week or so to see how it performs now that we are setup to print from all of the work stations that need access to the RIP.
3. The overall quality of the film and halftones do see to look a little cleaner (by the naked eye) to what we were getting from Accurip, but I honestly have not had time to look at them or compare them under a loop with all of the other issues we have had with just getting the software working and to a point we can print something.
4. Speed seems really slow to send a file to the rip - as compared to Accurip (which is what we have been using) - that said I think we can probably tweak performance some on this through several of the available setting within the rip tomorrow so I do expect to be able to improve this some in the next day or so.
I plan on linearizing and comparing films in more detail over the next couple of days - once done I will post more info if I have it.
Overall it looks like a robust and good product - BUT so far the stability and ease of use seems pretty unstable (ease of use in this case just being quirks - not so much understanding the software - at least I don't think so anyway).
We are probably a kind of rare case for this software as I highly doubt there are many other screen printers out there using two 9800's at the same time, from the same computer, with this rip, with multiple work stations accessing the rip and them - if anyone here is I would love to hear your experiences.
Hope someone at least finds this info informative and if not maybe it will help someone more in the future. My desire for having a clean install of windows and thinking that after 180 updates we should have surely been up to SP1 was the start of this fiasco and I take full responsibility for the start of my issues in that regard. For the rest....well.....we'll see!