hello guys,

i am trying to package HP 2300. After I have created the package, by taking snapshots/installmon, and add the printer, it gives me an error saying "Some files on PDL_COMMON are needed" When I click Browse, its looking for a dll, even though that DLL is already in the package but not seeing it. By default, the drive its pointing to is E:\ which I dont understand how its pointing there because i do not even have a E drive. When I redirect the file manually, it follows up with another DLL that is cannot find. They are all there but its looking in the wrng directory.

help!!!

thanks
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Trey,

I would advice against using snapshots for drivers.. for printers you can use one of these methods...

DIFx http://msdn2.microsoft.com/en-us/library/ms790264.aspx
printui.dll http://www.microsoft.com/windowsserver2003/techinfo/overview/printuidll.mspx
Append devicepath with path to inf file, HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath = %systemroot%\inf;c:\drivers\printers\HP2300

:)
Answered 04/10/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
0
tx for the help Tone. I ended up doing a snapshot on it anyway but after I had installed it, i did a reboot before addingthe printer and it worked flawlessly.

thanks
Answered 04/12/2007 by: trey_999
Senior Yellow Belt

Please log in to comment
0
Not sure how you have done it but one of the problems with snapshoting is you capture oemXXX.* and these are created dynamically.

If you captured oem10.inf, oem10.pnf they may not exist on the packaging\test machine but could exist in your live environment.. so you could brake an existing driver or cause new one not to work as the oem files on PC are newer so packaged ones wont be delivered..

:)
Answered 04/13/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
0
you could change the name of the oemXXX to a name that would be unique to that driver e.g HP2300oem.inf and make it a key file. Even though its a unique name, it would self heal if altered making sure your driver files do not get appended or replaced.
Answered 04/13/2007 by: trey_999
Senior Yellow Belt

Please log in to comment
0
Just pointing out its far from the best method of doing things as there is no way of knowing what microsoft are going to name their inf, hence the oemXXX format being used as a means to identifying drivers that dont ship with the OS or patches.. and it wouldnt be a supported if you had issue's with your printers..

So not to package would be my answer..

;)
Answered 04/13/2007 by: Tone
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity