[coLinux-devel] [ colinux-Bugs-2893343 ] host BSOD on with 20091105

[SourceForge.net <no...@so...>]

Bugs item #2893343, was opened at 2009-11-06 16:25
Message generated for change (Comment added) made by henryn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&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: Crash / BSOD
Group: v0.8.x (devel)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: host BSOD on with 20091105

Initial Comment:
with snapshot 0.8.0-20091105, the host got BSOD. no problem with 0.8.0-20090905.
downloaded from http://www.colinux.org/snapshots/
os: windows xp sp3 with all hotfix installed

i have retried many time, double check file permission, no luck

----------------------------------------------------------------------

>Comment By: Henry N. (henryn)
Date: 2009-11-06 21:43

Message:
Do clean upgrade steps by step:
* Download archive "daemons-0.8.0-20091105.zip" form:
http://www.henrynestler.com/colinux/testing/devel-0.8.0/20091105-Snapshot/packages/
* Unpack all the files into new directory, for example to
c:\coLinux-2.6.25
* Copy your colinux config file or your BAT file from old installation
into the new directory. Edit the new config- or bat- file and add the full
path for your image files (cobd, scsi or hda). - If you not have used full
path names before.
* Remove or comment out the "initrd=initrd.gz" from config, and save the
config.
* Stop all running colinux
* Open command prompt on old installation directory
* Remove the driver
  colinux-daemon --remove-driver
* Check, that the driver is truely removed:
  colinux-daemon --status-driver
* Reboot your windows now!
* Open command prompt on the new directory and perform the manual
install:
  colinux-daemon --install-driver
* Reboot your Windows now!
  (This step is need, if the start would crash at next step.)
* Run your new colinux versioon from new directory.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=622063&aid=2893343&group_id=98788