Well, I can certainly see a need for ethernet upon recovery. I'll try to find out how to add the missing driver to the Ghost recovery discs.
The reason I'm using Norton Ghost 15 (or Acronis True Image as a runner up) is because of my odd requirements. I want a bootable clone, not a recoverable image (though I may end up doing the latter when I've become more comfortable with managing partitions). Furthermore, the target HDD is smaller than the source HDD, and I want the cloning app to downsize partitions in the cloning process. That way, I don't have to mess around with the partitions on the source drive before making and verifying the clone. Finally, I want to clone all 4 partitions (Toshiba has extra partitions for recovery operations), so the app should have the flexibility to downsize the C-drive partition in the cloning process.
I did some googling around to find which apps have shown evidence of meeting such (not-so-common) requirements, and somewhere, Macrium was vetted out. I don't recall the exact reason, but would you be able to comment on its ability to meet all the above requirements?
As for Paragon, a respondent in one of their forums suggested Migrate OS to SSD, which I bought and tried. I wasn't able to select all 4 partitions. I'm assuming that it detected the boot partition (partition 1) and the C-drive partition (partition 2), but the former wasn't very clear. Tech support was not sure that it was designed for what I was trying to do, and suggested other apps.
The reason I'm using Norton Ghost 15 (or Acronis True Image as a runner up) is because of my odd requirements. I want a bootable clone, not a recoverable image (though I may end up doing the latter when I've become more comfortable with managing partitions). Furthermore, the target HDD is smaller than the source HDD, and I want the cloning app to downsize partitions in the cloning process. That way, I don't have to mess around with the partitions on the source drive before making and verifying the clone. Finally, I want to clone all 4 partitions (Toshiba has extra partitions for recovery operations), so the app should have the flexibility to downsize the C-drive partition in the cloning process.
I did some googling around to find which apps have shown evidence of meeting such (not-so-common) requirements, and somewhere, Macrium was vetted out. I don't recall the exact reason, but would you be able to comment on its ability to meet all the above requirements?
As for Paragon, a respondent in one of their forums suggested Migrate OS to SSD, which I bought and tried. I wasn't able to select all 4 partitions. I'm assuming that it detected the boot partition (partition 1) and the C-drive partition (partition 2), but the former wasn't very clear. Tech support was not sure that it was designed for what I was trying to do, and suggested other apps.
![Ethernet Ethernet](/uploads/1/2/6/6/126677093/603053648.png)
The thread WAN miniport ikev2, windows cannot load the driver - Pb for VPN connection how to transplant the relevant part of the registry, but I would like to avoid mucking with the registry if possible. I would feel much more confident about having a driver that can be installed by more conventional means (if there is such a thing). These WAN drivers support the Remote Access Service (RAS) and the Point-to-Point Protocol (PPP) over such media as ISDN, Frame Relay, or Switched 56. This section includes the following topics: Choosing a WAN Driver Model. Overview of the WAN Architecture. Implementing CoNDIS WAN Miniport Drivers. CoNDIS WAN Operations That Support Telephonic.
Ethernet Controller Driver Wan Miniport Windows 7 Download
Not sure, if this will help?
Here are the steps to re-install WAN miniport devices
Step 1: Uninstall WAN Miniport Devices
1. Open Device Manager (devmgmt.msc) and on the view menu select Show hidden devices
2. Under Network adapters, you will see WAN miniport devices (IP, L2TP, Pppoe, PPTP). If you don’t see these, skip to the Step 2 section
3. Open Registry editor (regedit.exe)
4. Browse to the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{4D36E972-E325-11CE-BFC1-08002BE10318} and Export this registry subkey
5. Click each of the registry subkeys under this key. Look up the data value in DriverDesc. Find the subkey that corresponds to the miniport device for example, WAN Miniport (IP).
6. Right click the subkey (for example 005), and then click delete. Click Yes to confirm deletion
7. Go into Device Manager and right click the miniport device that corresponds to the subkey that was deleted. Select uninstall and confirm uninstallation
8. Repeat this process for all miniport devices that you need to uninstall
Step 2: Reinstall WAN Miniport Devices
9. Find netrasa.inf in c:windowsinf
10. Make a copy of this file (netrasa.bak)
11. Open netrasa.inf and comment out the following section:
13. Select Yes, I have already connected the hardware, then Next
14. Select Add a new hardware device, then Next
15. Select Install the hardware that I manually select from a list (Advanced), then Next
16. Select Network Adapters, then Next
17. Select Microsoft in the Manufacturer section and then on the Network Adapter, select the desired WAN Miniport device, then Next and Finish the wizard
18. Repeat 13 – 18 for each device you are re-installing
19. After the devices are re-installed, reboot the system
20. Run netsh int ip reset c:resetlog.txt and reboot the system again (Resetting the TCP/IP stack)
21. Check the network connections in device manager and in Network Connection (ncpa.cpl)
22. Delete c:windowsinfnetrasa.inf and rename netrasa.bak to netrasa.inf
Here are the steps to re-install WAN miniport devices
Step 1: Uninstall WAN Miniport Devices
1. Open Device Manager (devmgmt.msc) and on the view menu select Show hidden devices
2. Under Network adapters, you will see WAN miniport devices (IP, L2TP, Pppoe, PPTP). If you don’t see these, skip to the Step 2 section
3. Open Registry editor (regedit.exe)
4. Browse to the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlClass{4D36E972-E325-11CE-BFC1-08002BE10318} and Export this registry subkey
5. Click each of the registry subkeys under this key. Look up the data value in DriverDesc. Find the subkey that corresponds to the miniport device for example, WAN Miniport (IP).
6. Right click the subkey (for example 005), and then click delete. Click Yes to confirm deletion
7. Go into Device Manager and right click the miniport device that corresponds to the subkey that was deleted. Select uninstall and confirm uninstallation
8. Repeat this process for all miniport devices that you need to uninstall
Step 2: Reinstall WAN Miniport Devices
9. Find netrasa.inf in c:windowsinf
10. Make a copy of this file (netrasa.bak)
11. Open netrasa.inf and comment out the following section:
Before12. Start the Add Hardware Wizard from control panel
[ControlFlags]
ExcludeFromSelect =
SW{eeab7790-c514-11d1-b42b-00805fc1270e},
MS_IrdaMiniport,
MS_IrModemMiniport,
MS_L2tpMiniport,MS_PptpMiniport,
MS_PppoeMiniport,
MS_NdisWanBh,
MS_NdisWanIp,
MS_NdisWanIpv6,
MS_NdisWanNbfIn,MS_NdisWanNbfOut
After
[ControlFlags]
;ExcludeFromSelect =
; SW{eeab7790-c514-11d1-b42b-00805fc1270e},
; MS_IrdaMiniport,
; MS_IrModemMiniport,
; MS_L2tpMiniport,MS_PptpMiniport,
; MS_PppoeMiniport,
; MS_NdisWanBh,
; MS_NdisWanIp,
; MS_NdisWanIpv6,
; MS_NdisWanNbfIn,MS_NdisWanNbfOut
13. Select Yes, I have already connected the hardware, then Next
14. Select Add a new hardware device, then Next
15. Select Install the hardware that I manually select from a list (Advanced), then Next
16. Select Network Adapters, then Next
17. Select Microsoft in the Manufacturer section and then on the Network Adapter, select the desired WAN Miniport device, then Next and Finish the wizard
18. Repeat 13 – 18 for each device you are re-installing
19. After the devices are re-installed, reboot the system
20. Run netsh int ip reset c:resetlog.txt and reboot the system again (Resetting the TCP/IP stack)
21. Check the network connections in device manager and in Network Connection (ncpa.cpl)
22. Delete c:windowsinfnetrasa.inf and rename netrasa.bak to netrasa.inf