Thanks, the 64 bit driver for external 250 RIP from Fiery Website appears to work properly.
There was a issue with not being able to use "Print"with windows 8 using drivers from Xerox website.
Xerox has never posted the latest Fiery drivers. EFI puts the driver right on the Fiery itself, it is listed as the "printer files" on the download tab of the webui.
As for getting drivers when you don't have access, or have a highly outdated and un-supported configuration. EFI provides the drivers as they always have on their own website.
The direct link for the Windows English driver is this https://d1m2uyedaojrqy.cloudfront.net/FSO/xerox/Xer_EXP250_v1.01_v1.1/all/english/v1.1/Ps_drvr_EXP25...
for the external and this for the bustled https://d1m2uyedaojrqy.cloudfront.net/FSO/xerox/Xer_DC250DC240/all/english/v1.1/Ps_drvr_DC250DC240_v...
I would hesitate to use either, the machine has been out of developement for 8 years, the final driver specific to the product are 2006. Go to the EFI website and grab the driver for the 260. Worst case scenario you need to change the default output profile to "Use media defined profile" and all the other options natively work.
The only reason you need to change the output profile is because the ones in use specify a 250 and will fail to print.
There is no issue with the print/hold or direct
We've tried downloading the latest docucolor driver for Windows 8, 64 bit, for external Fiery EXP250 and it only works set to LPR and "hold" it will not work for "print".
Another person indicated to me they have the same issue with Windows 7 and the current Xerox driver on the Xerox site. I've linked to a older version I have at http://dc.communityprinters.com/x250 which allows one to use the "Raw" setting, which then prints and saves to the Queue. Then one can use the 2nd tab in the preferences of the printer driver and change from "print" to "process and hold" . This has the advantage of processing the extra instructions of the driver, such as mirror or printing 2 up in the booklet section so that the preview shows the file as it will output in Command Workstation.
It would be nice however if Xerox and Fiery could fix the latest drivers so it can be set to "print" not just "hold" for use in Windows 8. Please forward this complaint to your 2nd level Analysts for repair, one should be able to "print" not just "hold" from Windows 8.
It's the 64bit , not the Windows 7 I believe.
The drivers on the server can be updated, but patching the system is finicky if you attempt doing "Just the ones I need".
To check what drivers are available just open the Fiery webui (Put the IP of the Fiery in your browser address bar)
Go to the "Configuration" tab and select "Check for product updates"
From Command Workstation print a config sheet for the Fiery and confirm the "PRODID" is installed in the patches section.
If it is not, go to xerox.com and get to the drivers for your Fiery, change the "Operating system" drop down to "All operating systems" and scroll to the bottom. Grab the Prodid patch and extract it to your desktop. Now in Command Workstation select File/Import Job and change the queue at the bottom to "Direct" and import the PS file for PRODID,
*******DO NOT PRINT ANYTHING ELSE FOR AT LEAST 5 MINUTES*******
Once the 5 minutes is over, restart the Fiery from Command Workstation , it could very easily take 15 minutes to boot back up.
When it does come back online, go into Command Workstation and select Server/Configure (Setup if CWS4)
Select Network/Protocol/TCPIP/DNS and set that to the correct settings for your LAN, add 126.96.36.199 if you don't know yours.
At this point just leave the Fiery on for a week and it should update to the latest patches and drivers automatically.
If you choose to manually update using the Composite patches on Xerox.com, be sure you do them in the correct order and do the full 5 minutes before rebooting.
Now that will get you up to date with the latest software and drivers, it will get a fully working Win7 x64 driver on the Fiery that can be downloaded from the webui under the "Downloads" tab (grab the "printer files" link from the windows section.)
BUT, it will still not most likely serve the drivers out via the SMB method you want, the 64bit users will need to manually add the driver from those clients.
Hopefully some of this info is useful to you, I know it was a lot of words for a "no", but there is a lot of good info there to help out.
you cant update the "stored driver" ....
The best approach is to setup a printerserver and install the latest drivers on that.
Use "Standard TCP/IP Port" to port 515 (LPR).
Queue name should be: Direct, Hold or Print.
Also on the older EFI Fiery Bustled its adviseble to remove the tick in "advanced printing features".
Also in "two-way communication" remove the "update driver when opened" as this causes the user experience to be somewhat slow.
Also be aware that there are quite a few updates/patches for the DC242 Bustled RIP as can be seen through this link:
This is the driver for Bustled Fiery
I don't believe you can. Make sure you have the latest software and patches loaded. You may want to try the EFI Fiery forum.
Thank you for using the forum. I see that you have already done quite a bit of research without locating a solution. Have you checked the product knowledgebase? http://www.support.xerox.com/support/docucolor-242-252-260/support/enus.html?associatedProduct=dc242...
If you are unable to locate a solution I would recommend calling Support at 1-800-821-2797 for assistance.
I am sorry I couldn't be of more help.
I have been arguing with a Xerox DocuColor 242 with a built in Fiery server all day. I am trying to make it easier for Windows 7 users to install the printer. With Windows XP, it is quite easy. I have the printer all set up and shared with the Windows domain. All I have to do with an XP computer is navigate to the server and pick either the print or hold printer and Windows does the rest. It asks the printer for the driver and gets one back and everything goes fine. However, with Windows 7, when I try that, it acts like it is going to install, then it give an error 0x000000d8, and says it cannot connect. I have researched a lot and found next to nothing. I personally suspect it is because the Fiery server still has a driver package from back when it was first made and is not compatible with Windows 7.So my question is (unless somebody has a better idea), is it possible to update the driver package on the server, that the server sends out to Windows 7 computers? And, of course, if it is possible, how? (Hopefully, without actually plugging a monitor and keyboard into the server and monkeying with Linux)