Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    WINDOWS    |    Bill Gates farts and we can ALL smell it    |    3,071 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 3,065 of 3,071    |
|    August Abolins to All    |
|    win7 boot stops at disk.sys    |
|    20 Mar 25 22:25:00    |
      MSGID: 2:221/1.58@fidonet 1e9aa80a       PID: OpenXP/5.0.64 (Win32)       CHRS: ASCII 1       TZUTC: -0400       I've been tasked to investigate a win7 32bit system that is        failing to load. It's an Acer Aspire 7715Z              I tried using a windows repair disk (created with another win 7        32bit system) ..but it doesn't get past the "select        language:US"              I can enter the Advanced Boot Options menu (via repeated F8        hits until it pops up).              I can select "Disable Restart" from that list and the system        enters BSOD with STOP code 0x000000ed              I've researched that stop code and the common strategy is to        get to the point where one can run CHKDSK /X /R /F ..but "Safe        Mode with command line) doesn't take me there either - the        system just stalls for a while, and then restarts. The last        driver loaded/reported is "disk.sys".              Selecting "Enable bootlogging" doesn't seem to write to the        ntbtlog.txt file in \Windows\System32 like it should.              Does anyone here have experience in sorting out this issue?              I can boot the pc with a linux live-cd (the Acer supports        64bit, so I chose antiX x64 Base) ...and that looks great.              fdisk -l lists the partitions fine. /dev/sda1 /dev/sda2 and        /dev/sda3 look good.              sudo mount /dev/sda3 /mnt ..works great and allows me to look        around on the Windows partition.              The driver files in /mnt/Windows/System32/drivers are viewable.              Should I just place all the matching driver files with the ones        from my good win7 32bit system?              Or.. should I only replace disk.sys first?              Common wisdom seems to indicate that the problem driver is        usually the one *after* disk.sys. But.. I can't be sure what        that next driver it was trying to load. If I could be sure        what that one is, maybe I could rename it so that it wouldn't        load?              If I look at \Windows\System32\ntbtlog.txt from my good win7        32bit machine, the next file after disk.sys is Classpnp.sys              So.. any ideas on how to resolve this mystery? Appreciated.                                                        --         ../|ug              --- OpenXP 5.0.64        * Origin: (2:221/1.58)       SEEN-BY: 19/25 105/81 106/201 987 124/5014 5016 128/187 129/305 130/330       SEEN-BY: 153/7715 154/110 218/700 226/30 227/114 229/110 114 206 300       SEEN-BY: 229/307 317 400 426 428 470 550 664 700 705 266/512 280/464       SEEN-BY: 291/111 292/854 320/219 322/757 342/200 387/18 25 396/45       SEEN-BY: 460/58 633/280 712/848 902/26 5075/35       PATH: 221/1 280/464 396/45 229/426           |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca