![]() After I moved a Windows XP machine it would not boot on the new PC, and kept bluescreening continuously. I use the export and then import feature in VirtualBox to do this. I am in the process of setting up a new computer and part of that means moving all my VMs. Lately I have been using it for all my host-based virtualization needs. ![]() USB NIC) to avoid this issue and keep using special industrial applications.I’ve got to handle it to Oracle their virtualization software VirtualBox is amazing…and free! It’s features surpass Windows Virtual PC by leaps and are on par with VMWare Workstation. In case special protocols are in use, activate them only on a separate physical network interface (e.g. There might be other applications that utilize NIC management and couple a protocol usage to it, which may be a rare but recurring issue in some corporate environments. Solution: see Control Panel -> Network and Sharing Center -> Change adapter settings -> select a FortiClient adapter -> uncheck the entries for special protocol(s), in my case the "SIMATIC Industrial Ethernet (ISO)" 98% connection status Windows will crash because of an exception in ndis.sys. In case the added FortiClient NIC adapters have active usage of the SIMATIC Industrial Ethernet (ISO) protocol, at ca. ![]() did not help) According to a Siemens-forum, tweaking the registry might help, but did not in my case. Only a complete reinstall of Windows (including everything) was the solution - until now. In my case, if the Siemens SIMATIC Automation Tool is installed, the crash becomes reproducible. The crash was reproducible on my workstation as well: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |