Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


glnz

POSReady 2009 updates ported to Windows XP SP3 ENU

Recommended Posts

Yes, I've been having problems with the e-mail notifications ever since the recent server crash.
I'm getting some again now, but I'm still not convinced that it's working as it should.
I've had a few e-mails about posts from a couple of days previously, which should have come through straight away of course.
:)

Share this post


Link to post
Share on other sites

35 minutes ago, Dave-H said:

Yes, I've been having problems with the e-mail notifications ever since the recent server crash.
I'm getting some again now, but I'm still not convinced that it's working as it should.
I've had a few e-mails about posts from a couple of days previously, which should have come through straight away of course.
:)

Thanks for input @Dave-H, so it's not just me. :)

I unfollowed it, and than followed it again, and mail of your post arrived. :D Now it could be it, or not, only time will tell.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi all,

I compiled the openfabrics driver nvme vers 1.3 for Win server 2003 bit 32 (checked build) and added

NEW  storport.sys from win server 2003 to target XP SP3.

Then I connect a Toshiba RD400 nvme disk. Gives yellow questionmark in device manager.

With host XP SP3 connected via Null Modem cable and Windbg now I get the following:

 

Microsoft (R) Windows Debugger Version 6.12.0002.633 X86
Copyright (c) Microsoft Corporation. All rights reserved.

Opened \\.\com1
Waiting to reconnect...
Connected to Windows XP 2600 x86 compatible target at (Sun Jun 24 13:56:38.484 2018 (UTC + 2:00)), ptr64 FALSE
Kernel Debugger connection established.
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 UP Free x86 compatible
Built by: 2600.xpsp.080413-2111
Machine Name:
Kernel base = 0x804d7000 PsLoadedModuleList = 0x80553fc0
System Uptime: not available
STORMINI: StorPortInitialize returns Status(0x0)
STORMINI: Access Range, VirtualAddr=0xB9D28000.
STORMINI: NVMeFindAdapter: Stride Size set to 0x4
STORMINI: NVMeEnumNumaCores: # of NUMA node(s) = 1.
STORMINI: FYI: SRB status 0x6 scsi 0x0 for CDB 0x0 BTL 0 0 0
ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5
Break instruction exception - code 80000003 (first chance)
*******************************************************************************
*                                                                             *
*   You are seeing this message because you pressed either                    *
*       CTRL+C (if you run kd.exe) or,                                        *
*       CTRL+BREAK (if you run WinDBG),                                       *
*   on your debugger machine's keyboard.                                      *
*                                                                             *
*                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
*                                                                             *
* If you did not intend to break into the debugger, press the "g" key, then   *
* press the "Enter" key now.  This message might immediately reappear.  If it *
* does, press "g" and "Enter" again.                                          *
*                                                                             *
*******************************************************************************
nt!RtlpBreakWithStatusInstruction:
80527bdc cc              int     3
kd> !analyze -v
Connected to Windows XP 2600 x86 compatible target at (Sun Jun 24 14:01:40.906 2018 (UTC + 2:00)), ptr64 FALSE
Loading Kernel Symbols
...............................................................
.............................

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

....................
Loading User Symbols

Loading unloaded module list
............
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Unknown bugcheck code (0)
Unknown bugcheck description
Arguments:
Arg1: 00000000
Arg2: 00000000
Arg3: 00000000
Arg4: 00000000

Debugging Details:
------------------


PROCESS_NAME:  Idle

FAULTING_IP:
nt!RtlpBreakWithStatusInstruction+0
80527bdc cc              int     3

EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 80527bdc (nt!RtlpBreakWithStatusInstruction)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 3
   Parameter[0]: 00000000
   Parameter[1]: 8054ad4c
   Parameter[2]: 000003f8

ERROR_CODE: (NTSTATUS) 0x80000003 - {AUSNAHME}  Haltepunkt  Im Quellprogramm wurde ein Haltepunkt erreicht.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - Mindestens ein Argument ist ung ltig.

EXCEPTION_PARAMETER1:  00000000

EXCEPTION_PARAMETER2:  8054ad4c

EXCEPTION_PARAMETER3:  000003f8

DEFAULT_BUCKET_ID:  DRIVER_FAULT

BUGCHECK_STR:  0x0

STACK_TEXT:  
80549bcc 8054109d 00000001 ff676902 00000030 nt!RtlpBreakWithStatusInstruction
80549bcc 806d772a 00000001 ff676902 00000030 nt!KeUpdateSystemTime+0x165
80549c50 80541af0 00000000 0000000e 00000000 hal!HalProcessorIdle+0x2
80549c54 00000000 0000000e 00000000 00000000 nt!KiIdleLoop+0x10


STACK_COMMAND:  kb

FOLLOWUP_IP:
nt!RtlpBreakWithStatusInstruction+0
80527bdc cc              int     3

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!RtlpBreakWithStatusInstruction+0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlpa.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4802516a

BUCKET_ID:  MANUAL_BREAKIN

Followup: MachineOwner
---------

 

From this I can only see, that ntkrnlpa.exe does not like to work with this nvme.sys.

But why? No error during compile.

I am happy, if someone here has an idea,

have a nice day

Dietmar

PS: With naked Win7 (very first version) this driver nvme.sys works fantastic.

 

PS:

kd> .trap 0xB9D28000
ErrCode = ffffffff
eax=ffffffff ebx=ffffffff ecx=ffffffff edx=ffffffff esi=ffffffff edi=ffffffff
eip=ffffffff esp=ffffffff ebp=ffffffff iopl=3 vip vif ov dn ei ng zr ac pe cy
cs=ffff  ss=ffff  ds=ffff  es=ffff  fs=ffff  gs=ffff             efl=ffffffff
ffff:ffff ??              ???

 

STORMINI: Access Range, VirtualAddr=0xB9D28000.

Can this be, because the nvme Toshiba RD400 is not seen in Bios?

Edited by Dietmar

Share this post


Link to post
Share on other sites
43 minutes ago, Dietmar said:

ERROR: DavReadRegistryValues/RegQueryValueExW(4). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(5). WStatus = 5
ERROR: DavReadRegistryValues/RegQueryValueExW(6). WStatus = 5

 

43 minutes ago, Dietmar said:

*   You are seeing this message because you pressed either                    *
*       CTRL+C (if you run kd.exe) or,                                        *
*       CTRL+BREAK (if you run WinDBG),                                       *
*   on your debugger machine's keyboard.                                      *
*                                                                             *
*                   THIS IS NOT A BUG OR A SYSTEM CRASH                       *
*                                                                             *
* If you did not intend to break into the debugger, press the "g" key, then   *
* press the "Enter" key now.  This message might immediately reappear.  If it *
* does, press "g" and "Enter" again.                                          *

hmm...

Share this post


Link to post
Share on other sites

@Dietmar  best of luck man.

Share this post


Link to post
Share on other sites
Posted (edited)

@Dietmar You compiled nvme.sys, but device access is enabled via StorNVMe.sys which is included in Windows Server 2012 R2, Windows 8.1, Windows 10 and has been released as KB update for Windows 7, Windows Server 2008 R2, Windows Server 2012 and Windows 8. I think that ntkrnlpa.exe tries to load nvme.sys but then fails to load StorNVMe.sys and Storport.sys.

I'm just speculating, though, I might be wrong.

Edited by FranceBB

Share this post


Link to post
Share on other sites

Storport from Server 2003 works fine.

Share this post


Link to post
Share on other sites
Posted (edited)

Hi,

I tested my nvme.sys driver on an z97 Asus motherboard,

where the Toshiba RD400 can be seen from Bios.

I get there exakt the same error message with DebugView as before with Windbg on the other compi.

So the error depends not on Bios.

This nice Debug program from Sysinternal can be used on the same compi without virtual machine.

Again I compared all dependencies from Win 7 and Xp.

They are absolut identic via nvme.sys to storport.sys.

New storport.sys from server 2003 is loaded in XP,  nvme.sys not.

But the ntkrnlpa.exe in Win7 works different from ntkrnlpa.exe in XP.

But still all dependencies for nvme.sys in XP are fullfilled.

I also tested, that may be some parameters from nvme.sys in registry work only for win7 but not in XP.

This is not the reason, why nvme.sys is not loaded in XP

have a nice day,

Dietmar

 

EDIT:

 

kd> !devnode 0x8b121820
DevNode 0x8b121820 for PDO 0x8b121ac0
  Parent 0x8b0e7828   Sibling 0000000000   Child 0000000000
  InstancePath is "PCI\VEN_1B85&DEV_6018&SUBSYS_60181B85&REV_01\3&9d5f036&0&00E4"
  ServiceName is "nvme"
  State = DeviceNodeRemoved (0x312)
  Previous State = DeviceNodeStartCompletion (0x306)
  StateHistory[06] = DeviceNodeStartCompletion (0x306)
  StateHistory[05] = DeviceNodeAwaitingQueuedRemoval (0x30f)
  StateHistory[04] = DeviceNodeStartCompletion (0x306)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
  StateHistory[02] = DeviceNodeDriversAdded (0x303)
  StateHistory[01] = DeviceNodeInitialized (0x302)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  StateHistory[13] = Unknown State (0x0)
  StateHistory[12] = Unknown State (0x0)
  StateHistory[11] = Unknown State (0x0)
  StateHistory[10] = Unknown State (0x0)
  StateHistory[09] = Unknown State (0x0)
  StateHistory[08] = Unknown State (0x0)
  StateHistory[07] = Unknown State (0x0)
  Flags (0x00002030)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_HAS_PROBLEM
  Problem = CM_PROB_FAILED_START
  Failure Status 0000000000

 

And here the same with win7, where this nvme.sys works:

0: kd> !devnode 0x863e36d0
DevNode 0x863e36d0 for PDO 0x863e7030
  Parent 0x863cf518   Sibling 0000000000   Child 0x864c28d8
  InstancePath is "PCI\VEN_1B85&DEV_6018&SUBSYS_60181B85&REV_01\4&26fb55b0&0&00E4"
  ServiceName is "nvme"
  State = DeviceNodeStarted (0x308)
  Previous State = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[15] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[14] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[13] = DeviceNodeStarted (0x308)
  StateHistory[12] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[11] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[10] = DeviceNodeStarted (0x308)
  StateHistory[09] = DeviceNodeEnumerateCompletion (0x30d)
  StateHistory[08] = DeviceNodeEnumeratePending (0x30c)
  StateHistory[07] = DeviceNodeStarted (0x308)
  StateHistory[06] = DeviceNodeStartPostWork (0x307)
  StateHistory[05] = DeviceNodeStartCompletion (0x306)
  StateHistory[04] = DeviceNodeStartPending (0x305)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
  StateHistory[02] = DeviceNodeDriversAdded (0x303)
  StateHistory[01] = DeviceNodeInitialized (0x302)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  Flags (0x6c0000f0)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_HAS_BOOT_CONFIG, DNF_BOOT_CONFIG_RESERVED,
                      DNF_NO_LOWER_DEVICE_FILTERS, DNF_NO_LOWER_CLASS_FILTERS,
                      DNF_NO_UPPER_DEVICE_FILTERS, DNF_NO_UPPER_CLASS_FILTERS
  CapabilityFlags (0x00002000)  WakeFromD3

EDIT:

The most important seems to me, that the child process is not populated:

XP:

Parent 0x8b0e7828   Sibling 0000000000   Child 0000000000

 

Win7:

Parent 0x863cf518   Sibling 0000000000   Child 0x864c28d8

 

This fits with the normal nvme.sys start, but fails during enumerate childs.

Oh, may be this can be fixed, because I read, that this can depend on the unknown Pci device ID of the Toshiba RD 400

PCI\VEN_1B85&DEV_6018&SUBSYS_60181B85&REV_01\4&26fb55b0&0&00E4

 

DNF_IDS_QUERIED

https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/irp-mn-query-id

 

Problem seems to be much bigger:))

Driver object (8af9b3d8) is for:
 \Driver\nvme
DriverEntry:   b971e03e    nvme!GsDriverEntry
DriverStartIo: 00000000    
DriverUnload:  00000000    
AddDevice:     00000000    

Dispatch routines:
[00] IRP_MJ_CREATE                      804f354a    nt!IopInvalidDeviceRequest
[01] IRP_MJ_CREATE_NAMED_PIPE           804f354a    nt!IopInvalidDeviceRequest
[02] IRP_MJ_CLOSE                       804f354a    nt!IopInvalidDeviceRequest
[03] IRP_MJ_READ                        804f354a    nt!IopInvalidDeviceRequest
[04] IRP_MJ_WRITE                       804f354a    nt!IopInvalidDeviceRequest
[05] IRP_MJ_QUERY_INFORMATION           804f354a    nt!IopInvalidDeviceRequest
[06] IRP_MJ_SET_INFORMATION             804f354a    nt!IopInvalidDeviceRequest
[07] IRP_MJ_QUERY_EA                    804f354a    nt!IopInvalidDeviceRequest
[08] IRP_MJ_SET_EA                      804f354a    nt!IopInvalidDeviceRequest
[09] IRP_MJ_FLUSH_BUFFERS               804f354a    nt!IopInvalidDeviceRequest
[0a] IRP_MJ_QUERY_VOLUME_INFORMATION    804f354a    nt!IopInvalidDeviceRequest
[0b] IRP_MJ_SET_VOLUME_INFORMATION      804f354a    nt!IopInvalidDeviceRequest
[0c] IRP_MJ_DIRECTORY_CONTROL           804f354a    nt!IopInvalidDeviceRequest
[0d] IRP_MJ_FILE_SYSTEM_CONTROL         804f354a    nt!IopInvalidDeviceRequest
[0e] IRP_MJ_DEVICE_CONTROL              804f354a    nt!IopInvalidDeviceRequest
[0f] IRP_MJ_INTERNAL_DEVICE_CONTROL     804f354a    nt!IopInvalidDeviceRequest
[10] IRP_MJ_SHUTDOWN                    804f354a    nt!IopInvalidDeviceRequest
[11] IRP_MJ_LOCK_CONTROL                804f354a    nt!IopInvalidDeviceRequest
[12] IRP_MJ_CLEANUP                     804f354a    nt!IopInvalidDeviceRequest
[13] IRP_MJ_CREATE_MAILSLOT             804f354a    nt!IopInvalidDeviceRequest
[14] IRP_MJ_QUERY_SECURITY              804f354a    nt!IopInvalidDeviceRequest
[15] IRP_MJ_SET_SECURITY                804f354a    nt!IopInvalidDeviceRequest
[16] IRP_MJ_POWER                       804f354a    nt!IopInvalidDeviceRequest
[17] IRP_MJ_SYSTEM_CONTROL              804f354a    nt!IopInvalidDeviceRequest
[18] IRP_MJ_DEVICE_CHANGE               804f354a    nt!IopInvalidDeviceRequest
[19] IRP_MJ_QUERY_QUOTA                 804f354a    nt!IopInvalidDeviceRequest
[1a] IRP_MJ_SET_QUOTA                   804f354a    nt!IopInvalidDeviceRequest
[1b] IRP_MJ_PNP                         804f354a    nt!IopInvalidDeviceRequest

nvme!DriverEntry:
b970a010 8bff            mov     edi,edi
kd> t
nvme!DriverEntry+0x8:
b970a018 c745a800000000  mov     dword ptr [ebp-58h],0

 

EDIT:

No, this means nothing, because I stopped nvme.sys, after it was loaded, but BEFORE its entry point was reached. So, nvme.sys until this time cant do anything good or bad:)).

 

EDIT:

The fail in win2003 Sp2 bit 32 is the same. Also Vista. I think, it is all about the new ContainerID

for numerating pci-e devices, starting with win7.

 

win2003: nvme.sys cant enumerate devices.

kd> !devnode 0x8aef6298
DevNode 0x8aef6298 for PDO 0x8aef6658
  Parent 0x8aeb5228   Sibling 0000000000   Child 0000000000
  InstancePath is "PCI\VEN_1B85&DEV_6018&SUBSYS_60181B85&REV_01\4&41a6924&0&00E4"
  ServiceName is "nvme"
  State = DeviceNodeRemoved (0x312)
  Previous State = DeviceNodeStartCompletion (0x306)
  StateHistory[06] = DeviceNodeStartCompletion (0x306)
  StateHistory[05] = DeviceNodeAwaitingQueuedRemoval (0x30f)
  StateHistory[04] = DeviceNodeStartCompletion (0x306)
  StateHistory[03] = DeviceNodeResourcesAssigned (0x304)
  StateHistory[02] = DeviceNodeDriversAdded (0x303)
  StateHistory[01] = DeviceNodeInitialized (0x302)
  StateHistory[00] = DeviceNodeUninitialized (0x301)
  StateHistory[19] = Unknown State (0x0)
  StateHistory[18] = Unknown State (0x0)
  StateHistory[17] = Unknown State (0x0)
  StateHistory[16] = Unknown State (0x0)
  StateHistory[15] = Unknown State (0x0)
  StateHistory[14] = Unknown State (0x0)
  StateHistory[13] = Unknown State (0x0)
  StateHistory[12] = Unknown State (0x0)
  StateHistory[11] = Unknown State (0x0)
  StateHistory[10] = Unknown State (0x0)
  StateHistory[09] = Unknown State (0x0)
  StateHistory[08] = Unknown State (0x0)
  StateHistory[07] = Unknown State (0x0)
  Flags (0x00002030)  DNF_ENUMERATED, DNF_IDS_QUERIED,
                      DNF_HAS_PROBLEM
  CapabilityFlags (0x00002000)  WakeFromD3
  Problem = CM_PROB_FAILED_START
  Failure Status 0000000000

 

EDIT:

The fail is NOT because of containerid. In win7, the containerid for nvme drive from openfabrics is just faked, but works. win 7 registry entry:

"ContainerID"="{00000000-0000-0000-ffff-ffffffffffff}"
"ConfigFlags"=dword:00000000
"LocationInformation"="@system32\\DRIVERS\\pci.sys,#65536;PCI-Bus %1, Gerät %2, Funktion %3;(4,0,0)"
"ClassGUID"="{4d36e97b-e325-11ce-bfc1-08002be10318}"
"Driver"="{4d36e97b-e325-11ce-bfc1-08002be10318}\\0000"
"Class"="SCSIAdapter"
"Mfg"="@oem1.inf,%comm%;Community"
"Service"="nvme"
"ParentIdPrefix"="5&15f2af2f&0"

 

Edit: Small success: On an Asus z97-k motherboard which knows from its Bios nvme drives,

I copied a working XP with debug enabled via Aomeid from an Fat32 partition to the Toshiba RD400, sector by sector. Nice, XP starts from this RD400 via Bios drivers and lives long enough, so that the debugger can start. Because no good working nvme.sys on this RD400, it crashes.

But now I catch via crash.dump XP in the moment, when the driver nvme.sys was still loaded.

I have a good chance to see, why the openfabrics driver nvme.sys crashes on XP.

Here you can see, that nvme and storeport.sys are still loaded (but crashes).

kd> lm
start    end        module name
804d7000 806e5000   nt         (pdb symbols)          c:\symbols\ntkrpamp.pdb\7D6290E03E32455BB0E035E38816124F1\ntkrpamp.pdb
806e5000 80705d00   hal        (pdb symbols)          c:\symbols\halmacpi.pdb\9875FD697ECA4BBB8A475825F6BF885E1\halmacpi.pdb
b95b7000 b95d0b80   Mup        (pdb symbols)          c:\symbols\mup.pdb\B725137B0D634A81A0BBAE29CFB0491A2\mup.pdb
b95d1000 b95fd980   NDIS       (pdb symbols)          c:\symbols\ndis.pdb\94A67EAE18514379881AE6FA7FC1C1FB2\ndis.pdb
b95fe000 b968a600   Ntfs       (pdb symbols)          c:\symbols\ntfs.pdb\AA4F4A5C7B1D4663A7E0891479090D8A2\ntfs.pdb
b968b000 b96a1880   KSecDD     (pdb symbols)          c:\symbols\ksecdd.pdb\019C3CABC0534E9B9C855F2A0FEE62A61\ksecdd.pdb
b96a2000 b96b3f00   sr         (pdb symbols)          c:\symbols\sr.pdb\9D5432B7234C4CD2A8F6275B9D9AF41F1\sr.pdb
b96b4000 b96d3b00   fltMgr     (pdb symbols)          c:\symbols\fltMgr.pdb\30197425FFC04385B84C0354E5035D5C1\fltMgr.pdb
b96d4000 b96f2000   storport   (pdb symbols)          c:\symbols\storport.pdb\C52B0EA7F7574A9AB0D5961C3E61C5021\storport.pdb
b96f2000 b970a000   nvme       (private pdb symbols)  c:\winddk\7600.16385.1\src\openfabricsall\nvme13\nvme\objchk_wnet_x86\i386\nvme.pdb
b970a000 b9721900   atapi      (pdb symbols)          c:\symbols\atapi.pdb\3379CE3C730640ADA2AEC243E90016481\atapi.pdb
b9722000 b9747a00   dmio       (pdb symbols)          c:\symbols\dmio.pdb\7DD31474CC0941E9B2175DDBC956E4601\dmio.pdb
b9748000 b9766d80   ftdisk     (no symbols)           
b9767000 b9777a80   pci        (pdb symbols)          c:\symbols\pci.pdb\46927BAFB8E740B6B4BAC813675A82871\pci.pdb
b9778000 b97a6180   ACPI       (pdb symbols)          c:\symbols\acpi.pdb\3E23085EEF9C4EB5AC40C386278F6D7E1\acpi.pdb
b98a8000 b98b1300   isapnp     (pdb symbols)          c:\symbols\isapnp.pdb\C88742CDDA0641E39B06BD20309F22991\isapnp.pdb
b98b8000 b98c2580   MountMgr   (pdb symbols)          c:\symbols\mountmgr.pdb\1E7C54F0C4714B9FB389A50F6A5FBDDA1\mountmgr.pdb
b98c8000 b98d5200   VolSnap    (pdb symbols)          c:\symbols\volsnap.pdb\063AE2CDED15450491E240111E7E66511\volsnap.pdb
b98d8000 b98e0e00   disk       (pdb symbols)          c:\symbols\disk.pdb\973C93819420401FB85626ABA3E8C2E21\disk.pdb
b98e8000 b98f4180   CLASSPNP   (pdb symbols)          c:\symbols\classpnp.pdb\79125526F95B483880DC8AC59206505E2\classpnp.pdb
b9b28000 b9b2e800   firadisk   (no symbols)           
b9b30000 b9b36180   PCIIDEX    (pdb symbols)          c:\symbols\pciidex.pdb\E5F499C1EEAB4ECDB880F669D946ACC81\pciidex.pdb
b9b38000 b9b3cd00   PartMgr    (pdb symbols)          c:\symbols\partmgr.pdb\2D84C75248124571A4A1066A9983AB951\partmgr.pdb
b9cb8000 b9cbb000   BOOTVID    (export symbols)       BOOTVID.dll
b9da8000 b9da9b80   kdcom      (export symbols)       kdcom.dll
b9daa000 b9dab100   WMILIB     (export symbols)       WMILIB.SYS
b9dac000 b9dad700   dmload     (no symbols)           
b9e70000 b9e70d00   pciide     (no symbols)           

 

Edited by Dietmar

Share this post


Link to post
Share on other sites

2019 is approaching, so is the end of extended support and it seems that ATM running Windows XP based OS are getting an ultimatum, at least in India.

 

"The Reserve Bank of India has given that country's banking sector a hard deadline to get Windows XP out of its ATMs: June 2019."

Share this post


Link to post
Share on other sites

Well, considering that:

  • Windows Embedded Standard 2009, Extended Support will end on Jan. 8, 2019.
  • Windows Embedded POSReady 2009, Extended support will end on Apr. 9, 2019.

...it does make sense. That's not to say we'll give up on XP so soon, of course!  :D

  • Like 4

Share this post


Link to post
Share on other sites
4 hours ago, dencorso said:

That's not to say we'll give up on XP so soon, of course!  :D

Wise words :thumbup

jaclaz

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

@heinoganda

After disable SSLv2, SSLv3 (HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\) and RC4, DES (HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\), everything is working again


1209968842_WindowsUpdate-again-thuthuatdoday.blogspot_com.thumb.png.f28db2a531ca5cbd1ff8e1d837111cc8.png

651084045_InternetExplorer8-SSL-thuthuatdoday.blogspot_com.thumb.png.c022a90f56107302b49cd7760e1aeabd.png

Edited by MaterSystem

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/15/2018 at 10:40 AM, heinoganda said:

@MaterSystem

The Windows update server cluster, which is distributed worldwide, has been struggling with various problems lately. This has been commented in this topic by me and other users who were affected (Non-availability and various error messages). Unfortunately, a certain amount of time has been lost after a crash with the server for the forum.

You can try at WU / MU in IE8 (currently only TLS 1.2 Encryption is enough) via https connection, has partly helped.


https://update.microsoft.com/windowsupdate
https://update.microsoft.com/microsoftupdate

:)

 

The first works, the second one shows "The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable."

I left the old http link scan for like almost 48 hours and it didn't show any results, it was still searching. I'm gonna leave the https one scan overnight, let's see if it will find the updates.

I know that I can just manually download the updates, but I wanna find out how long it takes for IE to find updates and if it finds them at all.

I know for sure that "Automatic Update" doesn't work, 'cause it has been showing the yellow shield for years, but it didn't show up in June, so...

 

Edited by FranceBB

Share this post


Link to post
Share on other sites

Hi all,

I compared the registry entries from XP before the install of nvme.sys and after.

I noticed, that all the registry entries from nvme.inf have been build correct in registry for XP.

Then I did the same for win7.

Hm, very interesting, in win7 this nvme.sys is then then also connected in registry to the drive Toshiba RD400,

but in XP not.

The scsi driver nvme.sys and storport.sys build a driver pair. nvme belongs to hardware, storport to operating system.

Can this simple be, that the storeport library, which functions build in the driver storport.sys to speak via nvme.sys to the hardware (RD400), which is sufficient for driving the hardware, does only know for the storport.sys from win7,

that the entry in nvme.inf file PCI\CC_010802 belongs to Toshiba RD400?

That would explain at once, why this driver nvme.sys does not work for XP, Server 2003, Vista.

This would be not the fault of nvme.sys, but for the storport.sys because build from incomplete library.

What do you think,

have a nice day

Dietmar

PS: If I am right, is there a chance to update the library for storeport.sys from Win 2003?

And, if not, can the needed entries build by hand in registry for RD400?

Share this post


Link to post
Share on other sites
Posted (edited)
On 6/27/2018 at 9:22 AM, MaterSystem said:

@heinoganda

After disable SSLv2, SSLv3 (HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\) and RC4, DES (HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Ciphers\), everything is working again


1209968842_WindowsUpdate-again-thuthuatdoday.blogspot_com.thumb.png.f28db2a531ca5cbd1ff8e1d837111cc8.png

651084045_InternetExplorer8-SSL-thuthuatdoday.blogspot_com.thumb.png.c022a90f56107302b49cd7760e1aeabd.png

 

After installing the last update ie8-windowsxp-kb4316682-x86-embedded-enu_cc345109f94dd7b763cc415385974632a058fd07

The search works quickly and without any problems.

Edited by Robinek

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×