colinux-users — coLinux users mailing list

Re: [coLinux-users] colinux cannot start working!

[Dustin W. <dus...@ya...>]

--- »ª·ã ÁÖ <lh...@ya...> wrote:
>        When I use the colinux, I meet a strange
> problem. I have install the colinux and exact the
> Debian-3.0r0.ext3.1gb to the install  directory. And
> then I edit the default.colinux.xml(the install
> directory is f:\colinux):

As was already pointed out this is because you must
specify the configuration file when you execute
colinux-daemon.exe. If you want to be able to start
coLinux by double clicking an icon then you could add
the following to a .bat file and then double click the
icon for that file.

REM BEGIN COLINUX.BAT
@echo off
f:
cd "f:\colinux"
colinux-daemon.exe -c default.colinux.xml
REM END COLINUX.BAT

Good luck,
Dustin
http://www.daemonmaker.net

Re: [coLinux-users] colinux cannot start working!

[<ti...@fu...>]

I have to use command prompt and cd to the directory, then type=20

colinux-daemon.exe -c default.xml (or whatever your configuration
file happens to be named)


On Tue, 10 Aug 2004, [gb2312] =BB=AA=B7=E3 =C1=D6 wrote:

>        When I use the colinux, I meet a strange problem. I have install t=
he colinux and exact the Debian-3.0r0.ext3.1gb to the install  directory. A=
nd then I edit the default.colinux.xml(the install directory is f:\colinux)=
:
> =20
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <colinux>
>     <!-- This line needs to point to your root file system.=20
>     For example change "root_fs" to the name of the Debian image.
>          Inside coLinux it will be /dev/cobd0 -->
>     <block_device index=3D"0" path=3D"\DosDevices\f:\colinux\Debian-3.0r0=
=2Eext3.1gb"=20
>     enabled=3D"true" />
>    =20
>     <!-- This line can specify a swap file if you wish, or an additional
>          image file, it will /dev/cobd1. Additional block_devices can
>   be specified in the same manner by increasing the index -->
>     <block_device index=3D"1" path=3D"\DosDevices\f:\coLinux\swap_device"=
=20
>     enabled=3D"false" />
>     <!-- bootparams allows you to pass kernel boot parameters -->
>     <bootparams>root=3D/dev/cobd0</bootparams>
>     <!-- image allows you to specify the kernel to boot -->
>     <image path=3D"vmlinux" />
>     <!-- this line allows you to specify the amount of memory available=
=20
>          to coLinux -->
>     <memory size=3D"64" />
>     <!-- This allows you to modify networking parameters, see the README=
=20
>          or website for more information -->
>     <network index=3D"0" type=3D"tap" name=3D"TAP"/>
> </colinux>
> =20
>      But when I double clip the colinux-daemon.exe, only can see that a D=
OS-like window thrills through the screen and then nothing is left. I want =
to know what is wrong with my colinux.
>     Thank you very much!
>                                                                   Hua-fen=
g LIN
>=20
>=20
>=20
>=20
>=20
> ---------------------------------
> Do You Yahoo!?
> 150=CD=F2=C7=FAMP3=B7=E8=BF=F1=CB=D1=A3=AC=B4=F8=C4=FA=B4=B3=C8=EB=D2=F4=
=C0=D6=B5=EE=CC=C3
> =C3=C0=C5=AE=C3=F7=D0=C7=D3=A6=D3=D0=BE=A1=D3=D0=A3=AC=CB=D1=B1=E9=C3=C0=
=CD=BC=A1=A2=D1=DE=CD=BC=BA=CD=BF=E1=CD=BC
> 1G=BE=CD=CA=C71000=D5=D7=A3=AC=D1=C5=BB=A2=B5=E7=D3=CA=D7=D4=D6=FA=C0=A9=
=C8=DD=A3=A1

--=20
timo

[coLinux-users] colinux cannot start working!

[<lh...@ya...>]

       When I use the colinux, I meet a strange problem. I have install the colinux and exact the Debian-3.0r0.ext3.1gb to the install  directory. And then I edit the default.colinux.xml(the install directory is f:\colinux):
 
<?xml version="1.0" encoding="UTF-8"?>
<colinux>
    <!-- This line needs to point to your root file system. 
    For example change "root_fs" to the name of the Debian image.
         Inside coLinux it will be /dev/cobd0 -->
    <block_device index="0" path="\DosDevices\f:\colinux\Debian-3.0r0.ext3.1gb" 
    enabled="true" />
    
    <!-- This line can specify a swap file if you wish, or an additional
         image file, it will /dev/cobd1. Additional block_devices can
  be specified in the same manner by increasing the index -->
    <block_device index="1" path="\DosDevices\f:\coLinux\swap_device" 
    enabled="false" />
    <!-- bootparams allows you to pass kernel boot parameters -->
    <bootparams>root=/dev/cobd0</bootparams>
    <!-- image allows you to specify the kernel to boot -->
    <image path="vmlinux" />
    <!-- this line allows you to specify the amount of memory available 
         to coLinux -->
    <memory size="64" />
    <!-- This allows you to modify networking parameters, see the README 
         or website for more information -->
    <network index="0" type="tap" name="TAP"/>
</colinux>
 
     But when I double clip the colinux-daemon.exe, only can see that a DOS-like window thrills through the screen and then nothing is left. I want to know what is wrong with my colinux.
    Thank you very much!
                                                                  Hua-feng LIN





---------------------------------
Do You Yahoo!?
150万曲MP3疯狂搜，带您闯入音乐殿堂
美女明星应有尽有，搜遍美图、艳图和酷图
1G就是1000兆，雅虎电邮自助扩容！

[coLinux-users] Re: only half of memory detected

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

Dani Ridhaswana, dando pulos de alegria, escreveu :
> Hi,
> 
> I have Z-pro machine with 4GB RAM installed. On
> colinux xml file I tried to use 1000MB of memory for
> colinux, but it's detected only ~500MB. Do you know
> why? Is it because I used 1024MB image file for swap?

CoLinux memory is limited by kernel memory.
Windows (and Linux in some configs) uses 2GB for user space and 2GB for 
kernel space, so you can only use 2GB for all your kernel address space.

Your graphics card AGP memory is also mapped into the kernel address 
space, which will probably give you only the ~500MB you say you have 
left (also, it's not easy to fit all kernel objects inside only 1GB of 
memory - that includes bitmaps (your desktop background), as GDI is in 
kernel space).

The swap file is not relevant.
The only fix I know is going for a 64 bits OS. There are some hacks for 
the normal 32 bits Linux to address more memory, but the real solution 
is 64-bit Linux and/or 64-bit Windows as the host OS (note that Linux 
doesn't use as much kernel memory as Windows, so the problem is not so big).

> Another question, can TAP-win32 driver has 100Mbps
> instead of 10Mbps connection?

That value is not relevant.
The network interface is known to be slow, but remember colinux is still 
in an early phase of development ;)

Regards,
~Nuno Lucas

[coLinux-users] UPDATE: LANless Networking between host and coLinux

[Dustin W. <dus...@ya...>]

Last week I sent out a question regarding how to setup
communication between the host OS and the coLinux OS
even though the host was not connected to a network
(see below for the original message). First I want to
thank those who responded with ideas. Second I want to
post the solution that I am using in case anyone else
is confronted with the same problem. It turns out all
I had to do was use the TAP interface and set it's
"Media Status" configuration option to "Always
Connected." I would have had this working sooner had I
figured out how to correctly configure coLinux to use
TAP in the first place. The reason I couldn't get the
coLinux OS and my host OS to communicate through TAP
was because I had set the "name" attribute of the
network element in my configuration file so that I
could use bridged networking. I didn't realize it
needed to be unset when the "type" attribute is set to
"tap." After making this change everything worked
because I already had both the coLinux interface and
the TAP adapter correctly configured. In the end it
was a simple mistake on my part :)

Thanks again for all the help,
Dustin
http://www.daemonmaker.net

--- Dustin Webb <dus...@ya...> wrote:
> Date: Fri, 6 Aug 2004 10:35:01 -0700 (PDT)
> From: Dustin Webb <dus...@ya...>
> Subject: LANless Networking between host and coLinux
> To: col...@li...
> 
> After that subject you're probably asking yourself
> "What does this guy want to do?" My problem seems
> fairly simple and while I've heard that there is a
> solution, I haven't found it. I want to be able to
> communicate between the host OS (in this case ms
> windows xp) and my coLinux OS via TCP/IP while the
> host machine *isn't* connected to a network. So far
> my
> experience has been, I unplug my box from the
> network
> and XP unloads the network drivers. I've checked the
> Wiki, spoken with a couple of people in IRC and have
> been perusing the mailing list archives with no
> luck.
> Can anyone offer any tips or point me towards the
> appropriate documention?
> 
> TIA from a first time poster,
> Dustin
> http://www.daemonmaker.net
> 

Re: [coLinux-users] LANless Networking between host and coLinux

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

Dustin Webb wrote:
> After that subject you're probably asking yourself
> "What does this guy want to do?" My problem seems
> fairly simple and while I've heard that there is a
> solution, I haven't found it. I want to be able to
> communicate between the host OS (in this case ms
> windows xp) and my coLinux OS via TCP/IP while the
> host machine *isn't* connected to a network. So far my
> experience has been, I unplug my box from the network
> and XP unloads the network drivers. I've checked the
> Wiki, spoken with a couple of people in IRC and have
> been perusing the mailing list archives with no luck.
> Can anyone offer any tips or point me towards the
> appropriate documention?
> 
> TIA from a first time poster,
> Dustin
> http://www.daemonmaker.net

That's right. I'm also use coLinux without network.
I'm not using bridging mode.

If you have installed coLinux, you should have two network adapters:
   1. real network and
   2. colinux "TAP-Win32 Adapter V8 (coLinux)"
I have renamed the coLinux TAP (in network connections) from 
LAN-Connection into "LAN colinux", so I can see which of these is the 
right LAN.
Than give TAP driver a other network as your real network.

Sample of my system
Real network under XP:
   1. LAN-Connection: 192.168.0.71
   default gateway: 192.168.0.1
   2. TAP coLinux: 192.168.4.200

Inside coLinux
   TAP driver: 192.168.4.10
   default gateway: 192.168.4.200

Connection between coLinux and XP goes only over network 192.168.4.0 and 
never outside of my computer. (with and without real LAN connected)

If I need connection from coLinux to computer outside of XP, I need some 
static routings and gateways in XP.

Henry

RE: [coLinux-users] only half of memory detected

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

> 
> Another question, can TAP-win32 driver has 100Mbps
> instead of 10Mbps connection?
afaict the reported connection speed is meaningless anyway
colinux networking probablly could do with some performance tweaking though
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.735 / Virus Database: 489 - Release Date: 06/08/2004

Re: [coLinux-users] coLinux/XP/IEEE 1394

[Dustin W. <dus...@ya...>]

--- Daniel Slater <dan...@ya...> wrote:
> I believe the IEEE 1394 Net adapter is actually a
> fire-wire port. I have a machine with a fire-wire
> port and it shows up this way on my machine. I
> believe Microsoft did this to support kernel
> debugging over fire-wire.

I guess I don't understand what you are trying to tell
me. The problem I am having is that I can't get my
host OS to communicate with my coLinux OS. In this
particular case the name of my network adapter is
"IEEE 1394 NET adapter" and it does not offer, as far
as I know, a configuration option like the "Checksum
Offload" option found on the Broadcom NICs. Are you
trying to tell me that I can't get this to work using
this NIC?

Thanks,
Dustin
http://www.daemonmaker.net

Re: [coLinux-users] coLinux/XP/IEEE 1394

[Daniel S. <dan...@ya...>]

I believe the IEEE 1394 Net adapter is actually a fire-wire port. I have a machine with a fire-wire port and it shows up this way on my machine. I believe Microsoft did this to support kernel debugging over fire-wire.

 


Dustin Webb <dus...@ya...> wrote:I've run into an interesting issue in which the host
OS (ms windows xp) and the coLinux OS cannot
communicate. On my desktop this works fine because I
disabled the Checksum Offload feature of my network
adapter. But on the laptop I am working with this does
not appear to be an option. I don't know if it
matters, but the adapter shows up as an IEEE 1394 NET
adapter. Does anyone know how to resolve this issue?

Thanks,
Dustin
http://www.daemonmaker.net


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
coLinux-users mailing list
coL...@li...
https://lists.sourceforge.net/lists/listinfo/colinux-users



Daniel R. Slater mailto:dan...@ya...

[coLinux-users] only half of memory detected

[Dani R. <rid...@ya...>]

Hi,

I have Z-pro machine with 4GB RAM installed. On
colinux xml file I tried to use 1000MB of memory for
colinux, but it's detected only ~500MB. Do you know
why? Is it because I used 1024MB image file for swap?

Another question, can TAP-win32 driver has 100Mbps
instead of 10Mbps connection?

thx in adv.
-Dani-


		
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 

[coLinux-users] Mouse and keyboard problems

[Tomas <tom...@2p...>]

Where is connected mouse in colinux to? In my real dual boot linux I
have link /dev/mouse to /dev/psaux but it does not work (device
/dev/mouse does not exist). I have PS2 mouse but it's probably not
important due virtualization. Can anybody help?

Second problem is with keyboard. Always when I enter to terminal (after
start, Alt+F2, ...) navigation keys does not work (writes digits), I
must press NumLock to get in work (does not matter if NumLock LED shines
- it switches num keyboard for other application). Shift+PgDn/Up does
not work, so is not possible make listing in terminal window.

Regards
Tomas

[coLinux-users] Re: LANless Networking between host and coLinux

[Martin K. <ka...@po...>]

Hi Dustin,

did you tried to install Microsoft Loopback device? if you configure 
this the same way as your ethernet device you should be able to get it 
working. you can't have two devices on same network so if you have just 
disabled your lan you have to use another one, e.g.:
LAN IP: 192.168.0.2 Mask:255.255.255.0
LoopBack: 192.168.1.2 Mask:255.255.255.0

and than you have to change your config to something like this:
<network index="0" type="bridged" name="Loopback Connection" />

and you have to configure your linux to setup eth0 in 192.168.1.x 
network. e.g. (using debian):
/etc/network/interfaces:
....
iface eth0 inet static
	address 192.168.1.1
	netmask 255.255.255.0

but i would prefer to use TAP - seems to be faster.

Regards,
Martin

Dustin Webb wrote:
> Any other
> thoughts?

[coLinux-users] Thanks for the newest console

[baldyeti <e_...@ho...>]

I just installed the latest snapshot available and am very pleased
with the improvements in the console keyboard support. This is 
a godsend for all non english/qwerty users. 

Many many thanks to whomever implemented it!
(Sascha according to the NEWS file) 

On a related note, when I was using the minimal debian image,
I noticed that loadkeys was not available, making it more complicated
than it ougt to for intl users. Not sure this is the right place for 
suggestions, but if those images are ever updated, please consider the
appropriate package (sorry, dunno which one) for inclusion.

RE: [coLinux-users] LANless Networking between host and coLinux

[Dustin W. <dus...@ya...>]

--- peter green <plu...@p1...> wrote:
> if you are using winpcap based netwokring and want
> to use it with the network unplugged you will need
to
> disable media sense on your network card

I should have mentioned that I looked for this option
in the configuration of my network card but it's not
available. It is available on the TAP interface but I
haven't been able to get my coLinux OS to speak with
my host OS through the TAP interface. I adjusted the
network element of the configuration file such that
type="tap" and assigned the TAP interface a static ip,
but it didn't work. I'm not really sure what I am
doing wrong with that configuration. Any other
thoughts?

Thanks,
Dustin
http://www.daemonmaker.net

Re: [coLinux-users] LANless Networking between host and coLinux

[Dustin W. <dus...@ya...>]

--- Tim Hunter <ti...@br...> wrote:
> Dustin Webb wrote:
> > After that subject you're probably asking yourself
> > "What does this guy want to do?" My problem seems
> > fairly simple and while I've heard that there is a
> > solution, I haven't found it. I want to be able to
> > communicate between the host OS (in this case ms
> > windows xp) and my coLinux OS via TCP/IP while the
> > host machine *isn't* connected to a network. So
> far my
> > experience has been, I unplug my box from the
> network
> > and XP unloads the network drivers. I've checked
> the
> > Wiki, spoken with a couple of people in IRC and
> have
> > been perusing the mailing list archives with no
> luck.
> > Can anyone offer any tips or point me towards the
> > appropriate documention?
> >
> 
>
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q239/9/24.asp&NoWebContent=1

Looked promising, but unfortunately it did not work.
XP still unloaded the drivers.

Dustin
http://www.daemonmaker.net

[coLinux-users] coLinux/XP/IEEE 1394

[Dustin W. <dus...@ya...>]

I've run into an interesting issue in which the host
OS (ms windows xp) and the coLinux OS cannot
communicate. On my desktop this works fine because I
disabled the Checksum Offload feature of my network
adapter. But on the laptop I am working with this does
not appear to be an option. I don't know if it
matters, but the adapter shows up as an IEEE 1394 NET
adapter. Does anyone know how to resolve this issue?

Thanks,
Dustin
http://www.daemonmaker.net

RE: [coLinux-users] LANless Networking between host and coLinux

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

if you are using winpcap based netwokring and want to use it with the
network unplugged you will need to disable media sense on your network card

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Dustin
> Webb
> Sent: 06 August 2004 18:35
> To: col...@li...
> Subject: [coLinux-users] LANless Networking between host and coLinux
>
>
> After that subject you're probably asking yourself
> "What does this guy want to do?" My problem seems
> fairly simple and while I've heard that there is a
> solution, I haven't found it. I want to be able to
> communicate between the host OS (in this case ms
> windows xp) and my coLinux OS via TCP/IP while the
> host machine *isn't* connected to a network. So far my
> experience has been, I unplug my box from the network
> and XP unloads the network drivers. I've checked the
> Wiki, spoken with a couple of people in IRC and have
> been perusing the mailing list archives with no luck.
> Can anyone offer any tips or point me towards the
> appropriate documention?
>
> TIA from a first time poster,
> Dustin
> http://www.daemonmaker.net
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004

Re: [coLinux-users] LANless Networking between host and coLinux

[Tim H. <ti...@br...>]

Dustin Webb wrote:
> After that subject you're probably asking yourself
> "What does this guy want to do?" My problem seems
> fairly simple and while I've heard that there is a
> solution, I haven't found it. I want to be able to
> communicate between the host OS (in this case ms
> windows xp) and my coLinux OS via TCP/IP while the
> host machine *isn't* connected to a network. So far my
> experience has been, I unplug my box from the network
> and XP unloads the network drivers. I've checked the
> Wiki, spoken with a couple of people in IRC and have
> been perusing the mailing list archives with no luck.
> Can anyone offer any tips or point me towards the
> appropriate documention?
>

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q239/9/24.asp&NoWebContent=1

> TIA from a first time poster,
> Dustin
> http://www.daemonmaker.net
>
>

[coLinux-users] LANless Networking between host and coLinux

[Dustin W. <dus...@ya...>]

After that subject you're probably asking yourself
"What does this guy want to do?" My problem seems
fairly simple and while I've heard that there is a
solution, I haven't found it. I want to be able to
communicate between the host OS (in this case ms
windows xp) and my coLinux OS via TCP/IP while the
host machine *isn't* connected to a network. So far my
experience has been, I unplug my box from the network
and XP unloads the network drivers. I've checked the
Wiki, spoken with a couple of people in IRC and have
been perusing the mailing list archives with no luck.
Can anyone offer any tips or point me towards the
appropriate documention?

TIA from a first time poster,
Dustin
http://www.daemonmaker.net

[coLinux-users] nt console keymaps

[Sam L. <sa...@li...>]

I've head that the nt console can't be made to use a UK keymap but 
recently I booted a debian install disk under colinux and selected a 
british keyboard and it worked - the right keys generated the right 
characters.

I cant get te debian console-data package to work on the supplied images 
tho, so it still doesn't work for my real setup.

Sam

[coLinux-users] Re: Simulateous installations of 0.6.1 and 0.6.2

[Sam L. <sa...@li...>]

peter green wrote:
> you can afaict only have one version of the colinux driver installed at a
> time
> 
> however you can use
> 
> colinux-daemon --remove-driver
> colinux-daemon --install-driver

I dont think this is true. I have two versions of the TAP driver 
installed on my system and I can add new LAN devices using either driver.

Sam

> 
> to uninstall whatever driver is currently installed and install the one from
> the copy of colinux you are working with
> 
> 
>>-----Original Message-----
>>From: col...@li...
>>[mailto:col...@li...]On Behalf Of Brendan J
>>Simon
>>Sent: 05 August 2004 03:17
>>To: col...@li...
>>Subject: [coLinux-users] Simulateous installations of 0.6.1 and 0.6.2
>>
>>
>>Hi all,
>>
>>Is it possible to have 0.6.1 and 0.6.2 coexist on my WinXP box ???
>>
>>I tried installing the 20040710 snapshot and it was having problems with
>>the ethernet driver.  I then retried my 0.6.1 system and it wouldn't
>>work at all.  The only way I could get the 0.6.1 to work was to
>>reinstall it.
>>
>>Any howtos or suggestions to have both installed ??
>>
>>Cheers,
>>Brendan Simon.
>>
>>
>>
>>-------------------------------------------------------
>>This SF.Net email is sponsored by OSTG. Have you noticed the changes on
>>Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
>>one more big change to announce. We are now OSTG- Open Source Technology
>>Group. Come see the changes on the new OSTG site. www.ostg.com
>>_______________________________________________
>>coLinux-users mailing list
>>coL...@li...
>>https://lists.sourceforge.net/lists/listinfo/colinux-users
>>---
>>Incoming mail is certified Virus Free.
>>Checked by AVG anti-virus system (http://www.grisoft.com).
>>Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004
>>
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com

Re: [coLinux-users] Swap Partition

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

Andrew Myers wrote:

> I have a 1GB swap partition on my system from a dual boot Redhat
> installation I used to have.  Is it possible to tell coLinux to use this,
> even though I'm running my root filesystem from my C drive as follows:
> 
>     <block_device index="0"
> path="\DosDevices\c:\coLinux\Debian-3.0r0.ext3.1gb" 
>     enabled="true" />
> 
> Thanks,
> Andrew.

http://www.colinux.org/wiki/index.php/WindowsDevicePaths

I'm use /dev/hda5 from real linux also for coLinux. This is the line in 
config.xml:
     <block_device index="5" path="\Device\Harddisk0\Partition4"
     alias="hda5"
     enabled="true" />

Remember: Extended Partion was not count under WinXP, so windows use 
partion4 and linux is hda5 (the first partion in extended partion).

Verify the size on boot, before you use this!
	cobd5 size: 1048576 kb

Henry

RE: [coLinux-users] Simulateous installations of 0.6.1 and 0.6.2

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

you can afaict only have one version of the colinux driver installed at a
time

however you can use

colinux-daemon --remove-driver
colinux-daemon --install-driver

to uninstall whatever driver is currently installed and install the one from
the copy of colinux you are working with

> -----Original Message-----
> From: col...@li...
> [mailto:col...@li...]On Behalf Of Brendan J
> Simon
> Sent: 05 August 2004 03:17
> To: col...@li...
> Subject: [coLinux-users] Simulateous installations of 0.6.1 and 0.6.2
>
>
> Hi all,
>
> Is it possible to have 0.6.1 and 0.6.2 coexist on my WinXP box ???
>
> I tried installing the 20040710 snapshot and it was having problems with
> the ethernet driver.  I then retried my 0.6.1 system and it wouldn't
> work at all.  The only way I could get the 0.6.1 to work was to
> reinstall it.
>
> Any howtos or suggestions to have both installed ??
>
> Cheers,
> Brendan Simon.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004
>
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.734 / Virus Database: 488 - Release Date: 04/08/2004

[coLinux-users] Simulateous installations of 0.6.1 and 0.6.2

[Brendan J S. <Bre...@fa...>]

Hi all,

Is it possible to have 0.6.1 and 0.6.2 coexist on my WinXP box ???

I tried installing the 20040710 snapshot and it was having problems with 
the ethernet driver.  I then retried my 0.6.1 system and it wouldn't 
work at all.  The only way I could get the 0.6.1 to work was to 
reinstall it.

Any howtos or suggestions to have both installed ??

Cheers,
Brendan Simon.

Re: [coLinux-users] Any plans to support hyperthreading?

[Chris D. <da...@ya...>]

I believe that this is an old issue.  I am running the most current snapshot on
a hyperthreaded p4 with no problems. 

Look in http://colinux.org/snapshots/

--Chris


--- Glen Stampoultzis <gs...@gm...> wrote:

> I've got a hyperthreaded system.  I'd rather not turn it off if
> possible.  Are there any plans for support of hyperthreading in
> colinux?
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by OSTG. Have you noticed the changes on
> Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
> one more big change to announce. We are now OSTG- Open Source Technology
> Group. Come see the changes on the new OSTG site. www.ostg.com
> _______________________________________________
> coLinux-users mailing list
> coL...@li...
> https://lists.sourceforge.net/lists/listinfo/colinux-users
> 


=====
There is a very fine line between "hobby" and "mental illness." --Dave Barry
Linux DVDs: http://www.LinuxDVDs.com
beginners robotics: http://www.robots101.com
personal pages: http://www.dahlweb.net