Josh Fisher wrote:
> I can confirm that version 6.39 of the nVidia nForce4 chipset (for
> AMD64) drivers causes this problem and that installing version 6.66
> fixes the problem with the Gigabyte GA-K8N Ultra-9 motherboard. That
> leads me to believe it is a bug in the version 6.39 XP driver and no
I can confirm that version 6.39 of the nVidia nForce4 chipset (for
AMD64) drivers causes this problem and that installing version 6.66
fixes the problem with the Gigabyte GA-K8N Ultra-9 motherboard. That
leads me to believe it is a bug in the version 6.39 XP driver and not a
hardware flaw.
Jo
--On Saturday, July 23, 2005 6:41 PM -0400 Phil Stracchino
<[EMAIL PROTECTED]> wrote:
> Chris Lee wrote:
>> I have a win32 machine whose motherboard (nforce2) has onboard 10/100
>> ethernet. I'll try to test this in the near future, but currently I'm
>> using a 3com card in that machine.
>
> The
Hi,
Phil Stracchino wrote:
Chris Lee wrote:
I have a win32 machine whose motherboard (nforce2) has onboard 10/100
ethernet. I'll try to test this in the near future, but currently I'm using
a 3com card in that machine.
The key factor is, is it an *nVidia* onboard 10/100?
An other key fa
Chris
> -Original Message-
> From: Phil Stracchino [mailto:[EMAIL PROTECTED]
> Sent: Saturday, 23 July, 2005 17:41
> To: Chris Lee
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Win32 client drops connection
>
> Chris Lee wrote:
>
Chris Lee wrote:
> I have a win32 machine whose motherboard (nforce2) has onboard 10/100
> ethernet. I'll try to test this in the near future, but currently I'm using
> a 3com card in that machine.
The key factor is, is it an *nVidia* onboard 10/100?
--
Phil Stracchino [EMAIL PROTECTED]
n Behalf
> Of Kern Sibbald
> Sent: Saturday, 23 July, 2005 16:23
> To: Phil Stracchino
> Cc: bacula-users@lists.sourceforge.net
> Subject: Re: [Bacula-users] Win32 client drops connection
>
> On Saturday 23 July 2005 22:22, Phil Stracchino wrote:
> > Kern Sibbald wrote:
On Saturday 23 July 2005 22:22, Phil Stracchino wrote:
> Kern Sibbald wrote:
> > You might make sure you have the latest drivers/firmware for the ethernet
> > card in your Windows system that is giving you problems. At least one
> > user recently found that this was the cause of his disconnects wi
Kern Sibbald wrote:
> You might make sure you have the latest drivers/firmware for the ethernet
> card
> in your Windows system that is giving you problems. At least one user
> recently found that this was the cause of his disconnects with a Windows
> machine -- he had a NVidia ethernet card.
On Saturday 23 July 2005 20:50, Phil Stracchino wrote:
> OK, I have the beginnings of a clue here. First of all, when I
> restarted bacula with debugging enabled (at -d200) on the sd, the sd
> reported 3 jobs on the volume and 1 on the catalog, and errored out the
> tape. I loaded a fresh tape, r
On Saturday 23 July 2005 20:17, Phil Stracchino wrote:
> Kern Sibbald wrote:
> > There is something going wrong in the network connection between the FD
> > and the SD. The first thing is to always (at first) believe the error
> > message, which says that the SD has closed the connection. Perhaps
Kern Sibbald wrote:
> There is something going wrong in the network connection between the FD and
> the SD. The first thing is to always (at first) believe the error message,
> which says that the SD has closed the connection. Perhaps turning on debug
> in the SD would give you a better idea w
On Saturday 23 July 2005 18:33, Phil Stracchino wrote:
> I've just updated all the existing clients I currently have running from
> v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
> current win32 clients, both of which are new client installs, one
> because it's a new client,
Phil Stracchino wrote:
> I've just updated all the existing clients I currently have running from
> v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
> current win32 clients, both of which are new client installs, one
> because it's a new client, one because it was recently rei
I've just updated all the existing clients I currently have running from
v1.36.0 to v1.36.3, and added one new win32 client. This gives me two
current win32 clients, both of which are new client installs, one
because it's a new client, one because it was recently reinstalled after
Windows shot its
15 matches
Mail list logo
