RE: Printer Driver Migration - XP to Vista

Tech-Archive recommends: Fix windows errors by optimizing your registry



1. I guess you should use windows Vista Enviornment to build. You should make
sure your code is backword compitable.

2. Dont know about your code, but I think WDK is enough to build the code.
Using VC6 you will not be able to debug the binaries built by WDK.
To debug use VS2005 or Windbg.

3. I guess you are building your driver as a project from VC6. I am not sure
how exactly it would work.
I dont use VC6 for compiling and building ..rather I use command window and
simply build by build-cZ..
Its dificult to guess...you problem with the info given...

4. 3 answers for this too..

5. Yes I guess you should have 1 binary for all the drivers..you should make
sure your driver is backword compatible.

6. Windows Vista have strict rules for inf files... and file stated in inf
is not found failes the instalation..There can be many more reasons..

Email id for printer driver inquiries is "prninfo @ microsoft dot com"

-Naveen


"Nitin" wrote:

Hi,

We had developed printer drivers few years back that works well on
Win-2K and Win-XP. now we want to migrate it to Windows-Vista. What all
we need to do.

I have investigated about it by reading WDK documentation and some
articles on internet but now I am confused.

At link https://ms.helifan.net/whdc/DevTools/WDK/Win2k_install.mspx,
its written that
"In conformance with Microsoft support policy, Microsoft is removing
Windows 2000 from its list of supported installation platforms for the
Windows Driver Kit (WDK). The WDK continues to provide a Windows 2000
build environment for the development of drivers targeting Windows
2000."

and at link http://www.microsoft.com/whdc/devtools/ddk/default.mspx,
its written under "When to Use the Windows Driver Kit (WDK)" that -
"Use the Windows 2000 build environments in the WDK to build drivers
designed to run on Windows Vista, Windows Server 2003, Windows XP, or
Windows 2000. The Windows 2000 build environment in the WDK includes
updated headers and libraries for Windows 2000 Service Pack 4 (SP4)."

I have few queries -
1. Please tell me which WDK build environment should we use to build
the driver that is targetted to run on Windows-Vista. Also please tell
us which source code should we take as a base, Win-2K or Win-XP

2. What all things need to be installed to build the source code
properly. The existing Win-XP source code requires Windows Server 2003
DDK, MS Platform SDK-Feb 2003, Visual C++ 6.0 [SP5] to build it
properly.

3. We have installed the WDK and tried to build the existing Win-2K
source code with W2K build environment, but we are getting the
following errors -
*********************************************************************************************
errors in directory c:\printerdriver\printerinterface
c:\winddk\6000\bin\makefile.new(803) : error U1080: operator and/or
operand usage illegal
nmake.exe /nologo BUILDMSG=Stop. -i BUILD_PASS=PASS1 NOLINK=1
MAKEDIR_RELATIVE_TO_BASEDIR=
MAKEDIR_LOWERCASE=c:\printerdriver\printerinterface failed - rc = 2

BUILD: Compile errors: not linking c:\printerdriver\printerinterface
directory
BUILD: Finish time: Wed Jan 24 13:00:02 2007
BUILD: Done

0 files compiled - 2 Errors
*********************************************************************************************

These errors are coming in different modules also. The errors pasted
above is only for one module.

4. Do we have to set the VC environment variables each time we open the
WDK build environment. Because otherwise it give errors like [could not
find string.h]. This file is located in WinDDK\6000\inc\crt folder but
this folder is not searched for the header files.

5. Is it possible to have a single version of Printer Driver that works
for all Windows versions [2000, xp and vista].

6. There is a Compatibility mode in Windows-Vista. We have installation
setup for our printer driver. I ran the installation setup using the
compatibility mode and it ran successfully. The installation utility
adds the port monitor and print processor and copies all other driver
files in a folder. After this we need to install the printer driver
using the add printer wizard. But when I try to install the printer
driver using add printer wizard, it gives error saying that "Printer
driver was not installed. Operation could not be completed (error
0x0000007e)."

Can anybody please give me some hints what could be the issues.
Anybody from Microsoft???

I tried to send the mail to wdkfb@xxxxxxxxxxxxx but it bounced back.
Does anybody know the correct mail address where I can send these
queries to microsoft people.

Thanks,
Nitin


.



Relevant Pages

  • Re: CHKDSK NTFS file system corruption boot screen message flooding (SOLVED)
    ... Your Installation Specialist ... Windows XP SP3 detects a disk problem at boot time and runs chkdsk. ... or registry fix for large LBA drives, ... older Microsoft-certified ultra.sys driver. ...
    (microsoft.public.windowsxp.general)
  • Re: Printer Driver Migration - XP to Vista
    ... I have used WDK XP build env to build ... link under "When to Use the Windows Driver Kit " it is written ... "Use the Windows XP build environments in the WDK to build drivers ... us which source code should we take as a base, ...
    (microsoft.public.development.device.drivers)
  • Re: 0x000000D1 Message
    ... Uninstall it and let Windows re-install it to see what happens. ... Update then check the hardware section to see if an updated driver ... Your Installation Specialist ...
    (microsoft.public.windowsxp.general)
  • Re: Build Failed Message
    ... I can't build any driver or subset of the OS by ... because there is still something wrong with your installation. ... I received no build.log file in the C:\WINCE600 folder. ... Windows CE 6.0 Platform Builder ...
    (microsoft.public.windowsce.platbuilder)
  • Re: How can I get rid of Brother brsplservice service?
    ... > The printer driver does not use Plug and Play for its installation. ... >> to load itself every time I start windows. ... >> the Brother registry folder under software but again each time I ...
    (microsoft.public.windowsxp.help_and_support)