I tried compiling and installing the sample print monitor localmon from the
WindowsIFT kit samples.
Using Win2K checked build the localmon dll got built, but localui failed. I
had to use teh winXP checked build option to build it. Why?
Also In the documentation it is stated that monitor.inf can be used to
install the driver.
I did so, but how do I actually check whether the dll is loaded and is
functioning. I cant find any dos about that.
Can some one help?
Bedanto
> Using Win2K checked build the localmon dll got built, but localui
failed. I had to use teh winXP > checked build option to build it. Why?
To answer the question, you’ll have to describe how the build of localui
failed.
To see if the monitor is installed and working, assign a printer driver
to use it and print from an application to that printer driver. You
could put some tracing code in the monitor and use a debugger or
DebugView to see it. Or you could put calls to MessageBox() in the
monitor (however, this could get pretty annoying :-))
Here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/graphic
s/hh/graphics/provider_81f595db-3146-48ba-8d0b-5eabe4fdb340.xml.asp
is some good information on print monitors.
ScottR
Scott,
To answer the question, you’ll have to describe how the build of localui
failed.
Here is the output of “build”
F:\WINDDK\3790\src\print\monitors\localui>build
BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang.
BUILD: Object root set to: ==> objchk_w2K_x86
BUILD: Compile and Link for i386
BUILD: Loading F:\WINDDK\3790\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Examining f:\winddk\3790\src\print\monitors\localui directory fo
o compile.
f:\winddk\3790\src\print\monitors\localui - 6 source files (1,416 l
BUILD: Saving F:\WINDDK\3790\build.dat…
BUILD: Compiling f:\winddk\3790\src\print\monitors\localui directory
BUILD: Linking f:\winddk\3790\src\print\monitors\localui directory
BUILD: Done
and that of build -cez
F:\WINDDK\3790\src\print\monitors\localui>build
BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang.
BUILD: Object root set to: ==> objchk_w2K_x86
BUILD: Compile and Link for i386
BUILD: Loading F:\WINDDK\3790\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Examining f:\winddk\3790\src\print\monitors\localui directory fo
o compile.
f:\winddk\3790\src\print\monitors\localui - 6 source files (1,416 l
BUILD: Saving F:\WINDDK\3790\build.dat…
BUILD: Compiling f:\winddk\3790\src\print\monitors\localui directory
BUILD: Linking f:\winddk\3790\src\print\monitors\localui directory
BUILD: Done
Strangely, both these work in the Xp environemnt.
To see if the monitor is installed and working, assign a printer driver
to use it and print from an application to that printer driver.
Well, exactly how do I do that, that is my question, I have no clue how to
procede with the assignment.
You
could put some tracing code in the monitor and use a debugger or
DebugView to see it. Or you could put calls to MessageBox() in the
monitor (however, this could get pretty annoying :-))
Aaah, that is trivial, once I can get the dll to work, those things can be
done…
no hassels in tht…
Bedanto
> Strangely, both these work in the Xp environemnt.
Well, if you look at the .LOG file build creates, you see a message
explaining that the sample is not valid for the current OS (win2000). I
*assume* it has something to do with mainifests, because there is a
.mainifest file in that directory. I think this is a XP UI feature.
To see if the monitor is installed and working, assign a printer driver
to use it and print from an application to that printer driver.
Well, exactly how do I do that, that is my question, I have no clue how
to procede with the assignment.
Open the printers folder. Right-click on one of the printers. Pick
properties. Select the ‘ports’ tab. In the list will be localmon.
Check the box for localmon. Press “OK”.
ScottR
>Well, if you look at the .LOG file build creates, you see a message
explaining that the sample is not valid for the current OS (win2000). I
*assume* it has something to do with mainifests, because there is a
.mainifest file in that directory. I think this is a XP UI feature.
Yes, I saw that, and made the same assumption, can any of the gurus here
explain the situation please.
I have seen teh manifest file many times, but dont know what exactly it is
used for. Can someone please enlighten me.
Open the printers folder. Right-click on one of the printers. Pick
properties. Select the ‘ports’ tab. In the list will be localmon.
Check the box for localmon. Press “OK”.
Well scott, even after installing the dlls by right clicking on
monitors.infand selecting the “Install” option the drivers don’t get
installed. I don’t
know why.
However, if I do an “Add Port Type” and direct it to minitors.inf it does
it, and then we have to do an “Add port” to create a port manually. Then we
can assign.I think the inf is incomplete.
But all this only work for XP, the monitor doesnt install on 2K, no matter
what I did.
I want to generate some additional custom logs when any document is printed,
I plan to tap the StartDoc method, I hope I am on the right track scott?
Bedanto
What is the issue with the manifest file? A manifest file just instructs
the windows common controls to use XP style themes opposed to the ‘classic’
windows look. It’s just an XML formatted file that the common controls
library reads… Manifest are also supposedly used for dll versioning
in xp,
but I’ve never used them that way, nor have I seen anyone else…
If you have any old applications on your xp system that have a w2k look,
you can add a manifest file to their directory and they will draw with the
XP style command buttons, xp progressbars, ect. (that is only if the old
app is references the windows common controls lib)
What again is the problem with the manifest file?? Since w2k doesn’t
support manifest, it should just ignore them…
Bedanto wrote:
>Well, if you look at the .LOG file build creates, you see a message
>explaining that the sample is not valid for the current OS (win2000). I
>*assume* it has something to do with mainifests, because there is a
>.mainifest file in that directory. I think this is a XP UI feature.Yes, I saw that, and made the same assumption, can any of the gurus
here explain the situation please.I have seen teh manifest file many times, but dont know what exactly
it is used for. Can someone please enlighten me.> Open the printers folder. Right-click on one of the printers. Pick
>properties. Select the ‘ports’ tab. In the list will be localmon.
>Check the box for localmon. Press “OK”.Well scott, even after installing the dlls by right clicking on
monitors.inf and selecting the “Install” option the drivers don’t get
installed. I don’t know why.However, if I do an “Add Port Type” and direct it to minitors.inf it
does it, and then we have to do an “Add port” to create a port
manually. Then we can assign.I think the inf is incomplete.But all this only work for XP, the monitor doesnt install on 2K, no
matter what I did.I want to generate some additional custom logs when any document is
printed, I plan to tap the StartDoc method, I hope I am on the right
track scott?Bedanto
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently
subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
unsubscribe send a blank email to xxxxx@lists.osr.com
Hi Matt,
What again is the problem with the manifest file?? Since w2k doesn’t
support manifest, it should just ignore them…
Well, that doesnt seem to be tha case. Try compiling the localui sample
inside \SRC\PRINT\MONITORS directory using the Windows 2000
checked build environment. It won’t compile. Check the log file for more
details.
Thanks,
Bedanto
Bedanto,
I don’t have a fully checked version of w2k, only partially checked…
It did build successfully, however, like I said, I’m only using a
partial checked version… Never the less, I don’t see why a manifest
file would affect you… Since I’m only using a partial check, try
removing the manifest and recompile on your FULLY checked machine.
Delete the manifest file out of the localui directory, and then open the
SOURCES file and comment out the SXS_ lines listed under #FUSIONIZED
Do that, and then try to compile and let me know if that works…
Matt
Bedanto wrote:
Hi Matt,
>What again is the problem with the manifest file?? Since w2k doesn’t
>support manifest, it should just ignore them…Well, that doesnt seem to be tha case. Try compiling the localui
sample inside \SRC\PRINT\MONITORS directory using the
> Windows 2000 checked build environment. It won’t compile. Check the
> log file for more details.
>
> Thanks,
>
> Bedanto
> — Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256 You are currently
> subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
> unsubscribe send a blank email to xxxxx@lists.osr.com
after reading this, I really think my english is not good enough. I never
said I am using a checked build of windows, I said I compiled using the
checked build option of build environments in IFS kit.
LOL, sad thing is I’m a native english speaker… I realized I
misinterpreted you after I sent the message… Regardless of my mistake,
I was using the Checked Option when compiling. The build on w2k was fine…
Bedanto wrote:
after reading this, I really think my english is not good enough. I
never said I am using a checked build of windows, I said I compiled
using the checked build option of build environments in IFS kit. —
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently
subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
unsubscribe send a blank email to xxxxx@lists.osr.com
well what ever be the case, it didnt compile in mine, neither did it for
scoot from Xerox, did it scott?
What is your config? I’m using W2k sp4 with ifs 2003 sp1 build 3700. In
partial checked and in retail it builds fine for me? Your not passing
some screwed up
path to the build tool are you? are you sure you don’t have any spaces
or dashes or anything stupid in the path to the source files? (I forget
the rules on that).
If you copy the localui folder to your root drive (assuming it’s C:)
will it compile there? This builds fine for me. Looking at your build
output listed the other day, BUILD didn’t even try it looks like, the
only time that has happened to me was when the builder didn’t like the
path I gave it…
Bedanto wrote:
well what ever be the case, it didnt compile in mine, neither did it
for scoot from Xerox, did it scott?— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently
subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
unsubscribe send a blank email to xxxxx@lists.osr.com
>What is your config? I’m using W2k sp4 with ifs 2003 sp1 build 3700.
I have win2K pro, Sp4, all patches installed.
IFSKIT build 3790
In partial checked and in retail it builds fine for me? Your not passing
some screwed up
path to the build tool are you? are you sure you don’t have any spaces
or dashes or anything stupid in the path to the source files? (I forget
the rules on that).
I just went into the folder and typed build, even buils -cez doesnt work.
the localmon dll builds, but hte ui part doesnt.
If you copy the localui folder to your root drive (assuming it’s C:)
will it compile there? This builds fine for me.
No it doesnt. Here is the output…
C:\localui>build
BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang.
BUILD: Object root set to: ==> objchk_w2K_x86
BUILD: Compile and Link for i386
BUILD: Loading F:\WINDDK\3790\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Examining c:\localui directory for files to compile.
c:\localui - 6 source files (1,416 lines)
BUILD: Compiling c:\localui directory
BUILD: Linking c:\localui directory
BUILD: Done
Looking at your build
output listed the other day, BUILD didn’t even try it looks like, the
only time that has happened to me was when the builder didn’t like the
path I gave it…
Hmmm looks like the damned builder doesnt like my face 
damn, don’t know what too tell you… actually, I’m using 3790 like
you, not 3700, my bad… Umm, this is working for me… I don’t see
why the build tool and linker are doing this… You didn’t make a dumb
basic mistake like I have before by installing a second ddk did you? I
installed the ifs ontop of and existing ddk when I first got it, and
that killed the build enviroment. When I made that fatal mistake, I also
had this same problem (just like when I had spaces in the path), same
output - whole lotta jack shit.
If you upgraded an existing ddk to the ifs, double check you did it
right… You can only have a single driver kit builder installed at a
time… Other than that, I’m out of ideas on this one…
Matt
Bedanto wrote:
>What is your config? I’m using W2k sp4 with ifs 2003 sp1 build 3700.
I have win2K pro, Sp4, all patches installed.
IFSKIT build 3790
>In partial checked and in retail it builds fine for me? Your not
passing some screwed up
>path to the build tool are you? are you sure you don’t have any spaces
>or dashes or anything stupid in the path to the source files? (I forget
>the rules on that).I just went into the folder and typed build, even buils -cez doesnt
work. the localmon dll builds, but hte ui part doesnt.>If you copy the localui folder to your root drive (assuming it’s C:)
>will it compile there? This builds fine for me.
No it doesnt. Here is the output…C:\localui>build
BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang.
BUILD: Object root set to: ==> objchk_w2K_x86
BUILD: Compile and Link for i386
BUILD: Loading F:\WINDDK\3790\build.dat…
BUILD: Computing Include file dependencies:
BUILD: Examining c:\localui directory for files to compile.
c:\localui - 6 source files (1,416 lines)
BUILD: Compiling c:\localui directory
BUILD: Linking c:\localui directory
BUILD: Done>Looking at your build
>output listed the other day, BUILD didn’t even try it looks like, the
>only time that has happened to me was when the builder didn’t like the
>path I gave it…Hmmm looks like the damned builder doesnt like my face
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently
subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
unsubscribe send a blank email to xxxxx@lists.osr.com
>You didn’t make a dumb
basic mistake like I have before by installing a second ddk did you? I
installed the ifs ontop of and existing ddk when I first got it, and
that killed the build enviroment. When I made that fatal mistake, I also
had this same problem (just like when I had spaces in the path), same
output - whole lotta jack shit.
Actually I have two machines, on one I *did* install the ifs with another
DDK, both co-exist (microsoft claims that it is possible), both compile and
link (except this sample), the second machine (same configuration h/w and
s/w) has only IFS, clean installation, and the same problem is there too!!!
You can only have a single driver kit builder installed at a
time… Other than that, I’m out of ideas on this one…
Wow, wow, I don’t think that is what was written in the documentaiton? Or am
I having a mem failure too…can’t help it, with X-mas round the
corner…remembering these things become difficult…
anyway, my first machine does have both and things do work, the second
machine being clean of DDK should behave , but doesnt…
Never heard of making two different ddk’s co-exist, although I’m sure
it’s possible somehow… Actually, I’ve read many times it is unwise to
install two different ddks. I would hope someone more experianced on
this list could clarify this…
Bedanto wrote:
>You didn’t make a dumb
>basic mistake like I have before by installing a second ddk did you? I
>installed the ifs ontop of and existing ddk when I first got it, and
>that killed the build enviroment. When I made that fatal mistake, I also
>had this same problem (just like when I had spaces in the path), same
>output - whole lotta jack shit.Actually I have two machines, on one I *did* install the ifs with
another DDK, both co-exist (microsoft claims that it is possible),
both compile and link (except this sample), the second machine (same
configuration h/w and s/w) has only IFS, clean installation, and the
same problem is there too!!!>You can only have a single driver kit builder installed at a
>time… Other than that, I’m out of ideas on this one…Wow, wow, I don’t think that is what was written in the documentaiton?
Or am I having a mem failure too…can’t help it, with X-mas round the
corner…remembering these things become difficult…anyway, my first machine does have both and things do work, the second
machine being clean of DDK should behave , but doesnt…
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently
subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
unsubscribe send a blank email to xxxxx@lists.osr.com
Actually, I am using DDK 3790.1830 (and assuming it’s pretty much the
same as the IFS). If you look at MAKEFILE, you will see that it checks
what the target is and produces the message if it is less than (nt 5.1).
It is possible that removing this check will make localui build. I
doubt it is supported, though.
ScottR
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Bedanto
Sent: Friday, December 23, 2005 8:19 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] localmon
You didn’t make a dumb
basic mistake like I have before by installing a second ddk did you? I
installed the ifs ontop of and existing ddk when I first got it, and
that killed the build enviroment. When I made that fatal mistake, I
also
had this same problem (just like when I had spaces in the path), same
output - whole lotta jack shit.
Actually I have two machines, on one I *did* install the ifs with
another DDK, both co-exist (microsoft claims that it is possible), both
compile and link (except this sample), the second machine (same
configuration h/w and s/w) has only IFS, clean installation, and the
same problem is there too!!!
You can only have a single driver kit builder installed at a
time… Other than that, I’m out of ideas on this one…
Wow, wow, I don’t think that is what was written in the documentaiton?
Or am I having a mem failure too…can’t help it, with X-mas round the
corner…remembering these things become difficult…
anyway, my first machine does have both and things do work, the second
machine being clean of DDK should behave , but doesnt…
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently subscribed
to ntdev as: unknown lmsubst tag argument: ‘’ To unsubscribe send a
blank email to xxxxx@lists.osr.com
Newer DDKs coexist easily. I have 3790, 3790.1830, and 5112 (which I
think is a longhorn beta, but I never use it and don’t remember why it’s
there) all on one machine right now.
Older DDKs didn’t coexist so happily.
ScottR
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of MM
Sent: Friday, December 23, 2005 8:41 AM
To: Windows System Software Devs Interest List
Subject: Re: [ntdev] localmon
Never heard of making two different ddk’s co-exist, although I’m sure
it’s possible somehow… Actually, I’ve read many times it is unwise to
install two different ddks. I would hope someone more experianced on
this list could clarify this…
Bedanto wrote:
>You didn’t make a dumb
>basic mistake like I have before by installing a second ddk did you?
>I installed the ifs ontop of and existing ddk when I first got it,
>and that killed the build enviroment. When I made that fatal mistake,
>I also had this same problem (just like when I had spaces in the
>path), same output - whole lotta jack shit.Actually I have two machines, on one I *did* install the ifs with
another DDK, both co-exist (microsoft claims that it is possible),
both compile and link (except this sample), the second machine (same
configuration h/w and s/w) has only IFS, clean installation, and the
same problem is there too!!!>You can only have a single driver kit builder installed at a time…
>Other than that, I’m out of ideas on this one…
Wow, wow, I don’t think that is what was written in the documentaiton?
Or am I having a mem failure too…can’t help it, with X-mas round the
corner…remembering these things become difficult…
anyway, my first machine does have both and things do work, the second
machine being clean of DDK should behave , but doesnt…
— Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256 You are currently
subscribed to ntdev as: unknown lmsubst tag argument: ‘’ To
unsubscribe send a blank email to xxxxx@lists.osr.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@xerox.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
scott,
with my limited knowledge, and what Matt told me about manifests, I cannot
understrand why this should be a show stopper!!!
Bedanto
MM wrote:
What is your config? I’m using W2k sp4 with ifs 2003 sp1 build 3700.
In partial checked and in retail it builds fine for me? Your not
passing some screwed up
path to the build tool are you? are you sure you don’t have any spaces
or dashes or anything stupid in the path to the source files? (I
forget the rules on that).
Well, I can tell you that it definitely does not build in the Windows
2000 environment in the 3790.1830 DDK. Building it gets this:
C:\DDK\3790~1.183\src\print\monitors\localui>type buildfre_w2K_x86.wrn
1>BUILDMSG: Warning : The sample
“c:\ddk\3790~1.183\src\print\monitors\localui” is not valid for the
current OS target.
101>BUILDMSG: Warning : The sample
“c:\ddk\3790~1.183\src\print\monitors\localui” is not valid for the
current OS target.
1>BUILDMSG: Warning : The sample
“c:\ddk\3790~1.183\src\print\monitors\localui” is not valid for the
current OS target.
Even if you comment out this check in makefile, it has a missing symbol.
None of that involves the manifest, however.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.