search for: fp5

...was that it was an oplock issue. However, setting 'oplocks = no' did not resolve the problem. I even tried 'level2 oplocks = no' with no joy. I set the log level to 3 and found this: [2005/06/23 16:15:24, 3] smbd/dosmode.c:unix_mode(111) unix_mode(FileMaker DB/main/Player File.fp5) returning 0666 [2005/06/23 16:15:24, 2] smbd/open.c:check_share_mode(530) Share violation on file (2,2,2,3129,FileMaker DB/main/Player File.fp5,fcbopen = 0, flags = 2) = 0 [2005/06/23 16:15:24, 2] smbd/open.c:open_file(245) user opened file FileMaker DB/main/Player File.fp5 read=Yes write=Yes...

Take a look at this output from lsof: smbd 11490 0 8u REG 3,3 55296 1136647 Maintenanc.fp5 afpd 31010 0 2u REG 3,3 3207 1136655 auction - envelope.rtf afpd 31010 0 5u REG 3,3 4156 1136656 Word Work File L 1 afpd 31010 0 8u REG 3,3 55296 1136647 Maintenanc.fp5 smbd 31386 0 9u REG 3,3 4156 1136656 Word Work File L 1...

...ble to provide me with 2 XML formats (DSO-XML and FMP-XML): *********** DSO-XML *********** <?xml version="1.0" encoding="UTF-8"?><FMPDSORESULT xmlns="http:// www.filemaker.com/fmpdsoresu lt"><ERRORCODE>0</ERRORCODE><DATABASE>Customers.fp5</ DATABASE><LAYOUT>XMLDump</LAYOUT><ROW MODID="0" RECORDID="13049791"><Company>Acme</ Company><Street>Somewherestreet 145 </Street><Postalcode>8200</Postalcode><City>Somecity</City></ROW><ROW MODI...

...llee now indeed saved/restored all the xmm regs I >> added, however the calling code did not change at all... > > Look in X86InstrControl.td. The call instructions are all prefixed > by: > > let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, > FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, > XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, > XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], > > This is the fixed list of call-clobbered registers. It should really > be controlled by the calling convent...

I am running FileMaker 6.0 via Wine on Ubuntu 6.10. I have a file/ table/whatever it is called Case.fp5 and another table called Actions.fp5. Case is a one to many relationship to Actions, related via the CaseID. Date Closed is calculated in Case: If Last(Actions::Action Type) = "Close" then Date Closed = Last(Actions::Date Created) (something like that since I can't actually see the...

Hi, I am new to this list but I have tried to search for answers to this one. Ever since we moved the *.fp5 files off a windows 2000 server and onto samba filemaker is now 20% the speed it was before. It was happening with samba 2.2.3a and I have just recently upgraded to 2.2.5 and it didn't fix the problem. I suspect it's a locking issue and the speed of getting locks on the files. Jeffrey Bo...

...0, 2010, at 7:46 AM, Roland Scheidegger wrote: > On 20.10.2010 05:00, Jakob Stoklund Olesen wrote: >> Look in X86InstrControl.td. The call instructions are all prefixed >> by: >> >> let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, >> FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, >> XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, >> XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], >> >> This is the fixed list of call-clobbered registers. It should really >> be controlled by...

...Scheidegger wrote: > >> On 20.10.2010 05:00, Jakob Stoklund Olesen wrote: >>> Look in X86InstrControl.td. The call instructions are all prefixed >>> by: >>> >>> let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, >>> FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, >>> XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, >>> XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], >>> >>> This is the fixed list of call-clobbered registers. It should really >>&gt...

...expected - the callee now indeed saved/restored all the xmm regs I > added, however the calling code did not change at all... Look in X86InstrControl.td. The call instructions are all prefixed by: let Defs = [RAX, RCX, RDX, RSI, RDI, R8, R9, R10, R11, FP0, FP1, FP2, FP3, FP4, FP5, FP6, ST0, ST1, MM0, MM1, MM2, MM3, MM4, MM5, MM6, MM7, XMM0, XMM1, XMM2, XMM3, XMM4, XMM5, XMM6, XMM7, XMM8, XMM9, XMM10, XMM11, XMM12, XMM13, XMM14, XMM15, EFLAGS], This is the fixed list of call-clobbered registers. It should really be controlled by the...

Thanks for giving it a look! On 19.10.2010 23:21, Jakob Stoklund Olesen wrote: > On Oct 19, 2010, at 11:40 AM, Roland Scheidegger wrote: > >> So I saw that the code is doing lots of register >> spilling/reloading. Now I understand that due to calling >> conventions, there's not really a way to avoid this - I tried using >> coldcc but apparently the backend

...-def,dead>, %RSI<imp-def,dead>, %RDI<imp-def,dead>, %R8<imp-def,dead>, %R9<imp-def,dead>, %R10<imp-def,dead>, %R11<imp-def,dead>, %FP0<imp-def,dead>, %FP1<imp-def,dead>, %FP2<imp-def,dead>, %FP3<imp-def,dead>, %FP4<imp-def,dead>, %FP5<imp-def,dead>, %FP6<imp-def,dead>, %ST0<imp-def,dead>, %ST1<imp-def,dead>, %MM0<imp-def,dead>, %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, %MM4<imp-def,dead>, %MM5<imp-def,dead>, %MM6<imp-def,dead>, %MM7<imp-def,de...

...lt;imp-def,dead>, > %RDI<imp-def,dead>, %R8<imp-def,dead>, %R9<imp-def,dead>, > %R10<imp-def,dead>, %R11<imp-def,dead>, %FP0<imp-def,dead>, > %FP1<imp-def,dead>, %FP2<imp-def,dead>, %FP3<imp-def,dead>, > %FP4<imp-def,dead>, %FP5<imp-def,dead>, %FP6<imp-def,dead>, > %ST0<imp-def,dead>, %ST1<imp-def,dead>, %MM0<imp-def,dead>, > %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, > %MM4<imp-def,dead>, %MM5<imp-def,dead>, %MM6<imp-def,dead>, &gt...

Folks, I was drawn to R, like many others, partly for the opportunity to draw nice, colorful graphs (occasionally ones with meaning, too :-) ). I am still quite a newbie to R. As such, I have been trying to understand the code for the graphics on the home page (the ones from the 2004 contest -- the dendrogram, the cluster plot with different coloured circles, etc.) I was wondering whether anyone

...f,dead>, %RSI<imp-def,dead>, %RDI<imp-def,dead>, %R8<imp-def,dead>, %R9<imp-def,dead>, %R10<imp-def,dead>, %R11<imp-def,dead>, %FP0<imp-def,dead>, %FP1<imp-def,dead>, %FP2<imp-def,dead>, %FP3<imp-def,dead>, %FP4<imp-def,dead>, %FP5<imp-def,dead>, %FP6<imp-def,dead>, %ST(0)<imp-def,dead>, %MM0<imp-def,dead>, %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, %MM4<imp-def,dead>, %MM5<imp-def,dead>, %MM6<imp-def,dead>, %MM7<imp-def,dead>, %XMM0<imp...

...;imp-def,dead>, %RDI<imp-def,dead>, > %R8<imp-def,dead>, %R9<imp-def,dead>, %R10<imp-def,dead>, %R11<imp- > def,dead>, > %FP0<imp-def,dead>, %FP1<imp-def,dead>, %FP2<imp-def,dead>, > %FP3<imp-def,dead>, %FP4<imp-def,dead>, %FP5<imp-def,dead>, > %FP6<imp-def,dead>, %ST(0)<imp-def,dead>, %MM0<imp-def,dead>, > %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, > %MM4<imp-def,dead>, %MM5<imp-def,dead>, %MM6<imp-def,dead>, > %MM7<imp-def,dead&g...

Hi all, I''ve got a very obscure problem. We''re trying to get Rails to talk to Filemaker. So we''ve setup an ODBC dsn and via RubyODBC we''re talking to it. Excellent. Try it under rails and rails won''t even startup, getting bus errors anytime we require ''odbc''. Environment OSX Tiger 10.4.6 Rails 1.1.2 Ruby 1.8.4 RubyODBC 0.998 via

...%RDI<imp-def,dead>, > > %R8<imp-def,dead>, %R9<imp-def,dead>, %R10<imp-def,dead>, %R11<imp- > > def,dead>, > > %FP0<imp-def,dead>, %FP1<imp-def,dead>, %FP2<imp-def,dead>, > > %FP3<imp-def,dead>, %FP4<imp-def,dead>, %FP5<imp-def,dead>, > > %FP6<imp-def,dead>, %ST(0)<imp-def,dead>, %MM0<imp-def,dead>, > > %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, > > %MM4<imp-def,dead>, %MM5<imp-def,dead>, %MM6<imp-def,dead>, > > %M...

...def,dead>, >>> %R8<imp-def,dead>, %R9<imp-def,dead>, %R10<imp-def,dead>, %R11<imp- >>> def,dead>, >>> %FP0<imp-def,dead>, %FP1<imp-def,dead>, %FP2<imp-def,dead>, >>> %FP3<imp-def,dead>, %FP4<imp-def,dead>, %FP5<imp-def,dead>, >>> %FP6<imp-def,dead>, %ST(0)<imp-def,dead>, %MM0<imp-def,dead>, >>> %MM1<imp-def,dead>, %MM2<imp-def,dead>, %MM3<imp-def,dead>, >>> %MM4<imp-def,dead>, %MM5<imp-def,dead>, %MM6<imp-def,dead>, &gt...

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