colinux-users — coLinux users mailing list

[coLinux-users] alternative link for console-gdi.zip

[Paolo M. <pao...@gm...>]

Hi,
I repeat that this is the main download link :
http://xoomer.alice.it/paolo.minazzi/console-gdi.zip

Hilany Cheng and Daniele say that it is not possible download my zip file.
I think they have some filter. For these persons I have uploaded the
same version on rapidshare.
It is the first time I use rapidshare.
I understand that on rapidshare the file can be downloaded only 10
times...I'm sorry for this ....
This is the rapidshare link :
http://rapidshare.com/files/182195706/console-gdi.zip

An alternative link (infinite download) is
http://mio.discoremoto.alice.it/carlominazzi
select console-gdi.zip and click on "Scarica" that is "download" in
italian language.

As Henry says, it is based on 2.6.22.18, colinux 0.7.3.
Modified ntdriver, vmlinux and daemons.
Please (to avoid crash!) use those of my zip file (reinstalling my linux.sys).

Thanks for interest.

Paolo

Re: [coLinux-users] new cocon

[Henry N. <hen...@ar...>]

Henry Nestler wrote:
> Missing only some keys: ALT-F1, ALT-F2, ALT-F3,... and Cursor-Right, 
> Cursor-Left don't work to switch to other virtual consoles. Only tty1 is 
> usable. Key "Print screen" is blocked for Windows?

ALT-F1, ALT-F2, ALT-F3, ... ALT-Cursor-Right, ALT-Cursor-Left works. I 
can change the consoles. I don't know, what it was. Perhaps a side 
effect from trying to print with ALT-Print-Screen. Sorry for false alert.

-- 
Henry N.

Re: [coLinux-users] new cocon

[Henry N. <hen...@ar...>]

Xuefer wrote:
> what version/branch is this demo release based on? any screen shots?

It is coLinux 2.6.22.18-co-0.7.3

You need all files from Paolo, because he has changed some in Linux 
kernel, Windows-Kernel driver and in the daemons.

Here is a screen shot:
http://www.henrynestler.com/colinux/screenshoots/Console-gdi-60x120-by-paolo.png

It's nice to see. It's simple and runs.
Very good works the copy and paste via mouse.

Missing only some keys: ALT-F1, ALT-F2, ALT-F3,... and Cursor-Right, 
Cursor-Left don't work to switch to other virtual consoles. Only tty1 is 
usable. Key "Print screen" is blocked for Windows?

Thanks Paolo. :-)

-- 
Henry N.

Re: [coLinux-users] new cocon

[Xuefer <xu...@gm...>]

what version/branch is this demo release based on? any screen shots?

[coLinux-users] new cocon

[Paolo M. <pao...@gm...>]

Hi colinux users,
after had trying for a while my SDL console, I have written a new
version using directly the win32 API.
This new version is very light.

Feature :

cut/paste :
************
copy : select moving with left mouse botton
paste : press the right mouse button
It works from/to other windows.

setfont :
************

You can change font runtime using the linux command :
Examples :

setfont lat4a-12
setfont lat4a-10
setfont lat4a-08
setfont

I'm interested to know if there are some problem.
Very interesting if there are some problems using cut/paste with
different keyboard layout (I think it should be all OK).

Where to download:
http://xoomer.alice.it/paolo.minazzi/console-gdi.zip

The archive contains all executable and driver.

Please use
colinux-daemon --remove-driver
to remove your current driver

Unzip my zip package, for example in C:\NEW

cd C:\NEW

Install the new driver
colinux-daemon --install-driver

Type go.bat to start

Important : edit configuration file "norm" to adjust your cobd0 (so it
can point to your harddisk image)

Thanks,
Paolo

[coLinux-users] start a lvm dual-boot linux

[Guang H. <pa...@gm...>]

Hi colinux-users!,

I've a lvm dual-boot linux installed in my system, is there a way to start
the linux with all lvm volumes mounted?
Currently I can start with the root fs mounted(which is not managed by lvm),
but can't find any lvm volumes even after system starts. Can anyone kindly
give me some tips?

thanks,
--pangwa--

Re: [coLinux-users] mv deletes entire folder with contents without asking

[Tobbe L. <tob...@gm...>]

> I often got a BSOD with BAD_POOL_CALLER

Yes, so did I...

Thanks for acknowledging this bug and for creating a patch for it :)

//Tobbe

Re: [coLinux-users] mv deletes entire folder with contents without asking

[Henry N. <hen...@ar...>]

Hello Tobbe,

thank for your report. A very interesting bug with big risk losing data.

I can reproduce it and I will warn all users, that this will corrupt 
Windows memory. I often got a BSOD with BAD_POOL_CALLER on shutting down 
Windows or on shutting down coLinux or opening new applications, after I 
have called this sequence in a bash:
  mkdir /cofs/TestDir
  mv /cofs/testdir

 From debugging, the Linux shell (bash) called such commands on cofs:
  stat /cofs/TestDir
  --> ntkernel returns success (file exist), cofs created inode=1
  stat /cofs/testdir
  --> ntkernel returns success (file exist), cofs created inode=2
  rename /cofs/TestDir /cofs/testdir/TestDir
  --> ntkernel returns success, but have deleted all

The shell saw the "testdir" as existing and tryed to move TestDir to 
testdir/TestDir. That is a badly idea, because the parent can not rename 
itself.

The attached patch is a workaround and prevents this situation.

--
Henry

Sam Moffatt wrote:
> You've got to remember that cofs is backed onto the NTFS file system
> which whilst being case preserving is by default not case sensitive on
> Windows even though it can be (much fun). What has more than likely
> happened that somewhere in one of the calls, Windows has behaved
> strangely and ended up nuking the file. You can do weird stuff by
> replicating this on Windows where you open a lower case file and cat
> to one that isn't however it goes back to the same place.
>
> In effect the command is telling it to move to the same location,
> consider the following from the Windows command line:
> C:\WINDOWS\Temp>mkdir pie
> C:\WINDOWS\Temp>cd pie
> C:\WINDOWS\Temp\pie>mkdir TestDir
> C:\WINDOWS\Temp\pie>move TestDir testdir
> The process cannot access the file because it is being used by another process.
>
>
> Its an interesting case of case sensitivities that I guess COFS should
> handle better, however try enabling case sensitivity in Windows and
> see if this makes a difference. I'm not entirely sure how you do this,
> but Google should know the answer.
>
> Sam Moffatt
> http://pasamio.id.au
>
>
>
> On Thu, Dec 25, 2008 at 2:14 AM, Tobbe Lundberg wrote:
>   
>> Hi
>>
>> I'm running coLinux 20081217 and have C:\ mounted as /mnt/windows using cofs.
>>
>> Let's say I'm in /mnt/windows/someDir. This is the output of ls -lR
>>
>> tobbe@debian:/mnt/windows/someDir$ ls -lR
>> .:
>> total 0
>> drwxr-xr-x 1 tobbe tobbe 0 Dec 24 10:57 TestTest
>>
>> ./TestTest:
>> total 0
>> -rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file1
>> -rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file2
>> -rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file3
>>
>> now I do 'mv TestTest testtest'
>>
>> Doing ls -lR again gives me this:
>>
>> tobbe@debian:/mnt/windows/someDir$ ls -lR
>> .:
>> total 0
>>
>> Where did my files and folder go?
>>
>> //Tobbe
>>
>>     

Re: [coLinux-users] mv deletes entire folder with contents without asking

[Tobbe L. <tob...@gm...>]

> What has more than likely
> happened that somewhere in one of the calls, Windows has behaved
> strangely and ended up nuking the file.

> Its an interesting case of case sensitivities that I guess COFS should
> handle better

Thanks for your reply.

Yes, a more robust handling of this would be good :) If it can't be
supported a simple(?) "Operation not permitted" message would suffice.

//Tobbe

Re: [coLinux-users] mv deletes entire folder with contents without asking

[Sam M. <pa...@gm...>]

You've got to remember that cofs is backed onto the NTFS file system
which whilst being case preserving is by default not case sensitive on
Windows even though it can be (much fun). What has more than likely
happened that somewhere in one of the calls, Windows has behaved
strangely and ended up nuking the file. You can do weird stuff by
replicating this on Windows where you open a lower case file and cat
to one that isn't however it goes back to the same place.

In effect the command is telling it to move to the same location,
consider the following from the Windows command line:
C:\WINDOWS\Temp>mkdir pie
C:\WINDOWS\Temp>cd pie
C:\WINDOWS\Temp\pie>mkdir TestDir
C:\WINDOWS\Temp\pie>move TestDir testdir
The process cannot access the file because it is being used by another process.


Its an interesting case of case sensitivities that I guess COFS should
handle better, however try enabling case sensitivity in Windows and
see if this makes a difference. I'm not entirely sure how you do this,
but Google should know the answer.

Sam Moffatt
http://pasamio.id.au



On Thu, Dec 25, 2008 at 2:14 AM, Tobbe Lundberg <tob...@gm...> wrote:
> Hi
>
> I'm running coLinux 20081217 and have C:\ mounted as /mnt/windows using cofs.
>
> Let's say I'm in /mnt/windows/someDir. This is the output of ls -lR
>
> tobbe@debian:/mnt/windows/someDir$ ls -lR
> .:
> total 0
> drwxr-xr-x 1 tobbe tobbe 0 Dec 24 10:57 TestTest
>
> ./TestTest:
> total 0
> -rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file1
> -rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file2
> -rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file3
>
> now I do 'mv TestTest testtest'
>
> Doing ls -lR again gives me this:
>
> tobbe@debian:/mnt/windows/someDir$ ls -lR
> .:
> total 0
>
> Where did my files and folder go?
>
> //Tobbe
>
> ------------------------------------------------------------------------------
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] mv deletes entire folder with contents without asking

[Tobbe L. <tob...@gm...>]

Hi

I'm running coLinux 20081217 and have C:\ mounted as /mnt/windows using cofs.

Let's say I'm in /mnt/windows/someDir. This is the output of ls -lR

tobbe@debian:/mnt/windows/someDir$ ls -lR
.:
total 0
drwxr-xr-x 1 tobbe tobbe 0 Dec 24 10:57 TestTest

./TestTest:
total 0
-rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file1
-rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file2
-rw-r--r-- 1 tobbe tobbe 0 Dec 24 10:57 file3

now I do 'mv TestTest testtest'

Doing ls -lR again gives me this:

tobbe@debian:/mnt/windows/someDir$ ls -lR
.:
total 0

Where did my files and folder go?

//Tobbe

Re: [coLinux-users] error driver version

[Tobbe L. <tob...@gm...>]

Dropping the 20081217 snapshot on top of the 20081130 snapshot install
worked just fine :) So now I'm able to boot the latest dev snapshot :)

On Mon, Dec 22, 2008 at 1:30 PM, Tobbe Lundberg <tob...@gm...> wrote:
> I'm using the 20081130 .exe snapshot for now. At least I can start that one :)
>
> On Mon, Dec 22, 2008 at 12:54 PM, Tobbe Lundberg <tob...@gm...> wrote:
>> I ran "colinux-daemon.exe --remove-driver" to remove the driver. Then
>> I ran "colinux-daemon.exe --remove-driver" again just to check that
>> everything was good and I got the expected "driver not installed".
>> Then I rebooted my computer and when it was back up I did
>> "colinux-daemon.exe --install-driver". After that, when I run
>> "colinux-daemon.exe @colinux.conf" I get the same error message again
>> about the wrong driver version.
>>
>> On Mon, Dec 22, 2008 at 12:32 PM, Sam Moffatt <pa...@gm...> wrote:
>>> Try doing a remove, restart windows and then redo the install just to
>>> ensure that everything is honky dory. It shoudn't make a difference
>>> but windows is a weird beast.
>>>
>>> Sam Moffatt
>>> http://pasamio.id.au
>>>
>>>
>>>
>>> On Mon, Dec 22, 2008 at 9:19 PM, Tobbe Lundberg <tob...@gm...> wrote:
>>>> Hi
>>>>
>>>> I just installed coLinux 0.7.3 and then dropped the 20081217 snapshot
>>>> on top of that. I did the --driver-remove --driver-install thing it
>>>> told me to do. When I try to run coLinux I get the following output:
>>>>
>>>> c:\Program\coLinux>colinux-daemon.exe @colinux.conf
>>>> Cooperative Linux Daemon, 0.8.0
>>>> Daemon compiled on Wed Dec 17 05:06:10 2008
>>>>
>>>> colinux: error, expected kernel API version 12, got 10
>>>> daemon: exit code 82e6fc03
>>>> daemon: error driver version, please reinstall driver!
>>>>
>>>> What more do I have to do to be able to run coLinux?
>>>>
>>>> //Tobbe
>>>>
>>>> ------------------------------------------------------------------------------
>>>> _______________________________________________
>>>> coLinux-users mailing list
>>>> coL...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>>
>>>
>>
>

Re: [coLinux-users] error driver version

[Tobbe L. <tob...@gm...>]

I ran "colinux-daemon.exe --remove-driver" to remove the driver. Then
I ran "colinux-daemon.exe --remove-driver" again just to check that
everything was good and I got the expected "driver not installed".
Then I rebooted my computer and when it was back up I did
"colinux-daemon.exe --install-driver". After that, when I run
"colinux-daemon.exe @colinux.conf" I get the same error message again
about the wrong driver version.

On Mon, Dec 22, 2008 at 12:32 PM, Sam Moffatt <pa...@gm...> wrote:
> Try doing a remove, restart windows and then redo the install just to
> ensure that everything is honky dory. It shoudn't make a difference
> but windows is a weird beast.
>
> Sam Moffatt
> http://pasamio.id.au
>
>
>
> On Mon, Dec 22, 2008 at 9:19 PM, Tobbe Lundberg <tob...@gm...> wrote:
>> Hi
>>
>> I just installed coLinux 0.7.3 and then dropped the 20081217 snapshot
>> on top of that. I did the --driver-remove --driver-install thing it
>> told me to do. When I try to run coLinux I get the following output:
>>
>> c:\Program\coLinux>colinux-daemon.exe @colinux.conf
>> Cooperative Linux Daemon, 0.8.0
>> Daemon compiled on Wed Dec 17 05:06:10 2008
>>
>> colinux: error, expected kernel API version 12, got 10
>> daemon: exit code 82e6fc03
>> daemon: error driver version, please reinstall driver!
>>
>> What more do I have to do to be able to run coLinux?
>>
>> //Tobbe
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>
>

Re: [coLinux-users] error driver version

[Sam M. <pa...@gm...>]

Try doing a remove, restart windows and then redo the install just to
ensure that everything is honky dory. It shoudn't make a difference
but windows is a weird beast.

Sam Moffatt
http://pasamio.id.au



On Mon, Dec 22, 2008 at 9:19 PM, Tobbe Lundberg <tob...@gm...> wrote:
> Hi
>
> I just installed coLinux 0.7.3 and then dropped the 20081217 snapshot
> on top of that. I did the --driver-remove --driver-install thing it
> told me to do. When I try to run coLinux I get the following output:
>
> c:\Program\coLinux>colinux-daemon.exe @colinux.conf
> Cooperative Linux Daemon, 0.8.0
> Daemon compiled on Wed Dec 17 05:06:10 2008
>
> colinux: error, expected kernel API version 12, got 10
> daemon: exit code 82e6fc03
> daemon: error driver version, please reinstall driver!
>
> What more do I have to do to be able to run coLinux?
>
> //Tobbe
>
> ------------------------------------------------------------------------------
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

Re: [coLinux-users] error driver version

[Tobbe L. <tob...@gm...>]

I'm using the 20081130 .exe snapshot for now. At least I can start that one :)

On Mon, Dec 22, 2008 at 12:54 PM, Tobbe Lundberg <tob...@gm...> wrote:
> I ran "colinux-daemon.exe --remove-driver" to remove the driver. Then
> I ran "colinux-daemon.exe --remove-driver" again just to check that
> everything was good and I got the expected "driver not installed".
> Then I rebooted my computer and when it was back up I did
> "colinux-daemon.exe --install-driver". After that, when I run
> "colinux-daemon.exe @colinux.conf" I get the same error message again
> about the wrong driver version.
>
> On Mon, Dec 22, 2008 at 12:32 PM, Sam Moffatt <pa...@gm...> wrote:
>> Try doing a remove, restart windows and then redo the install just to
>> ensure that everything is honky dory. It shoudn't make a difference
>> but windows is a weird beast.
>>
>> Sam Moffatt
>> http://pasamio.id.au
>>
>>
>>
>> On Mon, Dec 22, 2008 at 9:19 PM, Tobbe Lundberg <tob...@gm...> wrote:
>>> Hi
>>>
>>> I just installed coLinux 0.7.3 and then dropped the 20081217 snapshot
>>> on top of that. I did the --driver-remove --driver-install thing it
>>> told me to do. When I try to run coLinux I get the following output:
>>>
>>> c:\Program\coLinux>colinux-daemon.exe @colinux.conf
>>> Cooperative Linux Daemon, 0.8.0
>>> Daemon compiled on Wed Dec 17 05:06:10 2008
>>>
>>> colinux: error, expected kernel API version 12, got 10
>>> daemon: exit code 82e6fc03
>>> daemon: error driver version, please reinstall driver!
>>>
>>> What more do I have to do to be able to run coLinux?
>>>
>>> //Tobbe
>>>
>>> ------------------------------------------------------------------------------
>>> _______________________________________________
>>> coLinux-users mailing list
>>> coL...@li...
>>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>>>
>>
>

[coLinux-users] error driver version

[Tobbe L. <tob...@gm...>]

Hi

I just installed coLinux 0.7.3 and then dropped the 20081217 snapshot
on top of that. I did the --driver-remove --driver-install thing it
told me to do. When I try to run coLinux I get the following output:

c:\Program\coLinux>colinux-daemon.exe @colinux.conf
Cooperative Linux Daemon, 0.8.0
Daemon compiled on Wed Dec 17 05:06:10 2008

colinux: error, expected kernel API version 12, got 10
daemon: exit code 82e6fc03
daemon: error driver version, please reinstall driver!

What more do I have to do to be able to run coLinux?

//Tobbe

Re: [coLinux-users] Is it possible to use the 1GB of inaccessible memory?

[Henry N. <hen...@ar...>]

Hello Michael

Michael McStarfighter wrote:
> BTW: When will there be a x64 version of coLinux? Anything in the 
> pipeline or the brains of the developers?
I wrote a todo list and some notes about problems:
http://colinux.wikia.com/wiki/Dashboard_for_developing_a_64_bit_coLinux

Additinallny developer needs to have 64 bit Windows. I don't have it.

-- 
Henry N.

Re: [coLinux-users] Is it possible to use the 1GB of inaccessible memory?

[Xuefer <xu...@gm...>]

On Thu, Dec 18, 2008 at 11:09 PM, Michael McStarfighter
<mcs...@gm...> wrote:
> BTW: When will there be a x64 version of coLinux? Anything in the pipeline
> or the brains of the developers?
my top RFE
 1. multi core
 2. x64
 3. share filesystem cache with host os, and activly return memory to host os
i'm sure the user base is ready. ddr2 4G no more than 200RMB
(RMB==CNY, 25~28 USD). 2/3/4 core is popular

Re: [coLinux-users] Is it possible to use the 1GB of inaccessible memory?

[Michael M. <mcs...@gm...>]

BTW: When will there be a x64 version of coLinux? Anything in the pipeline
or the brains of the developers?

2008/12/18 Sam Moffatt <pa...@gm...>

> Actually I think you'll find that for the most part this is actually a
> Windows limitation, see:
> http://support.microsoft.com/kb/283037
>
> Windows the operating system will limit the amount of memory that it
> can address even if the system can support more underneath. So whilst
> it might be an issue with the hardware, these days what is more than
> likely the case is that its an issue with Windows. Of course, it
> doesn't help that both Windows and the x86 instruction set are almost
> the worst performing products in the market (e.g. compared to say
> Linux and PPC respectively) so you're really in a doomed position to
> begin with anyway.
>
> Sam Moffatt
> http://pasamio.id.au
>
>
>
> On Thu, Dec 18, 2008 at 9:28 PM, Michael McStarfighter
> <mcs...@gm...> wrote:
> > I can say: No, it isn't possible. Why? The adress violation begins at the
> > BIOS and the CPU directly. Windows can only use what the CPU and BIOS
> make
> > available. And coLinux can't have more rights then the windows kernel ...
> >
> > 2008/12/18 Louis <net...@ya...>
> >>
> >> Hi,
> >>
> >>  I have a 32-bit Windows system with "4 GB" of RAM, of which of course
> >> only 3GB is accessible, so I was wondering, would it be possible for
> coLinux
> >> to use that inaccessible 1 GB of RAM? Probably not, if it wants to stay
> in
> >> good terms with the Windows kernel huh?
> >>
> >> Yours,
> >>
> >> Louis
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> ------------------------------------------------------------------------------
> >> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
> >> Nevada.
> >> The future of the web can't happen without you.  Join us at MIX09 to
> help
> >> pave the way to the Next Web now. Learn more and register at
> >>
> >>
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> >> _______________________________________________
> >> coLinux-users mailing list
> >> coL...@li...
> >> https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
> >
> >
> ------------------------------------------------------------------------------
> > SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
> Nevada.
> > The future of the web can't happen without you.  Join us at MIX09 to help
> > pave the way to the Next Web now. Learn more and register at
> >
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> > _______________________________________________
> > coLinux-users mailing list
> > coL...@li...
> > https://lists.sourceforge.net/lists/listinfo/colinux-users
> >
> >
>

Re: [coLinux-users] Is it possible to use the 1GB of inaccessible memory?

[Sam M. <pa...@gm...>]

Actually I think you'll find that for the most part this is actually a
Windows limitation, see:
http://support.microsoft.com/kb/283037

Windows the operating system will limit the amount of memory that it
can address even if the system can support more underneath. So whilst
it might be an issue with the hardware, these days what is more than
likely the case is that its an issue with Windows. Of course, it
doesn't help that both Windows and the x86 instruction set are almost
the worst performing products in the market (e.g. compared to say
Linux and PPC respectively) so you're really in a doomed position to
begin with anyway.

Sam Moffatt
http://pasamio.id.au



On Thu, Dec 18, 2008 at 9:28 PM, Michael McStarfighter
<mcs...@gm...> wrote:
> I can say: No, it isn't possible. Why? The adress violation begins at the
> BIOS and the CPU directly. Windows can only use what the CPU and BIOS make
> available. And coLinux can't have more rights then the windows kernel ...
>
> 2008/12/18 Louis <net...@ya...>
>>
>> Hi,
>>
>>  I have a 32-bit Windows system with "4 GB" of RAM, of which of course
>> only 3GB is accessible, so I was wondering, would it be possible for coLinux
>> to use that inaccessible 1 GB of RAM? Probably not, if it wants to stay in
>> good terms with the Windows kernel huh?
>>
>> Yours,
>>
>> Louis
>>
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas,
>> Nevada.
>> The future of the web can't happen without you.  Join us at MIX09 to help
>> pave the way to the Next Web now. Learn more and register at
>>
>> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
>> _______________________________________________
>> coLinux-users mailing list
>> coL...@li...
>> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>
>

Re: [coLinux-users] coLinux-users Digest, Vol 32, Issue 2

[Olaf S. <ca...@gm...>]

"I can say: No, it isn't possible. Why? The adress violation begins at the
BIOS and the CPU directly. Windows can only use what the CPU and BIOS make
available. And coLinux can't have more rights then the windows kernel ..."

This is not quite right. XP prof 32bit is detecting and using maximum of 4gb
ram. The most common misconception is that only 3GB can be used. Actually,
the upper limit is around 3.5GB, for usermode. Single app is maxxed out at
2GB. What happens with the remaining memory? I could roughly explain it, but
better read this article, done by Mark Russinovich:
http://blogs.technet.com/markrussinovich/archive/2008/07/21/3092070.aspx

Re: [coLinux-users] Is it possible to use the 1GB of inaccessible memory?

[Michael M. <mcs...@gm...>]

I can say: No, it isn't possible. Why? The adress violation begins at the
BIOS and the CPU directly. Windows can only use what the CPU and BIOS make
available. And coLinux can't have more rights then the windows kernel ...

2008/12/18 Louis <net...@ya...>

> Hi,
>
>  I have a 32-bit Windows system with "4 GB" of RAM, of which of course only
> 3GB is accessible, so I was wondering, would it be possible for coLinux to
> use that inaccessible 1 GB of RAM? Probably not, if it wants to stay in good
> terms with the Windows kernel huh?
>
> Yours,
>
> Louis
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you.  Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
>
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
>

[coLinux-users] Is it possible to use the 1GB of inaccessible memory?

[Louis <net...@ya...>]

Hi,

 I have a 32-bit Windows system with "4 GB" of RAM, of which of course only 3GB is accessible, so I was wondering, would it be possible for coLinux to use that inaccessible 1 GB of RAM? Probably not, if it wants to stay in good terms with the Windows kernel huh?

Yours,

Louis



      

Re: [coLinux-users] ndis-bridge can't work well with pppoe?

[Henry N. <hen...@ar...>]

> On 24.11.2008 15:32, panhudie gmail wrote:
>> I tried to use pppoe in colinux, but pppoeconf can't find modem when
>> using ndis-bridge, changing to pcap-bridge seems not have this problem.
>>
>> I tested the latest version coLinux-20081123 under a winxp sp3 machine
>> and a win2003 sp2 machine. The host Windows's network card is connected
>> to a switch, and the switch is connected to a adsl modem.

Thanks for your report. All packet types will bridge now, not only ARP 
and IP.
The new filter rule is your MAC for the coLinux interface and broadcasts.

Is committed as SVN revision r1151 and todays snapshot included the 
changes http://www.colinux.org/snapshots/

-- 
Henry N.

Re: [coLinux-users] ndis-bridge can't work well with pppoe?

[Henry N. <hen...@ar...>]

On 24.11.2008 15:32, panhudie gmail wrote:
> I tried to use pppoe in colinux, but pppoeconf can't find modem when
> using ndis-bridge, changing to pcap-bridge seems not have this problem.
>
> I tested the latest version coLinux-20081123 under a winxp sp3 machine
> and a win2003 sp2 machine. The host Windows's network card is connected
> to a switch, and the switch is connected to a adsl modem.

I can confirm the problem. Please feel free to fillout a bug report
https://sourceforge.net/tracker/?func=add&group_id=98788&atid=622063

-- 
Henry N.