On 8.6.2012 10:31, Mark Benson wrote:
On 8 Jun 2012, at 08:23, Dave McGuire<mcguire at neurotica.com> wrote:
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
I take it TK50 tapes won't read in a later drive?
Yes, a TZ87 (DLT2000) can read TK50 tapes and TK70 tapes as well.
Kari
On 06/08/2012 05:08 AM, Mark Benson wrote:
The TK85 can read TK50s? I didn't know that! If that's the case,
it's likely that the TF85 (DSSI version) may as well, and I have one of those. That may be one more option to get my huge pile of TK50s read.
I had a feeling the later TKs read TK50. I read it on on of HP's DLT
compatibility docs but couldn't remember if it was TK50 or TK70 that
was the oldest compatible format. I have a SCSI-II DLT4000 drive (TK88
or 89??) and I know that doesn't read any old TK tapes, only DLT1,2
etc.
The general rule with most of those format is that the current drive
will read and write the current format, and read (but not write) the
previous format. There are of course exceptions, but not many.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 06/08/2012 04:58 AM, Sampsa Laine wrote:
Dave outside your door is a well dressed gentleman in a
suit that looks like something a certain outrageous poet and author
wore, and has hair to match. (Hint: its the same daft stuff I
sometimes pull on Sampsa.) There's also a blue colored box
outside.........
Ok, you lost me there, my friend.
Welcome to the world of strange Dr Who references..
Uh-oh.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 8 Jun 2012, at 09:24, Johnny Billquist <bqt at softjar.se> wrote:
On 2012-06-08 09:56, Dave McGuire wrote:
The TK85 can read TK50s? I didn't know that! If that's the case,
it's likely that the TF85 (DSSI version) may as well, and I have one of those. That may be one more option to get my huge pile of TK50s read.
I had a feeling the later TKs read TK50. I read it on on of HP's DLT
compatibility docs but couldn't remember if it was TK50 or TK70 that
was the oldest compatible format. I have a SCSI-II DLT4000 drive (TK88
or 89??) and I know that doesn't read any old TK tapes, only DLT1,2
etc.
Yes, it should.
See http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&ved=0CGYQFjA…
(Page 5)
Page 5 of the PDF or the URL? ;)
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 8 Jun 2012, at 02:35, Dave McGuire wrote:
Dave outside your door is a well dressed gentleman in a
suit that looks like something a certain outrageous poet and author
wore, and has hair to match. (Hint: its the same daft stuff I
sometimes pull on Sampsa.) There's also a blue colored box
outside.........
Ok, you lost me there, my friend.
Welcome to the world of strange Dr Who references..
Sampsa
On 2012-06-08 10:06, Sampsa Laine wrote:
On 8 Jun 2012, at 00:10, Dave McGuire wrote:
Of course it'd be preferable in a dozen ways to have the native
kernel-based DECnet support continue to be maintained, alongside IPv4,
IPv6, etc where it belongs...but if we can't find anyone to do that
work, we'll have to solve the problem some other way, when it actually
becomes a problem.
The upside of this solution is that it's relatively portable though - I'd love to have a DECNET stack on my OS X boxes, for example (in fact as mentioned before latd DOES work on OS X as it's kinda implemented in a similar way)..
Which reminds me that I should work on/write a replacement lat suite, since the version out there today have some bugs. I've tried looking at it, but I'm just not into C++, or able to penetrate the code enough.
Anyway, using the lat client program supplied, connecting to RSX, it seems like it breaks the lat protocol sometimes. And unfortunately, the RSX LAT server have a bug triggered by the free lat implementation, in which the session gets lost, and as a result some memory is lost in RSX. This eventually cause the system to crash because no more free memory is available in DECnet.
Johnny
On 2012-06-08 09:56, Dave McGuire wrote:
On 06/08/2012 03:55 AM, Johnny Billquist wrote:
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
I take it TK50 tapes won't read in a later drive?
They will. TK70 and TK85 (if I remember right) can both read TK50.
You also have the TZ30 (I think the name is), which is a TK50
compatible, but smaller drive, with SCSI.
The TK85 can read TK50s? I didn't know that! If that's the case,
it's likely that the TF85 (DSSI version) may as well, and I have one of
those. That may be one more option to get my huge pile of TK50s read.
Yes, it should.
See http://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&ved=0CGYQFjA…
(Page 5)
Johnny
On 8 Jun 2012, at 00:10, Dave McGuire wrote:
Of course it'd be preferable in a dozen ways to have the native
kernel-based DECnet support continue to be maintained, alongside IPv4,
IPv6, etc where it belongs...but if we can't find anyone to do that
work, we'll have to solve the problem some other way, when it actually
becomes a problem.
The upside of this solution is that it's relatively portable though - I'd love to have a DECNET stack on my OS X boxes, for example (in fact as mentioned before latd DOES work on OS X as it's kinda implemented in a similar way)..
Sampsa
On 06/08/2012 03:55 AM, Johnny Billquist wrote:
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
I take it TK50 tapes won't read in a later drive?
They will. TK70 and TK85 (if I remember right) can both read TK50.
You also have the TZ30 (I think the name is), which is a TK50
compatible, but smaller drive, with SCSI.
The TK85 can read TK50s? I didn't know that! If that's the case,
it's likely that the TF85 (DSSI version) may as well, and I have one of
those. That may be one more option to get my huge pile of TK50s read.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-06-08 09:31, Mark Benson wrote:
On 8 Jun 2012, at 08:23, Dave McGuire<mcguire at neurotica.com> wrote:
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
I take it TK50 tapes won't read in a later drive?
They will. TK70 and TK85 (if I remember right) can both read TK50.
You also have the TZ30 (I think the name is), which is a TK50 compatible, but smaller drive, with SCSI.
Johnny
On 06/08/2012 03:39 AM, Kari Uusim ki wrote:
There is a DECnet stack for DOS and Windows in the Pathworks V5 or V6
client kit. Those versions were meant to be used on Windows'es before
Windows NT4. Then the Pathworks32 kit was released and that could be
used on WNT4.0 and Windows 2000. Maybe on XP as well. Don't remember for
sure.
Is this the same as DECnet-DOS? I ran that a long time ago. Does
anyone have a copy? It included drivers for that weird DEC ISA Ethernet
card, the DEPCA, which was a full-length 8-bit board that also included
(strangely) a mouse interface.
If not exactly the same, but a newer (and possibly enhanced) version. I
didn't deal with the PCSA versions (< V4.1) so I don't know about them.
Unfortunately I don't have the V4.1 either. Just the V5 and V6, which
were distributed on CD's.
Anyhow, the V5 or V6 DECnet stack should work on MS-DOS V5 and newer. I
don't remember if it was possible to install on older DOS versions. The
client medium has the supported adapter drivers (like DEPCA) included.
Neat!
Yes, indeed, I also have one or two DEPCA's somewhere. I think the mouse
port was meant for the DEC workstation mouse ("hockey puck") as PC mice
were serial port attached.
Yes, there were drivers in some packages that recognized those puck
mice with the DEPCA's controller. I ran Ventura Publisher (the GEM
version, pre-Windows port, under DOS 3.3) that way for a long time. It
worked well.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 8.6.2012 1:58, Dave McGuire wrote:
On 06/07/2012 12:11 PM, Kari Uusim ki wrote:
There is a DECnet stack for DOS and Windows in the Pathworks V5 or V6
client kit. Those versions were meant to be used on Windows'es before
Windows NT4. Then the Pathworks32 kit was released and that could be
used on WNT4.0 and Windows 2000. Maybe on XP as well. Don't remember for
sure.
Is this the same as DECnet-DOS? I ran that a long time ago. Does
anyone have a copy? It included drivers for that weird DEC ISA Ethernet
card, the DEPCA, which was a full-length 8-bit board that also included
(strangely) a mouse interface.
-Dave
If not exactly the same, but a newer (and possibly enhanced) version. I didn't deal with the PCSA versions (< V4.1) so I don't know about them. Unfortunately I don't have the V4.1 either. Just the V5 and V6, which were distributed on CD's.
Anyhow, the V5 or V6 DECnet stack should work on MS-DOS V5 and newer. I don't remember if it was possible to install on older DOS versions. The client medium has the supported adapter drivers (like DEPCA) included.
Yes, indeed, I also have one or two DEPCA's somewhere. I think the mouse port was meant for the DEC workstation mouse ("hockey puck") as PC mice were serial port attached.
Kari
On 06/08/2012 03:31 AM, Mark Benson wrote:
On 8 Jun 2012, at 08:23, Dave McGuire <mcguire at neurotica.com> wrote:
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
I take it TK50 tapes won't read in a later drive?
TK70 drives can read, but not write, TK50 tapes. I have several TK70
drives as well...that is my backup plan. (no pun intended! ;))
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
There are copies of WordPerfect for Solaris currently available on ebay UK.
I asked the question about WordPerfect for VMS on comp.os.vms - turns out there is a company still selling it. However, when I mentioned I was a hobbyist the communications went silent.
Mark.
Fri, Jun 8, 2012 at 4:40 AM, Dave McGuire <mcguire at neurotica.com> wrote:
On 06/07/2012 11:37 PM, Boyanich, Alastair wrote:
> There was wordperfect on VMS? Wow.
>
> I used to use the shared version of it on SCO in the early 90's. I
> didn't know there was a VMS version. That'd be interesting to see.
There was even a version for SunOS, with a fairly respectable WYSIWYG
GUI. I used that quite a bit Back In The Day(tm). I think I still have
it somewhere.
Those binaries will likely run under current Solaris on UltraSPARC;
I've been amazed at the degree of both architectural and ABI
compatibility between BSD-based SunOS 4 and SysV-based Solaris.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 8 Jun 2012, at 08:23, Dave McGuire <mcguire at neurotica.com> wrote:
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
I take it TK50 tapes won't read in a later drive?
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
On 06/08/2012 03:17 AM, Johnny Billquist wrote:
Ok. The next obvious thing is just cleaning. As with all tape drives,
the heads needs cleaning once in a while. Get isopropanol, some cotton
heads, and just clean them.
If things still fails after that, then I don't have any more quick
fixes. :-)
But next to the pickup, the cleaning have fixed countless of them for me.
I haven't tried cleaning TK50 heads in years, but I will (now that I
have a more respectable workspace) start trying that. I will let you
know how things go. I'll probably start digging into those within the
next month or two. Thank you for the suggestion!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-06-08 09:12, Dave McGuire wrote:
On 06/08/2012 03:09 AM, Johnny Billquist wrote:
The most common problem with the TK50 is that the tape pickup gets off
the holding arm. Easy to fix if you are comfortable with a screw driver.
I've had one or two TK50 go bad in other ways, but in my experience it's
pretty uncommon for them to really break.
It's almost always that pickup. Let me know if you need help
understanding that.
The "tongue"? Been fixing that problem for years. At one point I
ordered a box of (I think) ten of those while DEC was still selling them
as repair parts, but they're all gone now. Eventually the little
grabber end breaks off due to plastic fatigue.
The drives whose tongues are intact simply refuse to read and cause
device timeouts. I have at least 7 or 8 in that condition, with no
obvious mechanical flaws. I haven't dug into them very deeply.
Ok. The next obvious thing is just cleaning. As with all tape drives, the heads needs cleaning once in a while. Get isopropanol, some cotton heads, and just clean them.
If things still fails after that, then I don't have any more quick fixes. :-)
But next to the pickup, the cleaning have fixed countless of them for me.
Johnny
On 06/08/2012 03:13 AM, Johnny Billquist wrote:
But reading it through now, I see that there was one implicit assumption
in my text which I could have pointed out.
If you need to share the device with the system, while using a different
MAC address, you need to place the device in promiscuous mode. And such
is the case if we talk DECnet, since DECnet requires that you use a
specific MAC address which is not the same as the default MAC address of
a device.
In the case of Linux DECnet, it actually changes the "main" MAC
address of the interface, it doesn't add another one.
Right. And in that case, you don't need promiscuous mode.
We could go on about details, corner cases, other systems, potential
network problems, and so on... But I think we both know what we're
talking about, and I doubt we need to drag this any further. Contact me
directly if you want us to continue. :-)
I think what we need to do is convince Chrissie to continue working on
her DECnet implementation. =)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-06-08 09:07, Dave McGuire wrote:
On 06/08/2012 02:00 AM, Johnny Billquist wrote:
But reading it through now, I see that there was one implicit assumption
in my text which I could have pointed out.
If you need to share the device with the system, while using a different
MAC address, you need to place the device in promiscuous mode. And such
is the case if we talk DECnet, since DECnet requires that you use a
specific MAC address which is not the same as the default MAC address of
a device.
In the case of Linux DECnet, it actually changes the "main" MAC
address of the interface, it doesn't add another one.
Right. And in that case, you don't need promiscuous mode.
We could go on about details, corner cases, other systems, potential network problems, and so on... But I think we both know what we're talking about, and I doubt we need to drag this any further. Contact me directly if you want us to continue. :-)
Johnny
On 06/08/2012 03:09 AM, Johnny Billquist wrote:
The most common problem with the TK50 is that the tape pickup gets off
the holding arm. Easy to fix if you are comfortable with a screw driver.
I've had one or two TK50 go bad in other ways, but in my experience it's
pretty uncommon for them to really break.
It's almost always that pickup. Let me know if you need help
understanding that.
The "tongue"? Been fixing that problem for years. At one point I
ordered a box of (I think) ten of those while DEC was still selling them
as repair parts, but they're all gone now. Eventually the little
grabber end breaks off due to plastic fatigue.
The drives whose tongues are intact simply refuse to read and cause
device timeouts. I have at least 7 or 8 in that condition, with no
obvious mechanical flaws. I haven't dug into them very deeply.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-06-08 09:04, Dave McGuire wrote:
On 06/08/2012 07:48 AM, Peter Lothberg wrote:
I will set it aside if I find it, and make sure to image it.
Image all your TK50's with distribution stuff on drop Al K a copy.
I definitely will, if I can keep a drive working long enough. I have
probably fifteen TK50 drives here...most of which are dead. Although it
was the forerunner of the rather marvelous DLT, the first generation
really was a crappy design. :-(
The most common problem with the TK50 is that the tape pickup gets off the holding arm. Easy to fix if you are comfortable with a screw driver.
I've had one or two TK50 go bad in other ways, but in my experience it's pretty uncommon for them to really break.
It's almost always that pickup. Let me know if you need help understanding that.
Johnny
On 06/08/2012 07:14 AM, Peter Lothberg wrote:
Can you talk to sol::
I can't seem to get to it from my Linux desktop machine, no, but I can
SET HOST to it from my Alpha running VMS. (which I'm reaching from the
aforementioned Linux machine!)
It seems that off-net DECnet routing isn't happening from the Linux
machine..? What's up with this, does anyone know?
Is it connetivity (routing), or the fact that the linux implementation
only speaks VMSnet?
That I do not know.
Does the linux box talk to stupi::
No, it times out. :-(
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 06/08/2012 02:00 AM, Johnny Billquist wrote:
But reading it through now, I see that there was one implicit assumption
in my text which I could have pointed out.
If you need to share the device with the system, while using a different
MAC address, you need to place the device in promiscuous mode. And such
is the case if we talk DECnet, since DECnet requires that you use a
specific MAC address which is not the same as the default MAC address of
a device.
In the case of Linux DECnet, it actually changes the "main" MAC
address of the interface, it doesn't add another one.
And to make a correction to your text, when not in promiscuous mode,
your ethernet controller will filter out packets that do not have your
MAC address, and packets that don't have the multicast bit set (possibly
you can also get it to filter more specific on multicast ethernet
packets, but multicast is a separate story from unicast packets on
ethernet controllers anyway).
Oh yes, I'm sorry for my omission.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 06/08/2012 07:48 AM, Peter Lothberg wrote:
I will set it aside if I find it, and make sure to image it.
Image all your TK50's with distribution stuff on drop Al K a copy.
I definitely will, if I can keep a drive working long enough. I have
probably fifteen TK50 drives here...most of which are dead. Although it
was the forerunner of the rather marvelous DLT, the first generation
really was a crappy design. :-(
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-06-08 08:39, Boyanich, Alastair wrote:
Hi Johnny,
Your welcome. Yes, it's pretty chatty. MIPSPro and DECC are my favourite
C compilers as they're quite anal and chatty warning wise.
Yeah. gcc is stupid. They added -Wall several years ago, but apparently people got upset by it's anal reporting, so they dumbed it down. So -Wall does not turn on all warnings anymore. And I just don't have the enery right now to figure out what more switches I should throw on it to actually make it complain about everything...
Sounds good. New code arrives I'll check it out. :)
The new code is already accessible. Same place as always...
Johnny
Al.
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Johnny Billquist
Sent: Friday, 8 June 2012 4:35 PM
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] New bridge.c feedback
On 2012-06-08 01:30, Boyanich, Alastair wrote:
Hi Johnny,
Yes. It seems to want<strings.h> 6.5.24 and above (or 6.5.29f in my
case) was aiming at SUSv3 compliance away from base XPG4 so things
were
moved to strings.h
(http://pubs.opengroup.org/onlinepubs/009695399/functions/index.html) ..
it's also in the 3c index man page, you were right.
Excellent. Included strings.h as well now. Not a problem on the
systems
here. We'll see if it hits problems for anyone else.
So, compiles on IRIX 6.5.29 if the header is included. Worth gating
it
in via #ifdef ? I'm also a fan of enum types. Binary emitted is
~298kb.
Also, your welcome to an account on the system if you wish to
poke/play
around, it's accessible over ssh and the general internet (it's my
daily
shell/hacking on code box).
-Wall makes the MIPSpro runtime *extremely* chatty. It's quite anal.
See
below.
Even better. Thanks.
cc-3201 cc: REMARK File = bridge.c, Line = 158
The parameter "data" was never referenced.
int lookup(struct sockaddr_in *sa, char *data)
^
Yeah. I noticed that one too. I don't remember why data was in there
in
the first place, since I'm not using it. Might as well drop it.
cc-1506 cc: REMARK File = bridge.c, Line = 460
There is an implicit conversion from "unsigned long" to "long";
rounding, sign
extension, or loss of accuracy may result.
delta = timedelta(bridge[index].lasttime);
^
Thanks.
cc-3201 cc: REMARK File = bridge.c, Line = 559
The parameter "r" was never referenced.
void dump_nomatch(struct sockaddr_in *r, struct DATA *d)
^
That one is because dump_nomatch is a function I wrote for debugging
help. The body of the function is normally empty, since it's inside a
#if
Need to think a little about how/if I'll get rid of that warning...
cc-3201 cc: REMARK File = bridge.c, Line = 559
The parameter "d" was never referenced.
void dump_nomatch(struct sockaddr_in *r, struct DATA *d)
^
Same story...
cc-1185 cc: WARNING File = bridge.c, Line = 579
An enumerated type is mixed with another type.
d->type = classify_packet(d);
^
That one should already have been fixed...
cc-1171 cc: WARNING File = bridge.c, Line = 685
The indicated expression has no effect.
if (port == 0) port == DPORT;
^
Also alredy fixed...
cc-1498 cc: REMARK File = bridge.c, Line = 709
There is no prototype for the call to read_conf.
read_conf();
^
Think I fixed that. However, this is a little messy, since I'm doing
things slightly unconventional. read_conf() is called both in the
normal
main program, and is also the signal handling function for SIGHUP.
However, signal functions actually takes one argument. By setting up a
prototype, I had to include one argument here, which is unused (I
totally don't care about it), so now you might get a warning about an
unused parameter. But prototypes are a good thing, so the unused
parameter warning is better to have.
cc-1209 cc: REMARK File = bridge.c, Line = 715
The controlling expression is constant.
while(1) {
^
Yes. That's how you get an infinite loop. :-)
Thanks for the feedback. See what happens with the fixed code...
Johnny