Re: [coLinux-devel] coLinux on NT4?

[Benoit M. <ben...@cg...>]

Hi

I'd like to use it at work, where i'm still using nt4 (really heavy to use
cL through vmware)
It is for a real usage AND optionnaly ;) for my pleasure ;)
but at home.... XP, colinux rulez
what do you mean by BSOD??
and the daemon doesn't trapp, just show a messagebox with "device driver
d:\col\linux.sys was unable to find entry point for ExFreePoolWithTag in
ntoskrnl.exe driver" (litteral traduction, original was in french ;) ) then
close the windows when I click on OK.

It all began with the same symptoms complaining about GlobalMemoryStatusEx
(not supported by NT4)
I made these modifications in /src/colinux/os/winnt/user/misc.c

diff says :
20,21c20,21
<  MEMORYSTATUSEX m;
<  BOOL ret;
---
>  MEMORYSTATUS m;
>  //BOOL ret;
24,25c24,25
<  ret = GlobalMemoryStatusEx(&m);
<  if (ret != TRUE) {
---
>  /*ret = */GlobalMemoryStatus(&m);
>  /*if (ret != TRUE) {
28c28
<  }
---
>  }*/
30c30
<  if (m.ullTotalPhys > (DWORDLONG)0xFF000000) {
---
>  if (m.dwTotalPhys > (DWORDLONG)0xFF000000) {
36c36
<  *mem_size = 0xFF000000 & (((unsigned long)m.ullTotalPhys) + 0xFFFFFF);
---
>  *mem_size = 0xFF000000 & (((unsigned long)m.dwTotalPhys) + 0xFFFFFF);


just using GlobalMemoryStatus instead of GlobalMemoryStatusEx (my NT4 system
is far below the 2GB limit ;) )

no pb anymore to compile it at home using cobuild.sh (edited to not
averwrite my modifications)
and when I tried it today here, the daemon complains about ExFreePoolWithTag

When I look at my NTOSKRNL.EXE (v4.00) it exports ExFreePool but not
ExFreePoolWithTag

The doc I found say that nt4 SP4 workstation support this API, i'm in sp6a.

Benoit


----- Original Message -----
From: "Digital Infra, Inc." <ok...@di...>
To: "Benoit MICHEL" <bem...@ca...>
Cc: "Cooperative Linux Development" <col...@li...>
Sent: Tuesday, March 02, 2004 4:07 PM
Subject: Re: [coLinux-devel] coLinux on NT4?


>
> Hello
>
> BTW, Why you have an interest about coLinux on NT4?
> Just your hobby? or you have real usage?
> but, at least, I welcome your effort very much.
> because, with your effort, we can collect more hints to
> stabilize coLinux. thanks Benoit!.
> and please give us your history of BSOD with a stack trace.
>
>             --- Okajima.