Image analysis with PS CS3 EE

First off, I need to apologize if I am not very clear on this issue Im fairly math challenged and know enough about Excel to fill out a time sheet and make an invoice. If this kind of thing is up your alley, you are just what were looking for.
We are attempting to use the image analysis tools in CS3 EE and Microsoft Excel to determine a number of things in order for a set of photo images to meet a given set of requirements. Most of this has to do with examining histograms and determining things like average pixel levels for each of RGB channels, % of pixels in a given range, and percentage of the image that is clipped. This analysis would be done on a random sample of files in order to show the client that the images meet their standards.
Some starting questions:
From what I see of the CS3 analysis tool, it seems to zero in on the gray channel information (perhaps this was developed for the medical diagnostic community) and Im wondering if you can export the same information (Gray Value Minimum-Maximum-Mean) for the R, G and B channels.
Does anyone already have the Excel formulas for extracting this information for the Histogram.csv that is generated by the analysis features?
This ones a bit murky - is there any method to calculate the numeric value of Contrast (the difference between the histogram reading at .01 and 99% and have that as exportable data?
This one is more like a feature request (or is there another plug-in or other software to do this):
Is it possible to view all three channels (RGB) with the same detailed histogram information as the main view, without having to toggle between the various bands?
Anyway, I know this long and I appreciate your time. I will follow this post closely and if you think you can help Id be happy to go off forum with this.
Thanks! TLL

I'm envisioning doing this in AppleScript, and am assuming a histogram in JS is the same...
>% of pixels in a given range
Divide 256 by however many "range segments" you need. For simplicity, let's say 3: highlight, midtone, and shadow ranges. So (roughly) levels 0-85 are shadows, 86-171 are midtones, and 172-255 are highlights. You would iterate through each range of the histogram counting the number of pixels for that range. Divide each count by the total number of pixels.
>percentage of the image that is clipped.
The amount of clipping can be determined by how many pixels are dedicated to levels 0 and 255 of the histogram. If those levels have a high number of pixels, then you have clipping. You have to define for yourself what "high number" means, but in a "perfect" photo, you won't have pixels at levels 0 or 255 (pure white and pure black).
Carl.

Similar Messages

Why can I no longer open images with Photoshop CS3, running on Mac OS 10.4.11?

Why can I no longer open images with Photoshop CS3, running on Mac OS 10.4.11?

You may be able to drag and drop the icons from one toolbar onto another, you can then hide the toolbar that you no longer need. For details on how to do that see https://support.mozilla.com/kb/How+to+customize+the+toolbar

Colours change badly when LR2.5 image sent to Photoshop CS3

When I right click in LR on an image and "edit in CS3" the image opens in CS3 with a horrible magenta and/or blue colour cast that is difficult to remove.
I have set LR to export in AdobeRGB, and CS3 edits in AdobeRGB.
This is new behaviour, since I got a Canon 50D but I assume this is coincidence.
The effect is variable, worse on some images than others, so I can use no automatic workaround to fix the shift.
It is ruining my workflow. I've searched on everything I can think of in forums and help.
- Win XP SP3
- both screens calibrated with GretaMacbeth Eye-one
I observe that:
a) even the dialog boxes in the two programs have completely different colours, not sure if that is supposed to be so.
b) CS3 says that my CS apps are not sync'd for consistent color. I don't know what other apps I may have, or why this is so.
Attached -
- my external edit prefs and CS3 colour settings
- sample image screen capture in LR
- same image screen captured in CS3
Thanks
Julian

This seems to have died. I've answered a few questions but no responses to those reqested infos, and no answer forthcoming.Some responses suggest that my post has not even been read properly and the only suggestions made have been inappropriate to my posted info.
Can anyone tell me how I get effective help for Adobe products? I am more than jaded with the facts that:
- Adobe software in general and Lightroom especially has almost useless help files/website. Adobe seems to rely on a) 3rd parties and b) a collection of informal only sometimes professional often independent (uncoordinated) resources that are as disparate as they are confused to provide help and usage training. The help available from "Help" menu item is incomplete and often, if not mostly, missing the point for which you are seeking info.
- Adobe software including Acrobat reader (inside Firefox), CS3 and Lightroom are the ONLY softwares that crash my system or do not work reliably.
- Adobe phone and email support is entirely, completely and fully useless for anything beyond certain standard problems. The only offered solution to anything I've ever rung or emailed about has been "uninstall and re-install" after demanding enormous amounts of information that was probably irrelevant or ignored but consumed considerable effort and time to provide.
- when you DO uninstall and reinstall Photoshop, you find it is the only software I know of that routinely loses all your settings and actions in the process.
- and so far, uninstall and reinstall has never resolved any Adobe problem on my machine.
- Adobe more than any other provider seem to rely on new PAID upgrades as the suggested means of resolving bugs and other problems that are intrinsic to the software, and Adobe don't continue to maintain older versions.
So - here I am with what is to me a serious problem, and I have no visible means of useful tech support.
People like me are always being criticised on these forums for being cross and frustrated, with smooth talking smug folk saying that you'd get better results if you were polite. The trouble is it is difficult to remain polite when you see no available solution, a lot of time taken up and no APPARENT determination by Adobe to provide support that actually meets people's needs, or at least people with non-standard problems.
I don't believe I've been rude here, but it's now 4 days and I'm no nearer to solving the problem.
Could someone suggest how to get effective help with this problem, or other problems from Adobe?
Thanks
Julian

Colour Management Issue with PS CS3 and Leopard 10.5.2

Hi Everyone,
Since I have installed Leopard I am having colour management issues with Photoshop CS3 and my Canon i9950 printer.
My screen is calibrated with a Spyder and I used to ask Photoshop (in 10.4.11) to manage colour when printing and used the Spyder profile. Everything came out as I saw it on screen.
Now in leopard when I do the same thing everything comes out too yellow on the print. If I ask Photoshop to let the printer manage the colour it is too red. If I use the default colour management (photoshop managing the colour and it choosing the colour space it is better, but still too yellow).
Photoshop gives the hint to turn off colour management in the printer but there is no option for this and it also said the same thing before of course (when it worked in 10.4.11).
Any ideas?
Thanks.

>It was working perfectly in Tiger with the monitor profile.
You were lucky.
the monitor profile is so Photoshop can display your images correctly.
the working space is Adobe RGB, sRGB, BruceRGB, ect... these are all known color spaces so when the file goes to another computer there is a consistent color space for reference. If you use your monitor profile as a working space then nobody else knows what is going on with your file.
when you print you need to use the printer profile for the type of paper you are printing on this is supplied by the printer manufacturer. you can also have custom profiles made.
you need to read up on color management:
http://www.gballard.net/psd.html
http://digitaldog.net/

Bridge 3 Image weirdnes with two monitorss

I have CS3 installed on a MAC G5 with two monitors.. When I open Bridge and choose a file to open, no images appear. If I move the window across to my second monitor, images appear. If I try to open a folder by dropping it on Bridge, same thing, no images appear, move it to the second monitor, images appear. If Itry to scroll down to other images, nothing happens, I drag the window across to the other monitor, the images appear scrolled.
I'm running the latest upgrade.
Any ideas?
Butch Hulett
PS: I have Bridge 2 installed as well, it works fine.

>PS: I have Bridge 2 installed as well, it works fine.
Bridge 2.1.1.9 is the current, latest version of Bridge in CS3.
The version of Bridge that comes with Photoshop CS3 is Bridge 1.x.
Have you trashed the Bridge preferences? Hold down the Option key as you relaunch Bridge, then check all the boxes in the dialog box that appears.
Also, use te Tools menu in Bridge to Purge the cache for each folder, one by one. DO NOT use the global Purge Cache command in Bridge. It's broken, and the caches do not rebuild properly after using it.

Image opens with reddish tinge

When I open one particular image in photoshop CS3 the thumb in the Open menu looks correct, but the image opens with a reddish tinge over the whole thing. If I then double-click the image layer in the Layers window, the Layer Style menu pops up, the tinge removes itself and the image looks as it should. None of the other images I've been working on have this happening.
Does anyone know what's up here. This is a .psd file with no layers above the image layer.

freedda wrote:
So, how do I disable quick mask in the image?
Press Q and save the file without the mask. You could also delete the extra channel in the Channels palette.

Little Problem with Photoshop CS3

Hi, I have a little problem with Photoshop CS3, I'm not sure if this's because a Windows option that I messed up, but the thing is that I didn't touch any options, or some kind of preferences.
I'm talking about the "little windows" (I don't know the correct name) that come from, in this case, the Filter and Analysis options, they're coming down from their right side, and usually, the come down from their left side. This is really annoying.
Not big deal, but I can't really work properly. I hope you guys can help me, and this's my first post, I hope I didn't break any rule.

Thanks Mylenium, that was the problem, I don't even have a tablet, but that fixed my problem =)
Thanks again.

Image analysis

Hi, I would like to know if the Cisco IronPort email security supports the Image analysis, If yes what is there any license required? Thank you

Yes, its under "Security Services>Image Analysis"
Its does require a feature key.
Check with your reseller for pricing... they might be able to get you a demo key so you can see if it catches what you want it to catch...

Intermedia Image Analysis cant find DLL

Win2k, Oracle 8.1.6EE. Fresh installations.
With a new installation of Oracle, create a SHARED database using connection pooling etc. On another identical machine also create a standard default database from the CD.
On both the standard default database and the shared one, can set the properties of images in ORDVIR objects.
Only on the default can I analyse the images. On the shared I get the following error:
err:ORA-06520: PL/SQL: Error loading external library
ORA-06522: Unable to load
DLL at 10000100
I've not changed the SQLNET, TNSNAMES or LISTENER since the setup did it for me as it looks OK, and as I say - works for setting the properties, just not the image analysis.
Any ideas?
Here are the files:
# SQLNET.ORA Network Configuration File: C:\Oracle\Ora81\network\admin\sqlnet.ora
# Generated by Oracle configuration tools.
NAMES.DEFAULT_DOMAIN = web.cre8tiv.com
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES)
# LISTENER.ORA Network Configuration File: C:\Oracle\Ora81\network\admin\listener.ora
# Generated by Oracle configuration tools.
LIVELISTENER1 =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rioja)(PORT = 1521))
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
SID_LIST_LIVELISTENER1 =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = C:\Oracle\Ora81)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = islive1.web.cre8tiv.com)
(ORACLE_HOME = C:\Oracle\Ora81)
(SID_NAME = islive1)
# TNSNAMES.ORA Network Configuration File: C:\Oracle\Ora81\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
ISLIVE1.WEB.CRE8TIV.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rioja)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = islive1.web.cre8tiv.com)
(INSTANCE_NAME = islive1)
EXTPROC_CONNECTION_DATA.WEB.CRE8TIV.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC0))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
Thanks, Jason.

Thanks - this does appear to be the problem.
I can reproduce this affect on any clean machine with a fresh install so there is obviously an Oracle bug here.
Running the command
select FILE_SPEC from all_libraries where library_name = 'ORDVIRLIBS';
gives the output
C:\Oracle\Ora81\lib\libordvir8.so
for any non-default installation of a database created using the DBCA which uses InterMedia&Virage.
The file libordvir8.so doesn't exist.
It should have been oraordvir8.dll in the bin directory which does exist.
Thanks,
Jason.
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by lguros():
You may want to do a
select library_name from all_libraries where library_name = 'ORDIMLIBS';
and
select library_name from all_libraries where library_name = 'ORDVIRLIBS';
and make sure the FILE_SPEC field is valid and points to a correct shared object or DLL.
If you DB location was moved, these will no longer be valid.<HR></BLOCKQUOTE>
null

Jpeg images produced by Ps CS3 won't play via DVD player

When I burn my jpeg digital camera images to CD or DVD, they display without problems on my TV via the DVD player.
However, when I process them using Ps CS3 (e.g. rotate, enhance etc.) then save them as jpeg images, they will not play when transferred to CD or DVD, giving a message 'jpeg decoding error'. They do display OK in the PC.
This does not happen when the camera originals are processed using Adobe Photoshop Elements 2. They all display properly.
Why do jpeg images created with Elements work, but those created with Ps CS3 not? Am I not setting some preference or other correctly?
I run Windows XP SP3 on an HP Pavilion PC with 512 Ram.

Did you set the button routing manually, or leave "Automatic" set instead?
Try unchecking the "Route Buttons Automatically" in the menu editor, and you will see a set of icons appear with a central number & 4 extensions going Up/Down/Left/Right.
These are the available options for navigation - just drag the pointer from the button to the button you want to link it to and all will be fine.
Note:
When previewing, never
i ever
just use the mouse. DVD players do not have mice, and navigation is done with the remote unit - so try previewing with the simulated remote control instead to avoid problems recurring!

White Lines appear on Images in Adobe Photoshop CS3

White Lines appear on Images in Adobe Photoshop CS3
Recently discover that on three different computers, while editing images in Adobe Photoshop CS3, white lines would appear on some of the images.
For example changing a image from a .jpg to a .psd or size, or enchantment features, the white lines would appear on the image.
The lines did not appear on any of the printed images, any suggestions.
Monitor: Sony Trintron Multiscan G4110
Computer: Mac G5

>The lines did not appear on any of the printed images,
Although it is odd that three computers exhibit the same problem, and unless you can provide other coincidences (same files, same monitor, etc.), I agree. The video card is typically the culprit IF the image anomalies don't print and if they move about with each image resizing or opening of a specific image. Check to see if it's properly seated and connected. Same for monitor cable. Try swapping in another card.
One other thought: as this is a CRT monitor, what happens if you change the resolution and refresh rate? Are you using a recommended combination for that monitor?
Neil

Problem with compression with flash cs3

our web developper says that she was unable to compress image
with flash cs3 any idea why and what i can do for her ?
Thanks

Mark,
> I have set my publish settings to Flash Player 9.0 and
Actionscript
> 3.0, but keep getting an error as follows:
>
> "WARNING: The component 'FLVPlayback' requires
ActionScript 2.0."
Gotcha. You must have started the document in AS2, then
changed the
publish settings. Each version of the language has its own
version of the
FLVPlayback Component (written in the relevant language).
Start over and
compare two compleley new FLA documents: make one for AS3 and
one for AS2.
Open the Components panel and note the differences between
the two. There
are a different set of Components depending on the language
chosen for the
document. Drag the FLVPlayback Component from the Components
panel in an
AS3 document, and you'll have the AS3 version.
David Stiller
Co-author, Foundation Flash CS3 for Designers
http://tinyurl.com/2k29mj
"Luck is the residue of good design."

Photoshop-When opening image without tab view, image opens with only a portion in view

I having an issue with CC.
When electing in the preferences to not open image in Tabs. The images open with only about 25% of the image area showing. Forcing me to (command) 0 for full to screen preview or (command) +/- to see the image.
I am not talking about seeing the image at 100% resolution just the entire image within the floating window without having to command before view.
Sidenote: Adobe Customer Service is all based in India. I spent 4 hours on the phone only to hear that this is that way photoshop works.
There would be no logical explanation for this. Since the first version of Photoshop this has not been the case.
I think this should be called view porn with wife in the room mode. Other than that I see no point.
Can anyone help?
Lv
Chadwick Tyler

Moving discussion to Photoshop forum.

Image processing with imaq vision with 2 webcams on the same computer

Hi,
I'm currently trying to set up 2 usb webcams (logitech quickcam for notebooks pro). I want to be able to have them both run simultaneously and do some image processing with the images that I get from both cameras with labview and imaq vision.
As of right now, I'm having trouble getting both cameras to run at the same time. Any help would be gladly appreciated. Thanks.

The USB IMAQ driver will not support running 2 USB cameras at a time (I believe it is a limitation of the DirectShow interface). You could open one camera, acuqire an image, close the reference to that camera and then do the same for the second camera.
If you need simultaneous acquisition, look at possibly moving to 1394 cameras or analog cameras.

Unable to run code analysis with WDK 9926

Hi,
I am trying to run code analysis with WDK 9926 and seeing below issue? can anybody help me to resolve this ?
Error:
====
C:\sw\dev\T4\windows\Src\kernel\vbd>msbuild.exe cht4vbd.vcxproj /p:Configuration="Windows 8.1 Debug" /P:Platform=x64 /P:RunCodeAnalysisOnce=True
Microsoft (R) Build Engine version 12.0.21005.1
[Microsoft .NET Framework, version 4.0.30319.33440]
Copyright (C) Microsoft Corporation. All rights reserved.
Build started 4/7/2015 12:08:30 AM.
Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" on node 1 (defaul
t targets).
DriverBuildNotifications:
Building 'cht4vbd' with toolset 'WindowsKernelModeDriver10.0' and the 'Deskto
p' target platform.
Using KMDF 1.11.
PrepareForBuild:
Creating directory "x64\Windows8.1Debug\".
Creating directory "C:\sw\dev\T4\windows\Src\kernel\vbd\x64\Windows8.1Debug\c
hk\x64\".
Creating directory "x64\Windows8.1Debug\cht4vbd.tlog\".
InitializeBuildStatus:
Creating "x64\Windows8.1Debug\cht4vbd.tlog\unsuccessfulbuild" because "Always
Create" was specified.
StampInf:
c:\Program Files (x86)\Windows Kits\10\bin\x86\stampinf.exe -d "*" -a "amd64"
   -k "1.11" -f x64\Windows8.1Debug\chvbdx64.inf
Copying "C:\sw\dev\T4\windows\Src\kernel\vbd\chvbdx64.inf" to "x64\Windows8.1
Debug\chvbdx64.inf" for stamping
Using version information from c:\Program Files (x86)\Windows Kits\10\Include
\shared\\ntverp.h
Could not open version header file c:\Program Files (x86)\Windows Kits\10\Inc
lude\shared\\bldnump.h. (0x00000002)
Could not determine version information. Please specify using -v option.
Updates common INF file directives
        USAGE:
        stampinf -f filename [-s section] [-d <xx/yy/zzzz> | *]
                 -a architecture -n [-c catalogfile]
                             [-v <w.x.y.z> | *]
                             [-k nnnnn] [-u nnnnn]
                             [-i path]
        -f specifies the INF file to process
        -s specifies the INF section to place the DriverVer= directive. By
            default this directive is placed in the [Version] section.
        -d specifies the date written in the DriverVer= directive. Note that
            a '*' given for a date value means for stampinf to write the
            current date. If the date is not specified, the date is taken
            from the STAMPINF_DATE environment variable.
        -v specifies the version written in the DriverVer= directive. Note
            that a '*' given for a version value means for stampinf to write
            the current time (h.m.s.ms). This is useful during development
            in order to get increasing version numbers. If the version is not
            specified, its value is taken from the STAMPINF_VERSION
            environment variable.
        -a specifies the architecture string to replace the $ARCH$ keyword.
            The $ARCH$ keyword is used to tailor a TargetOSVersion decoration
            in a [Manufacturer] section, as well as its respective section
            name, to a specific platform. If no value is specified, stampinf
            takes its value from the _BuildArch environment variable.
        -c specifies the value to be written in the CatalogFile= directive
            in the [Version] section. By default, this directive is not
            written.
        -k specifies the version of KMDF that this driver depends on. This
            is used to tailor the KmdfLibraryVersion & KMDF co-installer name
            in the INF. This will replace the $KMDFVERSION$ and
            $KMDFCOINSTALLERVERSION$ keywords in the INF. The string is of
            the format:
                <major_version>.<minor_version>
            As an example, supplying 1.5 as the version string will result in
            values of 1.5 and 01005 for the two keywords (respectively).
        -u specifies the version of UMDF that this driver depends on. This
            is used to tailor the UmdfLibraryVersion & UMDF co-installer name
            in the INF. This will replace the $UMDFVERSION$ and
            $UMDFCOINSTALLERVERSION$ keywords in the INF. The string is of
            the format:
                <major_version>.<minor_version>.<service_version>
            (where service_version is generally zero)
            As an example, supplying 1.5.0 as the version string will result
            in values of 1.5.0 and 01005 for the two keywords (respectively).
        -i specifies the location of ntverp.h file.
            path represent the fully qualified
            location of the directory containing ntverp.h.
        -n noisy mode shows verbose stampinf output
          -x removes the coinstaller tag from the file and replaces the line w
ith a ";"
        NOTES:
        The environment variable PRIVATE_DRIVER_PACKAGE can be set to
        enable stampinf's 'developer mode' behavior. When this is
        set, the date and version used for DriverVer is set to the
        current date and time, regardless of the command line
        settings. Also, 'CatalogFile=delta.cat' is written to the
        version section, unless a catalog was already specified
        with '-c'.
c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355,5
): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Src\
kernel\vbd\cht4vbd.vcxproj]
Done Building Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (de
fault targets) -- FAILED.
Build FAILED.
"C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (default target) (1) ->
(StampInf target) ->
c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355
,5): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Sr
c\kernel\vbd\cht4vbd.vcxproj]
    0 Warning(s)
    1 Error(s)
Time Elapsed 00:00:04.07
Thanks, Krishna

Hi,
I am trying to run code analysis with WDK 9926 and seeing below issue? can anybody help me to resolve this ?
Error:
====
C:\sw\dev\T4\windows\Src\kernel\vbd>msbuild.exe cht4vbd.vcxproj /p:Configuration="Windows 8.1 Debug" /P:Platform=x64 /P:RunCodeAnalysisOnce=True
Microsoft (R) Build Engine version 12.0.21005.1
[Microsoft .NET Framework, version 4.0.30319.33440]
Copyright (C) Microsoft Corporation. All rights reserved.
Build started 4/7/2015 12:08:30 AM.
Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" on node 1 (defaul
t targets).
DriverBuildNotifications:
Building 'cht4vbd' with toolset 'WindowsKernelModeDriver10.0' and the 'Deskto
p' target platform.
Using KMDF 1.11.
PrepareForBuild:
Creating directory "x64\Windows8.1Debug\".
Creating directory "C:\sw\dev\T4\windows\Src\kernel\vbd\x64\Windows8.1Debug\c
hk\x64\".
Creating directory "x64\Windows8.1Debug\cht4vbd.tlog\".
InitializeBuildStatus:
Creating "x64\Windows8.1Debug\cht4vbd.tlog\unsuccessfulbuild" because "Always
Create" was specified.
StampInf:
c:\Program Files (x86)\Windows Kits\10\bin\x86\stampinf.exe -d "*" -a "amd64"
   -k "1.11" -f x64\Windows8.1Debug\chvbdx64.inf
Copying "C:\sw\dev\T4\windows\Src\kernel\vbd\chvbdx64.inf" to "x64\Windows8.1
Debug\chvbdx64.inf" for stamping
Using version information from c:\Program Files (x86)\Windows Kits\10\Include
\shared\\ntverp.h
Could not open version header file c:\Program Files (x86)\Windows Kits\10\Inc
lude\shared\\bldnump.h. (0x00000002)
Could not determine version information. Please specify using -v option.
Updates common INF file directives
        USAGE:
        stampinf -f filename [-s section] [-d <xx/yy/zzzz> | *]
                 -a architecture -n [-c catalogfile]
                             [-v <w.x.y.z> | *]
                             [-k nnnnn] [-u nnnnn]
                             [-i path]
        -f specifies the INF file to process
        -s specifies the INF section to place the DriverVer= directive. By
            default this directive is placed in the [Version] section.
        -d specifies the date written in the DriverVer= directive. Note that
            a '*' given for a date value means for stampinf to write the
            current date. If the date is not specified, the date is taken
            from the STAMPINF_DATE environment variable.
        -v specifies the version written in the DriverVer= directive. Note
            that a '*' given for a version value means for stampinf to write
            the current time (h.m.s.ms). This is useful during development
            in order to get increasing version numbers. If the version is not
            specified, its value is taken from the STAMPINF_VERSION
            environment variable.
        -a specifies the architecture string to replace the $ARCH$ keyword.
            The $ARCH$ keyword is used to tailor a TargetOSVersion decoration
            in a [Manufacturer] section, as well as its respective section
            name, to a specific platform. If no value is specified, stampinf
            takes its value from the _BuildArch environment variable.
        -c specifies the value to be written in the CatalogFile= directive
            in the [Version] section. By default, this directive is not
            written.
        -k specifies the version of KMDF that this driver depends on. This
            is used to tailor the KmdfLibraryVersion & KMDF co-installer name
            in the INF. This will replace the $KMDFVERSION$ and
            $KMDFCOINSTALLERVERSION$ keywords in the INF. The string is of
            the format:
                <major_version>.<minor_version>
            As an example, supplying 1.5 as the version string will result in
            values of 1.5 and 01005 for the two keywords (respectively).
        -u specifies the version of UMDF that this driver depends on. This
            is used to tailor the UmdfLibraryVersion & UMDF co-installer name
            in the INF. This will replace the $UMDFVERSION$ and
            $UMDFCOINSTALLERVERSION$ keywords in the INF. The string is of
            the format:
                <major_version>.<minor_version>.<service_version>
            (where service_version is generally zero)
            As an example, supplying 1.5.0 as the version string will result
            in values of 1.5.0 and 01005 for the two keywords (respectively).
        -i specifies the location of ntverp.h file.
            path represent the fully qualified
            location of the directory containing ntverp.h.
        -n noisy mode shows verbose stampinf output
          -x removes the coinstaller tag from the file and replaces the line w
ith a ";"
        NOTES:
        The environment variable PRIVATE_DRIVER_PACKAGE can be set to
        enable stampinf's 'developer mode' behavior. When this is
        set, the date and version used for DriverVer is set to the
        current date and time, regardless of the command line
        settings. Also, 'CatalogFile=delta.cat' is written to the
        version section, unless a catalog was already specified
        with '-c'.
c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355,5
): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Src\
kernel\vbd\cht4vbd.vcxproj]
Done Building Project "C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (de
fault targets) -- FAILED.
Build FAILED.
"C:\sw\dev\T4\windows\Src\kernel\vbd\cht4vbd.vcxproj" (default target) (1) ->
(StampInf target) ->
c:\Program Files (x86)\Windows Kits\10\build\WindowsDriver.common.targets(355
,5): error MSB6006: "stampinf.exe" exited with code 1. [C:\sw\dev\T4\windows\Sr
c\kernel\vbd\cht4vbd.vcxproj]
    0 Warning(s)
    1 Error(s)
Time Elapsed 00:00:04.07
Thanks, Krishna

Image analysis with PS CS3 EE

Similar Messages

Maybe you are looking for