Re: LNK1218 error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Ok David, you'r right!!
I'm using Windows Server 2003 SP1 DDK, I'm compiling driver for Windows XP
using appropriate enviroment. I bought IFS a month ago from Micorosft...

Sources follow...
Thnaks
Ale

[sources] ---------------------------------------------------

!include sources.inc

!IF $(MONOLITHIC_MINIRDR)

TARGETLIBS= $(TARGETLIBS) \
$(DDK_LIB_PATH)\rxce.lib \
$(DDK_LIB_PATH)\copysup.lib

!ENDIF

SOURCES= $(MOST_SOURCES) \
bwbmrx.rc

[sources.inc] ------------------------------------------------

!INCLUDE .\master.src

TARGETNAME=bwbmrx
TARGETPATH=obj
TARGETTYPE=EXPORT_DRIVER

SYNCHRONIZE_DRAIN=1

INCLUDES=$(INCLUDES); \
$(IFSKIT_INC_PATH);

TARGETLIBS=$(DDK_LIB_PATH)\ksecdd.lib \
$(DDK_LIB_PATH)\rdbsslib.lib

#NTLAYGO=1

MSC_WARNING_LEVEL=/W3 /WX
C_DEFINES= $(C_DEFINES) -DEXPLODE_POOLTAGS
!IF $(MONOLITHIC_MINIRDR)
C_DEFINES=$(C_DEFINES) -DMONOLITHIC_MINIRDR
!ENDIF

MOST_SOURCES= \
devfcb.c \
fileinfo.c \
init.c \
locks.c \
netroot.c \
ea.c \
devctrl.c \
notimpl.c \
openclos.c \
read.c \
rename.c \
srvcall.c \
write.c \
downlvli.c \
string.c \
global.c \
queue.c

PRECOMPILED_INCLUDE=precomp.h
PRECOMPILED_PCH=precomp.pch
PRECOMPILED_OBJ=precomp.obj

DLLDEF=$(_OBJ_DIR)\*\bwbmrx.def

[makefile] ----------------------------------------------------

!INCLUDE $(NTMAKEENV)\makefile.def

[master.src] --------------------------------------------------

MONOLITHIC_MINIRDR=1

-----------------------------------------------------------------

Thanks

"David J. Craig" wrote:

> Use the current version. It is Server 2003 SP1. Also post your sources,
> makefile, and makefile.inc if you want help.
>
> "Ale" <Ale@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:E6FA2512-F745-4DB4-B482-CB152D11CF45@xxxxxxxxxxxxxxxx
> > While linking my IFS driver the linker reports this error:
> >
> > Building Library - objchk_wxp_x86\i386\bwbmrx.lib for i386
> > errors in directory d:\bwbnt\bwbmrx
> > LIB : error LNK1218: warning treated as error; no output file generated
> > BUILD: Linking d:\bwbnt\bwbmrx directory
> > Building Library - objchk_wxp_x86\i386\bwbmrx.lib for i386
> > LIB : error LNK1218: warning treated as error; no output file generated
> > Linking Executable - objchk_wxp_x86\i386\bwbmrx.sys for i386
> > LINK : error LNK1181: cannot open input file
> > 'objchk_wxp_x86\i386\bwbmrx.exp'
> > BUILD: Done
> >
> > 21 files compiled
> > 2 libraries built - 2 Warnings - 2 Errors
> > 1 executable built - 1 Error
> >
> > I'm compiling my driver using IFS KIT for XP, it didn't hppen on older IFS
> > KIT for Windows 2000
> >
> > Thanks
> > Ale
> >
>
>
>
.

Relevant Pages

  • Re: Video editing in Linux?
    ... picked the visual.net package because the compiling was virtually all ... but the majority of windows based games were using the Directx ... shit scared to switch over to openoffice and a linux server here, ... So is that a program or a driver or some kind of wrapper? ...
    (alt.linux)
  • Re: WinDDK does not build
    ... Windows Filesystem and Driver Consulting ... BUILD: Compile errors: not linking ...
    (microsoft.public.development.device.drivers)
  • Re: FS driver
    ... The IFS kit is actually obsolete as of the Vista beta Windows Driver Kit which contains the former IFS kit. ... I am created my own file system, i want "Windows Explorer" able to view/edit its file, how can i write a driver for it? ...
    (microsoft.public.development.device.drivers)
  • Re: unresolved symbol - KeSetTargetProcessorDpc
    ... I am building on windows 2000. ... I am doing both checked and free builds of my driver for windows 2000 ... when compiling for windows 2000 or windows xp free build, ... I get unresolved external symbol ...
    (microsoft.public.development.device.drivers)
  • Re: Kernel to non-kernel comms
    ... The IFS Kit and not the DDK contains two examples. ... Active filters are the most difficult to write. ... Don't forget to run every thing you can find against the driver. ...
    (microsoft.public.win32.programmer.kernel)