Talk:Dashboard for developing a 64 bit coLinux

TAP Win32 won't work on XP64 - you need TAP Win64

Is this true? I run XP x64 and have a TAP Win32 network device which works just fine.

I have only tested Windows Server 2008 64bit. I don't have XP 64bit. I don't think you can use 32bit drivers in 64bit Windows. But you can use 32bit programs. Are you shure, that your Windows XP is 64bit? Running a 32bit Windows on 64bit CPU is ok, and no problems. What says the overview from key code "Windows + Pause"? What says the coLinux-Installer, if you try to install coLinux there? Our installer has a detection for running 64bit OS and would you block from installing very shortely after start with an error message. HenryNe 20:21, 16 April 2009 (UTC)

32 bit compatability ....

.... is not actually something of import. it would be better to simply do a 64 bit build of colinux. this would ensure that the code can be optimized for 64 bit systems and there would be no need to worry about 32 bit constraints that would make life harder for the maintainer.

as it is if you were to do a pure 64 bit build you could strike about half of the problems from the list.

it is obvious that such a decision would mean that colinux would have (basically) 2 code bases but it would ensure that both versions could be best optimized for said architecture.

chuck

I dont care if colinux64 would run 2ms faster than a 32 bit Version. What I care is that it runs on 64 bit, so the optimization should bet the very last step!

MrKra

Porting the driver to 64 bit should be enough

AFAIK a linux64.sys version should do it, since WoW64 should handle the rest. If this is true, everything else can remain as it is.

Bebbo

Yes, WoW64 helps to run 32 bit applications. But, we must change the driver API between linux64.sys and the daemons, and between Linux kernel and Daemons to work with 64 bit sizes of variables. So, we need also to change the daemons, and in this step we would have a 64 bit application. HenryNe 22:09, December 17, 2009 (UTC)

Disabling driver signing check in vista/win7

"Driver signing can also be bypassed in Windows Vista/7, so I wouldn't worry about driver signing"

Please don't think like this. Checking for driver signature is a good extra security protection, so disabling it will just make it easier to install a malicious driver by mistake (some windows users might actually do something like this)

Driver signing would prevent us to use our self build driver. So, it is everybody own decision to use non-signed drivers, or use self signed drivers, or - in the last case - don't run coLinux. HenryNe 18:20, February 26, 2010 (UTC)

These guys offer free signing for open source projects - Reactos Foundation driver signing. Perhaps for releases these people can help? Cloudy 90.208.157.115 14:02, February 5, 2011 (UTC)

Fixing the casts from pointer to int

This is mostly a matter of replacing ints with ptrdiff_t or size_t on all variables that use these casts isn't it?91.11.116.204 09:52, September 17, 2011 (UTC)

the mingw version mentioned is gone, which one to use

tried this one, http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/sezero_4.5_20111101/mingw-w64-bin_i686-linux_20111101_sezero.tar.gz/download

seems missing libmpc.so.2, have to install libmpc2, libmpfr4 to host linux i686 and link them manually

would that easier to make a colinux guest inside 64bit linux first?

only need to compile the colinux guest in 64bit and fix the passage page. Ofcouse that still requires to fix all the 64/32 register conversion.

76.254.42.33 22:07, May 27, 2012 (UTC)sunyin

project schedule

Hello everybody,

I am a new member at the wikia community and I hope you can help me regarding my question.

I just wanted to know if anybody can tell me if there is a project schedule with developing the 64 bit coLinux.

The reason therefore is: Our company sells an industry product which has the possibility to have an own HMI created by the customer.

Regarding this HMI development we offer a programming package in combination with Qt to run on our embedded Linux system.
Therefore we use coLinux to get the necessary so-files.
Nowadays many customers have a 64-bit Windows7 engineering system and want to have the comfort not to change to a virtual machine to get the code from coLinux.

Therefore my question: Can anybody tell me if there is a defined project end or if there are perhaps some problems which might cause more time?

Thank you very much in advance for the help and pointing me to a direction.

Alwe1704 (talk) 07:31, August 8, 2014 (UTC)