how to connect tru64 v 40. D to pc windows xp

[MNMC]

It happend a dangeruos proplem, pleaese help:

in the manuall of the alpha, in section of netwoking, there is this explaination:

- set the variable to Twisted-Pair to support thichnet or twisted-pair networks. Type:
>>> set eaw0_mode Twisted-Pair [CR]

- set the variable " bus_prope_algorithm " to old to allow the system to properly map the ewa0 and ewb0 Ethernet ports (ewb0 support XP CAP interfaces). Type:
>>> set bus_prope_algorithm old [CR
>>> b [CR}

end

I do that explaination, and after I boot, I cant connect with the gantery of the Gamma camera (XP CAP interfaces), which is more interset than the pc network, now the whole machine become useless.

I treid to do many things, chick the caples, all thing is OK, I set the ewa0 to AUI as it was before, but still cant connect, I set " bus_prope_algorithm " to new, last, old and nothing ( ), but still the problem.

I dont know what the pre settings of
" bus_prope_algorithm " was before.

I trusted the company manual but that is the result!!

please help me If you can.

the version of the SRM is V6.8-2 May 11 1998 10:58:48

[Rob Leadbeater]

Hi,

You should be able to check all of the network card settings with:

>>> show ew*

Double check that it has gone back to AUI. If you type a set command incorrectly like this:

>>> set eaw0_mode AUI

you won't get an error. This will just create a variable called eaw0_mode.

After you make any changes, it would also be wise to reset the server by typing

>>> init

Cheers,

Rob

[Steven Schweda]

> in the manuall of the alpha, [...]

Which manual is "the manual"?

Before you changed anything, you said:

> >>>show device
> [...]
> ewa0.0.0.14.0 EWA0 00-00-F8-23-3A-BA
> ewb0.0.0.11.0 EWB0 00-00-F8-31-24-4C
> [...]

What does it say now? Follow the Ethernet
addresses (xx-xx-xx-xx-xx-xx) to see if
changing "bus_probe_algorithm" (not
"bus_prope_algorithm") changes which
interface is EWA0 and EWB0. Set
"bus_probe_algorithm" so that they look the
same as they did before.

Figure out which interface (EWx0, tuX) is
used for the camera, and set its mode back to
the correct value for its cable type.

> threre is tow ethernet ports, one is to the
> motherboard, ther other is a separated
> card with a port
> beside it is like paralell but smaller
> connected to the gantry of the Gamma
> Camera, [...]

Is the camera connected to an Ethernet
interface or to something else? Is it
connected to the add-in PCI Ethernet card?
An AUI cable uses a 15-pin D-connector,
usually with a sliding latch.

If the camera uses an AUI cable, and you
changed its interface to twisted-pair, then
that would stop it from working.

If you switched the names (EWA0 <-> EWB0 and
tu0 <-> tu1), then that would probably stop
it from working, too.

On my (200) system, the built-in interface
is:

ewa0.0.0.11.0 EWA0 00-00-F8-23-5F-1D

and the add-in PCI card is:

ewb0.0.0.12.0 EWB0 08-00-2B-C4-4E-C2

It's only a guess, but I'd guess that your
".0.0.11.0" interface is the built-in one,
and your ".0.0.14.0" interface is the add-in
PCI card. When in doubt, remove the PCI
card, and see which one disappears.

[MNMC]

thanks Mr Rob

> You should be able to check all of the network card settings with:

>>> show ew*

Double check that it has gone back to AUI. If you type a set command incorrectly like this:

>>> set eaw0_mode AUI

of coures I have to it, and try to make the no on AUI mode, but useless.

is that devil " bus_probe_algorithm " is the reason??, how I can get it back?? I also try:
>>> set bus_probe_algorithm algorithm

then I have tow " bus_probe_algorithm ":

>>> show bus*
bus_probe_algorithm old
bus_probe_algorithm algorithm

so perhaps that "bus_probe_algorithm old" was not exist before, can I delete it, how??

> After you make any changes, it would also be wise to reset the server by typing

>>> init

of course I did it.

[Rob Leadbeater · Accepted solution]

Hi,

Based on a handful of 255s which I've just looked at, the built in interface on yours is ewa0, and the add on card which links to the camera is ewb0.

So double check the settings for ewb0.

If you've accidentally created an additional bus_probe... entry then you can use clear to get rid of it.

>>> clear bus_probe_algorithm

The SRM console shouldn't let you enter an incorrect value, so you may have a typo in one of the values.

If things still don't work, check the output of the Unix startup again with:

# uerf -R -r 300 | more

that should tell you the state of the network cards as they boot. In your case

tu0 is the onboard card.
tu1 is the add on card that links to the camera.

Cheers,

Rob

[Steven Schweda]

On my 200:

>>>show bus*
bus_probe_algorithm new
>>>show dev ew
ewa0.0.0.11.0 EWA0 00-00-F8-23-5F-1D
ewb0.0.0.12.0 EWB0 08-00-2B-C4-4E-C2

>>>set bus_probe_algorithm
bad value - valid selections:
new
old
bad value - bus_probe_algorithm not modified
>>>set bus_probe_algorithm old
>>>init

>>>show bus*
bus_probe_algorithm old
>>>show dev ew
ewa0.0.0.11.0 EWA0 00-00-F8-23-5F-1D
ewb0.0.0.12.0 EWB0 08-00-2B-C4-4E-C2


On mine, EWB0 is a (10/100) DE500-BA, not
another (10-only) of the same thing, but,
around here, bus_probe_algorithm has no
obvious effect on these device names. The
built-in one is always EWA0, and the add-in
one is always EWB0.

According to:

http://www.compaq.com/alphaserver/download/ek-vllxa-ui-b01.pdf

"The default is new."


Of course, my firmware is probably newer than
yours, too:

>>>show config

Firmware
SRM Console: V7.0-9
show_arc: Can't find Flash Rom containing ARC console.
PALcode: VMS PALcode V5.56-2, OSF PALcode X1.46-2
Serial Rom: V4.6
Diag Rom: V1.7
[...]


> > in the manuall of the alpha, [...]
>
> Which manual is "the manual"?

Still wondering.

[MNMC]

Mr Steven

> Which manual is "the manual"?

its the book or cataloge which come with any machine from the factory.

> Before you changed anything, you said:

> >>>show device
[...]
ewa0.0.0.14.0 EWA0 00-00-F8-23-3A-BA
ewb0.0.0.11.0 EWB0 00-00-F8-31-24-4C
[...]

>What does it say now?

they still the same, no changed.

Follow the Ethernet
addresses (xx-xx-xx-xx-xx-xx) to see if
changing "bus_probe_algorithm" (not
"bus_prope_algorithm") changes which
interface is EWA0 and EWB0. Set
"bus_probe_algorithm" so that they look the
same as they did before.

I dont know waht is this "bus_probe_algorithm", but there is no any changes in addresses (xx-xx-xx-xx-xx-xx), and how I can get back??

Figure out which interface (EWx0, tuX) is
used for the camera, and set its mode back to
the correct value for its cable type.

now I make the both on AUI to look the
same as they did before.


> Is the camera connected to an Ethernet
interface or to something else? Is it
connected to the add-in PCI Ethernet card?
An AUI cable uses a 15-pin D-connector,
usually with a sliding latch.

its connected by AUI cabel to the same PCI Ethernet card by an AUI ports beside ethernet, the tow are on the same card


> If the camera uses an AUI cable, and you
changed its interface to twisted-pair, then
that would stop it from working.

I dont changed the ewb0.

If you switched the names (EWA0 <-> EWB0 and
tu0 <-> tu1), then that would probably stop
it from working, too.

No I dont.

On my (200) system, the built-in interface
is:

ewa0.0.0.11.0 EWA0 00-00-F8-23-5F-1D

and the add-in PCI card is:

ewb0.0.0.12.0 EWB0 08-00-2B-C4-4E-C2

It's only a guess, but I'd guess that your
".0.0.11.0" interface is the built-in one,
and your ".0.0.14.0" interface is the add-in
PCI card. When in doubt, remove the PCI
card, and see which one disappears.

That is a good idea, but first I want the ganrty to connect, then I see for the pc network

perhaps your guess is true, but now I mak the both to AUI without make "set bus_prope_algorithm old" and its not work, then I try after make "set bus_prope_algorithm old, but not work.

I Have cleared tha additional "set bus_prope_algorithm", so can I clear the "set bus_prope_algorithm old" too?, because It's only a guess than it make the problem!!

Mr rob


> Based on a handful of 255s which I've just looked at, the built in interface on yours is ewa0, and the add on card which links to the camera is ewb0.

> So double check the settings for ewb0.

how I double check the settings for ewb0? I dont understand this "double check".

> If you've accidentally created an additional bus_probe... entry then you can use clear to get rid of it.

>>> clear bus_probe_algorithm

Thanks.I Have cleared tha additional "set bus_prope_algorithm", so can I clear the "set bus_prope_algorithm old" too?, because It's only a guess than it make the problem!!


> If things still don't work, check the output of the Unix startup again with:

# uerf -R -r 300 | more

> that should tell you the state of the network cards as they boot. In your case

its the same with thast one. see text file attachmented.

[Rob Leadbeater]

Double check = check it again.

>>> show ewb*


The output from uerf still shows both cards with "no carrier" which usually means not connected.

Check that the cables are connected firmly.

Cheers,

Rob

[MNMC]

Double check = check it again.

>>> show ewb*


The output from uerf still shows both cards with "no carrier" which usually means not connected.

Check that the cables are connected firmly.


in the last time, the camera wasnt connected, it was in disconnect mode because it was turned off electricity.

[MNMC]

Thank you all

the problem solved

I well tell after

now Im going

very thanks