Original Post
Replies sorted oldest to newest
I would just like to add that while I think the mainframe copier is a good system, the software side (plotbase) has given us a few issues.
Hopefully updates will be forthcoming and our next demo will go smoothly.
Worst demo I have had in 10 years on this system connected. Lost 5 machine deal.
Hopefully updates will be forthcoming and our next demo will go smoothly.
Worst demo I have had in 10 years on this system connected. Lost 5 machine deal.
The main issue was that scantool kept locking up and we would have to reboot each time. After a total of 7 times the client was not very impressed as his interest was 75% scanning.
Mentioned that they were going to upgrade to Autocad 2005 and I knew from a post here that there were no drivers for it yet.
Just would like to know if these are common issues associated with the 240 and will they be fixed?
Mentioned that they were going to upgrade to Autocad 2005 and I knew from a post here that there were no drivers for it yet.
Just would like to know if these are common issues associated with the 240 and will they be fixed?
Art Post (Guest)
All of the systems that I have in the field have a power supply hummm, it happens once every five minutes (my tech department has told me its NATURAL). I've been in the biz 24 years and that is not NATURAL.
I have not seen the problems with Scan Tool, however that does not mean that they do not exist.
Art
I have not seen the problems with Scan Tool, however that does not mean that they do not exist.
Art
I found no problems with plotbase software, other than the customer turns off the AUTO KEY, then can’t print. As for lock ups, I exercise patients after reboots, sometimes the software can take a few minutes to completely load and run.
The noise is caused by the fuser lamp cycling on and off. Xerox 2510 series were louder, and would make florescence lights flicker
The noise is caused by the fuser lamp cycling on and off. Xerox 2510 series were louder, and would make florescence lights flicker
yose (Guest)
thanx for the correction on the noise, is there a way to make it go away?
scantool locking up is usually caused by A) not enough RAM / HD on computer
B) non supported chip set on computer
C) incorrect install of scantool
Can you give me a few more details on the computer system, and the settings (memory allocation) on scantool?
B) non supported chip set on computer
C) incorrect install of scantool
Can you give me a few more details on the computer system, and the settings (memory allocation) on scantool?
Just wanted to add my two cents here. I thought I heard that you shouldn't scan with this version of scantool higher than than 300 dpi and the fix for many of the scantool errors was coming in the next version.
actually, if you scan at 200 or 300 dpi on this vesion, you get a scanned page, but no image (blank page). fix for now is to set custom scan size of 35.99 x 24 ", or to scan at 150 or 600 dpi. Bug will be fixed in version 3.3, due out in October - pln on Nov - Dec!
Regarding bandit's last post, I will try that tomorrow on a newly installed system. We have one problem and that is that when we scan a PDF at 150dpi we do not see it in the image window or in Acrobat, but when we scan at 400dpi, we can see it and open it up in Acrobat reader. But when we open either one on a clients computer in Acrobat reader and try to send it to print, a blank page comes out of the 240. Maybe I just had a bad day, but what am I doing wrong?
do you have postscript option installed? What size document are you scanning? If it is a D size (36 x 24) try setting a custom size in scanner settings window to 35.99" by 24" and see if that is a fix. If not, let me know, would like to dupicate so I can alert tech support!
Is “lock pages in memory” assigned to the correct user?
Add Reply
Sign In To Reply