On Wed, 2003-09-17 at 14:37, Steve Kargl wrote:
> On Wed, Sep 17, 2003 at 01:21:39PM -0700, Scott Reese wrote:
> > On Tue, 2003-09-16 at 18:48, Matthias Andree wrote:
> > > Scott Reese <[EMAIL PROTECTED]> writes:
> > >
> > > > Though I'm not sur
On Tue, 2003-09-16 at 18:48, Matthias Andree wrote:
> Scott Reese <[EMAIL PROTECTED]> writes:
>
> > Though I'm not sure if RAM is my problem because I'm not getting Sig 11
> > errors. I keep getting extremely consistent internal compiler errors
> > prett
Hello all,
I've been wrestling with my nice, shiny new PITA system all week long.
The consensus seems to be that the RAM is suspect. I'm on my second
stick of 512 MB 2700 DDRAM for this thing and this one seems to be worse
than the first one I got. The first one was a Samsung and this one is
so
On Fri, 2003-09-12 at 12:56, [EMAIL PROTECTED] wrote:
> Quoting Scott Reese <[EMAIL PROTECTED]>:
>
> > Hello all, I'm rephrasing my previous question to reflect new findings
> > in my situation in the hopes that someone may have an idea of what's
> > goin
Hello all, I'm rephrasing my previous question to reflect new findings
in my situation in the hopes that someone may have an idea of what's
going on here (see thread "Internal compiler error in
reload_cse_simplify_operands" from earlier this week).
In a nutshell, I have upgraded my machine to a PI
On Wed, 2003-09-10 at 17:22, Steve Kargl wrote:
> On Wed, Sep 10, 2003 at 04:45:47PM -0700, Scott Reese wrote:
> > On Wed, 2003-09-10 at 16:40, Steve Kargl wrote:
> > > On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
> > > > On Wed, 2003-09-
On Wed, 2003-09-10 at 16:40, Steve Kargl wrote:
> On Wed, Sep 10, 2003 at 04:34:31PM -0700, Scott Reese wrote:
> > On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
> > > [I'm not presently subscribed to this list so please CC me in any
> > > replies. Thank you]
>
On Wed, 2003-09-10 at 14:14, Scott Reese wrote:
> [I'm not presently subscribed to this list so please CC me in any
> replies. Thank you]
>
> Hello,
>
> I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a PIII
> 800 MHz processor with 256 MB RAM to
[I'm not presently subscribed to this list so please CC me in any
replies. Thank you]
Hello,
I'm running 5.1-RELEASE-p2 and I just upgraded my machine from a PIII
800 MHz processor with 256 MB RAM to a PIV 2.4 GHz processor and VIA P4B
400 motherboard with 512 MB RAM. The system starts and runs
On Tue, 2003-07-01 at 19:36, Jud wrote:
[snip]
> > I have two physical drives (ad0, ad1). XP is on ad0 (the first drive)
> > and FreeBSD is on ad1 (the second drive). I have been using booteasy on
> > the *first* drive with a regular mbr on the second and that worked just
> > fine until I did a f
On Tue, 2003-07-01 at 01:34, Jud wrote:
> >> > > to boot FreeBSD with no problems at all, but when I went to boot up
> >> > > Windows, I received the dreaded 'NTLDR missing' message.
> [grub stuff snipped]
>
> A few comments about the thread so far:
>
> ISTM the easiest thing for you to do is ins
On Mon, 2003-06-30 at 22:10, Andrew Boothman wrote:
> On Monday 30 June 2003 7:19 pm, Scott Reese wrote:
> >
> > Previously, I had a dual-boot setup with FreeBSD 5.0 and Windows XP. I
> > was using booteasy as the boot loader and I had no problem booting into
> >
On Mon, 2003-06-30 at 22:14, Doug White wrote:
> On Mon, 30 Jun 2003, Andrew Boothman wrote:
>
> > This seems to be a recurring problem after 5-RELEASE. I had exactly the same
> > problem, and I know of others that are the same. For some reason -current
> > doesn't seem to be inter-operating well
On Fri, 2002-06-07 at 14:02, Kris Kennaway wrote:
> On Fri, Jun 07, 2002 at 04:56:45PM -0400, Joe Marcus Clarke wrote:
> > On Fri, 2002-06-07 at 10:52, Jun Kuriyama wrote:
> > > At Fri, 7 Jun 2002 12:43:27 + (UTC),
> > > John Angelmo wrote:
> > > > (cd /usr/ports/www/mozilla/work/mozilla/dis
On Wed, 2002-05-22 at 18:27, Kris Kennaway wrote:
>
> > I just upgraded my 4-STABLE machine to -CURRENT via source. Everything
> > seemed to go smoothly and things are running fine, EXCEPT when I try to
> > build *any* of the ports in the ports collection. Every time I run
> > 'make' it gets st
Hello,
I just upgraded my 4-STABLE machine to -CURRENT via source. Everything
seemed to go smoothly and things are running fine, EXCEPT when I try to
build *any* of the ports in the ports collection. Every time I run
'make' it gets stuck in an infinite loop and doesn't build the port.
Some exa
16 matches
Mail list logo
