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 Windwos 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 Windwos 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
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 hav a 64 bit application. HenryNe 22:09, December 17, 2009 (UTC)
Disabling driver signin 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)