Menu
▾
▴
[coLinux-devel] [ colinux-Bugs-1421858 ] daemon: exit code 87c0a001: couldn't get driver handle
|
From: SourceForge.net <no...@so...> - 2008-04-16 22:18:48
|
Bugs item #1421858, was opened at 2006-02-01 21:54 Message generated for change (Comment added) made by henryn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1421858&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: None Group: None >Status: Closed >Resolution: Out of Date Priority: 5 Private: No Submitted By: Ricky Ng-Adam (rngadam) Assigned to: Nobody/Anonymous (nobody) Summary: daemon: exit code 87c0a001: couldn't get driver handle Initial Comment: After installing 0.6.3-rc4, I've been able to boot into Debian image. But due to a problem with Firefox completly locking up and not responding to even the "End now" (could this be related to something coLinux installs?) I had to shut it down and reboot the machine. While shutting down and at "Closing network connections" XP locked up also and I had to hard reset the computer. Now, when I try to start it I get the following: C:\coLinux>colinux-daemon -c colinux.default.xml colinux: manager open: last error: The system cannot find the file specified. Cooperative Linux Daemon, 0.6.3-rc4 Compiled on Sun Jan 15 06:24:56 2006 colinux: manager open: last error: The system cannot find the file specified. error initializing colinux: manager open: last error: The system cannot find the file specified. couldn't get driver handle daemon: exit code 87c0a001 daemon: error - CO_RC_ERROR_ERROR, line 40, file colinux/user/monitor.o (62) ---------------------------------------------------------------------- >Comment By: Henry N. (henryn) Date: 2008-04-17 00:18 Message: Logged In: YES user_id=579204 Originator: NO Some changes (SVN r602 2007-04-11) are in the current release for shutting down race conditions. Will close this bug tracker now. ---------------------------------------------------------------------- Comment By: Ray Ward (rayfward) Date: 2006-11-19 13:58 Message: Logged In: YES user_id=1260917 Originator: NO I have had a similar problem and the solution was to remove the driver although it could only be removed through properties – hardware – device manager in windows. If you look under hidden devices you can see the colinux driver probably with a yellow exclamation mark against it. This stopped colinux-daemon –remove-driver from working so you could neither remove or install the driver. After removing you will have to reboot. Both colinux system I have installed booted up fine after that. The freezing thing looks to be colinux though. I can replicate it by using a dos prompt then going to full screen mode, this has hung windows a number of times while colinux and xming were open. System AMD Tbird Asus Mother board Windows 2000 ---------------------------------------------------------------------- Comment By: George P Boutwell (gboutwel) Date: 2006-09-11 03:01 Message: Logged In: YES user_id=30412 Has this issue been resolved? ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2006-02-02 16:59 Message: Logged In: YES user_id=579204 Under normal use, can remove and install coLinux and TAP driver without reboot. Only if driver open, sometimes coLinux does not can remove and install driver. Than a reboot helps. With name of driver I'm a liddle surprised, because a I have such driver from 0.7.1 version. But after remove all by hand and fresh install coLinux, I have also only CoLinuxDriver. http://www.henrynestler.com/colinux/screenshoots/HardwareDev iceManager.png ---------------------------------------------------------------------- Comment By: Ricky Ng-Adam (rngadam) Date: 2006-02-02 15:32 Message: Logged In: YES user_id=16351 Well, when I rebooted I moved the c:\coLinux directory to c:\coLinux-0.6.3-rc4 and reinstalled coLinux only. I then moved back the Debian image and it seems to work fine at the moment. I'll report back if I get more problems the next time I reboot. I suspect my problem was due more to TAP-win32 affecting the networking than coLinux itself? Perhaps a reboot was necessary after installing TAP? > There should see the driver CoLinuxDriver > and CoLinuxDriver-0.6.3 I only see CoLinuxDriver. C:\coLinux>colinux-daemon.exe --status-driver Cooperative Linux Daemon, 0.6.3-rc4 Compiled on Sun Jan 15 06:24:56 2006 checking if the driver is installed current state: 4 (fully initialized) current number of monitors: 1 current linux api version: 10 current periphery api version: 15 ---------------------------------------------------------------------- Comment By: Henry N. (henryn) Date: 2006-02-02 12:14 Message: Logged In: YES user_id=579204 Perhaps Windows has disabled coLinux driver on your hard crash? Only for interesting: Go into your hardware device manager, enable "hidden drivers", open the tree with "non pnp drivers". There should see the driver CoLinuxDriver and CoLinuxDriver-0.6.3, make a screenshot, if somethin not not normal. Please check drivers status on command line colinux-daemon.exe --status-driver To repair, try follow steps: Run on command line colinux-daemon.exe --remove-driver Reboot windows Install driver again colinux-daemon.exe --install-driver ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=622063&aid=1421858&group_id=98788 |
