I found the problem was caused by Command Processor (cmd.exe) autorun
parameter in registry. After I removed the parameter from registry, this
problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory > NMAKE : U1064: MAKEFILE not found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
You are lucky. My autorun entry was “cd \somedir”. That caused the
problem.
Because the build program starts some cmd sessions that use the current
directory. If the current directory changed to somewhere, the build
command
will fail.
Shangwu
“Philip D Barila” wrote in message > news:xxxxx@ntfsd… > > What was your autorun entry? I have an autorun entry: > > > > DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases” > > > > where CMDAliases are a bunch of useful command shortcuts like: > > deltree=rd /s /q $* > > > > Since there isn’t a deltree in Windows since 2000 (I think). > > > > That’s never caused me any build problems, so I’m curious what your > > autorun is that could. > > > > Phil > > > > Philip D. Barila > > Seagate Technology LLC > > (720) 684-1842 > > > > > > > > “Shangwu” > > Sent by: xxxxx@lists.osr.com > > No Phone Info Available > > 02/02/2005 07:23 AM > > Please respond to > > “Windows File Systems Devs Interest List” > > > > > > To > > “Windows File Systems Devs Interest List” > > cc > > > > Subject > > Re:[ntfsd] IFS Kit build problem > > > > > > > > > > > > > > I found the problem was caused by Command Processor (cmd.exe) autorun > > parameter in registry. After I removed the parameter from registry, this > > problem has gone. Just let you know in case you encounter the same > > problem. > > > > “Shangwu” wrote in message news:xxxxx@ntfsd… > >> Hello, > >> > >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > >> build -cZ command. > >> The command failed and the following messages showed. > >> > >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > >> BUILD: Object root set to: ==> objchk_wxp_x86 > >> BUILD: Compile and Link for i386 > >> BUILD: Examining c:\devdriver directory for files to compile. > >> BUILD: Compiling c:\devdriver directory > >> NMAKE : U1064: MAKEFILE not found and no target specified > >> BUILD: nmake.exe failed - rc = 2 > >> BUILD: Compile errors: not linking c:\devdriver directory > >> BUILD: Done > >> > >> If you encountered the same problem and overcame it, please post your > >> solution. > >> Thank you very much. > >> > >> Shangwu > >> > >> > >> > > > > > > > > — > > Questions? First check the IFS FAQ at > > https://www.osronline.com/article.cfm?id=17 > > > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > > To unsubscribe send a blank email to xxxxx@lists.osr.com > > > > > > > > — > Questions? First check the IFS FAQ at https://www.osronline. > com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > To unsubscribe send a blank email to xxxxx@lists.osr.com
What was your autorun entry? I have an autorun entry:
DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases”
where CMDAliases are a bunch of useful command shortcuts like:
deltree=rd /s /q $*
Since there isn’t a deltree in Windows since 2000 (I think).
That’s never caused me any build problems, so I’m curious what your
autorun is that could.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
“Shangwu” Sent by: xxxxx@lists.osr.com No Phone Info Available 02/02/2005 07:23 AM Please respond to “Windows File Systems Devs Interest List”
To “Windows File Systems Devs Interest List” cc
Subject Re:[ntfsd] IFS Kit build problem
I found the problem was caused by Command Processor (cmd.exe) autorun parameter in registry. After I removed the parameter from registry, this problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory > NMAKE : U1064: MAKEFILE not found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
From the error message, it sounds that there is no makefile in the
c:\devdriver directory. You need a makefile that points to the makefile.def
(see a sample makefile in the source code samples).
Danilo
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu
Sent: Wednesday, February 02, 2005 6:24 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] IFS Kit build problem
I found the problem was caused by Command Processor (cmd.exe) autorun
parameter in registry. After I removed the parameter from registry, this
problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran > the build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory NMAKE : U1064: MAKEFILE not > found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
You are lucky. My autorun entry was “cd \somedir”. That caused the problem.
Because the build program starts some cmd sessions that use the current
directory. If the current directory changed to somewhere, the build command
will fail.
Shangwu
“Philip D Barila” wrote in message news:xxxxx@ntfsd… > What was your autorun entry? I have an autorun entry: > > DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases” > > where CMDAliases are a bunch of useful command shortcuts like: > deltree=rd /s /q $* > > Since there isn’t a deltree in Windows since 2000 (I think). > > That’s never caused me any build problems, so I’m curious what your > autorun is that could. > > Phil > > Philip D. Barila > Seagate Technology LLC > (720) 684-1842 > > > > “Shangwu” > Sent by: xxxxx@lists.osr.com > No Phone Info Available > 02/02/2005 07:23 AM > Please respond to > “Windows File Systems Devs Interest List” > > > To > “Windows File Systems Devs Interest List” > cc > > Subject > Re:[ntfsd] IFS Kit build problem > > > > > > > I found the problem was caused by Command Processor (cmd.exe) autorun > parameter in registry. After I removed the parameter from registry, this > problem has gone. Just let you know in case you encounter the same > problem. > > “Shangwu” wrote in message news:xxxxx@ntfsd… >> Hello, >> >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the >> build -cZ command. >> The command failed and the following messages showed. >> >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. >> BUILD: Object root set to: ==> objchk_wxp_x86 >> BUILD: Compile and Link for i386 >> BUILD: Examining c:\devdriver directory for files to compile. >> BUILD: Compiling c:\devdriver directory >> NMAKE : U1064: MAKEFILE not found and no target specified >> BUILD: nmake.exe failed - rc = 2 >> BUILD: Compile errors: not linking c:\devdriver directory >> BUILD: Done >> >> If you encountered the same problem and overcame it, please post your >> solution. >> Thank you very much. >> >> Shangwu >> >> >> > > > > — > Questions? First check the IFS FAQ at > https://www.osronline.com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > To unsubscribe send a blank email to xxxxx@lists.osr.com > >
I found the problem was caused by Command Processor (cmd.exe) autorun
parameter in registry. After I removed the parameter from registry, this
problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory > NMAKE : U1064: MAKEFILE not found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
There is a makefile in the directory. The problem was caused by autorun of
Command Processor that is cmd.exe. Please check another message I posted in
this thread.
Thanks,
Shangwu
“Danilo Almeida” wrote in message news:xxxxx@ntfsd… > Shangwu, > > From the error message, it sounds that there is no makefile in the > c:\devdriver directory. You need a makefile that points to the > makefile.def > (see a sample makefile in the source code samples). > > - Danilo > > -----Original Message----- > From: xxxxx@lists.osr.com > [mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu > Sent: Wednesday, February 02, 2005 6:24 AM > To: Windows File Systems Devs Interest List > Subject: Re:[ntfsd] IFS Kit build problem > > I found the problem was caused by Command Processor (cmd.exe) autorun > parameter in registry. After I removed the parameter from registry, this > problem has gone. Just let you know in case you encounter the same > problem. > > “Shangwu” wrote in message news:xxxxx@ntfsd… >> Hello, >> >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran >> the build -cZ command. >> The command failed and the following messages showed. >> >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. >> BUILD: Object root set to: ==> objchk_wxp_x86 >> BUILD: Compile and Link for i386 >> BUILD: Examining c:\devdriver directory for files to compile. >> BUILD: Compiling c:\devdriver directory NMAKE : U1064: MAKEFILE not >> found and no target specified >> BUILD: nmake.exe failed - rc = 2 >> BUILD: Compile errors: not linking c:\devdriver directory >> BUILD: Done >> >> If you encountered the same problem and overcame it, please post your >> solution. >> Thank you very much. >> >> Shangwu >> >> >> > > > > — > Questions? First check the IFS FAQ at > https://www.osronline.com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@mit.edu To unsubscribe > send a blank email to xxxxx@lists.osr.com > >
What was your autorun entry? I have an autorun entry:
DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases”
where CMDAliases are a bunch of useful command shortcuts like:
deltree=rd /s /q $*
Since there isn’t a deltree in Windows since 2000 (I think).
That’s never caused me any build problems, so I’m curious what your
autorun is that could.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
“Shangwu” Sent by: xxxxx@lists.osr.com No Phone Info Available 02/02/2005 07:23 AM Please respond to “Windows File Systems Devs Interest List”
To “Windows File Systems Devs Interest List” cc
Subject Re:[ntfsd] IFS Kit build problem
I found the problem was caused by Command Processor (cmd.exe) autorun parameter in registry. After I removed the parameter from registry, this problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory > NMAKE : U1064: MAKEFILE not found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
You are lucky. My autorun entry was “cd \somedir”. That caused the
problem.
Because the build program starts some cmd sessions that use the current
directory. If the current directory changed to somewhere, the build
command
will fail.
Shangwu
“Philip D Barila” wrote in message > news:xxxxx@ntfsd… > > What was your autorun entry? I have an autorun entry: > > > > DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases” > > > > where CMDAliases are a bunch of useful command shortcuts like: > > deltree=rd /s /q $* > > > > Since there isn’t a deltree in Windows since 2000 (I think). > > > > That’s never caused me any build problems, so I’m curious what your > > autorun is that could. > > > > Phil > > > > Philip D. Barila > > Seagate Technology LLC > > (720) 684-1842 > > > > > > > > “Shangwu” > > Sent by: xxxxx@lists.osr.com > > No Phone Info Available > > 02/02/2005 07:23 AM > > Please respond to > > “Windows File Systems Devs Interest List” > > > > > > To > > “Windows File Systems Devs Interest List” > > cc > > > > Subject > > Re:[ntfsd] IFS Kit build problem > > > > > > > > > > > > > > I found the problem was caused by Command Processor (cmd.exe) autorun > > parameter in registry. After I removed the parameter from registry, this > > problem has gone. Just let you know in case you encounter the same > > problem. > > > > “Shangwu” wrote in message news:xxxxx@ntfsd… > >> Hello, > >> > >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > >> build -cZ command. > >> The command failed and the following messages showed. > >> > >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > >> BUILD: Object root set to: ==> objchk_wxp_x86 > >> BUILD: Compile and Link for i386 > >> BUILD: Examining c:\devdriver directory for files to compile. > >> BUILD: Compiling c:\devdriver directory > >> NMAKE : U1064: MAKEFILE not found and no target specified > >> BUILD: nmake.exe failed - rc = 2 > >> BUILD: Compile errors: not linking c:\devdriver directory > >> BUILD: Done > >> > >> If you encountered the same problem and overcame it, please post your > >> solution. > >> Thank you very much. > >> > >> Shangwu > >> > >> > >> > > > > > > > > — > > Questions? First check the IFS FAQ at > > https://www.osronline.com/article.cfm?id=17 > > > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > > To unsubscribe send a blank email to xxxxx@lists.osr.com > > > > > > > > — > Questions? First check the IFS FAQ at https://www.osronline. > com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > To unsubscribe send a blank email to xxxxx@lists.osr.com
From the error message, it sounds that there is no makefile in the
c:\devdriver directory. You need a makefile that points to the makefile.def
(see a sample makefile in the source code samples).
Danilo
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu
Sent: Wednesday, February 02, 2005 6:24 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] IFS Kit build problem
I found the problem was caused by Command Processor (cmd.exe) autorun
parameter in registry. After I removed the parameter from registry, this
problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran > the build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory NMAKE : U1064: MAKEFILE not > found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
There is a makefile in the directory. The problem was caused by autorun of
Command Processor that is cmd.exe. Please check another message I posted in
this thread.
Thanks,
Shangwu
“Danilo Almeida” wrote in message news:xxxxx@ntfsd… > Shangwu, > > From the error message, it sounds that there is no makefile in the > c:\devdriver directory. You need a makefile that points to the > makefile.def > (see a sample makefile in the source code samples). > > - Danilo > > -----Original Message----- > From: xxxxx@lists.osr.com > [mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu > Sent: Wednesday, February 02, 2005 6:24 AM > To: Windows File Systems Devs Interest List > Subject: Re:[ntfsd] IFS Kit build problem > > I found the problem was caused by Command Processor (cmd.exe) autorun > parameter in registry. After I removed the parameter from registry, this > problem has gone. Just let you know in case you encounter the same > problem. > > “Shangwu” wrote in message news:xxxxx@ntfsd… >> Hello, >> >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran >> the build -cZ command. >> The command failed and the following messages showed. >> >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. >> BUILD: Object root set to: ==> objchk_wxp_x86 >> BUILD: Compile and Link for i386 >> BUILD: Examining c:\devdriver directory for files to compile. >> BUILD: Compiling c:\devdriver directory NMAKE : U1064: MAKEFILE not >> found and no target specified >> BUILD: nmake.exe failed - rc = 2 >> BUILD: Compile errors: not linking c:\devdriver directory >> BUILD: Done >> >> If you encountered the same problem and overcame it, please post your >> solution. >> Thank you very much. >> >> Shangwu >> >> >> > > > > — > Questions? First check the IFS FAQ at > https://www.osronline.com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@mit.edu To unsubscribe > send a blank email to xxxxx@lists.osr.com > >
What was your autorun entry? I have an autorun entry:
DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases”
where CMDAliases are a bunch of useful command shortcuts like:
deltree=rd /s /q $*
Since there isn’t a deltree in Windows since 2000 (I think).
That’s never caused me any build problems, so I’m curious what your
autorun is that could.
Phil
Philip D. Barila
Seagate Technology LLC
(720) 684-1842
“Shangwu” Sent by: xxxxx@lists.osr.com No Phone Info Available 02/02/2005 07:23 AM Please respond to “Windows File Systems Devs Interest List”
To “Windows File Systems Devs Interest List” cc
Subject Re:[ntfsd] IFS Kit build problem
I found the problem was caused by Command Processor (cmd.exe) autorun parameter in registry. After I removed the parameter from registry, this problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory > NMAKE : U1064: MAKEFILE not found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
I found the problem was caused by Command Processor (cmd.exe) autorun
parameter in registry. After I removed the parameter from registry, this
problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory > NMAKE : U1064: MAKEFILE not found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
You are lucky. My autorun entry was “cd \somedir”. That caused the
problem.
Because the build program starts some cmd sessions that use the current
directory. If the current directory changed to somewhere, the build
command
will fail.
Shangwu
“Philip D Barila” wrote in message > news:xxxxx@ntfsd… > > What was your autorun entry? I have an autorun entry: > > > > DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases” > > > > where CMDAliases are a bunch of useful command shortcuts like: > > deltree=rd /s /q $* > > > > Since there isn’t a deltree in Windows since 2000 (I think). > > > > That’s never caused me any build problems, so I’m curious what your > > autorun is that could. > > > > Phil > > > > Philip D. Barila > > Seagate Technology LLC > > (720) 684-1842 > > > > > > > > “Shangwu” > > Sent by: xxxxx@lists.osr.com > > No Phone Info Available > > 02/02/2005 07:23 AM > > Please respond to > > “Windows File Systems Devs Interest List” > > > > > > To > > “Windows File Systems Devs Interest List” > > cc > > > > Subject > > Re:[ntfsd] IFS Kit build problem > > > > > > > > > > > > > > I found the problem was caused by Command Processor (cmd.exe) autorun > > parameter in registry. After I removed the parameter from registry, this > > problem has gone. Just let you know in case you encounter the same > > problem. > > > > “Shangwu” wrote in message news:xxxxx@ntfsd… > >> Hello, > >> > >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the > >> build -cZ command. > >> The command failed and the following messages showed. > >> > >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > >> BUILD: Object root set to: ==> objchk_wxp_x86 > >> BUILD: Compile and Link for i386 > >> BUILD: Examining c:\devdriver directory for files to compile. > >> BUILD: Compiling c:\devdriver directory > >> NMAKE : U1064: MAKEFILE not found and no target specified > >> BUILD: nmake.exe failed - rc = 2 > >> BUILD: Compile errors: not linking c:\devdriver directory > >> BUILD: Done > >> > >> If you encountered the same problem and overcame it, please post your > >> solution. > >> Thank you very much. > >> > >> Shangwu > >> > >> > >> > > > > > > > > — > > Questions? First check the IFS FAQ at > > https://www.osronline.com/article.cfm?id=17 > > > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > > To unsubscribe send a blank email to xxxxx@lists.osr.com > > > > > > > > — > Questions? First check the IFS FAQ at https://www.osronline. > com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > To unsubscribe send a blank email to xxxxx@lists.osr.com
From the error message, it sounds that there is no makefile in the
c:\devdriver directory. You need a makefile that points to the makefile.def
(see a sample makefile in the source code samples).
Danilo
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu
Sent: Wednesday, February 02, 2005 6:24 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] IFS Kit build problem
I found the problem was caused by Command Processor (cmd.exe) autorun
parameter in registry. After I removed the parameter from registry, this
problem has gone. Just let you know in case you encounter the same problem.
“Shangwu” wrote in message news:xxxxx@ntfsd… > Hello, > > I installed IFS Kit on a laptop machine with Windows XP SP2 and ran > the build -cZ command. > The command failed and the following messages showed. > > BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. > BUILD: Object root set to: ==> objchk_wxp_x86 > BUILD: Compile and Link for i386 > BUILD: Examining c:\devdriver directory for files to compile. > BUILD: Compiling c:\devdriver directory NMAKE : U1064: MAKEFILE not > found and no target specified > BUILD: nmake.exe failed - rc = 2 > BUILD: Compile errors: not linking c:\devdriver directory > BUILD: Done > > If you encountered the same problem and overcame it, please post your > solution. > Thank you very much. > > Shangwu > > >
You are lucky. My autorun entry was “cd \somedir”. That caused the problem.
Because the build program starts some cmd sessions that use the current
directory. If the current directory changed to somewhere, the build command
will fail.
Shangwu
“Philip D Barila” wrote in message news:xxxxx@ntfsd… > What was your autorun entry? I have an autorun entry: > > DosKey /MACROFILE=“C:\Documents and Settings\All Users\CMDAliases” > > where CMDAliases are a bunch of useful command shortcuts like: > deltree=rd /s /q $* > > Since there isn’t a deltree in Windows since 2000 (I think). > > That’s never caused me any build problems, so I’m curious what your > autorun is that could. > > Phil > > Philip D. Barila > Seagate Technology LLC > (720) 684-1842 > > > > “Shangwu” > Sent by: xxxxx@lists.osr.com > No Phone Info Available > 02/02/2005 07:23 AM > Please respond to > “Windows File Systems Devs Interest List” > > > To > “Windows File Systems Devs Interest List” > cc > > Subject > Re:[ntfsd] IFS Kit build problem > > > > > > > I found the problem was caused by Command Processor (cmd.exe) autorun > parameter in registry. After I removed the parameter from registry, this > problem has gone. Just let you know in case you encounter the same > problem. > > “Shangwu” wrote in message news:xxxxx@ntfsd… >> Hello, >> >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran the >> build -cZ command. >> The command failed and the following messages showed. >> >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. >> BUILD: Object root set to: ==> objchk_wxp_x86 >> BUILD: Compile and Link for i386 >> BUILD: Examining c:\devdriver directory for files to compile. >> BUILD: Compiling c:\devdriver directory >> NMAKE : U1064: MAKEFILE not found and no target specified >> BUILD: nmake.exe failed - rc = 2 >> BUILD: Compile errors: not linking c:\devdriver directory >> BUILD: Done >> >> If you encountered the same problem and overcame it, please post your >> solution. >> Thank you very much. >> >> Shangwu >> >> >> > > > > — > Questions? First check the IFS FAQ at > https://www.osronline.com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@seagate.com > To unsubscribe send a blank email to xxxxx@lists.osr.com > >
Here is a tip that can generaly help when using autorun:
Have your autorun batch start out like this:
if defined AUTORUN_DONE goto :EOF
set AUTORUN_DONE=1
That ensures that invocations of cmd from your cmd (or processes started
from your cmd) will not cause your autorun code to run again.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu
Sent: Wednesday, February 02, 2005 10:41 AM
To: Windows File Systems Devs Interest List
Subject: Re:[ntfsd] IFS Kit build problem
Danilo,
There is a makefile in the directory. The problem was caused by autorun of
Command Processor that is cmd.exe. Please check another message I posted in
this thread.
Thanks,
Shangwu
“Danilo Almeida” wrote in message news:xxxxx@ntfsd… > Shangwu, > > From the error message, it sounds that there is no makefile in the > c:\devdriver directory. You need a makefile that points to the > makefile.def (see a sample makefile in the source code samples). > > - Danilo > > -----Original Message----- > From: xxxxx@lists.osr.com > [mailto:xxxxx@lists.osr.com] On Behalf Of Shangwu > Sent: Wednesday, February 02, 2005 6:24 AM > To: Windows File Systems Devs Interest List > Subject: Re:[ntfsd] IFS Kit build problem > > I found the problem was caused by Command Processor (cmd.exe) autorun > parameter in registry. After I removed the parameter from registry, > this problem has gone. Just let you know in case you encounter the > same problem. > > “Shangwu” wrote in message news:xxxxx@ntfsd… >> Hello, >> >> I installed IFS Kit on a laptop machine with Windows XP SP2 and ran >> the build -cZ command. >> The command failed and the following messages showed. >> >> BUILD: Adding /Y to COPYCMD so xcopy ops won’t hang. >> BUILD: Object root set to: ==> objchk_wxp_x86 >> BUILD: Compile and Link for i386 >> BUILD: Examining c:\devdriver directory for files to compile. >> BUILD: Compiling c:\devdriver directory NMAKE : U1064: MAKEFILE not >> found and no target specified >> BUILD: nmake.exe failed - rc = 2 >> BUILD: Compile errors: not linking c:\devdriver directory >> BUILD: Done >> >> If you encountered the same problem and overcame it, please post your >> solution. >> Thank you very much. >> >> Shangwu >> >> >> > > > > — > Questions? First check the IFS FAQ at > https://www.osronline.com/article.cfm?id=17 > > You are currently subscribed to ntfsd as: xxxxx@mit.edu To > unsubscribe send a blank email to xxxxx@lists.osr.com > >