Announcement

Collapse
No announcement yet.

Problems using EWF booting from second drive

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problems using EWF booting from second drive

    I have an EEE 901, which has has a 4 GB soldered-in SSD, and a 16 GB SSD which can be removed/replaced if necessary. When booting using D: I'm getting a blue screen STOP error (0x0000007B) just after the Windows XP banner, on XP professional (not XPe).

    I successfully set up EWF on the C: drive, which is drive 0 located on the 4 GB SSD. This works perfectly, it boots fine; EWF is enabled after boot and all writes are cached in memory and committed to disk at shutdown only.

    However, what I really want to do is to move the OS to the second removable/replacable drive and only use the 4 GB for files that are not going to be updated normally. I have installed the OS on the second SSD, and it boots fine without EWF configured, but it is extremely slow when being written to - these SSD cards are well known for this. I thought EWF would be ideal for this, as there would be no writing during normal operation, just when shutting down.

    However I can't get EWF to work on this drive at all. Using the same procedure that I used to get it booting on C: just results in the BSOD as described above. The only thing I have changed is the "ArcName" string in the EWF service registry entry to "multi(0)disk(0)rdisk(1)partition(1)" to point to the second SSD.

    Everything else is the same as the other working configuration; ewf.sys is in D:\Windows\System32\drivers, and ewfmgr.exe is in D:\Windows\System32, UpperFilters has VolSnap and ewf (as separate values, not entered on the same line). The only way I can get it to boot normally after this is to revert to the last known good configuration, which removes the "ewf" entry from UpperFilters and boots without EWF.

    Does EWF have a limitation that it dosen't actually work on a bootable drive other than drive 0, or does anyone know what's going on in this case? Is there any way to get this configuration working?

  • #2
    you probably need to play around with the multi or disk settings....what controller is the 16GB on? what's the boot.ini setting look like?
    EWF, HORM, MinLogon on XP.

    Zotac ION Atom N330, 2GB low-profile RAM, M3-ATX
    Win Embedded Std 2011 RC
    OCZ Vertex Turbo 30GB SSD
    Lilliput 629 Transflective, WRX Screen Mount
    BlueSoleil BT, i-Blue GM-2 GPS, DirectedHD Radio, Andrea Mic
    VoomPC 2

    Comment


    • #3
      Hi SFiorito,

      This is my boot.ini below. As it works when booting the second drive without EWF, it indicates that the two drives use the same controller.

      [boot loader]
      timeout=10
      default=multi(0)disk(0)rdisk(1)partition(1)\WINDOW S
      [operating systems]
      multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windo ws XP - HDD 0" /noexecute=optin /fastdetect
      multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Windo ws XP - HDD 1" /noexecute=optin /fastdetect

      The ArcName entry is configured to match the boot multi path, as I mentioned. Has anyone else ever done a configuration to boot from a second drive and protect it with EWF?

      Are there any other registry parameters that might need to be changed to enable this configuration?

      Comment


      • #4
        To try to gather more information on this particular problem , I decided to build an identical setup under VMware, and the results are the same - a stop error when booting with EWF on a second drive:

        Here are the service registry entries I am using:

        [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\ewf]
        "ErrorControl"=dword:00000001
        "Group"="System Bus Extender"
        "Start"=dword:00000000
        "Type"=dword:00000001

        [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\ewf\Parameters]

        [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\ewf\Parameters\Protected]

        [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\ewf\Parameters\Protected\Volume0]
        "Enabled"=dword:00000000
        "Type"=dword:00000001
        "ArcName"="multi(0)disk(0)rdisk(1)partition(1) "

        [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\ewf\Enum]
        "0"="Root\\LEGACY_EWF\\0000"
        "Count"=dword:00000001
        "NextInstance"=dword:00000001



        The Class {71A27CDD-812A-11D0-BEC7-08002BE2092F} UpperFilters contains separate VolSnap and EWF entries.


        The BSOD error is:

        *** STOP: 0x0000007B (0xBACCF524, 0xC000000E, 0x00000000, 0x00000000)

        Comment


        • #5
          try removing the VolSnap entry
          EWF, HORM, MinLogon on XP.

          Zotac ION Atom N330, 2GB low-profile RAM, M3-ATX
          Win Embedded Std 2011 RC
          OCZ Vertex Turbo 30GB SSD
          Lilliput 629 Transflective, WRX Screen Mount
          BlueSoleil BT, i-Blue GM-2 GPS, DirectedHD Radio, Andrea Mic
          VoomPC 2

          Comment


          • #6
            Originally posted by SFiorito View Post
            try removing the VolSnap entry
            Hi SFiorito, I've removed the VolSnap entry but no, it dosent change the result - still the same problem unfortunately.

            Comment

            Working...
            X