Page 3 of 3 FirstFirst 123
Results 31 to 34 of 34

Thread: XP on modern systems

  1. #31
    Quote Originally Posted by WaxfordSqueers View Post
    VEN_8086&DEV_15BC for an Intel 1219-v LAN chip.
    maybe i shot into the dark, i just try to make it quick

    but looking at the intel website for:
    "Intel® Ethernet Connection I219-V"

    the I219-V is listed as "os independed" supported (Date: 11/4/2019)
    https://downloadcenter.intel.com/download/22283/Intel-Ethernet-Adapter-Complete-Driver-Pack

    can i have the motherboard name and identifier ?

    im not certain what is searched anymore: lan driver, chipset, usb 3.0 driver, grafics card driver or for softice functionality (joke) :-)
    they installed as single drivers or procedure

    for a big update to kernelbase.dll and kernel32.dll and maybe ntoskrnl we would need some people to call together
    in this case maybe there is some room from different websites too
    a similiar idea exited in the thread kayaker posted
    if the people come together there might be a solution to that question

    the export if is made by either supervisor mode or user mode is given by windows to the searching module (executable,dll ect.) it does this over the pe header/structure by reading out the exports/imports, what follows a norm in the pe header
    system driver do have a pe header/structure too
    the identifiers are the name of the exporting module "like kernel32.dll"
    then the name of the function in that module like "GetProcAddress"

  2. #32
    Quote Originally Posted by Elenil View Post
    "Intel® Ethernet Connection I219-V"...can i have the motherboard name and identifier ?
    The mobo is an Asus B360M-C/CSM. It's a 300-series mobo and there is the problem with the LAN driver being declared OS-independent by Intel. It's their chipset and they have not issued a mobo since 2014, or so. Any specifications I have seen from them is in reference to the 200-series mobos. They seem to be supporting Micro$oft's boycott off XP and W7 on mobo's after the 200-series.

    The current driver for W7 on this mobo is e1d62x64.sys. My XP driver is e1e5132.sys. I am a bit foggy on this since I have not looked at it closely for a while, due to other commitments, but when I run Depends on the current XP driver with the current ntoskrnl and NDIS version 5.1, I get no missing exports. Naturally, that is to be expected but it raises the question as to what exactly am I looking for?

    My experience with other XP drivers that 'should not' work with 300-series mobo is that they work fine. Therefore, should I try to somehow upgrade the current XP Intel LAN driver, since it is rated in the INF file for version 6.0 (W7) as well as 5.1 (XP) or try to adapt a W7 x86 driver which has many exports missing in ntoskrnl and ndis.sys?

    missing exports....

    If I use the x86 e1d6232.sys driver in Depends, aimed at a W7 NTx86.6.1.1 OS, I get about 12 errors in ntoskrnl and about 30 errors in ndis.sys.

    ntoskrnl exports...

    *** marks missing

    ***EtwWrite
    ExAllocatePoolWithTag
    ExFreePoolWithTag
    IoAllocateErrorLogEntry
    ***IoGetAffinityInterrupt
    IoGetDeviceProperty
    IoWMIRegistrationControl
    IoWriteErrorLogEntry
    IofCompleteRequest
    KeAcquireInStackQueuedSpinLockAtDpcLevel
    KeBugCheckEx
    ***KeGetProcessorIndexFromNumber
    ***KeGetProcessorNumberFromIndex
    KeInitializeMutex
    ***KeQueryHighestNodeNumber
    KeQuerySystemTime
    KeReleaseInStackQueuedSpinLockFromDpcLevel
    KeReleaseMutex
    KeWaitForSingleObject
    KefAcquireSpinLockAtDpcLevel
    KefReleaseSpinLockFromDpcLevel
    MmGetSystemRoutineAddress
    MmMapLockedPagesSpecifyCache
    ***PoRegisterPowerSettingCallback
    ***PoUnregisterPowerSettingCallback
    RtlAppendUnicodeStringToString
    RtlCompareMemory
    RtlCopyUnicodeString
    RtlGetVersion
    RtlInitUnicodeString
    ZwClose
    ZwOpenFile
    _alldiv
    _allmul
    _allshl
    _aulldiv
    _aullshr
    _purecall
    _vsnwprintf
    memcpy
    ***memcpy_s
    memset
    ***sprintf_s
    ***strcpy_s
    ***vsprintf_s

    ndis exports...

    NdisAcquireReadWriteLock
    ***NdisAllocateIoWorkItem
    ***NdisAllocateMdl
    NdisAllocateMemoryWithTag
    ***NdisAllocateMemoryWithTagPriority
    ***NdisAllocateNetBufferAndNetBufferList
    ***NdisAllocateNetBufferListPool
    NdisCloseConfiguration
    ***NdisDeregisterDeviceEx
    ***NdisFreeIoWorkItem
    ***NdisFreeMdl
    NdisFreeMemory
    ***NdisFreeNetBufferList
    ***NdisFreeNetBufferListPool
    NdisGetRoutineAddress
    NdisGetVersion
    ***NdisGroupActiveProcessorCount
    NdisInitializeEvent
    NdisInitializeReadWriteLock
    NdisInitializeString
    ***NdisMAllocateNetBufferSGList
    NdisMAllocateSharedMemory
    NdisMCancelTimer
    ***NdisMDeregisterInterruptEx
    ***NdisMDeregisterMiniportDriver
    ***NdisMDeregisterScatterGatherDma
    ***NdisMFreeNetBufferSGList
    NdisMFreeSharedMemory
    ***NdisMGetBusData
    NdisMGetDeviceProperty
    ***NdisMIndicateReceiveNetBufferLists
    ***NdisMIndicateStatusEx
    NdisMInitializeTimer
    NdisMMapIoSpace
    NdisMQueryAdapterInstanceName
    ***NdisMRegisterInterruptEx
    ***NdisMRegisterMiniportDriver
    ***NdisMRegisterScatterGatherDma
    NdisMRemoveMiniport
    NdisMResetComplete
    ***NdisMSendNetBufferListsComplete
    ***NdisMSetBusData
    ***NdisMSetMiniportAttributes
    NdisMSetPeriodicTimer
    NdisMSleep
    NdisMUnmapIoSpace
    ***NdisOpenConfigurationEx
    ***NdisQueueIoWorkItem
    NdisReadConfiguration
    NdisReadNetworkAddress
    ***NdisRegisterDeviceEx
    NdisReleaseReadWriteLock
    NdisResetEvent
    NdisSetEvent
    ***NdisSetOptionalHandlers
    NdisSetTimer
    NdisWaitEvent

  3. #33
    you probaly right
    there any kinds of drivers even for ms-dos
    so microsoft really trying to take out any kind of the nt-series 4.0 - vista
    even tho microsoft is saying those are os independed supported

    but at least you found the e1e5132.sys you can use
    that might fixed the problem? or did that cause a different problem?

    it looks like kernelbase was invented with windows 7 instead of vista and therefore got version 6.1

    the problem here looks not very big when you look the missing functions in ntosrkl
    ***sprintf_s
    ***strcpy_s
    ***vsprintf_s
    ***memcpy_s
    for example those would be a childsplay


    if we load a newer ndis.sys like 6.1 that would cause more missing functions to ntoskrnl
    so in this case we would have to add many missing functions to ntoskrnl


    the other road maybe leads to write the missing exports to both ntoskrnl and ndis.sys (instead of using a newer ndis.sys and only going for ntoskrnl)
    then only that single driver will work since it found those functions on ndis and ntoskrnl


    since microsoft wrote a ms-dos useable driver there certainly got os independed solutions but do not offer them

  4. #34
    Quote Originally Posted by Elenil View Post
    ...but at least you found the e1e5132.sys you can use
    that might fixed the problem? or did that cause a different problem?
    That's the stock XP LAN driver and it does not have the B360 300-series device code in the INF file. I might add it to see what happens but the W7 INF file has many more registry entries in the INF file and uses a co-installer.

    Quote Originally Posted by Elenil View Post
    ...if we load a newer ndis.sys like 6.1 that would cause more missing functions to ntoskrnl so in this case we would have to add many missing functions to ntoskrnl ...
    I have tried ndis 6.2 in Depends with the equivalent ntoskrnl from W7 x86 and it creates more problems. It is looking for missing exports in another driver used by W7 that XP does not use.

    Quote Originally Posted by Elenil View Post
    ...the other road maybe leads to write the missing exports to both ntoskrnl and ndis.sys (instead of using a newer ndis.sys and only going for ntoskrnl) then only that single driver will work since it found those functions on ndis and ntoskrnl
    Yeah...I think that might be the best way.

Similar Threads

  1. Embembeded systems
    By tazBRC in forum Off Topic
    Replies: 2
    Last Post: April 26th, 2010, 21:29
  2. dr7.gd on mp systems running sice
    By deroko in forum Blogs Forum
    Replies: 5
    Last Post: February 11th, 2008, 10:16
  3. Realtime systems and OS dependency
    By Hero in forum Advanced Reversing and Programming
    Replies: 5
    Last Post: September 17th, 2006, 12:34
  4. keyboard problem with SoftICE on NT systems
    By quasar in forum Tools of Our Trade (TOT) Messageboard
    Replies: 4
    Last Post: March 31st, 2004, 03:40
  5. Replies: 6
    Last Post: August 25th, 2003, 13:02

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •