Changes between Version 2 and Version 3 of Ticket #74, comment 24


Ignore:
Timestamp:
May 27, 2018, 11:58:53 PM (6 years ago)
Author:
Valery V. Sedletski

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #74, comment 24

    v2 v3  
    11Probably, it was cachef32.exe has been quit or crashed, and this unblocked the wait on line #475. No idea why waiting on line #475 (which is normal) should stop the system booting.
    22
    3 Did you checked, if cachef32.exe is in the process list, after it booted?
     3Did you checked, if cachef32.exe is in the process list, after it booted to desktop?
    44
    55Are you sure that it stops booting with cachef32.exe commented out? Because if cachef32.exe didn't started, then no "GET_REQ" fsctl function is called, so no blocking in this function, an nothing can stop the boot process. As far as I can see, at line #475 cachef32.exe is blocked in "GET_REQ" fsctl (function 0x8014). Without cachef32.exe, this function is not called at all, so no block.