Henry N.

Show:

What's happening?

  • Comment: Crash on coLinux start

    Testet 650 loops with Windows XP P2, 2048MB PAE (foreced with "/PAE" in boot.ini), and 200 loops with 5128 PAE, also Windwos XP SP2. All without crash.

    2012-04-08 04:44:11 PDT in Cooperative Linux

  • Comment: Crash on coLinux start

    Please try to run without "kill". Add "init=/sbin/halt" to colinux config, and remove the "kill" from test.sh. Additional add "export COLINUX_CONSOLE_EXIT_ON_DETACH=1" to the test.sh and remove the "-d". This lets see the boot process and close the console after every shut down. I also stored the count into file and have installed sync.exe...

    2012-04-08 02:58:25 PDT in Cooperative Linux

  • Comment: Crash on coLinux start

    The analyze give not enough output for precise point into code. Have seen, that you stops colinux-damon with "kill -9" (SIGKILL). Does it also crash with normal termination "kill -15" (SIGTERM)?.

    2012-04-08 01:39:48 PDT in Cooperative Linux

  • Comment: Crash on coLinux start

    Post your file "squeeze.conf" here. How many MEM do you have installed in your machine and how many have configured for coLinux? Do you also use CygWin shell to start colinux-daemon under normal usage?.

    2012-03-28 16:45:00 PDT in Cooperative Linux

  • Comment: Crash on coLinux start

    Hello Lorne, the dump file not helps. I have not sane of your binary files here. Please use WinDbg, load the dump and post the text output from "!analyze -v" here. Debuggers help page was moved, but the old link is still available: http://msdl.microsoft.com/download/symbols/debuggers/dbg_x86_6.7.05.1.exe.

    2012-03-28 16:38:56 PDT in Cooperative Linux

  • Followup: RE: Redirecting X

    On the Windows side you must xming start with “-ac” parameter to disable access control restrictions.

    2012-03-19 14:28:25 PDT in Cooperative Linux

  • Followup: RE: Redirecting X

    Environment can see from apllication only, if the variable is expored or it is in same line with the commandn. Try [code]export DISPLAY=192.168.3.2:0.0 xclock[/code] or [code]DISPLAY=192.168.3.2:0.0 xclock[/code].

    2012-03-19 14:26:53 PDT in Cooperative Linux

  • Followup: RE: Beginner Installation question

    Is it a 32 bit Windows? What version is it? It's crashing by clicking the file "colinux-console-fltk.exe"? If yes, please fill out a [url=https://sourceforge.net/tracker/?group_id=98788&atid=622063]Bug report[/url]. Do you have created a configuration file? If not, see in [url=http://colinux.wikia.com/wiki/Getting_Started_with_coLinux#Configuration]Wiki "Getting Started...

    2012-03-11 18:14:28 PDT in Cooperative Linux

  • Followup: RE: How to use a USB stick from inside colinux

    Hello, the problem is, that you should do it carefully. If you have mounted the USB stick under coLinux and written some bytes, then you should never touch (no read and never write) the same stick under Windows. The problem is the read/write cache of filesystem meta data on both sides. There is no problem, if you unmounted the stick under Windows by removing the drive letter in the disk...

    2012-03-04 13:08:46 PST in Cooperative Linux

  • Followup: RE: running something from config file after boot

    Oh, a very old question. Simple set a variable with '=' between, this can read from /proc/cmdline later in Linux. For example add "myvar=foo.bar" top the coLinux config file, and you can see it later under running Linux in the /proc/cmdline exactly so as "myvar=foo.bar". You should something do with "sed" to parse it out from file and use it.

    2012-02-11 15:30:50 PST in Cooperative Linux

About Me

  • 2002-07-16 (10 years ago)
  • 579204
  • henryn (My Site)
  • Henry N.

  • MinGW/MSYS (MS Windows) Microsoft MS-DOS Assembly C C++ Pascal Python Unix Shell Hardware Drivers Linux Framebuffer SDL

Send me a message