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

[MNMC]

In fact I cant find words to talk about my glad and thanks for your help and interst with my case.

> Some people have had problems with some
drives. Alphas may be easier to satisfy than
old VAXes. I've had success with many
Toshiba drives (and some others), and with
some Yamaha CD-R/RW drives (which might be
nice if you also wish to write your data to a
CD-R). A drive which has a block-size jumper
(512 or 2048 bytes) might be more likely to
work when set to 512.

There have been many discussions of CD-ROM
drives over the years in comp.os.vms. A
drive which works for VMS is probably good
for Tru64, too.

by the way, today some one suggest to replace the fulty CD-ROM with CD-R/RW or DVD-CD-R/RW,
with scsi port of cource, and to trancefare files from alpha ro the CD-DVD by Nero or some other burning
program, but I doubt if I can find it for this old digital unix v 4.0 d??

> How old is it? My AlpSta 200 systems were
new in 1995. Your box is probably a little
newer. How long do you expect a computer to
live?

It was new in 1997, I dont know how long do a computer to
live, but I expect the Gamma Camera which is work on this alpha to live 20 years, for it is very
expencive it cost about (100 thousand USA dollars).

> but both are configured for AUI wich is not connected:
console mode: selecting 10Base5 _(AUI) port: no carrier

check output of "set ewa0_mode ?" and "set ewb0_mode ?"

to see if they can be switched to twisted_pair

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, the gantry contain
some kind of computer without hardisk, it boot from floppy disk, the cabel between alpha and gantry
is a couple of thennet, at the tow end of them there is an adapter small box from thennen ro that
port which like paralle, perhaps it is a thicknet!!.

I remmember that I read somewere in the manuals of the alpha, that ewb0 is for the gantry network,
and the ewa0 is for networking with other alphas.

I was searched in the manual about network, but I was not undrestand alot, but now after I read your greats helps
,I find that there is a three ways to connect netwrork in the manual:

1- Thicknet.
2- thennent.
3- twisted pair (10Base-T), that need 10Base-T hub.

The third way seems to be better, so I would to ask:
Is the twisted pair (10Base-T) and its hub is still exist in the shops??
Or is it the same usuall cables and the hub is the usuall twist?? If the answer is no.
Can usuall cables and usuall twist connect??, is it need other settings?? for the manual contain
only settings about that three ways only.

> Did you try anything like:

>>>show config | more
>>>help

yes I have but nothing happend, its the same of "show config".

> Or one built-in interface and one PCI card.
It might help a little if you looked at
what's in this box, and let us know what you
find.

it seems very exiting to look inside and knnw more, indeed!!!

[Rob Leadbeater]

Hi,

No, you probably won't find any CD burning software for 4.0D, so fitting a CD writer wouldn't help you. Although they are becoming more difficult to hold of, it shouldn't be that difficult to source a replacement drive, part number is RRD46. Swan Computers (www.swancomp.co.uk) have 15 on their stock list.


> Is the twisted pair (10Base-T) and its hub
> is still exist in the shops??

Yes, the cabling used for 10Base-T is the same as any "normal" network cable that you'd find on a modern PC.

A cheap modern hub will suffice. Something like this:

http://www.netgear.com/Products/Switches/EthernetHubs.aspx?for=Home+Networking


As for the connection between the AlphaStation and the camera, that sounds like it is using the AUI connector (parallel but smaller) with converters to thin ethernet or 10-Base 2.

http://en.wikipedia.org/wiki/Attachment_Unit_Interface

http://en.wikipedia.org/wiki/10BASE-2

I'll guess that the connection status of one of the network cards was "no carrier" because the camera system was powered off at the time.

Cheers,

Rob

[MNMC]

> No, you probably won't find any CD burning software for 4.0D, so fitting a CD writer wouldn't help you. Although they are becoming more difficult to hold of, it shouldn't be that difficult to source a replacement drive, part number is RRD46. Swan Computers (www.swancomp.co.uk) have 15 on their stock list.

> part number is RRD46.
what this mean??

> A cheap modern hub will suffice.

I really don`t know the meaning of this word " suffice ", I sow google tranlate, tell me it mean " not enuogh ", so is that you mean??

> I'll guess that the connection status of one of the network cards was "no carrier" because the camera system was powered off at the time.

yes the ew0a has "no carrier", so I think to make the network of pc windows on it.

I have seen the commands of networking in the manual, it contains some (perhaps) dangerous oparations, such as changing primary hard disk, and delete /usr and /prism foldrs, the /prism folder is the only user can use the camera connection, and log in to the software of imaging automaticaly, but it is not the root, the root is not log in to the software of imaging as prism user.

so I lettle fear if the network failed, that occure some non-return changed or proplems.

[Rob Leadbeater]

RRD46 is the Digital part number of the original CD-ROM drive in the AlphaStation 255.

"Suffice" means it will work.
A cheap modern hub will work.

Cheers,
Rob

[Steven Schweda]

> No, you probably won't find any CD burning
> software for 4.0D, [...]

I'd expect cdrecord to work on Tru64 at least
as well as it does on VMS. You would need
a C compiler (which, I assume, you have).

I'd also expect a network connection to be
easier to use than any CD-writing method.

[MNMC]

> I'd expect cdrecord to work on Tru64 at least
as well as it does on VMS. You would need
a C compiler (which, I assume, you have).

I wanted to ask wether I can compile it from its source, but you reply me before I ask.

Does any C compiler well work on this v 4.0 d?? for expample this "GCC":

http://gcc.gnu.org/

I'd also expect a network connection to be
easier to use than any CD-writing method.

I don`t doubt your opinion, although the the terminal commands of the network settings in the manual of my digital unix is about pure 2 pages, but some one who comes from windows environment well think its easier to install burner software than the network settings and its troubleshooting??

how ever I need both of them, CD copier and the network.

So now I well ask my employer of what I need of cabels and hub, and begin the real work and faces the hardships with God's help, of these settings of the network.

[MNMC]

Can I use an usaual CD-ROM, with IDE to SCSI converter, such as this:

http://www.addonics.com/products/io/ide_scsi.asp

because I need a new CD-ROM however.

[Rob Leadbeater]

Hi,

The IDE to SCSI converter you've found, might work, but it has the wrong SCSI connector for an AlphaStation 255. (68 pin not 50 pin).

You should hopefully have cc installed on 4.0D to be able to compile programs, however getting the network working should be much easier than getting a CD recorder working.


Cheers,

Rob

[MNMC]

> The IDE to SCSI converter you've found, might work, but it has the wrong SCSI connector for an AlphaStation 255. (68 pin not 50 pin).

Oh thanks, I know that, but I wanted to ask about the idea itself, then I well search other sutable converter.

> You should hopefully have cc installed on 4.0D to be able to compile programs, however getting the network working should be much easier than getting a CD recorder working.

There is some one of networking windows only local to me, he wonder how well Unix and windows well see each other??

and he don`t know about compiling unix insall software, he think it similar to windows exe programs, so he insest that CD RW is bsetter.

however, the manual of my alpha contain the command shell settings of alpha unix to alph unix, but not the alpha unix to pc windows, Is it the same or little diffrent??

[Steven Schweda]

> There is some one of networking windows
> only local to me, he wonder how well Unix
> and windows well see each other??

TCP/IP is TCP/IP. FTP was designed to let
different operating systems use it. FTP is
used to exchange files between different
operating systems every day. Yes, even
Windows. I don't use Windows here, but I
do use VMS (including versions as old as
1994), Linux, AIX, Solaris (SunOS 5.x),
SunOS 4.x, Tru64, HP-UX, Mac OS X, Mac OS
9.x, and probably some things I can't
remember, and they can all exchange files
with each other using FTP. I have even done
it between Windows systems (owned by other
people) and my VMS systems.

> and he don`t know about compiling unix
> insall software, he think it similar to
> windows exe programs, so he insest that
> CD RW is bsetter.

Perhaps you should find an expert with better
information.

> [...] but some one who comes from windows
> environment well think its easier to
> install burner software than the network
> settings and its troubleshooting??

Perhaps you should find an expert with better
information.

You don't need to compile anything to get
FTP to work on Tru64 (any version). You
almost certainly would need to compile some
software (like, say, cdrtools) if you wish to
write a CD on Tru64.

> however, the manual of my alpha contain
> the command shell settings of alpha unix to
> alph unix, but not the alpha unix to pc
> windows, Is it the same or little
> diffrent??

Which "the manual? Where? What are "command
shell settings"? Is _what_ the same or
different?

> Does any C compiler well work on this
> v 4.0 d?? for expample this "GCC":

I know nothing about Tru64 before V5.0
(1999), but I believe that they all included
a DEC/Compaq C compiler. You should also be
able to find some version of GCC which would
work, but it may not be easy to find anything
now which has been built for such an old
version of Tru64.

Around here (now):

urtx# sizer -v
HP Tru64 UNIX V5.1B (Rev. 2650); Fri Mar 20 20:19:48 CDT 2009

urtx# cc -V
Compaq C V6.5-303 (dtk) on HP Tru64 UNIX V5.1B (Rev. 2650)
Compiler Driver V6.5-302 (dtk) cc Driver

urtx# gcc --version
gcc (GCC) 4.3.2
[...]

As usual, many things are possible. Some
things are easier than others. You should
start with the easy things. Like, say, FTP.

I use cdrtools mostly on my VMS systems, and
I can't remember if I've ever used it on a
Tru64 system, but I do have an old version
installed:

urtx# cdrecord -version
Cdrecord 1.10 (alphaev56-dec-osf5.1) Copyright (C) 1995-2001 Jörg Schilling

and a newer one:

urtx# ./cdrecord/OBJ/alpha-osf1-cc/cdrecord -version
Cdrecord-ProDVD-ProBD-Clone 2.01.01a37 (alphaev6-dec-osf5.1) Copyright (C) 1995-
2008 Jörg Schilling

I have no way to verify that any cdrtools
kit will work on Tru64 V4.x, but I also have
no reason to doubt that it would. (But
that's still not where I would start.)

[MNMC]

> TCP/IP is TCP/IP. FTP was designed to let
different operating systems use it. FTP is
used to exchange files between different
operating systems every day[...].

I was frightend a little because there isn`t any thing about windows in the manual, the whole explanation is abuot alpha machines network exept a diagram contain 2 alpha and 2 other "remote terminal" without identify its OS, it seems no problem what ever it is.


> Which "the manual? Where? What are "command shell settings"? Is _what_ the same or different?

today I was reading in deep this manual which come with the Gamma Camera, in the section od networking, I red about the files of network such as /etc/hosts, hodts.equiv, exports, fstab, and rc.config.

then the components of twisted pair network:

1- 10BaseT Network Hub or mutiport repeater 10Base.

2- 10Base-T network cable (100 ft) with RJ-45.

and abuot the hosts name an inernet number or address...etc

tommoro I well see this shell commands, but I looked to it, is not commands, it is editing that network files, and the coomands of changenig primary disk and changing names of partions is perhaps only for alpha camrera to other kind of alpha cameras such as CT or MRI.

for my good luck it seems very easy !!


> Around here (now):

[...]

No please, Im linux user of ubuntu,
I know the ./compile, ./make ./make install... etc so I think cpmiling in tru64 is somehow simillar.

but are joke to help me convince him that it very hard to intall recorder.

[Steven Schweda]

> I was frightend a little because there
> isn`t any thing about windows in the
> manual, [...]

Nor about VMS, nor Solaris, nor AIX, nor any
other OS.

> > TCP/IP is TCP/IP. [...]

No one cares what the other OS is, so long as
it does TCP/IP.

> for my good luck it seems very easy !!

What could go wrong?


You will also need to configure TCP/IP for
the Ethernet interface in the Windows system.

> [...] /etc/hosts [...]

http://en.wikipedia.org/wiki/Hosts_file

There is one on Windows, but it's hidden
better there.

If you have only the two computers (and no
router) in your new network, then I'd suggest
using static IP addresses (not DHCP).
Addresses in 192.168.0.x (subnet =
255.255.255.0) are popular. For example:

192.168.0.2 Tru64_host_name
192.168.0.3 Windows_host_name

[MNMC]

for my good luck it seems very easy !!

> What could go wrong?

If I have any problem I well tell you, But I think no.

> You will also need to configure TCP/IP for
the Ethernet interface in the Windows system.

> I well call that windows networker, for he is my employer officer too, or I well install the new PC-BSD 8.0, then make the tru64 with it.

> If you have only the two computers (and no
router) in your new network, then I'd suggest
using static IP addresses (not DHCP).
Addresses in 192.168.0.x (subnet =
255.255.255.0) are popular. For example:

192.168.0.2 Tru64_host_name
192.168.0.3 Windows_host_name

oh thats is the same on my manual, but is that well effect the dail up internt connection of the pc?? although Im not too intrest with it, I well get other pc for the dail up, If It can`t coexist with the alpha network.

now today I well see the manual about editing the hosts file, I think I well have some quastions.

[Steven Schweda]

> [...] but is that well effect the dail up
> internt connection of the pc??

I'd guess that the dial-up connection gets an
address from your ISP using DHCP. Again,
this is a Windows question, and I'm not a
Windows expert. I'd guess that the Network
Control Panel or an "ipconfig" command would
show you what that address is.

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/ipconfig.mspx

If it's in the 192.168.0.x range, then use
something different, like, say, 192.168.1.x
for the Ethernet network. (Or 2, or 3, ...)

[MNMC]

Very Thanks for all

I have fineshed reading, no any more quastions.

now Im going to make it, its very easy to do, it need not all this huge story, so Im ashamed, but my excuse is that no any one local know thing abuot this system and its machine, they all thinks, it is a closed or encrypted by the manufacture, and cant to do any thing.

when I fineshed I well tell you.

Thank you all.

[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