Menu
▾
▴
colinux-users — coLinux users mailing list
You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(100) |
Jun
(134) |
Jul
(149) |
Aug
(123) |
Sep
(185) |
Oct
(122) |
Nov
(59) |
Dec
(127) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(128) |
Feb
(233) |
Mar
(210) |
Apr
(196) |
May
(85) |
Jun
(96) |
Jul
(76) |
Aug
(149) |
Sep
(65) |
Oct
(78) |
Nov
(121) |
Dec
(82) |
| 2006 |
Jan
(249) |
Feb
(181) |
Mar
(176) |
Apr
(156) |
May
(128) |
Jun
(102) |
Jul
(157) |
Aug
(80) |
Sep
(42) |
Oct
(49) |
Nov
(36) |
Dec
(42) |
| 2007 |
Jan
(64) |
Feb
(38) |
Mar
(45) |
Apr
(74) |
May
(26) |
Jun
(20) |
Jul
(17) |
Aug
(12) |
Sep
(40) |
Oct
(7) |
Nov
(14) |
Dec
(16) |
| 2008 |
Jan
(52) |
Feb
(49) |
Mar
(90) |
Apr
(80) |
May
(78) |
Jun
(82) |
Jul
(25) |
Aug
(8) |
Sep
(10) |
Oct
(11) |
Nov
(3) |
Dec
(17) |
| 2009 |
Jan
(12) |
Feb
(16) |
Mar
(20) |
Apr
(14) |
May
(17) |
Jun
(10) |
Jul
(13) |
Aug
(12) |
Sep
(21) |
Oct
(10) |
Nov
(30) |
Dec
(1) |
| 2010 |
Jan
(2) |
Feb
(7) |
Mar
(22) |
Apr
(6) |
May
(33) |
Jun
(5) |
Jul
(4) |
Aug
(38) |
Sep
(46) |
Oct
(23) |
Nov
(9) |
Dec
(5) |
| 2011 |
Jan
(21) |
Feb
(27) |
Mar
(1) |
Apr
(18) |
May
(12) |
Jun
(12) |
Jul
(10) |
Aug
(30) |
Sep
(4) |
Oct
|
Nov
(9) |
Dec
(19) |
| 2012 |
Jan
(26) |
Feb
(6) |
Mar
(8) |
Apr
(7) |
May
(3) |
Jun
|
Jul
(10) |
Aug
(1) |
Sep
(18) |
Oct
(5) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(27) |
Feb
|
Mar
(11) |
Apr
(14) |
May
|
Jun
(1) |
Jul
|
Aug
(7) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(25) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
(2) |
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bob W. <bwh...@my...> - 2012-01-22 20:44:38
|
>Henry N. Wrote on 1/7/12: >What you can do is to check that the ndis-driver is >truly the problem. >If you installs WinPcap and changes the coLinux config >from ndis-bridge into pcap-bridge. Disappears this the >problem? I have tried WinPCap and Slirp, both crash with memory corruption. >An other candidate for memory leakages is the option >"setcobd=async". It also crashes without this? Yes it crashes. >Can you give a command example for console to force >this bug on other distributions? For example running >"netio" under Debian 6.0 Squeeze It tried netio under Debian and it only runs for 4 or 5 minutes and does not use much additional memory. Since the crash occurs at memory utilization above 95% and this only got to 80% there was no crash. Can you suggest another console program that can be run continuously to use up enough memory to get above 95%. >I see, that you have only 384 MB for the virtual >machine. Comes the crash faster, if you use less memory >(for example 256)? Maybe it is a generally problem with >memory. I tried 256 and it crashed in about the same amount of time. The results of all these tests were reported in the bug tracker as comments. These things that you have asked me to try seem like a waste of time so far. It would be better if somebody that understands colinux well looked at the patterns in memory where the corruption is detected to see if they recognize anything related to what colinux is doing. Regards, Bob W. |
|
From: Henry N. <hen...@ar...> - 2012-01-17 20:53:40
|
At 17.01.2012 12:41, mattias wrote: > now i have built my own colinux kernel > but after i have do > make modules > must i create a initrd.gz? > and if so > how? No. Mostly you don't need to create an initrd, unless you would use special file systems or boot devices. Simple run "sudo make modules_install" to have the modules in running system. I suggest you to change the CONFIG_LOCALVERSION to have no problems with any older installations of same kernel. -- Henry N. |
|
From: mattias <mj...@mj...> - 2012-01-17 11:41:36
|
now i have built my own colinux kernel but after i have do make modules must i create a initrd.gz? and if so how? |
|
From: Henry N. <hen...@ar...> - 2012-01-16 19:50:52
|
At 16.01.2012 17:51, mattias wrote: > anyone using physical partitions with lvm on colinux > if so > i try it and it try to mount but fail > no root fs to mount > what should i enter as root partion? > /dev/cobd0? > i have created cobd devices on the physical linux > but no luck Please ask Google "lvm under colinux" http://colinux.wikia.com/wiki/CoLinuxNativeRAID#LVM_Specific -- Henry N. |
|
From: mattias <mj...@mj...> - 2012-01-16 16:51:34
|
anyone using physical partitions with lvm on colinux if so i try it and it try to mount but fail no root fs to mount what should i enter as root partion? /dev/cobd0? i have created cobd devices on the physical linux but no luck |
|
From: Johann P. <joh...@gm...> - 2012-01-10 08:40:19
|
Letze Mail ging leider an die Falsche Adresse. Bitte löschen wenn das möglch ist. Johann Pascher 2012/1/10 Johann Pascher <joh...@gm...>: > Hallo Martin, > > sehr schön, dass du dich meldest. > > Das ist halt so, dass sich keiner meldet ich bin da keine Ausnahme. > Ich hab wohl hin und wieder mal and dich gedacht aber zu einer Mail > hat es ohne egoistischen Grund auch nicht gereicht. > Bei mir ist es halt so dass ich auch nicht unnötig blöd irgendwas > schreiben will. > Bei anderen wird es ähnlich sein, man müsste die einzelne Personen > selber ansprechen. > Jeder ist zu sehr im System eingespannt, und wir passen da halt mit > Krankheit oder Ruhestand nicht wirklich mehr hinein. > > Ich müsste mal bei dir wieder vorbeischauen dann könnte man darüber > sicher einiges ausführlicher besprechen. > Komischerweise bin auch ich wieder ziemlich eingespannt, zumindest aus > meiner Sicht, auch wenn mir direkt keiner was anschafft. > Ich unterbreche hier mal ... mein Anliegen kommt später das rennt nicht davon. > > Mal sehen was Heute anliegt, hab erst gefrühstückt. > > bis später Hannes > > > 2012/1/9 <col...@li...>: >> Send coLinux-users mailing list submissions to >> col...@li... >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> or, via email, send a message with subject or body 'help' to >> col...@li... >> >> You can reach the person managing the list at >> col...@li... >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of coLinux-users digest..." >> >> >> Today's Topics: >> >> 1. Re: Colinux Blue Screen Crashes (Bob Wheater) >> 2. Re: Colinux Blue Screen Crashes (Miller, Shao) >> 3. Re: Colinux Blue Screen Crashes (Bob Wheater) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 9 Jan 2012 15:04:08 -0500 >> From: "Bob Wheater" <bwh...@my...> >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> To: <col...@li...> >> Message-ID: <003401cccf09$d9d87a40$8d896ec0$@net> >> Content-Type: text/plain; charset="iso-8859-1" >> >>> Vincent Rivi?re wrote: >> >>>My complete boot.ini line is: >> >>>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP >> Professionnel" /fastdetect >/noexecute=alwaysoff /nopae >> >> >> >>>To check if PAE is actually on or off, look at the >system properties >> (Win+Pause), on the General tab (the >default one). Look at the bottom, >> after the line with >frequency and amount of RAM. If "Physical Address >>>Extension" >> >>>is written, then PAE is on. If there is no such text, >PAE is off. >> >> >> >>>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check >> it is actually disabled and see if >coLinux works better. >> >> >> >> My general tab on the system properties does NOT have ?Physical Address >> Extension?. >> >> >> >> You seem to be confusing PAE with DEP (Data Execution Prevention). See >> http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx >> >> The /noexecute switch controls DEP. >> >> >> >> However DEP may only apply to windows server 2003 and not XP. >> >> >> >> ? The PAE mode kernel requires an Intel Architecture processor, Pentium Pro >> or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows >> Server 2003.? >> >> From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 >> >> According to this PAE does NOT apply to a 1gb system. It only applies to 4gb >> and greater systems. >> >> >> >> Regards, >> >> Bob >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 2 >> Date: Mon, 9 Jan 2012 15:13:55 -0500 >> From: "Miller, Shao" <sha...@yr...> >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> To: "Bob Wheater" <bwh...@my...> >> Cc: col...@li... >> Message-ID: >> <F0E...@YR...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Did you get my last message regarding possibly useful info you could share? If not, I'd appreciate it if you could review it. >> >> >> >> There are several kernels: >> >> * Uniprocessor, no-PAE (the default ntoskrnl.exe) >> * Uniprocessor, PAE (ntkrnlpa.exe) >> * Multiprocessor, no-PAE (ntkrnlmp.exe) >> * Multiprocessor, PAE (ntkrpamp.exe) >> >> >> >> Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), highlight the System process, then choose View -> Lower Pane View -> DLLs and make sure that View -> Show Lower Pane has a check-mark. Then scroll through the list of DLLs and observe which one matches the pattern ntXXX.exe. >> >> >> >> You can be using a PAE kernel without knowing it and without the /PAE switch in BOOT.INI. >> >> >> >> - Shao Miller >> >> ________________________________ >> >> From: Bob Wheater [mailto:bwh...@my...] >> Sent: Monday, January 09, 2012 15:04 >> To: col...@li... >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> >> >> >>> Vincent Rivi?re wrote: >> >>>My complete boot.ini line is: >> >>>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP Professionnel" /fastdetect >/noexecute=alwaysoff /nopae >> >> >> >>>To check if PAE is actually on or off, look at the >system properties (Win+Pause), on the General tab (the >default one). Look at the bottom, after the line with >frequency and amount of RAM. If "Physical Address >Extension" >> >>>is written, then PAE is on. If there is no such text, >PAE is off. >> >> >> >>>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check it is actually disabled and see if >coLinux works better. >> >> >> >> My general tab on the system properties does NOT have "Physical Address Extension". >> >> >> >> You seem to be confusing PAE with DEP (Data Execution Prevention). See http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx >> >> The /noexecute switch controls DEP. >> >> >> >> However DEP may only apply to windows server 2003 and not XP. >> >> >> >> " The PAE mode kernel requires an Intel Architecture processor, Pentium Pro or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows Server 2003." >> >> From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 >> >> According to this PAE does NOT apply to a 1gb system. It only applies to 4gb and greater systems. >> >> >> >> Regards, >> >> Bob >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 3 >> Date: Mon, 9 Jan 2012 16:11:22 -0500 >> From: "Bob Wheater" <bwh...@my...> >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> To: <col...@li...> >> Message-ID: <004201cccf13$3e4661f0$bad325d0$@net> >> Content-Type: text/plain; charset="us-ascii" >> >> Its using the default uniprocess kernel (nopae): >> >> ntoskrnl.exe NT Kernel & System Microsoft Corporation >> 5.1.2600.6165 >> >> according to process explorer. >> >> >> >> What last message? I though everything was posted to the list. I checked my >> files and the only message from you concerns posting the top part of windbg >> output which I did post when I reported the problem to the bug tracker. >> >> -Bob >> >> >> >> From: Miller, Shao [mailto:sha...@yr...] >> Sent: Monday, January 09, 2012 3:14 PM >> To: Bob Wheater >> Cc: col...@li... >> Subject: RE: [coLinux-users] Colinux Blue Screen Crashes >> >> >> >> Did you get my last message regarding possibly useful info you could share? >> If not, I'd appreciate it if you could review it. >> >> >> >> There are several kernels: >> >> * Uniprocessor, no-PAE (the default ntoskrnl.exe) >> * Uniprocessor, PAE (ntkrnlpa.exe) >> * Multiprocessor, no-PAE (ntkrnlmp.exe) >> * Multiprocessor, PAE (ntkrpamp.exe) >> >> >> >> Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), >> highlight the System process, then choose View -> Lower Pane View -> DLLs >> and make sure that View -> Show Lower Pane has a check-mark. Then scroll >> through the list of DLLs and observe which one matches the pattern >> ntXXX.exe. >> >> >> >> You can be using a PAE kernel without knowing it and without the /PAE switch >> in BOOT.INI. >> >> >> >> - Shao Miller >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> ------------------------------------------------------------------------------ >> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >> infrastructure or vast IT resources to deliver seamless, secure access to >> virtual desktops. With this all-in-one solution, easily deploy virtual >> desktops for less than the cost of PCs and save 60% on VDI infrastructure >> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >> >> ------------------------------ >> >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> >> End of coLinux-users Digest, Vol 68, Issue 7 >> ******************************************** |
|
From: Johann P. <joh...@gm...> - 2012-01-10 08:34:25
|
Hallo Martin, sehr schön, dass du dich meldest. Das ist halt so, dass sich keiner meldet ich bin da keine Ausnahme. Ich hab wohl hin und wieder mal and dich gedacht aber zu einer Mail hat es ohne egoistischen Grund auch nicht gereicht. Bei mir ist es halt so dass ich auch nicht unnötig blöd irgendwas schreiben will. Bei anderen wird es ähnlich sein, man müsste die einzelne Personen selber ansprechen. Jeder ist zu sehr im System eingespannt, und wir passen da halt mit Krankheit oder Ruhestand nicht wirklich mehr hinein. Ich müsste mal bei dir wieder vorbeischauen dann könnte man darüber sicher einiges ausführlicher besprechen. Komischerweise bin auch ich wieder ziemlich eingespannt, zumindest aus meiner Sicht, auch wenn mir direkt keiner was anschafft. Ich unterbreche hier mal ... mein Anliegen kommt später das rennt nicht davon. Mal sehen was Heute anliegt, hab erst gefrühstückt. bis später Hannes 2012/1/9 <col...@li...>: > Send coLinux-users mailing list submissions to > col...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/colinux-users > or, via email, send a message with subject or body 'help' to > col...@li... > > You can reach the person managing the list at > col...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of coLinux-users digest..." > > > Today's Topics: > > 1. Re: Colinux Blue Screen Crashes (Bob Wheater) > 2. Re: Colinux Blue Screen Crashes (Miller, Shao) > 3. Re: Colinux Blue Screen Crashes (Bob Wheater) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 9 Jan 2012 15:04:08 -0500 > From: "Bob Wheater" <bwh...@my...> > Subject: Re: [coLinux-users] Colinux Blue Screen Crashes > To: <col...@li...> > Message-ID: <003401cccf09$d9d87a40$8d896ec0$@net> > Content-Type: text/plain; charset="iso-8859-1" > >> Vincent Rivi?re wrote: > >>My complete boot.ini line is: > >>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP > Professionnel" /fastdetect >/noexecute=alwaysoff /nopae > > > >>To check if PAE is actually on or off, look at the >system properties > (Win+Pause), on the General tab (the >default one). Look at the bottom, > after the line with >frequency and amount of RAM. If "Physical Address >>Extension" > >>is written, then PAE is on. If there is no such text, >PAE is off. > > > >>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check > it is actually disabled and see if >coLinux works better. > > > > My general tab on the system properties does NOT have ?Physical Address > Extension?. > > > > You seem to be confusing PAE with DEP (Data Execution Prevention). See > http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx > > The /noexecute switch controls DEP. > > > > However DEP may only apply to windows server 2003 and not XP. > > > > ? The PAE mode kernel requires an Intel Architecture processor, Pentium Pro > or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows > Server 2003.? > > From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 > > According to this PAE does NOT apply to a 1gb system. It only applies to 4gb > and greater systems. > > > > Regards, > > Bob > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 2 > Date: Mon, 9 Jan 2012 15:13:55 -0500 > From: "Miller, Shao" <sha...@yr...> > Subject: Re: [coLinux-users] Colinux Blue Screen Crashes > To: "Bob Wheater" <bwh...@my...> > Cc: col...@li... > Message-ID: > <F0E...@YR...> > Content-Type: text/plain; charset="iso-8859-1" > > Did you get my last message regarding possibly useful info you could share? If not, I'd appreciate it if you could review it. > > > > There are several kernels: > > * Uniprocessor, no-PAE (the default ntoskrnl.exe) > * Uniprocessor, PAE (ntkrnlpa.exe) > * Multiprocessor, no-PAE (ntkrnlmp.exe) > * Multiprocessor, PAE (ntkrpamp.exe) > > > > Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), highlight the System process, then choose View -> Lower Pane View -> DLLs and make sure that View -> Show Lower Pane has a check-mark. Then scroll through the list of DLLs and observe which one matches the pattern ntXXX.exe. > > > > You can be using a PAE kernel without knowing it and without the /PAE switch in BOOT.INI. > > > > - Shao Miller > > ________________________________ > > From: Bob Wheater [mailto:bwh...@my...] > Sent: Monday, January 09, 2012 15:04 > To: col...@li... > Subject: Re: [coLinux-users] Colinux Blue Screen Crashes > > > >> Vincent Rivi?re wrote: > >>My complete boot.ini line is: > >>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP Professionnel" /fastdetect >/noexecute=alwaysoff /nopae > > > >>To check if PAE is actually on or off, look at the >system properties (Win+Pause), on the General tab (the >default one). Look at the bottom, after the line with >frequency and amount of RAM. If "Physical Address >Extension" > >>is written, then PAE is on. If there is no such text, >PAE is off. > > > >>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check it is actually disabled and see if >coLinux works better. > > > > My general tab on the system properties does NOT have "Physical Address Extension". > > > > You seem to be confusing PAE with DEP (Data Execution Prevention). See http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx > > The /noexecute switch controls DEP. > > > > However DEP may only apply to windows server 2003 and not XP. > > > > " The PAE mode kernel requires an Intel Architecture processor, Pentium Pro or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows Server 2003." > > From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 > > According to this PAE does NOT apply to a 1gb system. It only applies to 4gb and greater systems. > > > > Regards, > > Bob > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > Message: 3 > Date: Mon, 9 Jan 2012 16:11:22 -0500 > From: "Bob Wheater" <bwh...@my...> > Subject: Re: [coLinux-users] Colinux Blue Screen Crashes > To: <col...@li...> > Message-ID: <004201cccf13$3e4661f0$bad325d0$@net> > Content-Type: text/plain; charset="us-ascii" > > Its using the default uniprocess kernel (nopae): > > ntoskrnl.exe NT Kernel & System Microsoft Corporation > 5.1.2600.6165 > > according to process explorer. > > > > What last message? I though everything was posted to the list. I checked my > files and the only message from you concerns posting the top part of windbg > output which I did post when I reported the problem to the bug tracker. > > -Bob > > > > From: Miller, Shao [mailto:sha...@yr...] > Sent: Monday, January 09, 2012 3:14 PM > To: Bob Wheater > Cc: col...@li... > Subject: RE: [coLinux-users] Colinux Blue Screen Crashes > > > > Did you get my last message regarding possibly useful info you could share? > If not, I'd appreciate it if you could review it. > > > > There are several kernels: > > * Uniprocessor, no-PAE (the default ntoskrnl.exe) > * Uniprocessor, PAE (ntkrnlpa.exe) > * Multiprocessor, no-PAE (ntkrnlmp.exe) > * Multiprocessor, PAE (ntkrpamp.exe) > > > > Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), > highlight the System process, then choose View -> Lower Pane View -> DLLs > and make sure that View -> Show Lower Pane has a check-mark. Then scroll > through the list of DLLs and observe which one matches the pattern > ntXXX.exe. > > > > You can be using a PAE kernel without knowing it and without the /PAE switch > in BOOT.INI. > > > > - Shao Miller > > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > > ------------------------------ > > _______________________________________________ > coLinux-users mailing list > coL...@li... > https://lists.sourceforge.net/lists/listinfo/colinux-users > > > End of coLinux-users Digest, Vol 68, Issue 7 > ******************************************** |
|
From: Vincent R. <vin...@fr...> - 2012-01-09 21:31:52
|
Bob Wheater wrote: > You seem to be confusing PAE with DEP (Data Execution Prevention). From the page you quoted: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 "The PAE kernel can be enabled automatically without the /PAE switch present in the boot entry if the system has DEP enabled (/NOEXECUTE switch is present) or the system processor supports hardware-enforced DEP. Presence of the /NOEXECUTE switch on a system with a processor that supports hardware-enforced DEP implies the /PAE switch. If the system processor is capable of hardware-enforced DEP and the /NOEXECUTE switch is not present in the boot entry, Windows assumes /NOEXECUTE=optin by default and enables PAE mode." > According to this PAE does NOT apply to a 1gb system. It only applies to 4gb > and greater systems. On my unhacked Windows XP SP3 virtual machine with 128 MB of RAM, PAE is enabled by default. Since Windows XP SP2, PAE is enabled by default on processors supporting hardware DEP. -- Vincent Rivière |
|
From: Bob W. <bwh...@my...> - 2012-01-09 21:11:35
|
Its using the default uniprocess kernel (nopae): ntoskrnl.exe NT Kernel & System Microsoft Corporation 5.1.2600.6165 according to process explorer. What last message? I though everything was posted to the list. I checked my files and the only message from you concerns posting the top part of windbg output which I did post when I reported the problem to the bug tracker. -Bob From: Miller, Shao [mailto:sha...@yr...] Sent: Monday, January 09, 2012 3:14 PM To: Bob Wheater Cc: col...@li... Subject: RE: [coLinux-users] Colinux Blue Screen Crashes Did you get my last message regarding possibly useful info you could share? If not, I'd appreciate it if you could review it. There are several kernels: * Uniprocessor, no-PAE (the default ntoskrnl.exe) * Uniprocessor, PAE (ntkrnlpa.exe) * Multiprocessor, no-PAE (ntkrnlmp.exe) * Multiprocessor, PAE (ntkrpamp.exe) Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), highlight the System process, then choose View -> Lower Pane View -> DLLs and make sure that View -> Show Lower Pane has a check-mark. Then scroll through the list of DLLs and observe which one matches the pattern ntXXX.exe. You can be using a PAE kernel without knowing it and without the /PAE switch in BOOT.INI. - Shao Miller |
|
From: Miller, S. <sha...@yr...> - 2012-01-09 20:15:38
|
Did you get my last message regarding possibly useful info you could share? If not, I'd appreciate it if you could review it. There are several kernels: * Uniprocessor, no-PAE (the default ntoskrnl.exe) * Uniprocessor, PAE (ntkrnlpa.exe) * Multiprocessor, no-PAE (ntkrnlmp.exe) * Multiprocessor, PAE (ntkrpamp.exe) Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), highlight the System process, then choose View -> Lower Pane View -> DLLs and make sure that View -> Show Lower Pane has a check-mark. Then scroll through the list of DLLs and observe which one matches the pattern ntXXX.exe. You can be using a PAE kernel without knowing it and without the /PAE switch in BOOT.INI. - Shao Miller ________________________________ From: Bob Wheater [mailto:bwh...@my...] Sent: Monday, January 09, 2012 15:04 To: col...@li... Subject: Re: [coLinux-users] Colinux Blue Screen Crashes > Vincent Rivière wrote: >My complete boot.ini line is: >multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP Professionnel" /fastdetect >/noexecute=alwaysoff /nopae >To check if PAE is actually on or off, look at the >system properties (Win+Pause), on the General tab (the >default one). Look at the bottom, after the line with >frequency and amount of RAM. If "Physical Address >Extension" >is written, then PAE is on. If there is no such text, >PAE is off. >So please change your boot.ini to /noexecute=alwaysoff >/nopae then check it is actually disabled and see if >coLinux works better. My general tab on the system properties does NOT have "Physical Address Extension". You seem to be confusing PAE with DEP (Data Execution Prevention). See http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx The /noexecute switch controls DEP. However DEP may only apply to windows server 2003 and not XP. " The PAE mode kernel requires an Intel Architecture processor, Pentium Pro or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows Server 2003." From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 According to this PAE does NOT apply to a 1gb system. It only applies to 4gb and greater systems. Regards, Bob |
|
From: Bob W. <bwh...@my...> - 2012-01-09 20:04:25
|
> Vincent Rivière wrote: >My complete boot.ini line is: >multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP Professionnel" /fastdetect >/noexecute=alwaysoff /nopae >To check if PAE is actually on or off, look at the >system properties (Win+Pause), on the General tab (the >default one). Look at the bottom, after the line with >frequency and amount of RAM. If "Physical Address >Extension" >is written, then PAE is on. If there is no such text, >PAE is off. >So please change your boot.ini to /noexecute=alwaysoff >/nopae then check it is actually disabled and see if >coLinux works better. My general tab on the system properties does NOT have Physical Address Extension. You seem to be confusing PAE with DEP (Data Execution Prevention). See http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx The /noexecute switch controls DEP. However DEP may only apply to windows server 2003 and not XP. The PAE mode kernel requires an Intel Architecture processor, Pentium Pro or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows Server 2003. From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 According to this PAE does NOT apply to a 1gb system. It only applies to 4gb and greater systems. Regards, Bob |
|
From: Vincent R. <vin...@fr...> - 2012-01-08 19:14:14
|
Bob Wheater wrote: > Added /nopae:” multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft > Windows XP Professional" /fastdetect /NoExecute=OptIn/NoPAE /bootlog” > > But, it did a blue screen crash again – so does not work for this case. PAE > applies to greater 4gb memory but my system is only 1gb. Sure, PAE is useful only for systems with more than 3 (or 4?) GB of RAM, but since Windows XP SP2 (?) it is enabled by default, whatever amount of RAM you have. Now I remember that /nopae also requires to disable DEP with the switch /noexecute=alwaysoff otherwise it is still enabled. Also (not sure if it is important) be sure to insert a space before /NoPAE in your boot.ini. My complete boot.ini line is: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professionnel" /fastdetect /noexecute=alwaysoff /nopae To check if PAE is actually on or off, look at the system properties (Win+Pause), on the General tab (the default one). Look at the bottom, after the line with frequency and amount of RAM. If "Physical Address Extension" is written, then PAE is on. If there is no such text, PAE is off. So please change your boot.ini to /noexecute=alwaysoff /nopae then check it is actually disabled and see if coLinux works better. -- Vincent Rivière |
|
From: Henry N. <hen...@ar...> - 2012-01-07 21:21:01
|
Hello Bob, Bob Wheater wrote: > Henry N. wrote: >> But this bug is very difficult to find, because the memory corruption >> was detected outside of coLinux. It would help more, if you would >> have a stack trace with module "linux" inside. >> >> Henry N. > > I checked my 15 crash dumps and none of them have “linux” in the STACK > TEXT section. Can you suggest what I can do to capture the stack > information that you need to help you solve this crash problem. The > problem is currently holding up the next release of Portable Ubuntu. > Thanks. > > Regards, > > Bob Wheater > No, you can nothing do with the dump or debugger. Assumed, coLinux ndis-driver will corrupt the memory of an other process, then very different task will see this, if they use the memory later. What you can do is to check that the ndis-driver is truly the problem. If you installs WinPcap and changes the coLinux config from ndis-bridge into pcap-bridge. Disappears this the problem? An other candidate for memory leakages is the option "setcobd=async". It also crashes without this? Can you give a command example for console to force this bug on other distributions? For example running "netio" under Debian 6.0 Squeeze I see, that you have only 384 MB for the virtual machine. Comes the crash faster, if you use less memory (for example 256)? Maybe it is a generally problem with memory. -- Henry N. |
|
From: Bob W. <bwh...@my...> - 2012-01-07 19:55:13
|
Hi Henry N.: >>> Bob Wheater wrote: >>> I have been having problems with blue screen crashes when running colinux. Vincent Rivière wrote: >>Vincent Rivière wrote: >> Adding /nopae in C:\boot.ini definitely solved the problem. Added /nopae: multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn/NoPAE /bootlog But, it did a blue screen crash again so does not work for this case. PAE applies to greater 4gb memory but my system is only 1gb. >But this bug is very difficult to find, because the >memory corruption was detected outside of coLinux. It >would help more, if you would have a stack trace with >module "linux" inside. >Henry N. I checked my 15 crash dumps and none of them have linux in the STACK TEXT section. Can you suggest what I can do to capture the stack information that you need to help you solve this crash problem. The problem is currently holding up the next release of Portable Ubuntu. Thanks. Regards, Bob Wheater |
|
From: baldyeti <e_...@ho...> - 2012-01-05 18:58:17
|
simply "mem=512" should do mattias wrote, On 2012-01-04 20:40: > if i will let my colinux vm have 512 ram > how should the line in my config look like > > |
|
From: Henry N. <hen...@ar...> - 2012-01-04 22:43:47
|
Vincent Rivière wrote: > Bob Wheater wrote: >> I have been having problems with blue screen crashes when running colinux. > I had similar trouble, especially when doing "aptitude upgrade", which is > both network and disk intensive. > > Adding /nopae in C:\boot.ini definitely solved the problem. > Hello Bob, you can fill out a bug report on SourceForge: http://sourceforge.net/tracker/?func=browse&group_id=98788&atid=622063 But this bug is very difficult to find, because the memory corruption was detected outside of coLinux. It would help more, if you would have a stack trace with module "linux" inside. -- Henry N. |
|
From: mattias <mj...@mj...> - 2012-01-04 20:41:21
|
if i will let my colinux vm have 512 ram how should the line in my config look like |
|
From: Vincent R. <vin...@fr...> - 2012-01-04 18:44:29
|
Bob Wheater wrote: > I have been having problems with blue screen crashes when running colinux. I had similar trouble, especially when doing "aptitude upgrade", which is both network and disk intensive. Adding /nopae in C:\boot.ini definitely solved the problem. -- Vincent Rivière |
|
From: Miller, S. <sha...@yr...> - 2012-01-04 03:39:25
|
I'm not a coLinux developer, but perhaps you could include the beginning of the WinDbg output that includes the Windows version and perhaps you could also list modules with lm. - Shao ________________________________ From: Bob Wheater [mailto:bwh...@my...] Sent: Tuesday, January 03, 2012 21:08 To: col...@li... Cc: bwh...@my... Subject: [coLinux-users] Colinux blue screen crashes Hi: I have been having problems with blue screen crashes when running colinux. They are usually memory corruptions, irql too high, corrupt page table list. The just started when I tried to get ndis bridge mode networking working on Portable Ubuntu which uses colinux. I never had any crashes when using the slirp mode networking. Also, I never have any crashes when colinux is not running. Many dumps had Kaspersky driver active at the time of crash. Kaspersky support has analyzed the dump and say that their driver Is not causing the problem. So to prove it, I uninstalled Kaspersky and used their clean up utility to removed all components, and registry items. It still crashed with memory corruption but this time the active module was nt . The windbg output of this dump is: kd> !analyze -v ************************************************************************ ******* * * * Bugcheck Analysis * * * ************************************************************************ ******* IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 9ded4804, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 804eb3b5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 9ded4804 CURRENT_IRQL: 2 FAULTING_IP: nt!MiDeletePte+15b 804eb3b5 8b420c mov eax,dword ptr [edx+0Ch] CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA TRAP_FRAME: f1c03aec -- (.trap fffffffff1c03aec) ErrCode = 00000000 eax=038202ff ebx=c000430c ecx=012b5655 edx=9ded47f8 esi=835d2fe8 edi=000fffff eip=804eb3b5 esp=f1c03b60 ebp=f1c03b84 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 nt!MiDeletePte+0x15b: 804eb3b5 8b420c mov eax,dword ptr [edx+0Ch] ds:0023:9ded4804=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 804eb3b5 to 804e1892 STACK_TEXT: f1c03aec 804eb3b5 badb0d00 9ded47f8 873c63e8 nt!KiTrap0E+0x233 f1c03b84 804eb6fe c000430c 010c3000 00000000 nt!MiDeletePte+0x15b f1c03c48 804f1d7c e122a614 010c9fff 00000000 nt!MiDeleteVirtualAddresses+0x162 f1c03cf4 8057a7c3 860fcb80 861acd00 f1c03d64 nt!MiRemoveMappedView+0x212 f1c03d38 8057a86f 85f21218 85eb8ee8 00000000 nt!MiUnmapViewOfSection+0x12b f1c03d54 804de7ec ffffffff 860fcb80 008beeec nt!NtUnmapViewOfSection+0x54 f1c03d54 7c90e514 ffffffff 860fcb80 008beeec nt!KiFastCallEntry+0xf8 WARNING: Frame IP not in any known module. Following frames may be wrong. 008beeec 00000000 00000000 00000000 00000000 0x7c90e514 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiDeletePte+15b 804eb3b5 8b420c mov eax,dword ptr [edx+0Ch] SYMBOL_STACK_INDEX: 1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ea6ba87 SYMBOL_NAME: nt!MiDeletePte+15b IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0xA_nt!MiDeletePte+15b BUCKET_ID: 0xA_nt!MiDeletePte+15b Followup: MachineOwner --------- I am using the stable snapshot of colinux dated 2/16/11 Linux version 2.6.33.7-co-0.7.9 (hn@hn-dt) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT Wed Feb 16 23:51:21 UTC 2011 The linux config file: kernel=vmlinux ro initrd=initrd.gz setcobd=async cobd0="F:\P_Ubuntu\Portable_Ubuntu_V4\images\rootfs.img" cofs0="F:\P_Ubuntu\Portable_Ubuntu_V4" cofs1="C:\DOCUME~1\RANGER~1\LOCALS~1\Temp" root=/dev/cobd0 cobd1="C:\DOCUME~1\RANGER~1\LOCALS~1\Temp\swap.img" hdc=\Device\Cdrom0 cofs2=c:\ exec0="F:\P_Ubuntu\Portable_Ubuntu_V4\pulseaudio\pulseaudio.exe" mem=384 eth0=ndis-bridge,"Local Area Connection",00:ff:75:39:D3:C2 This crash is fairly easy to create immediately when using XEMACS for editing. However, it takes longer to crash if you are just surfing the web. Since this is a memory corruption the program/driver active at the time of the crash is the victim of the corruption and it is likely some other driver/program caused it, in this case colinux. How to I submit a problem report on this and what additional information does the Colinux team need to solve this problem? Thanks for your help. Regards Bob |
|
From: Bob W. <bwh...@my...> - 2012-01-04 02:08:10
|
Hi: I have been having problems with blue screen crashes when running colinux. They are usually memory corruptions, irql too high, corrupt page table list. The just started when I tried to get ndis bridge mode networking working on Portable Ubuntu which uses colinux. I never had any crashes when using the slirp mode networking. Also, I never have any crashes when colinux is not running. Many dumps had Kaspersky driver active at the time of crash. Kaspersky support has analyzed the dump and say that their driver Is not causing the problem. So to prove it, I uninstalled Kaspersky and used their clean up utility to removed all components, and registry items. It still crashed with memory corruption but this time the active module was nt . The windbg output of this dump is: kd> !analyze -v **************************************************************************** *** * * * Bugcheck Analysis * * * **************************************************************************** *** IRQL_NOT_LESS_OR_EQUAL (a) An attempt was made to access a pageable (or completely invalid) address at an interrupt request level (IRQL) that is too high. This is usually caused by drivers using improper addresses. If a kernel debugger is available get the stack backtrace. Arguments: Arg1: 9ded4804, memory referenced Arg2: 00000002, IRQL Arg3: 00000000, value 0 = read operation, 1 = write operation Arg4: 804eb3b5, address which referenced memory Debugging Details: ------------------ READ_ADDRESS: 9ded4804 CURRENT_IRQL: 2 FAULTING_IP: nt!MiDeletePte+15b 804eb3b5 8b420c mov eax,dword ptr [edx+0Ch] CUSTOMER_CRASH_COUNT: 3 DEFAULT_BUCKET_ID: DRIVER_FAULT BUGCHECK_STR: 0xA TRAP_FRAME: f1c03aec -- (.trap fffffffff1c03aec) ErrCode = 00000000 eax=038202ff ebx=c000430c ecx=012b5655 edx=9ded47f8 esi=835d2fe8 edi=000fffff eip=804eb3b5 esp=f1c03b60 ebp=f1c03b84 iopl=0 nv up ei pl nz na pe nc cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010206 nt!MiDeletePte+0x15b: 804eb3b5 8b420c mov eax,dword ptr [edx+0Ch] ds:0023:9ded4804=???????? Resetting default scope LAST_CONTROL_TRANSFER: from 804eb3b5 to 804e1892 STACK_TEXT: f1c03aec 804eb3b5 badb0d00 9ded47f8 873c63e8 nt!KiTrap0E+0x233 f1c03b84 804eb6fe c000430c 010c3000 00000000 nt!MiDeletePte+0x15b f1c03c48 804f1d7c e122a614 010c9fff 00000000 nt!MiDeleteVirtualAddresses+0x162 f1c03cf4 8057a7c3 860fcb80 861acd00 f1c03d64 nt!MiRemoveMappedView+0x212 f1c03d38 8057a86f 85f21218 85eb8ee8 00000000 nt!MiUnmapViewOfSection+0x12b f1c03d54 804de7ec ffffffff 860fcb80 008beeec nt!NtUnmapViewOfSection+0x54 f1c03d54 7c90e514 ffffffff 860fcb80 008beeec nt!KiFastCallEntry+0xf8 WARNING: Frame IP not in any known module. Following frames may be wrong. 008beeec 00000000 00000000 00000000 00000000 0x7c90e514 STACK_COMMAND: kb FOLLOWUP_IP: nt!MiDeletePte+15b 804eb3b5 8b420c mov eax,dword ptr [edx+0Ch] SYMBOL_STACK_INDEX: 1 FOLLOWUP_NAME: MachineOwner MODULE_NAME: nt DEBUG_FLR_IMAGE_TIMESTAMP: 4ea6ba87 SYMBOL_NAME: nt!MiDeletePte+15b IMAGE_NAME: memory_corruption FAILURE_BUCKET_ID: 0xA_nt!MiDeletePte+15b BUCKET_ID: 0xA_nt!MiDeletePte+15b Followup: MachineOwner --------- I am using the stable snapshot of colinux dated 2/16/11 Linux version 2.6.33.7-co-0.7.9 (hn@hn-dt) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 PREEMPT Wed Feb 16 23:51:21 UTC 2011 The linux config file: kernel=vmlinux ro initrd=initrd.gz setcobd=async cobd0="F:\P_Ubuntu\Portable_Ubuntu_V4\images\rootfs.img" cofs0="F:\P_Ubuntu\Portable_Ubuntu_V4" cofs1="C:\DOCUME~1\RANGER~1\LOCALS~1\Temp" root=/dev/cobd0 cobd1="C:\DOCUME~1\RANGER~1\LOCALS~1\Temp\swap.img" hdc=\Device\Cdrom0 cofs2=c:\ exec0="F:\P_Ubuntu\Portable_Ubuntu_V4\pulseaudio\pulseaudio.exe" mem=384 eth0=ndis-bridge,"Local Area Connection",00:ff:75:39:D3:C2 This crash is fairly easy to create immediately when using XEMACS for editing. However, it takes longer to crash if you are just surfing the web. Since this is a memory corruption the program/driver active at the time of the crash is the victim of the corruption and it is likely some other driver/program caused it, in this case colinux. How to I submit a problem report on this and what additional information does the Colinux team need to solve this problem? Thanks for your help. Regards Bob |
|
From: Jeff B. <sp...@ya...> - 2012-01-03 21:38:35
|
> From: Johann Pascher <joh...@gm...> > To: coL...@li... > Sent: Wednesday, December 28, 2011 6:31 AM > Subject: Re: [coLinux-users] Contents of coLinux-users digest... > > Hi, is it possible that you did not exclude this cofs images from windos index? > http://www.win-tipps-tweaks.de/cms/windows-7-tipps/tricks/windows-7-schneller-machen.html Hi, I'm not sure if you were replying to my question or not; if so, thank you. Unfortunately, I'm not hosting coLinux on Windows 7 and indexing isn't really the problem. It seems there's just some overhead involved in mapping cofs to a Windows drive that results in relatively slow disk access, so I was hoping there was a configuration option to help with this, or at least some confirmation from others that yes, accessing native Windows drives via cofs takes a performance hit. |
|
From: Johann P. <joh...@gm...> - 2011-12-28 15:27:32
|
One thing more i also exude images from Windows backup, with adding a registry key. In NSIS Installer it looks like this my case: WriteRegStr HKLM SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup "speedLinux" "$INSTDIR\Drives\*" coLinux installer does not write a similar key so you should do this yourself. May be Henry can but things right if i am mistaken. Johann Pascher |
|
From: Johann P. <joh...@gm...> - 2011-12-28 14:31:34
|
Hi, is it possible that you did not exclude this cofs images from windos index? http://www.win-tipps-tweaks.de/cms/windows-7-tipps/tricks/windows-7-schneller-machen.html |
|
From: Jeff B. <sp...@ya...> - 2011-12-27 22:45:23
|
Hi, I'm a new user, using coLinux 0.7.9 with the 2.6.33.7 kernel. I'm using cofs for a certain application, and it seems to be the bottleneck with throughput. In researching this, it seems that cofs is just slow, and that's how it is, but I was wondering if there's any way at all to speed it up. I think I read that cofs already writes asynchronously, and that in tests -noatime didn't seem to make a difference. Is there anything else to try? Any little performance gain would really help out a lot. Thanks! |
|
From: Johann P. <joh...@gm...> - 2011-12-16 18:04:37
|
Hi Boris, i is correct that you cant us the image with read only kernel command line (ro). There a also some other errors that come up if the image is used without the suggest speedlinux installer. But this errors don't relay matter and you can fix this quit easy. I also use a tweaked initrd in combination with speedlinux. You my use the initrd.gz from speedlinux to get red of some errors. Still the image comes up and is usable. Put the base.vdi and the swap.vdi into the install directory. Don't rename this files. Copy the following text into the files an place the two files also into the install directory. Here are my startup.bat and my settings.txt (example.conf) startup.bat: @echo off set COLINUX_CONSOLE_FONT=Lucida Console:12 set COLINUX_CONSOLE_EXIT_ON_DETACH=0 :: Enable the following line by removing the "::" if you want to use all core 2 of the CPU. set COLINUX_NO_CPU0_WORKAROUND=Y start "speedServer (coLinux)" /min colinux-daemon.exe -d -k @settings.txt pause settings.txt: exec0="colinux-console-fltk.exe" cocon=80x40x500 kernel=vmlinux root=/dev/cobd0 initrd=initrd.gz mem=512 cobd0=base.vdi cobd1=swap.vdi cofs0=C:\ eth0=slirp #eth2=ndis-bridge,"LAN1", best regards, Johann Pascher |
119 messages has been excluded from this view by a project administrator.
