search for: cautio

Hi I am running chisq as below and getting a warning. Can anyone tell me the significance or the warning? > chisq.test(c(10 ,4 ,2 ,6 ,5 ,3 ,4 ,4 ,6 ,3 ,2 ,2 ,2 ,4 ,7 ,10 ,0 ,6 ,19 ,3 ,2 ,7 ,2 ,2 ,2 ,1 ,32 ,2 ,3 ,10 ,1 ,3 ,9 ,4 ,10 ,2 ,2 ,4 ,5 ,7 ,6 ,3 ,7 ,4 ,3 ,3 ,7 ,1 ,4 ,2 ,2 ,3 ,3 ,5 ,5 ,4 ), p =c(0.01704142 ,0.017988166 ,0.018224852 ,0.017751479 ,0.017988166 ,0.018224852 ,0.017278107

...uild from sources) Forest function level: (Windows) 2008 R2 Domain function level: (Windows) 2008 R2 DNS via BIND_DLZ with bind version 9.9.5 (Extended Support Version) The domain was created with samba3 as an NT-style domain and migrated with samba 4.0.7(?) using classicupgrade. Since I'm a cautios guy I tried this with a copy of my live env in an isolated vlan first (cloned my dc VMs, added a windows vm) Doing this allowed me a bit of testing while debugging the problem. The windows dc I'm trying to add is running windows 2008 r2 standard edition with the latest patches. I tried witho...

Yes, it should find windows.h with the default configuration. But you have to be suspicious of beta code that Microsoft gives out for free. It might just be very buggy, or it might be deliberately crippled. Considering the price tag on Visual Studio, it's one or the other (and probably both). Out of curiosity, did it accept the solution and project files as is, or did it want to

----Original Message Follows---- From: Jeff Cohen <jeffc at jolt-lang.org> Reply-To: jeffc at jolt-lang.org, LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> Subject: Re: [LLVMdev] VC++: Cannot open include file: 'windows.h': No suchfile or directory Date: Tue, 21 Dec 2004 16:29:47 -0800

...icrosoft gives out for free. It might >just be very buggy, or it might be >deliberately crippled. Considering the >price tag on Visual Studio, it's one or the other (and >probably both). For a month ago I was at a .NET seminar hosted by MS and the spokesman said, you should be cautios with beta software. They don't delibrately cribble the software, but sometimes, depending on the scope of the build, known errors e.t.c., they disable known buggy or other functionality. And I did take it that way. >Out of curiosity, did it accept the solution and project files as is, o...