colinux-users — coLinux users mailing list

Re: [coLinux-users] coLinux-20040910.exe errors

[Eric S. J. <es...@ha...>]

Nuno Lucas wrote:
> I am learning to use cscope ;) and from my inspection of the code, it
> can only be triggered at colinux/os/winnt/user/file.c, line 33, function
> co_os_file_load().
> 
> The reason is that colinux failed to open the file (obviously ;).
> This can be two things:
> 1) File does not exist
> 2) Access denied
> 3) Some operating system error (like corrupt disk)
> 
> 1) and 3) are obvious and 2) can be triggered if  another program opened
> the file in exclusive mode (thus denying access to colinux).
> 
> A reason for this error can be an anti-virus.

no antivirus here, it tends to interfere with speech recognition 
accuracy.  So the question then becomes is it a file missing or access 
control?  Is there any indication of which file it is looking at?

---eric

[coLinux-users] An article about Aloni's lecture.

[Digital I. Inc. <ok...@di...>]

Hello.

See this url with a machine traslation software.
http://itpro.nikkeibp.co.jp/free/ITPro/NEWS/20040914/149921/

Lucas:
As far as I know, Aloni did not mentioned about coFB stuff in the lectures.
but the article says,
"Currently, coLinux has a big overhead about displaying, becuase it uses Cygwin/X.
 They (who?) said that it soon is going to have a shared memory between Windows
 and display a FB on the mem with Direct/X.".

Ummmm... WHO said this?

BTW, this photo of Aloni is very cool, dont you think so, everybody?
 
            --- Okajima
 

Re: [coLinux-users] WiFi bridge with XP

[Ronald P. <pij...@ds...>]

> I have a Dell D800 with WiFi and GigEth networking.
> I have colinux-20040710 running with XP in bridged mode.
> 
> Is there a way to get my WiFi interface to work with colinux, using XP 
> bridging or some other method ???
> 
> Does the WiFi interface look like any other Ethernet interface or is it 
> a different beast.  If it looks like an ordinary Ethernet then it should 
> work with XP bridging without any problems, but I can't get it to work.

I tried both XP bridging using the TAP way, which worked, but requires XP
doing the translation from 192.168.0.255 network to the actual network
you are on.

Later I tried bridging WinPCap style. Initially this didn't work for me
(and I noted this on the Wiki). However, since then I've changed the
setup such that both sides (windows and colinux) use the same mac address
-- as opposed to what is described in the wiki -- and this works fine.

However, I have no idea what problems can arise from using the same mac
address on two different IP-addresses.

Btw. I use static IP-addresses. I can immagine more problems when using
dhcp.

Regards,

Ronald.

Re: [coLinux-users] coLinux-20040910.exe errors

[Nuno L. <lu...@nl...>]

Joe Wells, dando pulos de alegria, escreveu :
> Eric S. Johansson writes:
>>installed coLinux-20040910.exe in c:/Program Files/colinux.
>>
>>saw  note saying  to install  in c:/colinux.   I met  it half  way and
>>installed all linux  related images in c:/colinux and  the colinux exe
>>in the installation directory.  on running the daemon, I get:
>>
>>esj@speaker /cygdrive/c/Program Files/coLinux
>>$ ./colinux-daemon.exe -t nt -c default.colinux.xml
>>Cooperative Linux Daemon, 0.6.2-pre1
>>Compiled on Fri Sep 10 17:03:35 2004
>>
>>daemon: exit code 80008401
>>daemon: error - CO_RC_ERROR_ERROR, line 33, file id 0
> 
> Whenever I get this error, it mysteriously goes away after I try again
> one or two times.  I haven't tried to figure it out yet due to having
> (until now) more important problems with coLinux.

I am learning to use cscope ;) and from my inspection of the code, it
can only be triggered at colinux/os/winnt/user/file.c, line 33, function
co_os_file_load().

The reason is that colinux failed to open the file (obviously ;).
This can be two things:
1) File does not exist
2) Access denied
3) Some operating system error (like corrupt disk)

1) and 3) are obvious and 2) can be triggered if  another program opened
the file in exclusive mode (thus denying access to colinux).

A reason for this error can be an anti-virus.

Regards,
~Nuno Lucas

[coLinux-users] coLinux FC2 package?

[John F. <J.P...@as...>]

Is there a package of FC2 for coLinux, similar to the one for FC1?

Thanks

John
-------------------------------------------------------------------
Dr John P. Fletcher          Tel: (44) 121 359 3611 ext 4625
Chemical Engineering and Applied Chemistry (CEAC),
School of Engineering and Applied Science (SEAS),
Aston University,            Fax: (44) 121 359 4094
Aston Triangle,              Email: J.P...@as...
BIRMINGHAM B4 7ET  U.K.      CEAC Web site 
http://www.ceac.aston.ac.uk/

[coLinux-users] Snapshot 20040910 alongside 0.6.1 ?

[John F. <J.P...@as...>]

Hello

First of all, thank you for coLinux.

I am using coLinux 0.6.1 release with Fedora Core 1 on two 
machines, one with Windows 2000 and one with Windows XP.  I 
am using Tap, and Windows XP bridging on the XP machine.

I would like to try out the new 20040910 snapshot.  Is it possible to 
install it alongside the present packages.  

My guess is that if I execute the 20040910 executable it will try to 
install e.g. Tap software on top of the present installation so I have 
not done that yet.

I have enough disk space to make two completely parallel 2 Gbyte 
installations.

Thanks

John


-------------------------------------------------------------------
Dr John P. Fletcher          Tel: (44) 121 359 3611 ext 4625
Chemical Engineering and Applied Chemistry (CEAC),
School of Engineering and Applied Science (SEAS),
Aston University,            Fax: (44) 121 359 4094
Aston Triangle,              Email: J.P...@as...
BIRMINGHAM B4 7ET  U.K.      CEAC Web site 
http://www.ceac.aston.ac.uk/

Re: [coLinux-users] coLinux-20040910.exe errors

[<sl...@bl...>]

"Eric S. Johansson" <es...@ha...> writes:

> installed coLinux-20040910.exe in c:/Program Files/colinux.
> 
> saw  note saying  to install  in c:/colinux.   I met  it half  way and
> installed all linux  related images in c:/colinux and  the colinux exe
> in the installation directory.  on running the daemon, I get:
> 
> 
> esj@speaker /cygdrive/c/Program Files/coLinux
> $ ./colinux-daemon.exe -t nt -c default.colinux.xml
> Cooperative Linux Daemon, 0.6.2-pre1
> Compiled on Fri Sep 10 17:03:35 2004
> 
> daemon: exit code 80008401
> daemon: error - CO_RC_ERROR_ERROR, line 33, file id 0

Whenever I get this error, it mysteriously goes away after I try again
one or two times.  I haven't tried to figure it out yet due to having
(until now) more important problems with coLinux.

-- 
Joe

[coLinux-users] coLinux-20040910.exe errors

[Eric S. J. <es...@ha...>]

installed coLinux-20040910.exe in c:/Program Files/colinux.

saw note saying to install in c:/colinux.  I met it half way and 
installed all linux related images in c:/colinux and the colinux exe in 
the installation directory.  on running the daemon, I get:

esj@speaker /cygdrive/c/Program Files/coLinux
$ ./colinux-daemon.exe -t nt -c default.colinux.xml
Cooperative Linux Daemon, 0.6.2-pre1
Compiled on Fri Sep 10 17:03:35 2004

daemon: exit code 80008401
daemon: error - CO_RC_ERROR_ERROR, line 33, file id 0

---

google shows nothing.  ideas?? rtfm??

thanks

--- eric

[coLinux-users] Re: enabling sound support under colinux?

[A. A. A. <alp...@tt...>]

On Fri, 10 Sep 2004 08:47:11 -0700, hank smith wrote:

>hello I am trying to use yasr its a screen reader for the blind, I did the following
>apt-get install yasr flite eflite
>yasr is the screen reader and flite and eflite is the tts engine stuff it needs how ever when I run 
>yasr at the command prompt I don't hear any speech.

There's no audio hw support in coLinux yet, you'll need a sound daemon
on windows side that handles streaming audio over network.

Actually, I have been testing latest festival release on
colinux-20040910. I have cygwin with esound package installed on
windows side, using tap adapter, daemon executing as follows (ip
address refers to windows side of tap):

esd -tcp -bind 192.168.0.1 -port 15001 -public

esound is also installed in colinux, and I've added following lines to
siteinit.scm :

(Parameter.set 'Audio_Method 'Audio_Command)
(Parameter.set 'Audio_Required_Rate 22050)
(Parameter.set 'Audio_Required_Format 'raw)
(Parameter.set 'Audio_Command 
	"esdcat -s 192.168.0.1:15001 -m -r 22050 < $FILE")

Now, I can hear speech synthesized in colinux by festival.

flite does not have scheme interface so this does not directly apply,
but I guess you've got the point.

>if sound support is not supported how easy would it be to put both in colinux, and in astwind? whitch is the colinux with asterisk support.

AstWind does not support any of that hardware, it is stated as a
packet voice installation:
http://www.digium.com/index.php?menu=astwind

<quote>
Most VoIP only features are available on the Windows version, although
there is currently no support for any hardware interfaces.
...
Through the coLinux networking subsystem, Asterisk has access to the
network and can participate fully as a unique server.
</quote>


--
A. Alper Atici               OpenPGP KeyID: 0xB824F550

Re: [coLinux-users] snapshot 20040910 (0.6.2-pre1)

[Nuno L. <lu...@nl...>]

Joe Wells, dando pulos de alegria, escreveu :
> Is there some way I can extract initrd.gz from coLinux-20040910.exe
> without running the latter?  I would rather not run a large monolithic
> installer that does a lot of things that I don't understand or need.

I have a private build in a zip file. You can get it here:
http://xpto.ath.cx/colinux/snapshots/colinux-0.6.2-pre1.zip

Regards,
~Nuno Lucas

[coLinux-users] Re: [coLinux-devel] snapshot 20040910 (0.6.2-pre1)

[Ian A. <ia...@ab...>]

On 13/09/2004 14:49, Joe Wells wrote:
> Ian Abbott <ia...@ab...> writes:
>>On 12/09/2004 12:23, Joe Wells wrote:
>>>Where is the initrd.gz file?  It does not seem to be in the
>>>colinux-0.6.2-pre1.zip file.
>>
>>The coLinux-20040910.exe file installs it along with the other binaries.
> 
> Is there some way I can extract initrd.gz from coLinux-20040910.exe
> without running the latter?  I would rather not run a large monolithic
> installer that does a lot of things that I don't understand or need.

None that I'm aware of.  Perhaps an "extract only" option could be 
added to the installer.

I suggest renaming your current coLinux directory, then running the 
installer to install coLinux to your usual coLinux directory (so the 
registry entries stay the same), but on the "Choose Components" 
page, deselect everything but the "coLinux" item.  After 
installation, rename the old and new coLinux directories to restore 
the old coLinux directory's previous name (which was usurped by the 
new coLinux installation).

[coLinux-users] Re: [coLinux-devel] snapshot 20040910 (0.6.2-pre1)

[Jaroslaw K. <ja...@zd...>]

There's a problem with the module installation script in initrd.

If i pass "ro root=/dev/cobd0" parameters it fails to isntall the modules. I
have to use "root=/dev/cobd0 ro" to be successful.

Jarek

----- Original Message ----- 
From: "Dan Aloni" <da...@co...>
To: "Cooperative Linux Development" <col...@li...>
Cc: "Cooperative Linux Users" <col...@li...>
Sent: Friday, September 10, 2004 4:39 PM
Subject: [coLinux-devel] snapshot 20040910 (0.6.2-pre1)


> Hello,
>
> I've released a snapshot to bring us a step closer to 0.6.2-final.
>
>     http://www.colinux.org/snapshots/coLinux-20040910.exe
>
> The problem with 0.6.2 is that people are expected to move from 2.4.x
> based coLinux system to 2.6.x based system on upgrade from 0.6.1 and
> prir. Many of the newbie users would wonder why their Gentoo stops
> working on this move (technically a script breakage over the /dev/cobdX-
> to-/dev/cobd/X notation change caused by devfs).
>
> Actually I think we should come with some sort of standard for a coLinux
> root file system, e.g a /etc/colinux file that could hint a fix-me-up
> initrd what's going on instead of auto-guessing.
>
> Apropos initrd, this snapshot contains a beta version of an initrd
> image that installs the kernel modules for the supplied vmlinux unto
> the root filesystem (thanks George). You can test it simply by
> adding the element: <initrd path="initrd.gz" />.
>
> Anyway, the list of changes from the last snapshot which was quite a
> while ago (20040710) includes:
>
>   * If the MAC address is unspecified, a random MAC is choosed
>     using the familiar TAP prefix (00:FF:XX:XX:XX:XX).
>   * Bug fix: Reception and delivery of network packets bigger than
>     2kb.
>   * Bug fix: Consoles and/or other daemons fail to connect to
>     colinux-daemon on startup (this is Windows only).
>   * Bug fix: Stop reboots where different gcc compiler versions are
>     used to compile linux.sys & vmlinux, with an error/warning
>     (George Boutwell).
>   * Enhanced coLinux keyboard handling support (sends raw scan codes
>     from Windows to linux) (Nuno Lucas).
>   * Bug fix: bad initialization caused unexpected SIGFPE for programs
>     compiled with -mpentium4 (me)
>
> You might also want to take a look at the monotone ChangeLog (under
> the snapshot directory for the monotone-declined users).
>
> -- 
> Dan Aloni
> da...@co...
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM.
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> coLinux-devel mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-devel
>

Re: [coLinux-users] Re: [coLinux-devel] snapshot 20040910 (0.6.2-pre1)

[<sl...@bl...>]

Ian Abbott <ia...@ab...> writes:

> On 12/09/2004 12:23, Joe Wells wrote:
> > Dan Aloni <da...@co...> writes:
> >> Apropos initrd, this snapshot contains  a beta version of an initrd
> >> image  that installs the  kernel modules  for the  supplied vmlinux
> >> unto the root filesystem (thanks George). You can test it simply by
> >> adding the element: <initrd path="initrd.gz" />.
> 
> > Where is the initrd.gz file?  It does not seem to be in the
> 
> > colinux-0.6.2-pre1.zip file.
> 
> The coLinux-20040910.exe file installs it along with the other binaries.

Is there some way I can extract initrd.gz from coLinux-20040910.exe
without running the latter?  I would rather not run a large monolithic
installer that does a lot of things that I don't understand or need.

-- 
Joe

[coLinux-users] Re: [coLinux-devel] snapshot 20040910 (0.6.2-pre1)

[Ian A. <ia...@ab...>]

On 12/09/2004 12:23, Joe Wells wrote:
> Dan Aloni <da...@co...> writes:
>>Apropos initrd, this snapshot contains a beta version of an initrd 
>>image that installs the kernel modules for the supplied vmlinux unto 
>>the root filesystem (thanks George). You can test it simply by 
>>adding the element: <initrd path="initrd.gz" />.
> 
> Where is the initrd.gz file?  It does not seem to be in the
> colinux-0.6.2-pre1.zip file.

The coLinux-20040910.exe file installs it along with the other binaries.

[coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Ian A. <ia...@ab...>]

On 10/09/2004 21:50, Ian Abbott wrote:
> On 10/09/2004 18:32, Nuno Lucas wrote:
> 
>> Ian Abbott, dando pulos de alegria, escreveu :
>>
>>> I'm just wondering what the reason for this notation change is, 
>>> particularly for aliases.  Sure, the /dev/cobd/X notation helps to 
>>> keep the /dev directory tidy, but /dev/hda/X seems to be going a bit 
>>> too far as /dev/hda is normally a block special file, not a directory!
>>
>> This has to do with devfs naming scheme and Gentoo uses and needs it 
>> to run.
> 
> But when I run Gentoo natively with a 2.6.x kernel with devfs enabled, I 
> get the normal /dev/hda1 etc.

More specifically, "/dev/hda1" ends up as a symlink to 
"ide/host0/bus0/target0/lun0/part1".  The devfsd daemon is 
responsible for creating this symlink, using the MKOLDCOMPAT command 
in /etc/devfsd.conf.

I tried using "ide/host0/bus0/target0/lun0/part1" as an alias in the 
coLinux xml file, but didn't expect it to work.  I thought the 
"part1" bit would end up as "part/1", but the alias was too long and 
ended up truncated to "ide/host0/bus0/targ".

I still maintain that the /dev/hda/1 naming scheme is purely an 
invention of coLinux (specifically, the cobd_spawn_alias function) 
and nothing to do with any pre-existing devfs naming scheme.

Sure I could create a symlink to /dev/hda1 in /dev/devfsd.conf but 
that kind of defeats the point - I could create a symlink to 
/dev/cobd/0 instead.  The only thing the aliasing buys me is the use 
of standard block major device numbers.

[coLinux-users] Re: [coLinux-devel] A fix for the SIGFPE problem (>20040622)

[<sl...@bl...>]

sl...@bl... (Joe Wells (reverse mailbox letters for non-public replies)) writes:

> > I've already commited the patch into the monotone server. If you can
> > check that firefox / xdvi aren't crashing anymore I'd be glad.
> 
> Okay, I am downloading the 20040910 snapshot.  (Am I correct in
> assuming the fix is in this snapshot?)  I hope I will have time to try
> it out next week.

I can now confirm that the 2004-09-10 snapshot fixes all of the
problems I had with wrong floating point exceptions.  Thanks again for
fixing this!

-- 
Joe

[coLinux-users] Re: [coLinux-devel] snapshot 20040910 (0.6.2-pre1)

[<sl...@bl...>]

Dan Aloni <da...@co...> writes:

> Apropos initrd, this snapshot contains a beta version of an initrd 
> image that installs the kernel modules for the supplied vmlinux unto 
> the root filesystem (thanks George). You can test it simply by 
> adding the element: <initrd path="initrd.gz" />.

Where is the initrd.gz file?  It does not seem to be in the
colinux-0.6.2-pre1.zip file.

-- 
Joe

[coLinux-users] Re: Problems with 20040710 snapshot

[<sl...@bl...>]

Henry Nestler <Hen...@ar...> writes:

> Joe Wells wrote:
> 
>  > Are you using the Pentium M?  (The "M" is for mobile.)
>
> Pentium 4M. Yes, it's mobile :-)

I don't know if this matters so much now that the floating point
exception problem is supposedly solved (will test later today), but a
Pentium 4M is a very different CPU from a Pentium M.  The Pentium M
series implements the same instruction set as the Pentium 4 series,
but is internally designed in radically different way.  I don't know
whether this has anything to do with why you couldn't reproduce the
floating point bug.

> You can self recompiling all executable and kernel.

Maybe someday.  If this latest coLinux snapshot fixes my problems,
then I hope I will not have to.

-- 
Joe

Re: [coLinux-users] Random signal 11 problems?

[Jules <ju...@ds...>]

> If you recompile kernel, you should also recompile colinux daemons.
> It's strictly recommented, to use the same GCC version for kernel and 
> daemons.

Surely the colinux daemons require a windows or cross-compiler?  FWIW, a 
kernel compiled with the default config packaged with the colinux source 
worked fine; it seems to be associated with one of the options I 
changed.  I haven't investigated enough to determine which one, exactly, 
but my prime suspect is the CPU type, which I changed to AMD Athlon, as 
that is the architecture I run on.

[coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Nuno L. <nt...@nl...>]

Nuno Lucas, dando pulos de alegria, escreveu :
> Eric S. Johansson, dando pulos de alegria, escreveu :
> 
>> apologies.  I did not frame the question right.  Maybe a better question
>> to ask would be since the world is moving towards udev, would it be
>> appropriate for co-linux to require use of udev as its baseline?
>>
>> no big deal either way I'm just wondering if it would simplify the
>> installation process.
>>

Just for completion, I switched my gentoo to udev today.
It's really quite simple:

1) emerge udev
2) change all hdb/? to hdb? in fstab
3) add "gentoo=nodevfs" in the bootparams
4) reboot

A litle warning appears because we didn't compiled hotplug in the 
kernel, but as we don't use it in colinux it doesn't matter.
If we get to use it, it's only a kernel recompile away.

Regards,
~Nuno Lucas

RE: [coLinux-users] [Fwd: Win XP Bridged Network Disconnecting]

[peter g. <plu...@bi...>]

no idea short of reinstalling windows


> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of overbored
> Sent: 11 September 2004 23:56
> To: col...@li...
> Subject: [coLinux-users] [Fwd: Win XP Bridged Network Disconnecting]
> 
> 
> Anybody?
> 

[coLinux-users] [Fwd: Win XP Bridged Network Disconnecting]

[overbored <ove...@ov...>]

Anybody?

[coLinux-users] Newbie question: linux.sys causing a BSOD

[Steve F. <ste...@be...>]

Hi, I'm getting a STOP error (Blue scree o' death) whenever I try to
start up colinux, with the failure on the linux.sys driver. I'm on XP
SP2 (and it works on another SP2 machine fine).  Immediately on startup
a 0x8e error occurs, so this is a no go.  The system is an Athlon64 with
a Via KT800Pro chipset, if that matters. Any ideas?

=20

Steve

=20

Re: [coLinux-users] Re: snapshot 20040910 (0.6.2-pre1)

[Nuno L. <lu...@nl...>]

Eric S. Johansson, dando pulos de alegria, escreveu :
> apologies.  I did not frame the question right.  Maybe a better question
> to ask would be since the world is moving towards udev, would it be
> appropriate for co-linux to require use of udev as its baseline?
>
> no big deal either way I'm just wondering if it would simplify the
> installation process.
>

As it is only more of a Gentoo problem, I don't think we should care
much about it than having the problem explained in the Wiki.

And it can be very easily solved either with symlinks or with "mknod".

I don't see any big problem here. And it's just a question of time to
the change occurs.

Regards,
~Nuno Lucas

RE: [coLinux-users] enabling sound support under colinux?

[peter g. <plu...@bi...>]

i think the easiest soloution to sound would be to pump it over to the
windows side and then send it down waveout and let windows take care of it
from there
  -----Original Message-----
  From: col...@li...
[mailto:col...@li...]On Behalf Of hank smith
  Sent: 10 September 2004 16:47
  To: coL...@li...
  Subject: [coLinux-users] enabling sound support under colinux?


  hello I am trying to use yasr its a screen reader for the blind, I did the
following
  apt-get install yasr flite eflite
  yasr is the screen reader and flite and eflite is the tts engine stuff it
needs how ever when I run
  yasr at the command prompt I don't hear any speech.
  if sound support is not supported how easy would it be to put both in
colinux, and in astwind? whitch is the colinux with asterisk support.
  thanks
  hank


----------------------------------------------------------------------------
--
  My Inbox is protected by SPAMfighter
  1063 spam mails have been blocked so far.
  Download free SPAMfighter today!