Setup Cannot Copy The File Ntprint.inf
Looks like you do have the Raid Striped.Try going to the MSI sitehttp://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=635&kind=1and download the RAID driver Windows XP 32 bit versionand create new floppies using the downloaded ones.Be sure to instructions for adding Vista drivers to Server 2003 but it's the same concept http://blogs.technet.com/askperf/archive/2008/09/19/installing-windows-vista-print-drivers-on-windows-server-2003.aspx Alan Morris Windows Printing Team; Search the Microsoft Knowledge Base here: http://support.microsoft.com/search/Default.aspx?adv=1 Hi / Hello Alan Morris, Solution This document helps you determine whether the NTprint.inf file is present on your computer. Not sure if it is universal but feel free to download and try. check over here
Then I saw yet2cabinetfiles in my drivers sectionas I had a.o. A pitty you can't just export one printer or driver , but this is asfar as itgoes for now. If you just need the ntprint portion of setup start by adding any 32bit driver included in Windows 7 or Vista remotely to the server. An easy way to install 32bit printer drivers on a 64bit server (or vice versa) is to push the drivers from theworkstation machine.
A: Forever. Now type: imagex /unmount C:\Win7Mount and press ENTER. The other requires a lot of searching and work.-> Given decades, why hasn't Microsoft provided a decent OS installer?Bob Flag Permalink This was helpful (0) Collapse - After slipstreaming the Raid
I can then share this as HP Laserjet 3050 x64. Tuesday, June 26, 2012 2:10 PM Reply | Quote 1 Sign in to vote Hi I know this is a pretty old post, and most people have probably figured some way it asks for the I386 folder for the windows x86 media so I copied the I386 folder from the XP cd and then it does nothing but keeps asking for the i386 unless someone can point me to the definitive location of the name of a printer in a INF, i have a nice script that takes a specified folder where you place
The file name has the .inf file icon () next to it, even if the .inf extension is not there. Now all of my printers (HP, Brother and QMS) are all fine on my 2008 x64 box with x86 drivers Admittedly I have had to build a 32-bit vista machine, but I guess I'll pop over to 4chan. https://social.technet.microsoft.com/Forums/office/en-US/59c1d8e4-76f4-415a-9ec1-7046c9d417a2/on-64bit-2k8-server-trying-to-add-x86-drivers-asks-for-ntprintinf?forum=winserverprint For me, by far the quickest solution was to use the global drivers provided by Xerox.
I finally figured out the problem. Bad programming!Anyway, I think you ought to just take credit for the solution yourself since you did find it. Then I decided to step up and went to my Windows 2008r2 server, and copied over the extracted (hp) cabinet from my Win 7 x86 initial setup and extracted it. The 64bit print server is using a different driver if you migrated a 32bit server to 64bit.
No digging around cab files, no looking for installation media, no playing with pnputil, etc. I hope to god that someone can help me with this because i am well and truely stuck. http://social.technet.microsoft.com/Forums/en-US/winserverprint/thread/71b16b14-20f4-4e4f-b66d-17cfa96377e4Alan Morris Windows Printing Team Proposed as answer by Cecilia_ZhouModerator Thursday, June 16, 2011 7:59 AM Unproposed as answer by Cecilia_ZhouModerator Thursday, June 16, 2011 7:59 AM Wednesday, February 16, 2011 This is the file you will use to restore to your new print server.
FFS Proposed as answer by Dave-McCoyIT Thursday, August 12, 2010 11:31 PM Wednesday, May 05, 2010 3:06 PM Reply | Quote 0 Sign in to vote I ran across a check my blog If you choose to participate, the online survey will be presented to you when you leave the Technet Web site.Would you like to participate? It won't work either. Eventually I happened upon the following line in the setupapi.log file. #-175 SPFILENOTIFY_COPYERROR: Source = "\\MyNetworkShare\hp_cp3525x\hp color laserje\drivers\i386(32 bit - 2000_xp_s2003_vista)\pcl6\hpcp3525.CF_", Target = "C:\WINDOWS\System32\spool\DRIVERS\W32X86\hewlett_packardhp_cof94c\hpcp3525.CFG", Flags = 0x00000000, Error = 0x0000001e.
Edited by Todd Parkin Friday, November 09, 2012 6:02 AM Corrected a typo. note: If you closed the Download Complete screen, browse to the folder where you saved the .exe file, and then click it. The demode requires upgrading either both x86 to x64 and OS to newer OS migration. http://stevemattley.com/setup-cannot/setup-cannot-copy-the-file-sp2-cab.html Lets face the Print Migration Tool.
How exactly are you supposed to run the Print Management utility on a W2K8 Server from Windows XP? I followed the suggestions above, but was not able to find a version of ntprint.inf that made it succeed. There was a problem installing this hardware:’ error message displays on the computer.
Monday, November 15, 2010 4:01 PM Reply | Quote 0 Sign in to vote Client computer?
CURRENT SOLUTION: Gather files from the wrong OS media to make the chosen OS function correctly. I'm just brainstorming to create some sort of solution... Proposed as answer by Vitornillo Tuesday, November 03, 2009 6:30 AM Tuesday, May 05, 2009 3:55 PM Reply | Quote 1 Sign in to vote While there are many work arounds I have selected both x64 and x86 at this point.
I get to the point where I'm asked for the E:\i386 media and give it a CD which contains what it tells me it wants. Tuesday, November 16, 2010 1:52 AM Reply | Quote 0 Sign in to vote I have the same problem. Click Start, click My Computer, double-click C:\, and then double-click the Windows folder. have a peek at these guys Restore to the temporary machine.
Obtain a copy of ImageX. They are distributing the ntprint driver package with some of their drivers.Alan Morris Windows Printing Team Saturday, December 17, 2011 12:21 AM Reply | Quote Answerer 0 Sign in to vote Flag Permalink This was helpful (0) Collapse - THIS IS IT!!!!!!! Microsoft Customer Support Microsoft Community Forums Windows Client Sign in United States (English) Brasil (Português)Česká republika (Čeština)Deutschland (Deutsch)España (Español)France (Français)Indonesia (Bahasa)Italia (Italiano)România (Română)Türkiye (Türkçe)Россия (Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国
I am going to use x86 or 32bit interchangeably, so try to keep up! I checked the length of my file path and it exceeded 128 characters. You might also need to click it in a list of similar products. Thanks again, I was losing my mind over this error.
Insert your Windows 7 DVD or mount your ISO. I expect to have pretty good success, but I am finding out from my own research that the current operations team may have used HP drivers on some xerox and lexmark In that case I looked at that site and for me it looks like somebody tried to create a site and just not finished yet. The clients using XP when trying to add the printer get asked for a driver - what is the solution?
I don't understand where to get "ntprint.inf, ntprint.cat, driver.cab" and EXPAND into flat file format." Is this on the Windows 2008 R2 install CD? I too had a need for an HP Deskjet 450 (anno 2004/2005) x86 printer driver on my new Windows 2008r2 (x64) printserver. This is helpful!! Friday, January 21, 2011 11:10 AM Reply | Quote 0 Sign in to vote I've been reading through this thread with increasing irritation.
Still I had no clue on what to expect and went experimental. Step three: Remove the product software Disconnect the USB cable connecting the product to the computer. If i try to add it from a XP pro machine it promts me for drivers. ???? Proposed as answer by fapricela Friday, September 20, 2013 1:54 PM Monday, April Installed the x64 driver (the problem one) on an x64 version of Windows 7.
Edited by StefT Friday, December 16, 2011 2:05 AM Friday, December 16, 2011 1:54 AM Reply | Quote Microsoft is conducting an online survey to understand your opinion of the Technet