新手安装问题

weixin_40624804 2017-12-05 12:09:45
各位前辈,我是新手刚接触变成,帮忙看下啊,谢谢
安装好测试时候出提示:
所有输出均为最新。
1>LINK : error LNK2001: 无法解析的外部符号 _DriverEntry
1>D:\vc\driverpass\driverpass\\driverpass.sys : fatal error LNK1120: 1 个无法解析的外部命令
百度了好久找不到原因啊
...全文
104 3 打赏 收藏 转发到动态 举报
写回复
用AI写文章
3 条回复
切换为时间正序
请发表友善的回复…
发表回复
漫天飞花 2017-12-05
  • 打赏
  • 举报
回复
看下环境变量是否设置好,还有对应的库文件是否在对应路径
赵4老师 2017-12-05
  • 打赏
  • 举报
回复
DriverEntry Routine A DriverEntry routine is the initial entry point for each driver, including each SCSI miniport driver. A miniport's DriverEntry routine is called with two input arguments (of type PVOID) and must do the following: 1 Initialize a HW_INITIALIZATION_DATA structure (on the stack) with zeros. 2 Set driver-specific and HBA-specific values in the HW_INITIALIZATION_DATA fields, including the miniport driver's entry points. The following entry points must be set: HwFindAdapter HwInitialize HwStartIo HwResetBus The following entry points can be set to a driver-supplied routine or must be set to NULL: HwInterrupt (NULL if the miniport uses polling exclusively) HwDmaStarted HwAdapterState (NULL) 3 Set up any driver-determined context data that the miniport's HwFindAdapter routine uses. 4 Call ScsiPortInitialize with the pointers that were input to the DriverEntry routine, the address of the filled-in HW_INITIALIZATION_DATA, and the address of the context data, if any. A miniport driver can have a set of bus-type-specific HwFindAdapter routines if its HBA can be connected on various types of I/O bus. Such a miniport driver must modify the AdapterInterfaceType and HwFindAdapter fields in the HW_INITIALIZATION_DATA after each call to ScsiPortInitialize, possibly modify the context data for the new bus type, and call ScsiPortInitialize for each type of bus on which a supported HBA might be connected. ScsiPortInitialize checks the validity of the HW_INITIALIZATION_DATA, collects and stores pertinent information in the device extension of a device object that it creates to represent the HBA, allocates memory for a PORT_CONFIGURATION_INFORMATION-type buffer, fills in as much configuration information as it can, and calls the miniport driver's HwFindAdapter routine, described in HwFindAdapter Routines. If the miniport driver sets a particular AdapterInterfaceType value in the HW_INITIALIZATION_DATA but there is no bus of that type in the machine, the port driver returns STATUS_DEVICE_DOES_NOT_EXIST. It does not call the driver-supplied HwFindAdapter routine for that bus type. The miniport driver does not remain loaded if its HBA can be connected only to one or more types of bus that are not present in the machine. Note that ScsiPortInitialize is responsible for the following before it returns control to the miniport's DriverEntry routine: Setting up all necessary system objects Getting configuration information from and setting configuration information in the registry Allocating system resources on behalf of the miniport driver, including memory for the miniport-specified DeviceExtensionSize, SpecificLuExtensionSize, and/or SrbExtensionSize in which the miniport driver can maintain HBA-specific state, per-logical-unit state, and/or per-request state, respectively The miniport driver defines the internal structure and contents of its device extension, logical unit extensions (if any), and SRB extensions (if any). A pointer to the device extension is an input argument to every system-defined miniport driver routine except DriverEntry. Many ScsiPortXxx routines require this pointer as an argument. When ScsiPortInitialize returns control, the DriverEntry routine propagates the return value of ScsiPortInitialize when DriverEntry itself returns control. If the miniport driver calls ScsiPortInitialize more than once, its DriverEntry routine should propagate the lowest return value. ScsiPortInitialize can be called only from a miniport driver's DriverEntry routine. For more information about the HW_INITIALIZATION_DATA structure and ScsiPortInitialize, see the Introduction to SCSI Port Driver Services Reference.
weixin_40624804 2017-12-05
  • 打赏
  • 举报
回复
对着教程检查过了,项目也重新创建过了 编译提示成功,生成就不成功 1>------ 已启动生成: 项目: dverpass, 配置: dverpass Win32 ------ 1>生成启动时间为 2017/12/5 15:54:16。 1>ClCompile: 1> 正在跳过...(未检测到相关更改) 1> mogui.cpp 1> 1>生成成功。 1> 1>已用时间 00:00:00.07 ========== 生成: 成功 1 个,失败 0 个,最新 0 个,跳过 0 个 ========== 上面是编译成功 下面是生成失败,朋友帮出出注意啊,搞了半天了 1>------ 已启动生成: 项目: dverpass, 配置: dverpass Win32 ------ 1>生成启动时间为 2017/12/5 15:55:10。 1>InitializeBuildStatus: 1> 正在对“dverpass\dverpass.unsuccessfulbuild”执行 Touch 任务。 1>ClCompile: 1> 所有输出均为最新。 1>LINK : error LNK2001: 无法解析的外部符号 _DriverEntry 1>C:\Users\guo\documents\visual studio 2010\Projects\dverpass\dverpass\\dverpass.sys : fatal error LNK1120: 1 个无法解析的外部命令 1> 1>生成失败。 1> 1>已用时间 00:00:00.11 ========== 生成: 成功 0 个,失败 1 个,最新 0 个,跳过 0 个 =========

24,854

社区成员

发帖
与我相关
我的任务
社区描述
C/C++ 工具平台和程序库
社区管理员
  • 工具平台和程序库社区
加入社区
  • 近7日
  • 近30日
  • 至今
社区公告
暂无公告

试试用AI创作助手写篇文章吧