colinux-users — coLinux users mailing list

[coLinux-users] Gentoo 2006 FATAL: Could not open '/System.map': No such file or directory [ !! ]

[Wisut H. <wi...@gm...>]

Hi All,
  I download http://jaist.dl.sourceforge.net/sourceforge/colinux/Gentoo-colinux-i686-2007-03-03.7z
(107.7MB), Extract to c:\gentoo, Test running c:\gentoo\gentoo.bat,
and found that there is FATAL: Could not open '/System.map': No such
file or directory    [ !! ].
 coLinux installer is
http://www.colinux.org/snapshots/devel-coLinux-20070425.exe (3.87MB)

  I think it is a kernel-building-related. Is the problem is realy
FALTAL ? How can I fix it ?
  The same problem occured with Gentoo 2007.0 stage3 i686 too when I
try to setup my own rootfs.

Wisut.

Below are readme.txt of downloaded rootfs

To get started, run gentoo.bat. This assumes that you've installed
coLinux in C:\Program Files\coLinux (the default) and extracted this
folder into C: (so that the files are in C:\gentoo). If you haven't,
you'll need to edit gentoo.conf and gentoo.bat.

The password for root is root.

eth0 is configured to work as slirp device.
eth1 is optional, if you have a TAP-win32 adapter with IP address
192.168.200.1 and no gateway address.

This is a basic install of Gentoo 2006.1, brought up to date with an
emerge --sync && emerge world on 2007-02-23 (+syslog-ng, vixie-cron,
dhcpcd, screen). It's setup to run on i686 with NPTL.

You'll probably need to change the following:

* The amount of memory allocated to Gentoo (gentoo.conf)
* Timezone (/etc/localtime)
* Portage and rsync mirrors (/etc/make.conf)
* TAP Network (gentoo.conf, /etc/conf.d/net)

Enjoy!

--Chris Forno, 2007-02-25
--Henry N., 2007-03-03

[coLinux-users] vi problem on cofs

[Samir K. <sam...@gm...>]

I am having problems using vi on cofs. I am getting errors regarding fsync.
>From a quick google search, I understand this is a known issue with cofs. Is
there anyway to work around this issue?

~Samir

[coLinux-users] Be no demagnify

[Alexandria F. <nvl...@ma...>]

HXPN IS GAINING GREAT MOMENTUM! 
WE ARE ABOUT TO SEE FIRWORKS! 
WATCH IT ON MONDAY MAY 21! 

__________

Company: Harris Exploration Inc
Symbol: HXPN
Price: 0.78
5-day Target: $2.5
Rating: Agressive Buy

__________

HXPN HAS GAINED OVER 50% IN 2 DAYS!
WE ARE EXPECTING GAINS TOPPING 200% AND MORE!
GET IN NOW WHILE YOU STILL CAN MAKE PROFIT!

________________________________________
"Yes, so I imagined. I was afraid there could be little chance of my h Small heart had Harriet for visiting. Only half an hour before her fri "Emma," said Mr. Knightley presently, "I have a piece of news for you. "Me!--not at all," replied Mr. Knightley, rather displeased; "I do not
"It is a most repulsive quality, indeed," said he. "Oftentimes very co "Yes--it seems to depend upon nothing but the ill-humour of Mrs. Churc This was too true for contradiction. Unwelcome as it was, Mr. Woodhous Mr. Weston, with triumph of a different sort, was confessing that he h
"And Mrs. Perry and the children, how are they? do the children grow?  "Almost every moment. She has been gone longer already than she intend "Very well; I will not plague you any more. Emma shall be an angel, an

[coLinux-users] USB printer

[Larry C. <lc...@di...>]

Hello,

Is it possible for coLinux to use a USB printer on the host PC?

I have an HP DeskJet 4168 running fine amongst the Windows users. CoLinux
(using CUPS and HPIJS) will send data that is spooled to the printer. The
problem is that the spooler suspends every on every coLinux print job after
sending 64KB to the printer.

This behavior repeats regardless of the print job (Iceweasel, OpenOffice,
etc.).



--
Larry Crouch
lc...@di...

Re: [coLinux-users] Where is Debian Etch Root Image?

[Henry N. <Hen...@Ar...>]

Holger Krull wrote:
> Henry Nestler wrote:
> 
>> Slirp is the first network eth0, users of tap-win32 should edit
>> /etc/network/interfaces.
> 
> Yes, and nano is the existing editor.
> 
>> Users should run
>>    apt-get install console-tools
>>    apt-get install dselect  and/or   apt-get install aptitude
>> to get a fontend for installing packages.

Removed warning "unable to initialize frontend: Dialog" by installing 
dialog.

The image file Debian-4.0r0-etch.ext3.1gb.bz2 is on SF now:
http://sourceforge.net/project/showfiles.php?group_id=98788&package_id=122245&release_id=248895

-- 
Henry

Re: [coLinux-users] RE : BSOD on Intel Core 2 Duo, Windows Vista

[BS R. <bsr...@gm...>]

Hi Henry

On 5/8/07, Henry Nestler <Hen...@ar...> wrote:
Thanks for your reply.

CoLinux 0.7.1 with builds after 2007-03-03 has a workarrount and tells
> the CPU every change on page tables with a special read CR3 and write
> back the same value.  This bug exist only on Intels, but we do this
> workarround on all CPU types.


Strange.  coLinux 0.7.1 RC3 which resulted in a BSOD on startup was built on
2007-03-26.  So, I expect 0.7.1 RC3 had the fix for 'noexecute'.  Could the
version of Vista may have been the cause for BSOD?  I tried to run 0.7.1 RC3
on Vista Home Premium.  If not, could the PC hardware configuration, say
motherboard etc. may have caused that BSOD?  If not, then I probably made
some error during installation.


> For Vista should use a build after 2007-04-25, there was fixed an other
> problem with halt/shutting down:
>
> http://www.henrynestler.com/colinux/testing/stable-0.7.1/20070425-Snapshot/


Ok, will give this a try.


Reddy

Re: [coLinux-users] Fuse module support

[Henry N. <Hen...@Ar...>]

Samir Kuthiala wrote:
> Thanks for replying. I have no problems building the kernel. I just want 
> to check whether fuse is a supported configuration? I remember hearing 
> that cofs has some namespace clashes with fuse?

No. All cofs names are separated from fuse. You can enable fuse_fs 
without problems.

-- 
Henry

Re: [coLinux-users] Fuse module support

[Samir K. <sam...@gm...>]

Hi

Thanks for replying. I have no problems building the kernel. I just want to
check whether fuse is a supported configuration? I remember hearing that
cofs has some namespace clashes with fuse?

Regards
Samir

On 5/8/07, Henry Nestler <Hen...@ar...> wrote:
>
> Samir Kuthiala wrote:
> > I have just installed co-linux 0.7.1 (with the debian image). I was
> > wondering whether colinux supports the fuse module as yet? I remember
> > there was some discussion on the mailing list sometime back with the
> > conclusion being that it was not currently supported.
> >
> > If it is, can somebody give me some pointers on how to go about setting
> > it up. Thanks.
>
> Fuse is not supported per default configuration. Check this on your
> running colinux:
>
> $ zcat /proc/config.gz | grep FUSE
> # CONFIG_FUSE_FS is not set
> CONFIG_COFUSE_FS=y
>
> The "COFUSE" is the Colinux host filesystem. It's your windows
> partition, you can configure it with "cofs=C:\coLinux" in your config,
> read more in the file COFS.TXT on your coLinux installtion.  This
> cofs-filesystem based on fuse, but this is not the "fuse_fs" for other
> programs.
>
> If you wand to use the real "fuse_fs" then you need to reconfigure the
> kernel and rebuild the modules.
>
> --
> Henry
>

Re: [coLinux-users] Colinux 0.6.3 problem

[Henry N. <Hen...@Ar...>]

Dominic Binks wrote:
> Dear All,
> 
> Hope someone can help me here.
> 
> I have a Fedora Core 5 system running on coLinux 0.6.3 running on 
> WinXPsp2 which will not boot - As soon as it has mounted the root 
> filesystem in readonly mode (kjournald has started) it restarts.  I 
> thought initially that there could some kind of corruption on the root 
> disk, but alas another root disk image I have (FC4) boots fine and I can 
> then mount the disk without a problem - I've also fsck the disk and that 
> checks out fine too.
> 
> I suspect that the problem is the in the FC5 boot scripts but I don't 
> know where.  Since I cannot see any output from the system during this 
> time (syslog isn't started before it restarts) I can't figure out how to 
> find out what's going wrong.  Is there any way I can get console output 
> from this phase of start-up (the fltk-console doesn't show me either 
> even with the system set to boot in "verbose" mode).

It's an hard idea:
- Mount your FC5 from your FC4
- Backup and edit the file etc/rc.d/rc
- locate this lines
     # Now run the START scripts.
     for i in /etc/rc$runlevel.d/S* ; do
   and add this line inner the "for" loop:
     echo "enter for %i"; read junk
- Next boot of FC5 you must quit every start script with ENTER key.  ;-)

Hm, but while reading in my FC3 (FC5 I not have), I found 
"/var/run/confirm".  It seems to do the same?  Create this file and try 
your boot.
In etc/rc.sysinit I found, you should set "confirm" in your bootparams, 
then it creates the file /var/run/confirm.  Perhaps you should then boot 
with "rw" for rootfs.

And last: Boot without initrd.

-- 
Henry

Re: [coLinux-users] RE : BSOD on Intel Core 2 Duo, Windows Vista

[Henry N. <Hen...@Ar...>]

Hello Reddy,

BS Reddy wrote:
>     (I posted this to the help forum, but did not receive any response, so
>     trying out here)

Sorry, the forum is not very active.

>     coLinux 0.7.1 RC3 crashed with a BSOD when I tried to run it on Windows
>     Vista, Intel Core 2 Duo (2GB RAM). I am aware of the coLinux problem
>     on new
>     CPUs and operating systems that support "noexecute" as documented here:
>     http://colinux.wikia.com/wiki/NoExecuteDEP
> 
>     I have read people managing to run coLinux on Windows Vista on the
>     web. So, I just wanted to know:
> 
>     a. Can coLinux 0.7.1 or 0.8.0 run on Windows Vista, Intel Core 2 Duo
>     with DEP setting set to default "OptIn"?

Yes.

>     b. Does the "noexecute" problem in coLinux need to be fixed on a
>     per-processor basis? (as it has been done for Intel P4 and Xeon)

Is fixed for all processors.

>     c. Does the fix for Intel P4 and Xeon processors allow coLinux to
>     run on
>     Windows Vista (or Windows XP SP2) on those processors with DEP
>     setting set to default "OptIn"?

Yes.

>     d. I am no OS expert, can someone explain (or point to an existing
>     thread)
>     as to why this "noexecute" setting causes the coLinux to crash,
>     where as
>     essential Windows programs and services keep running?

All other Windows programms have typically pages for code (execute) and 
some other pages for data (noexecute).
While switching from windows, coLinux needs to run in a memory "page" 
where all is in one single page.  For this coLinux changed the flag from 
"noexecute" into "execute" before enter this page.  Now, this typicaly 
CPUs don't see this flag-change and you see the typicaly BSOD directly 
on start of coLinux.

The crashing CPU types has an bigger internal cache for Page Tables 
(PTE).  Colinux has changed a flag in this tables without telling the 
CPU the changes.  All other CPUs automatic detects changes on page 
tables and updated theyr internal caches.  But the both types of P4 and 
Xeon does no updates automaticly.

CoLinux 0.7.1 with builds after 2007-03-03 has a workarrount and tells 
the CPU every change on page tables with a special read CR3 and write 
back the same value.  This bug exist only on Intels, but we do this 
workarround on all CPU types.

Devel version 0.8.0 with builds after 2007-03-02 has an optimiszed 
workarrount: It reloads Page Tables only ones on init, not on every 
context switch.

Here is the initial mail, the changes you can read here:
http://marc.info/?l=colinux-devel&m=116885210617337&w=1

For Vista should use a build after 2007-04-25, there was fixed an other 
problem with halt/shutting down:
http://www.henrynestler.com/colinux/testing/stable-0.7.1/20070425-Snapshot/


-- 
Henry

Re: [coLinux-users] Fuse module support

[Henry N. <Hen...@Ar...>]

Samir Kuthiala wrote:
> I have just installed co-linux 0.7.1 (with the debian image). I was 
> wondering whether colinux supports the fuse module as yet? I remember 
> there was some discussion on the mailing list sometime back with the 
> conclusion being that it was not currently supported.
> 
> If it is, can somebody give me some pointers on how to go about setting 
> it up. Thanks.

Fuse is not supported per default configuration. Check this on your 
running colinux:

$ zcat /proc/config.gz | grep FUSE
# CONFIG_FUSE_FS is not set
CONFIG_COFUSE_FS=y

The "COFUSE" is the Colinux host filesystem. It's your windows 
partition, you can configure it with "cofs=C:\coLinux" in your config, 
read more in the file COFS.TXT on your coLinux installtion.  This 
cofs-filesystem based on fuse, but this is not the "fuse_fs" for other 
programs.

If you wand to use the real "fuse_fs" then you need to reconfigure the 
kernel and rebuild the modules.

-- 
Henry

Re: [coLinux-users] is the archive accessible elsewhere ?

[Henry N. <Hen...@Ar...>]

Oh,

Henry Nestler wrote:
> Didier BRETIN wrote:
>> apparently the archive of this mailing list is out of order. Is there a 
>> copy on gmane.org ?
> 
> User list:
> http://news.gmane.org/gmane.linux.colinux.general
> http://sourceforge.net/mailarchive/forum.php?forum=colinux-users 
> (temporaly fail)
> 
> Devel list:
> http://news.gmane.org/gmane.linux.colinux.devel
> http://sourceforge.net/mailarchive/forum.php?forum=colinux-devel 
> (temporaly fail)
> http://marc.info/?l=colinux-devel&r=1&w=2

think SF has changed some.  It's a new link:

http://sourceforge.net/mailarchive/forum.php?forum_name=colinux-users
http://sourceforge.net/mailarchive/forum.php?forum_name=colinux-devel

-- 
Henry

Re: [coLinux-users] is the archive accessible elsewhere ?

[Henry N. <Hen...@Ar...>]

Didier BRETIN wrote:
> apparently the archive of this mailing list is out of order. Is there a 
> copy on gmane.org ?

User list:
http://news.gmane.org/gmane.linux.colinux.general
http://sourceforge.net/mailarchive/forum.php?forum=colinux-users 
(temporaly fail)

Devel list:
http://news.gmane.org/gmane.linux.colinux.devel
http://sourceforge.net/mailarchive/forum.php?forum=colinux-devel 
(temporaly fail)
http://marc.info/?l=colinux-devel&r=1&w=2

[coLinux-users] Fuse module support

[Samir K. <sam...@gm...>]

Hi

I have just installed co-linux 0.7.1 (with the debian image). I was
wondering whether colinux supports the fuse module as yet? I remember there
was some discussion on the mailing list sometime back with the conclusion
being that it was not currently supported.

If it is, can somebody give me some pointers on how to go about setting it
up. Thanks.

Regards
Samir

Re: [coLinux-users] is the archive accessible elsewhere ?

[David K. <da...@gi...>]

Hi Didier,

Didier BRETIN <di...@br...> wrote:
> Hi,
>
> apparently the archive of this mailing list is out of order. Is there
> a copy on gmane.org ?

I don't know... why don't you search gmane.org for one?  Surely entering 
"colinux" into this gmane search: 
http://gmane.org/search.php?match=colinux would answer the question 
faster and more reliably than entering it into your mail reader, 
transmitting a message to hundreds of other colinux users around the 
world, waiting for one of them to enter it into gmane's search box, 
press enter, and then email the answer back to you ...wouldn't it?

http://www.slash7.com/pages (i vont to drink your blood)

-dave

[coLinux-users] Cobuntu (or better)?

[Bothari <bo...@gm...>]

Greetings all!

I am using the cobuntu image from Chris Dahl's web site, and have been
off and on for over a year.  I need to give a talk on cobuntu for a
Ruby User Group this week, but when I went to his site I saw that it
was cleaned out.

Is there still a cobuntu site floating around, or is there something
new that I missed?

Thanks,
Joe

-- 
"For a new software system, the requirements will not be completely
known until after the users have used it."  Humphrey's Requirements
Uncertainty Principle.

[coLinux-users] is the archive accessible elsewhere ?

[Didier B. <di...@br...>]

Hi,

apparently the archive of this mailing list is out of order. Is there a 
copy on gmane.org ?

Regards.
-- 
Didier BRETIN
http://www.bretin.net/

[coLinux-users] Fuse module support

[Samir K. <sam...@gm...>]

Hi

I have just installed co-linux 0.7.1 (with the debian image). I was
wondering whether colinux supports the fuse module as yet? I remember there
was some discussion on the mailing list sometime back with the conclusion
being that it was not currently supported.

If it is, can somebody give me some pointers on how to go about setting it
up. Thanks.

Regards
Samir

[coLinux-users] Fwd: Dual cores and multiprocessor plan ?

[Wisut H. <wi...@gm...>]

---------- Forwarded message ----------
From: Wisut Hantanong <wi...@gm...>
Date: May 3, 2007 4:12 PM
Subject: Dual cores and multiprocessor plan ?
To: Cooperative Linux Development <col...@li...>


Hi delvelopers,

 Do you plan to add multiprocess/multicore support to colinux ? and when ?

These are what I got from my Intel centrino duo (dual core).
===========================
wisut-colinux ~ # cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 14
model name      : Genuine Intel(R) CPU           T2300  @ 1.66GHz
stepping        : 8
cpu MHz         : 0.000
cache size      : 2048 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 10
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca
cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx
constant_tsc up pni monitor est tm2 xtpr
bogomips        : 444.00
==========================

And ofcorse the colinux process seem to take only one core as I see
from my Vista's resource manager.

Thank for the best linux on windows VM.
Wisut.

Re: [coLinux-users] unable to install package

[<agu...@ya...>]

You'd better install cygwin or even MinGW then.

Anyway, if you insist on colinux, do you have working internet conection fr=
om=20
inside colinux?


On Monday 30 April 2007 00:19, floratush wrote:
> am sorry for being so naive, but please help me out. i also have the
> problem of failing to connect to the debian image . it complains that
> connection to backports.org couldnt be made and that hence the package is
> not found. then goes ahead and says out of mmap space etc..please help me
> and elaborate how exactly i should solve this problem.
> I have just downloaded colinux today and hence find it illogical that the
> image package its using is out of date (i could be wrong - but even then
> dont know where and how to point to the current version)
>
> NB i just want to run gcc in windows. thats how i landed on colinux
>
> florence
>
> Sam Moffatt wrote:
> > There are a few issues here
> > 1) Stable has updated twice since 3.0 (first Sarge [3.1] and now Etch
> > [4.0]) so it is unlikely that the APT locations are still valid.
> > 2) You're running out of allocated space for packages, this is a known
> > fault when updating to Etch. See the release notes for a solution.
> >
> > I would suggest using a more recent image. I would also suggest
> > acquainting yourself with the target operating system in a full
> > virtual machine (e.g. one of VMWare's products) or a fully fledged
> > box.
> >
> > Sam
> >
> > On 13/04/07, Wolfram Wadepohl <Wol...@ek...> wrot=
e:
> >> paulo donizete gardinalli filho schrieb:
> >> >     Hi, when you use debian for the first time on colinux, before any
> >> > installation, you need to execute de following command:
> >> > apt-get update
> >> > this command will update the apt database..
> >>
> >> No, did not help:
> >>
> >> Hit http://security.debian.org stable/updates/main Packages
> >> Hit http://security.debian.org stable/updates/main Release
> >> Err http://www.backports.org stable/kernel-image-2.6.6-i386 Packages
> >>    404 Not Found
> >> Ign http://www.backports.org stable/kernel-image-2.6.6-i386 Release
> >> Hit http://ftp.us.debian.org stable/main Packages
> >> Hit http://ftp.us.debian.org stable/main Release
> >> Hit http://ftp.us.debian.org stable/main Sources
> >> Hit http://ftp.us.debian.org stable/main Release
> >> Reading Package Lists...
> >> Failed to fetch
> >> http://www.backports.org/debian/dists/stable/kernel-image-2.6.6-i386/b=
in
> >>ary-i386/Packages 404 Not Found
> >> E: Dynamic MMap ran out of room
> >> E: Error occured while processing wzdftpd-dev (NewPackage)
> >> E: Problem with MergeList
> >> /var/lib/apt/lists/ftp.us.debian.org_debian_dists_stable_main_binary-i=
38
> >>6_Packages E: The package lists or status file could not be parsed or
> >> opened.
> >>
> >> i think the URL to the backports is no longer valid.
> >>
> >> > -----Mensagem original-----
> >> > De: Wolfram Wadepohl <Wol...@ek...>
> >> > Para: col...@li...
> >> > Data: Quinta, 12 de Abril de 2007 16:04
> >> > Assunto: [coLinux-users] unable to install package
> >> >
> >> > Hello,
> >> >
> >> > i tried to install a new package into the
> >> > Debian-3.0r2.ext3-mit-backports.1gb.bz2 root image.
> >> >
> >> > result:
> >> > # apt-get install make
> >> > Reading Package Lists...
> >> > Building Dependency Tree...
> >> > The following NEW packages will be installed:
> >> >    make
> >> > 0 packages upgraded, 1 newly installed, 0 to remove and 0  not
> >>
> >> upgraded.
> >>
> >> > Need to get 386kB of archives. After unpacking 799kB will be used.
> >> > Err http://ftp.us.debian.org stable/main make 3.79.1-14
> >> >    404 Not Found [IP: 35.9.37.225 80]
> >> >
> >> > how can i install new packages?
> >>
> >> --
> >> Sch=C3=B6ne Gr=C3=BC=C3=9Fe aus Reutlingen
> >>
> >> Wolfram Wadepohl
> >> Forschung & Entwicklung
> >>
> >> E&K AUTOMATION
> >> Indumat GmbH & Co. KG
> >> Siemensstra=C3=9Fe 3
> >> 72766 Reutlingen
> >> Deutschland
> >>
> >> Tel.  +49 7121 514-289
> >> Fax   +49 7121 514-299
> >> eMail Wol...@ek...
> >>        W.W...@in...
> >>        W.W...@ie...
> >> WWW   http://www.ek-automation.com
> >>        http://www.indumat.de
> >>
> >> Diese Nachricht ist keine gesch=C3=A4ftliche Mitteilung i. S. des EHUG.
> >>
> >> Bitte senden Sie mir keine Word- oder PowerPoint- (tm Microsoft)
> >> Anh=C3=A4nge. Senden Sie mir einfachen Text, HTML oder PDF.
> >> Siehe http://www.gnu.org/philosophy/no-word-attachments.de.html
> >>
> >>
> >> ----------------------------------------------------------------------=
=2D-
> >>- Take Surveys. Earn Cash. Influence the Future of IT
> >> Join SourceForge.net's Techsay panel and you'll get the chance to share
> >> your
> >> opinions on IT & business topics through brief surveys-and earn cash
> >> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDE
> >>V _______________________________________________
> >> coLinux-users mailing list
> >> coL...@li...
> >> https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
> > -----------------------------------------------------------------------=
=2D-
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your
> > opinions on IT & business topics through brief surveys-and earn cash
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users

[coLinux-users] Colinux 0.6.3 problem

[Dominic B. <dom...@th...>]

Dear All,

Hope someone can help me here.

I have a Fedora Core 5 system running on coLinux 0.6.3 running on 
WinXPsp2 which will not boot - As soon as it has mounted the root 
filesystem in readonly mode (kjournald has started) it restarts.  I 
thought initially that there could some kind of corruption on the root 
disk, but alas another root disk image I have (FC4) boots fine and I can 
then mount the disk without a problem - I've also fsck the disk and that 
checks out fine too.

I suspect that the problem is the in the FC5 boot scripts but I don't 
know where.  Since I cannot see any output from the system during this 
time (syslog isn't started before it restarts) I can't figure out how to 
find out what's going wrong.  Is there any way I can get console output 
from this phase of start-up (the fltk-console doesn't show me either 
even with the system set to boot in "verbose" mode).

Can anyone point me to any ways to get the output from starting up?  I 
reckon if I can see the output then I can modify the start-up scripts so 
I can at least find out where it is rebooting from.

Many thanks.

BTW coLinux is a magnificent piece of software and after running this 
instance handling all my families email for a year this is the first 
significant problem I've run into!

Re: [coLinux-users] Xrealvnc uses all my CPU

[James H. <Jam...@ro...>]

Thanks. I've been using freenx with coLinux for a week now and its highly=20
usable. The only problem I had was that bitmapped fonts don't work.=20

In fullscreen mode with no JPEG compression I sometimes forget that I am no=
t=20
in native Linux.

Cheers,
James

On Saturday 14 April 2007 04:04, you wrote:
> The highest way i found with colinus and kde was freenx of nomachine.
> I've tried VNC and tight vnc, but my system became so slow that it was not
> possible to use the gimp for example.
> You can find frenx on nomachine site and you must install the deb package=
s:
> freenx viewer, freenxnode and freenxserver. You must also install ssh on
> linux.
> Regards,
> Francis
>
> James Hirschorn a =E9crit :
> > I recently setup my native linux operating system to run under coLinux.
> > It was amazing!
> >
> > Unfortunately, after a couple of hours colinux became so slow that it w=
as
> > unusable. The Xrealvnc executable was using about 75% of the colinux CP=
U,
> > and the colinux-daemon about 80-90% of the Windows XP CPU.
> >
> > I have no previous experience with the VNC server. My KDE desktop deman=
ds
> > a lot of resources to run all the applications. Is this a known issue
> > with VNC? Is Cgywin X more suitable for more instensive use? (I haven't
> > tried it out yet.)
> >
> > Thanks,
> > James
> >
> > -----------------------------------------------------------------------=
=2D-
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> > your opinions on IT & business topics through brief surveys-and earn ca=
sh
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users

Re: [coLinux-users] RE : BSOD on Intel Core 2 Duo, Windows Vista

[BS R. <bsr...@gm...>]

Hi,

Thanks for your information.  I was trying to run coLinux 0.7.1. RC3 on
Windows Vista Home Premium.

Regards
Reddy


On 4/30/07, Francois Liot <fl...@ky...> wrote:
>
>  Hello,
>
> I'm using coLinux 0.7.1 RC3 under Vista Professional,
> everything works except the "install-service" action.
>
> Regards,
>
> Francois Liot
>
>
> -------- Message d'origine--------
> De: col...@li... de la part de BS Reddy
> Date: ven. 4/27/2007 11:57
> =C0: col...@li...
> Objet : [coLinux-users] BSOD on Intel Core 2 Duo, Windows Vista
>
> Hi all
>
> (I posted this to the help forum, but did not receive any response, so
> trying out here)
>
> coLinux 0.7.1 RC3 crashed with a BSOD when I tried to run it on Windows
> Vista, Intel Core 2 Duo (2GB RAM). I am aware of the coLinux problem on
> new
> CPUs and operating systems that support "noexecute" as documented here:
> http://colinux.wikia.com/wiki/NoExecuteDEP
>
> I have read people managing to run coLinux on Windows Vista on the web.
> So,
> I just wanted to know:
>
> a. Can coLinux 0.7.1 or 0.8.0 run on Windows Vista, Intel Core 2 Duo with
> DEP setting set to default "OptIn"?
>
> b. Does the "noexecute" problem in coLinux need to be fixed on a
> per-processor basis? (as it has been done for Intel P4 and Xeon)
>
> c. Does the fix for Intel P4 and Xeon processors allow coLinux to run on
> Windows Vista (or Windows XP SP2) on those processors with DEP setting se=
t
> to default "OptIn"?
>
> d. I am no OS expert, can someone explain (or point to an existing thread=
)
> as to why this "noexecute" setting causes the coLinux to crash, where as
> essential Windows programs and services keep running?
>
> Answers to above questions, will rule out the doubt that I may have made
> an
> error during my installation.
>
> Thanks
> Reddy
>
>

[coLinux-users] RE : RE : BSOD on Intel Core 2 Duo, Windows Vista

[Francois L. <fl...@ky...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE : RE : [coLinux-users] BSOD on Intel Core 2 Duo, Windows =
Vista</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I forgot to add,<BR>
<BR>
This runs on a brand new laptop Intel Centrino Duo in OptIn mode.<BR>
<BR>
Regards<BR>
<BR>
-------- Message d'origine--------<BR>
De: Francois Liot<BR>
Date: lun. 4/30/2007 8:52<BR>
=C0: BS Reddy; col...@li...<BR>
Objet : RE : [coLinux-users] BSOD on Intel Core 2 Duo, Windows Vista<BR>
<BR>
Hello,<BR>
<BR>
I'm using coLinux 0.7.1 RC3 under Vista Professional,<BR>
everything works except the &quot;install-service&quot; action.<BR>
<BR>
Regards,<BR>
<BR>
Francois Liot<BR>
<BR>
<BR>
-------- Message d'origine--------<BR>
De: col...@li... de la part de BS =
Reddy<BR>
Date: ven. 4/27/2007 11:57<BR>
=C0: col...@li...<BR>
Objet : [coLinux-users] BSOD on Intel Core 2 Duo, Windows Vista<BR>
<BR>
Hi all<BR>
<BR>
(I posted this to the help forum, but did not receive any response, =
so<BR>
trying out here)<BR>
<BR>
coLinux 0.7.1 RC3 crashed with a BSOD when I tried to run it on =
Windows<BR>
Vista, Intel Core 2 Duo (2GB RAM). I am aware of the coLinux problem on =
new<BR>
CPUs and operating systems that support &quot;noexecute&quot; as =
documented here:<BR>
<A =
HREF=3D"http://colinux.wikia.com/wiki/NoExecuteDEP">http://colinux.wikia.=
com/wiki/NoExecuteDEP</A><BR>
<BR>
I have read people managing to run coLinux on Windows Vista on the web. =
So,<BR>
I just wanted to know:<BR>
<BR>
a. Can coLinux 0.7.1 or 0.8.0 run on Windows Vista, Intel Core 2 Duo =
with<BR>
DEP setting set to default &quot;OptIn&quot;?<BR>
<BR>
b. Does the &quot;noexecute&quot; problem in coLinux need to be fixed on =
a<BR>
per-processor basis? (as it has been done for Intel P4 and Xeon)<BR>
<BR>
c. Does the fix for Intel P4 and Xeon processors allow coLinux to run =
on<BR>
Windows Vista (or Windows XP SP2) on those processors with DEP setting =
set<BR>
to default &quot;OptIn&quot;?<BR>
<BR>
d. I am no OS expert, can someone explain (or point to an existing =
thread)<BR>
as to why this &quot;noexecute&quot; setting causes the coLinux to =
crash, where as<BR>
essential Windows programs and services keep running?<BR>
<BR>
Answers to above questions, will rule out the doubt that I may have made =
an<BR>
error during my installation.<BR>
<BR>
Thanks<BR>
Reddy<BR>
<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>

[coLinux-users] RE : BSOD on Intel Core 2 Duo, Windows Vista

[Francois L. <fl...@ky...>]

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7651.59">
<TITLE>RE : [coLinux-users] BSOD on Intel Core 2 Duo, Windows =
Vista</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hello,<BR>
<BR>
I'm using coLinux 0.7.1 RC3 under Vista Professional,<BR>
everything works except the &quot;install-service&quot; action.<BR>
<BR>
Regards,<BR>
<BR>
Francois Liot<BR>
<BR>
<BR>
-------- Message d'origine--------<BR>
De: col...@li... de la part de BS =
Reddy<BR>
Date: ven. 4/27/2007 11:57<BR>
=C0: col...@li...<BR>
Objet : [coLinux-users] BSOD on Intel Core 2 Duo, Windows Vista<BR>
<BR>
Hi all<BR>
<BR>
(I posted this to the help forum, but did not receive any response, =
so<BR>
trying out here)<BR>
<BR>
coLinux 0.7.1 RC3 crashed with a BSOD when I tried to run it on =
Windows<BR>
Vista, Intel Core 2 Duo (2GB RAM). I am aware of the coLinux problem on =
new<BR>
CPUs and operating systems that support &quot;noexecute&quot; as =
documented here:<BR>
<A =
HREF=3D"http://colinux.wikia.com/wiki/NoExecuteDEP">http://colinux.wikia.=
com/wiki/NoExecuteDEP</A><BR>
<BR>
I have read people managing to run coLinux on Windows Vista on the web. =
So,<BR>
I just wanted to know:<BR>
<BR>
a. Can coLinux 0.7.1 or 0.8.0 run on Windows Vista, Intel Core 2 Duo =
with<BR>
DEP setting set to default &quot;OptIn&quot;?<BR>
<BR>
b. Does the &quot;noexecute&quot; problem in coLinux need to be fixed on =
a<BR>
per-processor basis? (as it has been done for Intel P4 and Xeon)<BR>
<BR>
c. Does the fix for Intel P4 and Xeon processors allow coLinux to run =
on<BR>
Windows Vista (or Windows XP SP2) on those processors with DEP setting =
set<BR>
to default &quot;OptIn&quot;?<BR>
<BR>
d. I am no OS expert, can someone explain (or point to an existing =
thread)<BR>
as to why this &quot;noexecute&quot; setting causes the coLinux to =
crash, where as<BR>
essential Windows programs and services keep running?<BR>
<BR>
Answers to above questions, will rule out the doubt that I may have made =
an<BR>
error during my installation.<BR>
<BR>
Thanks<BR>
Reddy<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>