From: SourceForge.net <no...@so...> - 2010-02-21 13:58:59
|
Bugs item #2956051, was opened at 2010-02-21 16:58 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2956051&group_id=98788 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Daemons (Windows) Group: v0.7.x (release) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Leonius () Assigned to: Nobody/Anonymous (nobody) Summary: colinux-net-daemon: error opening registry key Initial Comment: At first, sample log: [code] Cooperative Linux Daemon, 0.7.4 Daemon compiled on Wed Apr 15 18:59:08 2009 PID: 3424 colinux: booting colinux-net-daemon: auto selecting TAP colinux-net-daemon: error opening registry key: SYSTEM\CurrentControlSet\Control \Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\SYSTEM\CurrentControlSet\Control \Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{016A6C21-3C79-4285-AEC2-A08BB7B B0215}\Connecticolinux-net-daemon: TAP device not found conet-slirp-daemon: running [/code] I discovered that * error happens when HKLM\SYSTEM\CurrentControlSet\Control\Network\{4D36E972-E325-11CE-BFC1-08002BE10318}\{016A6C21-3C79-4285-AEC2-A08BB7BB0215}\Connection is empty ("Default" key has no value and there are no keys). Yes, emptiness of that key can mean something abnormal (i'm not expert in Windows registry), but IMHO that's not a reason to fail searching for tap device. (I've lost estimately a day discovering a reason why there isn't connection to TAP device from andLinux :) ) And also, * Error message format is obscure, you'd better use "%s\Connection" instead of "%s\%s\Connection". ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2956051&group_id=98788 |