INFO-VAX Mon, 05 May 2008 Volume 2008 : Issue 250 Contents: Re: OT: Digital responsible for first SPAM message ! Re: OT: Digital responsible for first SPAM message ! Re: OT: Digital responsible for first SPAM message ! Re: RMS record much longer that format attribute proclaims. Re: TCPIP$CONFIG What systems can use USB? Re: What systems can use USB? Re: XP1000 workstations going low pricing ! ---------------------------------------------------------------------- Date: Sun, 4 May 2008 16:01:34 -0400 From: "John Vottero" Subject: Re: OT: Digital responsible for first SPAM message ! Message-ID: "Richard B. Gilbert" wrote in message news:jcKdnZUaj92rO4DVnZ2dnUVZ_oTinZ2d@comcast.com... > JF Mezei wrote: >> It ahs been 30 years on May 1st that the first spam was allegedly sent. >> >> http://www.templetons.com/brad/spamreact.html >> >> It came from Digital Equipment Corportation ! >> >> >> Another "first" that DEC can claim :-) > > A "technical" violation perhaps. But I've always thought of the Canter & > Siegel "Green Card" mailing as the first spam. That was Usenet. ------------------------------ Date: Sun, 4 May 2008 14:06:22 -0600 From: "Michael D. Ober" Subject: Re: OT: Digital responsible for first SPAM message ! Message-ID: "Richard B. Gilbert" wrote in message news:jcKdnZUaj92rO4DVnZ2dnUVZ_oTinZ2d@comcast.com... > JF Mezei wrote: >> It ahs been 30 years on May 1st that the first spam was allegedly sent. >> >> http://www.templetons.com/brad/spamreact.html >> >> It came from Digital Equipment Corportation ! >> >> >> Another "first" that DEC can claim :-) > > A "technical" violation perhaps. But I've always thought of the Canter & > Siegel "Green Card" mailing as the first spam. > I concur with Richard Gilbert. This was a "directed marketing email" that went awry. The Canter & Segel Green Card went to everyone on the internet at the time regardless of the recipients citizenship/immigration status. Mike Ober. ------------------------------ Date: Sun, 04 May 2008 18:08:20 -0700 From: foo@bar.com Subject: Re: OT: Digital responsible for first SPAM message ! Message-ID: On Sun, 4 May 2008 14:06:22 -0600, "Michael D. Ober" wrote: >"Richard B. Gilbert" wrote in message >news:jcKdnZUaj92rO4DVnZ2dnUVZ_oTinZ2d@comcast.com... >> JF Mezei wrote: >>> It ahs been 30 years on May 1st that the first spam was allegedly sent. >>> >>> http://www.templetons.com/brad/spamreact.html >>> >>> It came from Digital Equipment Corportation ! >>> >>> >>> Another "first" that DEC can claim :-) >> >> A "technical" violation perhaps. But I've always thought of the Canter & >> Siegel "Green Card" mailing as the first spam. >> > >I concur with Richard Gilbert. This was a "directed marketing email" that >went awry. The Canter & Segel Green Card went to everyone on the internet >at the time regardless of the recipients citizenship/immigration status. So what ever happened to Spamford Wallace? ------------------------------------------ NO, use John Mee3 at comcast dot net (remove the spaces and do the obvious with the "dot" and the "at" ------------------------------ Date: Sun, 4 May 2008 16:29:49 -0400 From: norm.raphael@metso.com Subject: Re: RMS record much longer that format attribute proclaims. Message-ID: This is a multipart message in MIME format. --=_alternative 0070CB5E8525743F_= Content-Type: text/plain; charset="US-ASCII" Hein RMS van den Heuvel wrote on 05/04/2008 02:15:04 AM: > On May 3, 10:42 pm, norm.raph...@metso.com wrote: > > DJD> > I read once that some programs use the LRL value at file ((SYS) > $)OPEN > DJD> > time to initially allocate buffer space. > > > > In this case, EVE refused to open the file until the attribute was > > adjusted. > > I think the TPU default USZ (RMS User Buffer siZe) currently is > min(2048,LRL) > Could be 2000 > > > I'm still unable to generate 255, 255 from a simple edit, modify, save.... > > Of course not. > You are not listening! > (Only minor disrespect intented :-) :-) Of course I'm not listening (no disrespect intended (or felt)). > > Normal RMS (such as used by simple edit) does not do this. > It takes a DECCRTL or similar 'smart' tool, to mess this up. > > You have an account on eisner (or an other system with perl) right? > Try this: > > $ delete x.x.* > $ x := x.x > $ perl -le "print qq($_ ) x $_ ** 3 for (1..10)" > 'x > $ write sys$output f$file(x,"MRS"), " ", f$file(x,"LRL") > $ def decc$default_lrl 255 > $ perl -le "print qq($_ ) x $_ ** 3 for (1..10)" > 'x > $ write sys$output f$file(x,"MRS"), " ", f$file(x,"LRL") > $ set file/attribute=mrs=255 'x > $ perl -le "print qq($_ ) x $_ ** 3 for (1..10)" > 'x > $ write sys$output f$file(x,"MRS"), " ", f$file(x,"LRL") > > So let me ask again... Who / What wrote the file? > I didn't mean to reopen this as I shall never see it again. When testing, our app will write the file max 255, longest 88 (if the longest record is 88) unless the last record written is empty, then we seem to see max 255, longest 255. When things are working and the input produces the really long output record, then we see max 0, longest 32767. So the app in testing is not always the same. That doesn't explain how a log file with a long record got the shorter attributes. I've never seen this in production, so it's not worth persuing by me. EVE (edt emulation) did balk at opening it at 255,255. > Cheers, > Hein. --=_alternative 0070CB5E8525743F_= Content-Type: text/html; charset="US-ASCII"



Hein RMS van den Heuvel <heinvandenheuvel@gmail.com> wrote on 05/04/2008 02:15:04 AM:

> On May 3, 10:42 pm, norm.raph...@metso.com wrote:
>
> DJD> > I read once that some programs use the LRL value at file ((SYS)
> $)OPEN
> DJD> > time to initially allocate buffer space.
> >
> > In this case, EVE refused to open the file until the attribute was
> > adjusted.
>
> I think the TPU default USZ (RMS User Buffer siZe) currently is
> min(2048,LRL)
> Could be 2000
>
> > I'm still unable to generate 255, 255 from a simple edit, modify, save....
>
> Of course not.
> You are not listening!
> (Only minor disrespect intented :-) :-)


Of course I'm not listening  (no disrespect intended (or felt)).

>
> Normal RMS (such as used by simple edit) does not do this.
> It takes a DECCRTL or similar 'smart' tool, to mess this up.
>
> You have an account on eisner (or an other system with perl) right?
> Try this:
>
> $ delete x.x.*
> $ x := x.x
> $ perl -le "print qq($_ ) x $_ ** 3 for (1..10)" > 'x
> $ write sys$output f$file(x,"MRS"), " ", f$file(x,"LRL")
> $ def decc$default_lrl 255
> $ perl -le "print qq($_ ) x $_ ** 3 for (1..10)" > 'x
> $ write sys$output f$file(x,"MRS"), " ", f$file(x,"LRL")
> $ set file/attribute=mrs=255 'x
> $ perl -le "print qq($_ ) x $_ ** 3 for (1..10)" > 'x
> $ write sys$output f$file(x,"MRS"), " ", f$file(x,"LRL")
>
> So let me ask again... Who / What wrote the file?
>

I didn't mean to reopen this as I shall never see it again.

When testing, our app will write the file max 255, longest 88
(if the longest record is 88) unless the last record written
is empty, then we seem to see max 255, longest 255.

When things are working and the input produces the really
long output record, then we see max 0, longest 32767.  So the
app in testing is not always the same.  That doesn't explain
how a log file with a long record got the shorter attributes.
I've never seen this in production, so it's not worth persuing
by me.

EVE (edt emulation) did balk at opening it at 255,255.

> Cheers,
> Hein.
--=_alternative 0070CB5E8525743F_=-- ------------------------------ Date: Sun, 04 May 2008 18:22:24 -0400 From: JF Mezei Subject: Re: TCPIP$CONFIG Message-ID: <481e37e4$0$20612$c3e8da3@news.astraweb.com> Tom Linden wrote: >> the CONFIGURATION.DAT one contains your interface definitions. (stuff > The file itself is not really readable It is a "binary" file. But the point is that if there is some corruption in it, you can delete it and start the tcpip$config procedure from scratch and it will create a new configuration.dat file. >> Does TCPIP> SHOW NAME provide any meaningful output ? > Yes, but it also has the old IPs for the servers, rerunning BIND doesn't > remove them. Except for SET NAME/INIT, all other aspects of SET NAME and SET HOST are related to the RESOLVER (aka: the client on this particular node). This is separate from the BIND server which can run on the same node, but could be anywhere. Restarting the BIND server (or doing SET NAME/INIT) rereads the config files in TCPIP$BIND_COMMON directory (notably TCPIP$BIND.CONF which points to the various zone files (.db) SET NAME/SYSTEM changes the dynamic RESOLVER settings. SET CONF NAME changes the permanent RESOLVER settings. If you wish to test the BIND SERVER despite the resolver being broken: $NSLOOKUP > SET SERVER ip.address.of.bind.server and then you can make requests and they will be resolved by that bind server. ------------------------------ Date: 5 May 2008 01:31:20 GMT From: healyzh@aracnet.com Subject: What systems can use USB? Message-ID: I just found my stash of USB 2.0 cards. What systems will work with a USB 2.0 PCI card? I gather they should work in my XP1000's, but what about something like my AlphaStation 200 4/233's? This would be while running OpenVMS 8.3. Zane ------------------------------ Date: Sun, 4 May 2008 20:40:07 -0700 (PDT) From: sms.antinode@gmail.com Subject: Re: What systems can use USB? Message-ID: <9df82609-7138-4545-aeec-5d2e27b024fd@b64g2000hsa.googlegroups.com> heal...@aracnet.com wrote: > I just found my stash of USB 2.0 cards. What systems will work with a USB > 2.0 PCI card? I gather they should work in my XP1000's, but what > about something like my AlphaStation 200 4/233's? This would be while > running OpenVMS 8.3. A better question might be, "Which USB cards will work in an Alpha VMS V8.3 system?" As it's likely that no such cards are supported in either system, and you've provided no identification for the cards, you'll probably need to run the experimant, in any case. I stopped using my AlpSta 200 4/233 systems before I got my USB cards, and their PCI slots were filled with graphics and network cards, so I was never tempted to try a USB card there. SMS. ------------------------------ Date: 5 May 2008 01:36:47 GMT From: healyzh@aracnet.com Subject: Re: XP1000 workstations going low pricing ! Message-ID: David J Dachtera wrote: > Found a couple on eBay in the $800 range. Not as filled out with extras. > So, Islandco's price is probably reasonable. > If I could justify it, I'd think about it. The fastest Alpha I have is > the AS200/EV4 at 233MHz. Sounds pretty reasonable to me as well, especially since you're buying from a reputable dealer. I guess I timed it right a couple years ago when I got a 500 and a 666 for $200 each on eBay. I was really shocked to see what they're going for on eBay now. Zane ------------------------------ End of INFO-VAX 2008.250 ************************