kernel load address

hi,

is it possible to specify/suggest a load address range for a driver?

thanks

ap

No, you cannot. Why in the world do you think you need this?


Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr

“A P” wrote in message news:xxxxx@ntdev…
> hi,
>
> is it possible to specify/suggest a load address range for a driver?
>
> thanks
>
> ap
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4311 (20090806)

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>

Information from ESET NOD32 Antivirus, version of virus signature database 4311 (20090806)

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

Yes, you can, but it doesn’t have to be honored.

See: link /BASE and ‘Choosing a Base Address’ in the WDK docs.

Good luck,

mm

thanks!

On Thu, Aug 6, 2009 at 6:18 PM, wrote:

> Yes, you can, but it doesn’t have to be honored.
>
> See: link /BASE and ‘Choosing a Base Address’ in the WDK docs.
>
>
> Good luck,
>
> mm
>
>
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

Not a problem.

mm

I don’t think that a custom image base will have any effect on a driver as
they are always relocated.
The documentation confirms this:
http://msdn.microsoft.com/en-us/library/ms792170.aspx

  • Cay

On Thu, 06 Aug 2009 14:48:51 +0200, wrote:
> Yes, you can, but it doesn’t have to be honored.
>
> See: link /BASE and ‘Choosing a Base Address’ in the WDK docs.
>
>
> Good luck,
>
> mm

I noticed that, but wasn’t quite sure what to make of it.

I mean, on one hand, it’s a pretty black and white statement, but on the other, there’s an awful lot going on there - DRIVERBASE, HALBASE and all the COFFBASE.TXT stuff - for it just to be cosmetic.

It seems like something there needs to be updated.

mm

This field is ignored for drivers.

For the OP, why do you think that you need to do this? Drivers must not depend on hardcoded aspects of the address space layout.

  • S

-----Original Message-----
From: xxxxx@evitechnology.com
Sent: Thursday, August 06, 2009 05:46
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] kernel load address

Yes, you can, but it doesn’t have to be honored.

See: link /BASE and ‘Choosing a Base Address’ in the WDK docs.

Good luck,

mm


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Some of these things might have one day had meaning but do not necessarily anymore. Or they may apply only to early boot before the kernel is up and running.

  • S

-----Original Message-----
From: xxxxx@evitechnology.com
Sent: Thursday, August 06, 2009 08:35
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] kernel load address

I noticed that, but wasn’t quite sure what to make of it.

I mean, on one hand, it’s a pretty black and white statement, but on the other, there’s an awful lot going on there - DRIVERBASE, HALBASE and all the COFFBASE.TXT stuff - for it just to be cosmetic.

It seems like something there needs to be updated.

mm


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Thanks, Ken.

mm