Re: big file became broken on 2003-03-11(cvsuped)

2003-03-13 Thread Norikatsu Shigemura
On Thu, 13 Mar 2003 01:23:00 -0500 (EST) Jeff Roberson [EMAIL PROTECTED] wrote: How much memory is in your machine? Can you go back to an earlier date and see if this is still a problem? Are you doing anything else with the machine while this is going on? 512MB. I used

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-13 Thread Jeff Roberson
On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: On Thu, 13 Mar 2003 01:23:00 -0500 (EST) Jeff Roberson [EMAIL PROTECTED] wrote: How much memory is in your machine? Can you go back to an earlier date and see if this is still a problem? Are you doing anything else with the machine while

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-13 Thread Julian Elischer
On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: (snip) Thu Mar 13 15:47:59 JST 2003 MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c Thu Mar 13 15:48:13 JST 2003 MD5 (OOo_1.0.2_source.tar.bz2) = 8a82b4dbdd4e305b6f6db70ea65dce8c Thu Mar 13 15:48:32 JST 2003

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-13 Thread Norikatsu Shigemura
On Thu, 13 Mar 2003 03:36:41 -0500 (EST) Jeff Roberson [EMAIL PROTECTED] wrote: Does your machine log ECC errors? If so can you check for them in the BIOS? If you don't make world and jdk14 does this problem still show up? My machine uses non-ECC unbuffered DDR SDRAM(Transcend -

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-13 Thread Norikatsu Shigemura
On Thu, 13 Mar 2003 00:41:37 -0800 (PST) Julian Elischer [EMAIL PROTECTED] wrote: We had a similar problem some time ago that turned out to be bad RAM in one case and a bad CMOS BIOS setting in another. (RAM speed setting). RAM speed setting! Ah, I don't test it yet. I'll change speed

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-13 Thread Norikatsu Shigemura
On Thu, 13 Mar 2003 18:08:01 +0900 Norikatsu Shigemura [EMAIL PROTECTED] wrote: RAM speed setting! Ah, I don't test it yet. I'll change speed setting and test. I seted FastCommand: normal from ultra on `Configure SDRAM Timing by, FastCommand'. More robust and reduce

big file became broken on 2003-03-11(cvsuped)

2003-03-12 Thread Norikatsu Shigemura
Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. # uname -a FreeBSD ***.*-.*** 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Wed Mar 12 18:39:05 JST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MELFINA i386 # mount /dev/ad0s1a

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-12 Thread Jeff Roberson
On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. How much memory is in your machine? Can you go back to an earlier date and see if this is still a problem? Are you doing anything else

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-12 Thread Jeff Roberson
On Thu, 13 Mar 2003, Jeff Roberson wrote: On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. How much memory is in your machine? Can you go back to an earlier date and see if this is

Re: big file became broken on 2003-03-11(cvsuped)

2003-03-12 Thread Jeff Roberson
On Thu, 13 Mar 2003, Jeff Roberson wrote: On Thu, 13 Mar 2003, Norikatsu Shigemura wrote: Big file like OOo_1.0.2_source.tar.bz2 became broken with making openoffice in my environment. How much memory is in your machine? Can you go back to an earlier date and see if this is