> Can you give an exact description (even if it has been done before)
> of your NIC card and system type.
Description of my NIC :
3c509b-TPO
ASSY:03-0020-006 REV-A
3com etherlink III
on the chip itself
3com 40-0130-004
9705S 16003554
LUCENT 40-01304
When I write "Enable or Disable", I mean I
> Yes, I tried that also : almost all the different IRQs ans adresses were
> tried, and 10 / 0x300 were the first tested.
Can you give an exact description (even if it has been done before)
of your NIC card and system type.
Give's the diffences within the hardware used on other's systems
you ow
Yes, I tried that also : almost all the different IRQs ans adresses were
tried, and 10 / 0x300 were the first tested.
Romain Surleau.
> If the Etherboot floopy doesn't find your card it because the work
> station don't show it.
>
> Your card seem's to be used on an ISA system. Some ISA syste
Il giorno Sat, 23 Mar 2002, Wouter DeBacker così ha scritto:
|From: Wouter DeBacker <[EMAIL PROTECTED]>
|To: [EMAIL PROTECTED]
|Date: Sat, 23 Mar 2002 01:49:18 +0100
|Subject: Re: RE: [Ltsp-discuss] No boot rom
|
[...]
|
|It seems to me that your problem is related to the setup of th
On Friday 22 March 2002 13:00, you wrote:
> Could it be that the 3c509B-TPO , not having a socket, doesn't
> recognize instructions of boot ROM included in the boot floppy
Negative ! The Etherboot code on a rom-o-matic floppy
completely replaces the functionality of a boot Rom on a Nic
regardl
. These are the markings off of my card
>
> 3c509b-TPO
>
> ASSY:03-0020-010-REV-A
>
> 3com etherlink III
>
> on the chip itself
>
> 3com 40-0411-001
> 9803KGA20
If the Etherboot floopy doesn't find your card it because the work
station don't show it.
Your card seem's to be used on an IS
ROTECTED]>
> Sent: Friday, March 22, 2002 10:33 AM
> Subject: RE: RE: [Ltsp-discuss] No boot rom
>
>
> > Images :
> >
> >
> eb-5.0.5-3c509.com
> -
> ---
> > Boot MS-DOS, launch i
You might be right. Maybe that fact this network adapter does not have a
boot ROM socket is affecting the Etherboot floppy.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 10:33 AM
Subject: RE: RE: [Ltsp-discuss]
d a different card (different 509 card)
Matt
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 22, 2002 8:34 AM
> To: [EMAIL PROTECTED]
> Subject: RE: RE: [Ltsp-discuss] No boot rom
;
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > Sent: Friday, March 22, 2002 5:00 AM
> > To: [EMAIL PROTECTED]
> > Subject: RE: RE: [Ltsp-discuss] No boot rom
> >
> >
> > >a rom-o-matic floppy imitates the b
D]>
> To: <[EMAIL PROTECTED]>
> Sent: Friday, March 22, 2002 7:00 AM
> Subject: RE: RE: [Ltsp-discuss] No boot rom
>
>
> >
> > >a rom-o-matic floppy imitates the behaviour of an Etherboot boot ROM. It
> is meant for users, like yourself,
> > &
-Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, March 22, 2002 5:00 AM
> To: [EMAIL PROTECTED]
> Subject: RE: RE: [Ltsp-discuss] No boot rom
>
>
> >a rom-o-matic floppy imitates the behaviour of an Etherboot boot ROM. It
> is me
Disable the Plug N Play option on the 3C509B card and try again.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 22, 2002 7:00 AM
Subject: RE: RE: [Ltsp-discuss] No boot rom
>
> >a rom-o-matic floppy imitates the behaviour
>a rom-o-matic floppy imitates the behaviour of an Etherboot boot ROM. It is meant for
>users, like yourself,
> who do not have a boot ROM for their network adapters or network
>adapters without a boot ROM socket.
>
> A rom-o-matic boot floppy and a boot ROM are normally mutually exclusive. I
Yves, to clarify - a rom-o-matic floppy imitates the behaviour of an Etherboot boot
ROM. It is meant for users, like yourself, who do not have a boot ROM for their
network adapters or network adapters without a boot ROM socket.
A rom-o-matic boot floppy and a boot ROM are normally mutually exc
15 matches
Mail list logo