Displaying 6 results from an estimated 6 matches for "m57".
Did you mean:
57
2011 Sep 02
1
[PATCH 0/7] hivex + hivexml: Add byte runs for nodes and values
...s byte run reporters for node and value metadata in the
hivexml program. This location reporting required several new ABI
functions, which required new ABI return types. One benefit to the byte
run functions is additional sanity checks, which have revealed new data
or parsing errors when run on M57 patents images. An example error:
Image: Charlie, 2009-12-11, available at <http://digitalcorpora.org/corpora/scenarios/m57-patents-scenario>.
hive: C:/WINDOWS/system32/config/SECURITY
Address 12624 is processed as a value, but it has a node signature.
Alex Nelson (7):
generator: Add ne...
2010 May 19
8
Generating all possible models from full model
...mantas~sinmonth+coslunar, data=mydata))
m46<-glm.convert(glm.nb(mantas~sinmonth+sinlunar, data=mydata))
m47<-glm.convert(glm.nb(mantas~sinmonth+plankton, data=mydata)) #Interaction term? Plankton may vary by season
m56<-glm.convert(glm.nb(mantas~coslunar+sinlunar, data=mydata))
m57<-glm.convert(glm.nb(mantas~coslunar+plankton, data=mydata))
m67<-glm.convert(glm.nb(mantas~sinlunar+plankton, data=mydata)) #Interaction term? Plankton may have lunar cycles
#Three terms - 35 models
m123<-glm.convert(glm.nb(mantas~site*year+cosmonth, data=mydata))
m124<-glm...
2008 Oct 29
34
iommu: mapping reserved region failed - Q35 - VT-D Issue
Xen 3.4 xen-unstable.hg from yesterday with debian etch on 64bit arch
Intel/Lenovo Q35 Mainboard with VT-d enabled
Bootoptions iommu=1 vtd=1
pci.backhide for a PCI-E nvidia graphiccard
xm dmesg Error messages includes:
[VT-D] iommu.c: 1694:d32767 iommu: mapping reserved region failed
[VT-D] iommu.c: 1542:d0 intel_iommu_add_device: context mapping failed
If i try to start my HVM by xm create
2005 Dec 21
9
question about changejournal
Hi,
I''ve got a newbie question--sorry if this is covered elsewhere, I parsed
through the archives for awhile and didn''t see it.
I''d like to listen for whenever a file is renamed (e.g. foo.txt -> foo.old)
and then magically change it back. This sounds odd, but I''m working with a
stubborn application and this will actually make things work nice.
So, if I do:
2006 Mar 15
0
Samba + Cups -> PPD Options problem - 1 attachment
...&86-E57`-"BI$969A=6QT0UA?0S)$7T9A8V55<#H@1&5F1F%C
M955P#0HJ0UA?0S)$7T9A8V55<"!$969&86-E57`O4')I;G1E<B=S($1E9F%U
M;'0Z("(E4T-)4%!$.B!$1D4@1F%C955P(%!R:6YT97(G<R(-"BI#6%]#,D1?
M1F%C955P($9A8V5$;W=N+T9A8V4@1&]W;CH@(B530TE04$0Z($1&12!&86-E
M57`@1F%C941O=VXB#0HJ0UA?0S)$7T9A8V55<"!&86-E57`O1F%C92!5<#H@
M(B530TE04$0Z($1&12!&86-E57`@1F%C955P(@T**D-L;W-E54DZ("I#6%]#
M,D1?1F%C955P#0H-"BI/<&5N54D@*D-87T,R1%]#;VQL871I;VXO0V]L;&%T
M:6]N.B!0:6-K3VYE#0HJ3W)D97)$97!E;F1E;F-Y.B`R,"!$;V-U;65N=%-E
M='...
2008 Jun 30
4
Rebuild of kernel 2.6.9-67.0.20.EL failure
Hello list.
I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without
modifications.
How did I try it?
Created a (non-root) build environment (not a mock )
Installed the kernel.scr.rpm and did a
rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee
prep-out.log
The build failed at the end:
Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL
Checking