Software Deployment

I guess you're using Wise Package Studio.
If you update your exclusion list you will not get that much crap during your capture.
Think the task is place at the default project or from the Tools tab.
When you build the exclusion list it basically runs a pre- and post-capture and then adds those to your list.
So what you need to do is to run the pre-snapshot, run your regular applications such as notepad, IE, regedit and so on, end with a reboot. Then perform the post-snapshot.

If I recall this is described in the Quick-start PDF.

These you can remove:
WindowsUpdate.log
certclas.PNF
printupg.PNF
edp.chk
edp.log


The ODBC.INI depends on if the application has added any entries to this INI-file. If not then remove it.
Often any file or registry that has the <> symbol should be removed, but not always as they may be updated with the application specific settings.

You will be after using "Setup Capture Configuration" when you want to automatically build your exclusion list.

As you certainly know the program (doPDF) works that way that you write something in for ex MS Word. you go to print. Select the doPDF printer and you got yourself a PDF file. The problem is when i pakage the program and test it. It dosent map any printer. Thers no printer att all. I did not exlude any files or keys my self just to test that it wasn't me how had exclude files.
Is it Wise that exclude files it shouldnt?
Do you think its files or key? or both?
I will give it one more try now and se if I can see any files/keys that wise exclude by her one.....

Sorry but couldn't quite follow your last post, but if you're installing printers you will have to restart the "Spooler" service for the new printers to show up. Use a Service Control to stop/start the service during install and uninstall.

When i Install doPDF.exe (original file) the printer is showing without any problems. When I install my doPDF.msi the printer is not there...! I tried the stop,start spooler service thing but the printer is still missing.
Please help me understand this!! [:@]

[:)]

Capturing PDF print drivers is tricky. Well it was for us when we repackaged Acrobat 5. We had to tweak the registry exclusions so that areas of HKLM\SYSTEM\CurrentControlSet were captured, specifically

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\
HKEY_LOCAL_MACHINE\System\CurrentControlSet\HardwareProfiles\

Prior to this, we had the same result as you i.e. no printer showing.

Alan

p.s. Also, when testing, make sure you reboot after installing your MSI

Thanks ab2cv!! I will try it as soon I have the time. I get back with the result.

But have I understand it right that i have to INCLUDE the registy keys you described above from the list of keys that Wise exclude by it self....?

ORIGINAL: aXz

Thanks ab2cv!! I will try it as soon I have the time. I get back with the result.

But have I understand it right that i have to INCLUDE the registy keys you described above from the list of keys that Wise exclude by it self....?


Yes. You need to capture changes to this area of the registry. It is most likely that the snapshot/discover process in Wise has these keys set as exclusions from the capture. I use WinInstall and not Wise, but I would presume that there is a similar method of customising this exclusion list during the snapshot process.

Alan

alot of these pdf type apps have an exe which installs the printer as a CA during install. If this is the case you can use active setup to launch the exe file in a similar fashion to that of the original installer.

It dosent work [:(]

When I go to the "Windows Installer Editor" after Setupcapture and add the registry keys you told me to do
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\
HKEY_LOCAL_MACHINE\System\CurrentControlSet\HardwareProfiles\

From the computer I installed the original Setup.exe file on the MSI file crasch after reboot. I get blue screen and windows dont starts. And theres no printer there. Lucky for me i Use WmWare.[:D]

But when i look at the registry keys in the Installer Editor I have some keys that have something to do with the PDF printer.
It looks like this.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\DsDriver
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\DsSpooler
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Print\Printers\PrinterDriverData

And in this folders there are alot of Keys.

Is there anyone how have any solution? Have someone repackage doPDF?

Thanks

ORIGINAL: jmcfadyen

alot of these pdf type apps have an exe which installs the printer as a CA during install. If this is the case you can use active setup to launch the exe file in a similar fashion to that of the original installer.




Can you tell me more? I didnt understand...

hi aXz,

have a look on captured files.. do you have any files like oemX.inf, oemX.pnf in C:\windows\inf?


monster™

No I dont. Is it good or bad? [:)]

The deadline for this package is comming closer and closer now. Is ther anyone how have any solution?

My question is still, why dose not the damn printer showing [>:]


Thanks for your help anyway!

I'll see if I can try this out later on today.
It's the product from www.dopdf.com, right?

ORIGINAL: AngelD

I'll see if I can try this out later on today.
It's the product from www.dopdf.com, right?


It would be real nice of you!! Thanks!
Yes it´s from dopdf.com. Version 5.2

Did a quick capture on the installation with less cleanup and had no issues.
Here is what registry information you should include in the package:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Devices
"doPDF v5"="winspool,DOP5:"

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\PrinterPorts
"doPDF v5"="winspool,DOP5:,15,45"

If you want the printer to be the default printer then add this
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows
"Device"="doPDF v5,winspool,DOP5:"

Everything under
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Printers\doPDF v5

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3
"Directory"="3"
"MajorVersion"=dword:00000003
"MinorVersion"=dword:00000000

Everything under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Environments\Windows NT x86\Drivers\Version-3\doPDF Desktop 5 Printer Driver

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Forms
"ANSI C"=hex:B8,96,06,00,D0,86,08,00,00,00,00,00,00,00,00,00,B8,96,06,00,D0,86,\
08,00,01,00,00,00,02,00,00,00
"ANSI D"=hex:D0,86,08,00,70,2D,0D,00,00,00,00,00,00,00,00,00,D0,86,08,00,70,2D,\
0D,00,02,00,00,00,02,00,00,00
"ANSI E"=hex:70,2D,0D,00,A0,0D,11,00,00,00,00,00,00,00,00,00,70,2D,0D,00,A0,0D,\
11,00,03,00,00,00,02,00,00,00
"ANSI F"=hex:20,DA,0A,00,C0,80,0F,00,00,00,00,00,00,00,00,00,20,DA,0A,00,C0,80,\
0F,00,04,00,00,00,02,00,00,00
"ARCH A"=hex:F8,7C,03,00,A0,A6,04,00,00,00,00,00,00,00,00,00,F8,7C,03,00,A0,A6,\
04,00,05,00,00,00,02,00,00,00
"ARCH B"=hex:A0,A6,04,00,F0,F9,06,00,00,00,00,00,00,00,00,00,A0,A6,04,00,F0,F9,\
06,00,06,00,00,00,02,00,00,00
"ARCH C"=hex:F0,F9,06,00,40,4D,09,00,00,00,00,00,00,00,00,00,F0,F9,06,00,40,4D,\
09,00,07,00,00,00,02,00,00,00
"ARCH D"=hex:40,4D,09,00,E0,F3,0D,00,00,00,00,00,00,00,00,00,40,4D,09,00,E0,F3,\
0D,00,08,00,00,00,02,00,00,00
"ARCH E"=hex:E0,F3,0D,00,80,9A,12,00,00,00,00,00,00,00,00,00,E0,F3,0D,00,80,9A,\
12,00,09,00,00,00,02,00,00,00
"ARCH E1"=hex:90,A0,0B,00,30,47,10,00,00,00,00,00,00,00,00,00,90,A0,0B,00,30,\
47,10,00,0A,00,00,00,02,00,00,00
"ARCH E2"=hex:B0,13,0A,00,50,BA,0E,00,00,00,00,00,00,00,00,00,B0,13,0A,00,50,\
BA,0E,00,0B,00,00,00,02,00,00,00
"ARCH E3"=hex:E8,76,0A,00,88,1D,0F,00,00,00,00,00,00,00,00,00,E8,76,0A,00,88,\
1D,0F,00,0C,00,00,00,02,00,00,00

Everything under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\doPDF Desktop 5 Monitor
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Printers\doPDF v5

ORIGINAL: aXz
I tried the stop,start spooler service thing but the printer is still missing.

Make sure to type in the correct name for the service as Spooler and not spooler, first character is uppercase.

apologies if you already mentioend this.

but that "S"pooler may also need to be stopped and started as part of the install.

I will try to do a SetupCapture now again. After the SetupCapture I go to Windows Installer Editor in wise an adds the registry keys you descripe abowe from the computer that dopdf.exe is installed on ??

Thanks for your help guys. Sorry if Im a bonehead [8D]
But as i sad Im new at this...

We were all newbs in the beginning [;)]
Wise Package Studio TUTORIAL for Newbies

When you run SetupCapture you will be presented with the "SetupCapture Configuration" dialog.
Check the "Capture changes in hardware registry entries" option as this will make sure registry entries under "HKLM\SYSTEM" will be monitored during capture.
Use snapshot comparison instead of SmartMonitor as the latter will capture more junk then you need.

YES! [:D]

Thansk for everything! its working... When I have added all the registry keys you told me to do AngelD, I installed it on my wmware computer and the printer still wasent showing! [:(] BUT when I restart the spooler service the printer was there!

So I have a question as allways [;)]

I dont want the users to have to restart the spooler service to get the application to work. So can I do a second setupcapture and do the stop and start on the spooler service? Or do I have to start allover again?

Use a Service Control to stop/start the Spooler service during install and uninstall.
In this way the service will first stop, the files are installed and then the service will be restared again during installation. For uninstall the same happens but intead of file installation the file gets removed instead.

The following thread at the Altiris forum should give you or others the exact way to accomplish this task.
http://forums.altiris.com/messageview.aspx?catid=19&threadid=43741

Thanks! Its working fine!
But how should I know as a newbie that it was all these registry kes I had to include?
Then I got like 4 or 5 marks when I do the validation but its works fine whene I test the application så sould I give a shit or what? [:)]

Eric,

By time you will learn what to include and not.
To get some more experience regarding printer registry entries you could always capture when you manually add a local USB or network printer at your office. That would give you a cleaner capture rather then snapshotting an installation doing the same but with the whole application included.

A general rule regarding validation is to always solve your own ICE# errors. Solving warnings can be tricky and not all of them can be solved but you'll have the SDK (MSI.CHM) at hand during this task and when manually creating MSIs and Transforms from WPS, ORCA or similar.
MSDN Library - Windows Installer will provide you with more information regarding the Windows Installer database and related information. When validating vendor packages you'll often hear to leave those alone and most will also do so. Some company's packaging standards involves in resolving all ICEs so it all depends on your company's or your way of handling the packaing process.

I solved some small ICE errors after capturing doPDF and at the end there were not errors or warnings, so that shouldn't stop you from doing the same. Due to Windows Installers resiliency/repair/self-healing (take a pick); the cleaner the package is the less possiblility it is that it will do some "harm". If you have some issues solving them then just post away and we'll try to help you as much as we can.
The forum users do help each others so don't be afraid of asking.

To speed up your learning curve I would suggest taking on a packaging course.

ORIGINAL: AngelD

To speed up your learning curve I would suggest taking on a packaging course.



I went to a course but it was early this spring. I had never worked with WPS before that. I had never even seen it before that. So then I come back to work and never had the time to start package. So I started off now with doPDF.

I know that I have to work hard to learn it good so I think Im gonna post alot here and it feels good to know that theres people out there that are ready to help out if it is something.

Thanks!

hi..guys..thanks for the information posted above. it helped me a lot but i m still stuck in creating msi for cutepdf. I am having same issue. Printer not showing up. For cutePDF to run we need to include convertor as well with cutewriter. If anyone have worked on same or related ..please advice..thanks

Cutepdf is very simple.
During capture you first install the converter and then cutewriter.
Make sure to restart the Spooler service, that's it.

AngelD: I'm new to this site but your explanation in this thread were a big help so I have joined the site.[:D] I use Wise and I had a default exclusion to hardware installations that prevented the capture from being successful. Once I recaptured the installation (CutePDF), I did not need to add the reg entries manually. I still needed to restart the Spooler for the printer to show up so, if you have a Wise solution to restart the Print Spooler from within the MSI, it would be greatly appreciated. I see you mentioned the solution in your post #24 and I think you were giving the URL for Altiris as a how to... in post #25 but the link is no longer valid. Thanks again for your help
Pat

to start spooler, net start spooler.
you may also want to look at prn*.vbs in your system32 directory as they offer a lot of functionality for printers without having to kludge stuff like cutepdf.

Altiris archives threads older then 180 days if I recall correct, so the "archive" link would be:
http://forums.altiris.com/messageview.aspx?catid=19&threadid=43741&arctab=arc