Custom Query (16363 matches)
Results (1651 - 1653 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2915 | fixed | XP SP2 Host full networking failure with VB2.1 | ||
| Description |
After upgrading from VB 2.0.6 to 2.1.0 on my host, all networking functions on my laptop started to fail. Uninstall had no effect, I had to do a Windows Restore Rollback to restore the machine to working order. Thinkpad X31 (JUU2884 model), Win XP SP2, 1GB RAM Cisco VPN adapter Hamachi VPN adapter OpenVPN client installed, but not enabled AVG Anti-Virus 8.0.176 Comodo Firewall 3.5.x Bridging interface present, but was disabled, members had been removed Bridging was enabled under V2.06, but did not function - rolled back to NAT IBM Thinkvantage Access Connections managing wireless+wired adapters in system Wireless: 802.11A+B (Atheros AR5001X) Mini-PCI card (factory stock) Ethernet: Intel Pro/1000 MT Mobile (motherboard/stock) After upgrading to VB2.1, the ThinkVantage app was unable to control the networking adapters in any shape or form - they could be enabled by key-combo *prior* to OS boot, but would not gain connectivity. Machine would turn mostly catatonic for minutes, as Win XP (and Thinkvantage) seemed to desperately try to get something out of the networking adapters. Uninstall of VB2.1 had no effect. Re-install of VB2.06 had no effect. Rollback performed - restored functionality Above steps repeated, and issue is 100% reproducible. |
|||
| #2916 | fixed | NDIS.sys BSOD (they don't play well together) => Fixed in SVN/2.1.4 | ||
| Description |
If some parts of this post seem redundant, it's because it is being cross posted to all applicable support sites. I did up a customised installation DVD of Win XP Pro x64 for my system, but found that it resulted in a BSOD with NDIS.sys being the culprit. Specifically it would blue screen the instant a Ethernet cable was plugged in OR if the Ethernet cable was plugged in when the computer was started up, then it would BSOD when one logged into any account (when network connections are activated). After a fair amount of removing programs I found that the following 4 programs are incompatible, but only if all 4 are installed. If there are only 3 installed then one does not cop the BSOD. SCSI Pass Through Direct (SPTD) layer v1.56 x64 (released 11 Mar 08) http://www.duplexsecure.com/home Microsoft Virtual PC sp1 x64 (released 15 May 2008) http://www.microsoft.com/windows/products/winfamily/virtualpc/default.mspx VirtualBox-2.1.0-41146-Win_amd64.msi (17 Dec 08) . Comodo Firewall tested both the current Comodo Internet Security 3.5.57173.439 (3 Dec 2008) http://www.personalfirewall.comodo.com/download_firewall.html and older but stable Comomdo Firewall Pro 3.0.25.378 (30th May 2008) http://download.comodo.com/cfp/download/setups/CFP_Setup_3.0.25.378_XP_Vista_x64.exe . The problem does not exist with the older 2.0.6 version of VirtualBox (21 Nov 2008). I can see how Comodo Firewall, VirtualPC and VirtualBox could interact badly as they will all interact with the network stack, but I don't understand why the SPTD driver should make a difference, being as it is a CD-ROM emulator. Also (and very strangely) she will BSOD in VMware server 1.0.8 and VirtualBox 2.0.4 and it did so on my desktop: GA-EP45-DS3R Mobo with PCI-E Realtek RTL8168/8111 Gigabit Ethernet NICs but not on my laptop: Acer Aspire 5024WLMi with PCI Realtek RTL8169/8110 Family Gigabit Ethernet NIC, using CFP 3.0.25.378 The DVD was created using nLite with SPTD added via SVCPACK at T-13 and the rest executed from a batch file at RunOnce, see this post for full details: http://www.msfn.org/board/HOWTO_create_fully_date_XP_x64_DVD_t105277.html |
|||
| #2920 | fixed | VirtualBox 2.1 winXP guest openGL GLSelect mode defect -> Fixed in SVN | ||
| Description |
It seems like picking over GLSelect mode crashes ogl apps. |
|||

