colinux-users

[coLinux-users] Colinux0-6-1 in windows2k

[Yonghao W. <yon...@ti...>]

Dear All,

=20

I am newbie to Colinux. I downloaded colinux 0.6.1 and installed it in
windows 2000 host. I downloaded Debian root filesystem
"Debian-3.0r0.ext3.1gb" and using "fsutil.exe" from XP to create swap
filesystem. I meet the following problems when I run colinux-daemon.

=20

1.	I must type "colinux-daemon -c colinux.default.xml". It seems
colinux-daemon cannot load default configuration script unless I use -c
filename.
2.	when I run the command line above it hangs on:

........

daemon: loading configuration from colinux.default.xml

=20

and it popup a windows error message:=20

=20

"The instruction at "0x0040af85" referenced memory at "0x00000000". The
memory could not be "read".

......"

=20

Can anyone give me some clue of this? Any suggestion will be
appreciated.

=20

Thank you

=20

Leo

Re: [coLinux-users] Colinux0-6-1 in windows2k

[tei <42...@in...>]

Yonghao Wang wrote:

> 
> 
> Dear All,
> 
>  
> 
> I am newbie to Colinux. I downloaded colinux 0.6.1 and installed it in 
> windows 2000 host. I downloaded Debian root filesystem 
> “Debian-3.0r0.ext3.1gb” and using “fsutil.exe” from XP to create swap 
> filesystem. I meet the following problems when I run colinux-daemon.
> 
>  
> 
>    1. I must type “colinux-daemon -c colinux.default.xml”. It seems
>       colinux-daemon cannot load default configuration script unless I
>       use –c filename.


Its te default beavior now.


>    2. when I run the command line above it hangs on:
> 
> ……..
> 
> daemon: loading configuration from colinux.default.xml
> 
>  
> 
> and it popup a windows error message:
> 
>  
> 
> “The instruction at “0x0040af85” referenced memory at “0x00000000”. The 
> memory could not be “read”.
> 
> ……”


Ok, crash.. a classic coding error at unexpected pointer to 0.  Sould 
this reported to the dev list?..


> 
>  
> 
> Can anyone give me some clue of this? Any suggestion will be appreciated.
> 

1) Report this error the devs, with info about your system. etc.. (will 
neeed a lot more info to gues WHAT is wrong or is not compatible (your 
system config vs colinux)).

2) Try other version.

If ALL versions crash, the problem is severe :P  but maybe the developers 
will provide you a more verbose version of colinux to have a much 
informativo log. If needed.


>  
> 
> Thank you
> 
>  
> 
> Leo
> 

Good Luck!

Re: [coLinux-users] Colinux0-6-1 in windows2k

[Dan A. <da...@co...>]

On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote:

> daemon: loading configuration from colinux.default.xml
> 
> and it popup a windows error message: 
> 
> "The instruction at "0x0040af85" referenced memory at "0x00000000". The
> memory could not be "read".

It appears the crash was inside mxml_string_getc. It is possible that 
the mxml library crashed on an invalid XML. Please send it over.

-- 
Dan Aloni
da...@co...

Re: [coLinux-users] Colinux0-6-1 in windows2k

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

Dan Aloni <da...@co...> wrote:
> On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote:
>
> > daemon: loading configuration from colinux.default.xml
> >
> > and it popup a windows error message:
> >
> > "The instruction at "0x0040af85" referenced memory at "0x00000000".
The
> > memory could not be "read".
>
> It appears the crash was inside mxml_string_getc. It is possible that
> the mxml library crashed on an invalid XML. Please send it over.
>
> -- 
> Dan Aloni
> da...@co...

hi Dan,

i ran into this bug too.  the first text editor i tried to use to edit
the coLinux config file was UltraEdit32.  this particular program feels
that it's necessary to prepend a BOM (or Byte Order Mark) to the
beginning of the file, just because it's "Unicode".  coLinux crashes if
the xml file starts with a BOM - perhaps it should be renamed a BOMB :-)

anyway i suppose colinux needs to be taught to tolerate this thing since
other editors do that as well -- apparently Notepad BOMbs xml files, too
(see
http://koti.mbnet.fi/akini/java/unicodereader/,
http://lists.xml.org/archives/xml-dev/200106/msg00389.html
and http://blogs.msdn.com/oldnewthing/archive/2004/03/24/95235.aspx).

it pisses me off that my editor did that, silently without telling me,
as it made my very first experience with coLinux a very frustrating one!
it was not until i opened the BOM-munged file in a real *text* editor
(rather than a wannabe Unicode editor) that i was warned that this
supposed text file now contained binary (high ASCII) characters, and
helped me avoid these nasty crashes.

and Yonghao, if you need a text editor that doesn't screw up the colinux
config file, check out MetaPad: http://liquidninja.com/metapad

hope this helps!

-dave

Re: [coLinux-users] Colinux0-6-1 in windows2k

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

Yonghao Wang <yon...@ti...> wrote:
>
> It seems Matepad still convert my txt file into Unicode format. Or
> operating system does this (colinux comes same error)? And I tried
> using ultraeditor to have looked HEX code of file. Even when I was
> editing file it looks fine and save and open again it prepend and
> convert into 2byte code.
>
> Any suggestions will be appreciated

hi Yonghao,

even though you can't see the BOM charaters in MetaPad because it ignores
the binary, after you've saved the file with UltraEdit, they are there.

for me, to get it working i had to re-install coLinux just to get a "clean"
text xml file, then edit it only with MetaPad, and *never* let UltraEdit
touch it.  even if you remove the BOM characters with UltraEdit's hex mode,
UltraEdit replaces them when you save the file.

BTW: it is not necessary to email me off-list.  i monitor the lists i'm
subscribed to regularly, and will direct my replies back to the list so that
others can benefit from the discussion, and find these types of useful
discussions in the list archives, later.

-dave



> David Kaufman <da...@gi...> wrote:
>
> Dan Aloni <da...@co...> wrote:
>> On Fri, Jun 04, 2004 at 03:04:11PM +0100, Yonghao Wang wrote:
>>
>>> daemon: loading configuration from colinux.default.xml
>>>
>>> and it popup a windows error message:
>>>
>>> "The instruction at "0x0040af85" referenced memory at "0x00000000".
>>> The memory could not be "read".
>>
>> It appears the crash was inside mxml_string_getc. It is possible that
>> the mxml library crashed on an invalid XML. Please send it over.
>>
>
> i ran into this bug too.  the first text editor i tried to use to edit
> the coLinux config file was UltraEdit32.  this particular program
> feels that it's necessary to prepend a BOM (or Byte Order Mark) to the
> beginning of the file, just because it's "Unicode".  coLinux crashes
> if the xml file starts with a BOM - perhaps it should be renamed a
> BOMB :-)
>
> [...] Yonghao, if you need a text editor that doesn't screw up the
> colinux config file, check out MetaPad: http://liquidninja.com/metapad
>
> hope this helps!
>
> -dave