We have a wierd problem here with the DDK. We use the W2K3 IFS Kit on a
Windows 2000 server build machine.
Our building process is automated with some kind of VC2003 automation and I
use a makefile project type in VC2003 that call a small batch file that
simply does a call setenv.bat and then executes build.
We have 3 projects of this type. Two of the three always worked without
problem.
But often in one project, DOSKEY.EXE throws an exception! That breaks our
entire build and that is becoming quite problematic.The particular project
being built just use the DDK and not the IFS. This does not happens all the
time though.
I looked at a dump file and Doskey is crashing after a call to
ULIB!Get_Standard_Input_Stream(void). This function returns an internal
object of ULIB and when it crashes this object is null. Doskey is called
from the setenv batch file to setup macros.
I have a memory dump if anyone is interested.
M-A which is quite desperate.
Just comment the Doskey call(s) in the setenv.bat. Doskey macros can’t be
called from a batch file or from a child process, so unless you use some
of those macros from the command prompt after you are done building, they
are useless.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
xxxxx@lists.osr.com wrote on 02/02/2005 11:57:33 AM:
We have a wierd problem here with the DDK. We use the W2K3 IFS Kit on a
Windows 2000 server build machine.
Our building process is automated with some kind of VC2003 automation
and I
use a makefile project type in VC2003 that call a small batch file that
simply does a call setenv.bat and then executes build.
We have 3 projects of this type. Two of the three always worked without
problem.
But often in one project, DOSKEY.EXE throws an exception! That breaks
our
entire build and that is becoming quite problematic.The particular
project
being built just use the DDK and not the IFS. This does not happens all
the
time though.
I looked at a dump file and Doskey is crashing after a call to
ULIB!Get_Standard_Input_Stream(void). This function returns an internal
object of ULIB and when it crashes this object is null. Doskey is called
from the setenv batch file to setup macros.
I have a memory dump if anyone is interested.
M-A which is quite desperate.
Questions? First check the Kernel Driver FAQ at http://www.
osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@seagate.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
I also had some problem with doskey when configured our build engine for DDK builds. The solution was simple. Create a dummy batch named doskey.bat and put it somewhere to the PATH before %systemroot%\system32 where original doskey.exe is. Build engine calls the dummy batch instead of real doskey and all problems are gone.
There are other possiilities: edit setenv.bat file and rem(ove) all doskey calls. Delete doskey.exe or replace it with a simply no-op command line app or batch file. It would be necessary to turn off WFP for this purpose.
Personally, I believe setting some useless doskey macros in setenv.bat is very bad idea. The batch should prepare operating enviromnent for automated build. Creating shell which allows user start build.exe interactively is different task which should create both build and user environment (if necessary at all – anybody ever used these doskey macros?).
Best regards,
Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]
From: xxxxx@lists.osr.com[SMTP:xxxxx@lists.osr.com] on behalf of Marc-Antoine Ruel[SMTP:xxxxx@pyxis.com]
Reply To: Windows System Software Devs Interest List
Sent: Wednesday, February 02, 2005 7:57 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] build problem: doskey error
We have a wierd problem here with the DDK. We use the W2K3 IFS Kit on a
Windows 2000 server build machine.
Our building process is automated with some kind of VC2003 automation and I
use a makefile project type in VC2003 that call a small batch file that
simply does a call setenv.bat and then executes build.
We have 3 projects of this type. Two of the three always worked without
problem.
But often in one project, DOSKEY.EXE throws an exception! That breaks our
entire build and that is becoming quite problematic.The particular project
being built just use the DDK and not the IFS. This does not happens all the
time though.
I looked at a dump file and Doskey is crashing after a call to
ULIB!Get_Standard_Input_Stream(void). This function returns an internal
object of ULIB and when it crashes this object is null. Doskey is called
from the setenv batch file to setup macros.
I have a memory dump if anyone is interested.
M-A which is quite desperate.
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@upek.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Thanks both for the help.
My build man told me he’ll try the doskey.bat trick so he doesn’t have to
change the DDK.
M-A