From: cesar t. <ces...@ya...> - 2006-03-26 12:53:36
|
Hi! I have just installed colinux 0.6.3. Installing as a service and running it gives me that awkful Blue Screen with the message in the subject. I tried modifying the file c:\boot.ini, like this: /NoExecute=AlwaysOff /NOPAE [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS /NoExecute=AlwaysOff /NOPAE [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect C:\CMDCONS\BOOTSECT.DAT="Consola de recuperaci¢n de Microsoft Windows XP" /cmdcons /NoExecute=AlwaysOff /NOPAE And doesn´t work either. On the BSOD I can find the following: STOP: 0X000000D1 (0XB96A101C,0X000000FF,0X00000008,0XB96A101C) My computer is a windowsXP Home Edition, SP2. (A new packard Bell iMedia P4@3.6GHz with 1Gb Ram) The error is when I try to start the service via services window or with net start ... Any hint? bye... ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com |
From: Sunil <fu...@ya...> - 2006-03-26 18:14:14
|
first line which boots has '/noexecute=optin /fastdetect' there is no effect of other /noexecute=alwaysoff and /nopae Put those things at the end of first OS to boot, like: --------------------------------------- [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=optin /fastdetect <rest of the boot.ini here> -------------------------------- cesar tejeda <ces...@ya...> wrote: Hi! I have just installed colinux 0.6.3. Installing as a service and running it gives me that awkful Blue Screen with the message in the subject. I tried modifying the file c:\boot.ini, like this: /NoExecute=AlwaysOff /NOPAE [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS /NoExecute=AlwaysOff /NOPAE [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect C:\CMDCONS\BOOTSECT.DAT="Consola de recuperaci¢n de Microsoft Windows XP" /cmdcons /NoExecute=AlwaysOff /NOPAE And doesn´t work either. On the BSOD I can find the following: STOP: 0X000000D1 (0XB96A101C,0X000000FF,0X00000008,0XB96A101C) My computer is a windowsXP Home Edition, SP2. (A new packard Bell iMedia P4@3.6GHz with 1Gb Ram) The error is when I try to start the service via services window or with net start ... Any hint? bye... ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big. |
From: Sunil <fu...@ya...> - 2006-03-26 19:02:52
|
somehow message editing in Yahoo screwed up. I meant: --------------------------------------- [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=alwaysoff /nopae <rest of the boot.ini here> -------------------------------- Sunil <fu...@ya...> wrote: first line which boots has '/noexecute=optin /fastdetect' there is no effect of other /noexecute=alwaysoff and /nopae Put those things at the end of first OS to boot, like: --------------------------------------- [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /fastdetect /noexecute=optin /fastdetect <rest of the boot.ini here> -------------------------------- cesar tejeda <ces...@ya...> wrote: Hi! I have just installed colinux 0.6.3. Installing as a service and running it gives me that awkful Blue Screen with the message in the subject. I tried modifying the file c:\boot.ini, like this: /NoExecute=AlwaysOff /NOPAE [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS /NoExecute=AlwaysOff /NOPAE [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect C:\CMDCONS\BOOTSECT.DAT="Consola de recuperaci¢n de Microsoft Windows XP" /cmdcons /NoExecute=AlwaysOff /NOPAE And doesn´t work either. On the BSOD I can find the following: STOP: 0X000000D1 (0XB96A101C,0X000000FF,0X00000008,0XB96A101C) My computer is a windowsXP Home Edition, SP2. (A new packard Bell iMedia P4@3.6GHz with 1Gb Ram) The error is when I try to start the service via services window or with net start ... Any hint? bye... ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ coLinux-users mailing list coL...@li... https://lists.sourceforge.net/lists/listinfo/colinux-users --------------------------------- New Yahoo! Messenger with Voice. Call regular phones from your PC and save big. --------------------------------- Yahoo! Messenger with Voice. Make PC-to-Phone Calls to the US (and 30+ countries) for 2¢/min or less. |
From: Henry N. <Henry.Ne@Arcor.de> - 2006-03-27 09:16:54
|
Hello, for new PC with Hardware support for noexecute bit (disable-NX) works=20 only under XP SP2 with /noexecute=3Dalwaysoff. Problem is inside design=20 of colinux driver, and currently no other workarrounts available. This=20 you need for versions 0.6.2, 0.6.3 and 0.7.1. /noexecute=3Doptin don't work. /nopae and /pae has no effect. You can let /pae enabled. Mostly devolopers have not such PC. Currently we can't solve it. Sorry. This are contains of your new boot.ini, the second menue line have=20 copied from your first and changed into "noexecute=3Dalwaysoff". colinux=20 should run with second menue: [boot loader] timeout=3D30 default=3Dmulti(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=3D"Microsoft Windows XP Home=20 Edition" /noexecute=3Doptin /fastdetect multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=3D"Microsoft Windows XP Home=20 Edition" /NoExecute=3DAlwaysOff /fastdetect C:\CMDCONS\BOOTSECT.DAT=3D"Consola de recuperaci=A2n de Microsoft Windows= =20 XP" /cmdcons /NoExecute=3DAlwaysOff /NOPAE PS: Many thanks, that you noted the hex code of blue sceen! --=20 Henry Nestler Sunil wrote: > somehow message editing in Yahoo screwed up. I meant: > --------------------------------------- > [operating systems] > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=3D"Microsoft > Windows XP Home Edition" /fastdetect /noexecute=3Dalwaysoff /nopae > <rest of the boot.ini here> >=20 > -------------------------------- >=20 > */Sunil <fu...@ya...>/* wrote: >=20 > first line which boots has '/noexecute=3Doptin /fastdetect' >=20 > there is no effect of other /noexecute=3Dalwaysoff and /nopae >=20 > Put those things at the end of first OS to boot, like: >=20 > --------------------------------------- > [operating systems] > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=3D"Microsoft > Windows XP Home Edition" /fastdetect /noexecute=3Doptin /fastdetec= t > <rest of the boot.ini here> >=20 > -------------------------------- >=20 > */cesar tejeda <ces...@ya...>/* wrote: >=20 > Hi! I have just installed colinux 0.6.3. >=20 > Installing as a service and running it gives me that > awkful Blue Screen with the message in the subject. >=20 > I tried modifying the file c:\boot.ini, like this: >=20 > /NoExecute=3DAlwaysOff /NOPAE > [boot loader] > timeout=3D0 > default=3Dmulti(0)disk(0)rdisk(0)partition(2)\WINDOWS > /NoExecute=3DAlwaysOff /NOPAE > [operating systems] > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=3D"Microsoft > Windows XP Home Edition" /noexecute=3Doptin /fastdetect > C:\CMDCONS\BOOTSECT.DAT=3D"Consola de recuperaci=A2n de > Microsoft Windows XP" /cmdcons > /NoExecute=3DAlwaysOff /NOPAE >=20 > And doesn=B4t work either. > On the BSOD I can find the following: >=20 > STOP: 0X000000D1 > (0XB96A101C,0X000000FF,0X00000008,0XB96A101C) >=20 > My computer is a windowsXP Home Edition, SP2. > (A new packard Bell iMedia P4@3.6GHz with 1Gb Ram) >=20 > The error is when I try to start the service via > services window or with net start ... >=20 > Any hint? >=20 > bye... >=20 |
From: cesar t. <ces...@ya...> - 2006-04-03 07:42:39
|
Thank you very much. The new boot.ini solved the problem. Thank you for colinux too. It is a wanderful software. Cesar. --- Henry Nestler <Henry.Ne@Arcor.de> escribió: > Hello, > > for new PC with Hardware support for noexecute bit > (disable-NX) works > only under XP SP2 with /noexecute=alwaysoff. > Problem is inside design > of colinux driver, and currently no other > workarrounts available. This > you need for versions 0.6.2, 0.6.3 and 0.7.1. > > /noexecute=optin don't work. > > /nopae and /pae has no effect. You can let /pae > enabled. > > Mostly devolopers have not such PC. Currently we > can't solve it. Sorry. > > > This are contains of your new boot.ini, the second > menue line have > copied from your first and changed into > "noexecute=alwaysoff". colinux > should run with second menue: > > [boot loader] > timeout=30 > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS > [operating systems] > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft > Windows XP Home > Edition" /noexecute=optin /fastdetect > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft > Windows XP Home > Edition" /NoExecute=AlwaysOff /fastdetect > C:\CMDCONS\BOOTSECT.DAT="Consola de recuperaci¢n de > Microsoft Windows > XP" /cmdcons /NoExecute=AlwaysOff /NOPAE > > > PS: Many thanks, that you noted the hex code of blue > sceen! > > -- > Henry Nestler > > Sunil wrote: > > somehow message editing in Yahoo screwed up. I > meant: > > --------------------------------------- > > [operating systems] > > > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft > > Windows XP Home Edition" /fastdetect > /noexecute=alwaysoff /nopae > > <rest of the boot.ini here> > > > > -------------------------------- > > > > */Sunil <fu...@ya...>/* wrote: > > > > first line which boots has '/noexecute=optin > /fastdetect' > > > > there is no effect of other > /noexecute=alwaysoff and /nopae > > > > Put those things at the end of first OS to > boot, like: > > > > --------------------------------------- > > [operating systems] > > > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft > > Windows XP Home Edition" /fastdetect > /noexecute=optin /fastdetect > > <rest of the boot.ini here> > > > > -------------------------------- > > > > */cesar tejeda <ces...@ya...>/* > wrote: > > > > Hi! I have just installed colinux 0.6.3. > > > > Installing as a service and running it > gives me that > > awkful Blue Screen with the message in the > subject. > > > > I tried modifying the file c:\boot.ini, > like this: > > > > /NoExecute=AlwaysOff /NOPAE > > [boot loader] > > timeout=0 > > > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS > > /NoExecute=AlwaysOff /NOPAE > > [operating systems] > > > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft > > Windows XP Home Edition" /noexecute=optin > /fastdetect > > C:\CMDCONS\BOOTSECT.DAT="Consola de > recuperaci¢n de > > Microsoft Windows XP" /cmdcons > > /NoExecute=AlwaysOff /NOPAE > > > > And doesn´t work either. > > On the BSOD I can find the following: > > > > STOP: 0X000000D1 > > > (0XB96A101C,0X000000FF,0X00000008,0XB96A101C) > > > > My computer is a windowsXP Home Edition, > SP2. > > (A new packard Bell iMedia P4@3.6GHz with > 1Gb Ram) > > > > The error is when I try to start the > service via > > services window or with net start ... > > > > Any hint? > > > > bye... > > > > ______________________________________________ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com |
From: <ra...@ab...> - 2006-03-26 20:43:25
|
cesar tejeda skrev: > Hi! I have just installed colinux 0.6.3. > > Installing as a service and running it gives me that > awkful Blue Screen with the message in the subject. > > I tried modifying the file c:\boot.ini, like this: > > /NoExecute=AlwaysOff /NOPAE > [boot loader] > timeout=0 > default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS > /NoExecute=AlwaysOff /NOPAE > [operating systems] > multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft > Windows XP Home Edition" /noexecute=optin /fastdetect > C:\CMDCONS\BOOTSECT.DAT="Consola de recuperaci¢n de > Microsoft Windows XP" /cmdcons > /NoExecute=AlwaysOff /NOPAE > > And doesn´t work either. > On the BSOD I can find the following: > > STOP: 0X000000D1 > (0XB96A101C,0X000000FF,0X00000008,0XB96A101C) > > My computer is a windowsXP Home Edition, SP2. > (A new packard Bell iMedia P4@3.6GHz with 1Gb Ram) > > The error is when I try to start the service via > services window or with net start ... > > Any hint? Does the same CoLinux run as non-service? My gear hangs hard if I give CoLinux 128 MB of memory. Less or more works fine. DEP works fine. /R |
From: George P B. <geo...@gm...> - 2006-03-28 15:45:24
|
On 3/26/06, ra...@ab... <ra...@ab...> wrote: > > Does the same CoLinux run as non-service? My gear hangs hard if I give > CoLinux 128 MB of memory. Less or more works fine. DEP works fine. > That's odd... What version of coLinux is it that you are having problem withe 128MB of RAM? How much Physical RAM do you have and how much is in use? -- George |
From: <ra...@ab...> - 2006-03-28 20:57:27
|
George P Boutwell skrev: > On 3/26/06, ra...@ab... <ra...@ab...> wrote: > >>Does the same CoLinux run as non-service? My gear hangs hard if I give >>CoLinux 128 MB of memory. Less or more works fine. DEP works fine. >> > > > That's odd... What version of coLinux is it that you are having > problem withe 128MB of RAM? How much Physical RAM do you have and how > much is in use? > > -- > George CoLinux is 0.6.3. I have 1.5 GB RAM with some 1.1 GB free after booting, with no applications (nor CoLinux) running. CPU is Celeron M 758 (1,5 GHz) and most other chips are also intel. I just tried again, a little further: 128 MB hangs everytime, whether started as a service or as a normal process. The last line I see is the "RAMDISK: Compressed image found at block 0". Then everything just freezes. I have to force power-off. 127 and 129 MB works fine! So does all others I've tried: 64, 256 and 512 MB. I think I once ran it with 1 GB without any problems. I normally run it with 256 MB. I now also tried /NoExecute=AlwaysOff with 128 MB and it still hangs. I normally go with /NoExecute=OptOut. /Rasmus |
From: George P B. <geo...@gm...> - 2006-03-28 21:32:47
|
On 3/28/06, ra...@ab... <ra...@ab...> wrote: > CoLinux is 0.6.3. I have 1.5 GB RAM with some 1.1 GB free after booting, > with no applications (nor CoLinux) running. CPU is Celeron M 758 (1,5 > GHz) and most other chips are also intel. > > I just tried again, a little further: > 128 MB hangs everytime, whether started as a service or as a normal > process. The last line I see is the "RAMDISK: Compressed image found at > block 0". Then everything just freezes. I have to force power-off. > > 127 and 129 MB works fine! So does all others I've tried: 64, 256 and > 512 MB. I think I once ran it with 1 GB without any problems. I normally > run it with 256 MB. > > I now also tried /NoExecute=3DAlwaysOff with 128 MB and it still hangs. I > normally go with /NoExecute=3DOptOut. > Can you try without the initrd.gz file... It's not actually need for colinux to run normally. -- George |
From: George P B. <geo...@gm...> - 2006-03-30 19:17:06
|
On 3/29/06, ra...@ab... wrote: > > Can you try without the initrd.gz file... It's not actually need for > > colinux to run normally. > > Yeah that did it! Strange. How did you know? :-) I'm a colinux developer... It's a common problem that we have been looking into and trying to come up with a good solution for. I think we have one, but it'll be part of the next 0.6.x bugfix release. In the mean-time boot the first time with the intrd.gz (so that it can automagically install the necessary linux kernel modules on your image), then after that you can disable it. -- George |