Re: RegisterDevice(GEN, 1, GenDriver.dll, 0x802ee68) failed ??? WHY??
From: Yannick Chamming's [eMVP] (ychammings_nospam_at_adeset.com)
Date: 01/25/05
- Next message: voidcoder: "Re: Porting a driver for ipaq without a ipaq BSP"
- Previous message: Yannick Chamming's [eMVP]: "Re: SOS on TaskMan Shell in WindowsCE 5.0"
- In reply to: jamestheDork: "RegisterDevice(GEN, 1, GenDriver.dll, 0x802ee68) failed ??? WHY??"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 25 Jan 2005 08:25:58 +0100
from your log, I suppose you are using a Viper board from Arcom. this log
indicates that gendriver.dll cannot be found by CE. You should include the
dll in your image, so that it can be mounted by system when calling
registerdevice.
-- ---------------------------------------------------------------- Yannick Chamming's (eMVP) ADESET Windows Embedded Manager ychammings AT adeset DOT com> http://www.adeset.com Tél : +33 (0)4.72.18.57.77 Fax : +33 (0)4.72.18.57.78 ---------------------------------------------------------------- "jamestheDork" <jamesevangelos@yahoo.com> wrote in message news:ca8a21b38a4074347c3ab43f9259d7ed@localhost.talkaboutsoftware.com... > I am using Platform Builder to learn how to create device drivers. I have > > the C/C++ code written for a Generic device driver. When I connect to the > > remote device from Platform Builder on the host Workstation I get this > result in the output diaglog: > > 4294774365 PID:43c63e2a TID:43c63152 0x83c5d23c: > DEVICE!ActivateDeviceEx(Drivers\BuiltIn\gendriver) entered > 4294774369 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\GenDriver.dll) returned 0xffffffff (2) > 4294774370 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\GenDriver.dll) returned 0x0 (2) > 4294774372 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\Arcom\GenDriver.dll) returned 0xffffffff > (2) > 4294774373 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\Arcom\GenDriver.dll) returned 0x0 (2) > 4294774374 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\User\GenDriver.dll) returned 0xffffffff (2) > 4294774375 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\User\GenDriver.dll) returned 0x0 (2) > 4294774376 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\Startup\GenDriver.dll) returned 0xffffffff > (2) > 4294774377 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\Startup\GenDriver.dll) returned 0x0 (2) > 4294774380 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\GenDriver.dll.dll) returned 0xffffffff (2) > 4294774381 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\GenDriver.dll.dll) returned 0x0 (2) > 4294774382 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\Arcom\GenDriver.dll.dll) returned 0xffffffff > (2) > 4294774383 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\Arcom\GenDriver.dll.dll) returned 0x0 (2) > 4294774385 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\User\GenDriver.dll.dll) returned 0xffffffff > (2) > 4294774386 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\User\GenDriver.dll.dll) returned 0x0 (2) > 4294774387 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_GetFileAttributesW(\Startup\GenDriver.dll.dll) returned > 0xffffffff > (2) > 4294774388 PID:63c9d23e TID:43c63152 0x83c5d23c: > FATFS!FAT_CreateFileW(\Startup\GenDriver.dll.dll) returned 0x0 (2) > 4294774388 PID:43c63e2a TID:43c63152 0x83c5d23c: DEVICE!StartOneDriver > RegisterDevice(GEN, 1, GenDriver.dll, 0x802ee68) failed > > Can anybody help me with this?? >
- Next message: voidcoder: "Re: Porting a driver for ipaq without a ipaq BSP"
- Previous message: Yannick Chamming's [eMVP]: "Re: SOS on TaskMan Shell in WindowsCE 5.0"
- In reply to: jamestheDork: "RegisterDevice(GEN, 1, GenDriver.dll, 0x802ee68) failed ??? WHY??"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|