SYSRUTH@UTORPHYS.BITNET.UUCP (02/10/87)
OK, here we go one more time. This is the third time I have tried to post this message (an URGENT one) to the list. I have not seen it come back. What I HAVE seen is about a dozen messages along the lines of "mail undeliverable for 2 days; will try 1 more day" etc. Some of you also appear to have exceeded your diskquota and it is undeliverable for that reason. My apologies (again) if you have seen this before. But I desperately need an answer to point 3, and I have received neither the message back, nor any replies. It is not a problem with my machine; MAIL waits for it if it is down (and then comes through in a torrent!). Does anyone have any idea what might have been happening? Is "info-vax@sri-kl.arpa" still the right destination, or did I miss that, too? Is there a BITNET address I could send it to instead (anybody out there have a 99% reliable gateway to sri-kl, or are you all going through Wiscarpa?). No offence to the Wiscarpa people, but this is getting very hard to take. Usually I see my own message within 24 hours of sending it! Anyway, here it is... ------------------------------------------------------------------ From: ATLAS::SYSRUTH 5-FEB-1987 12:48 To: Orig_To! info-vax@sri-kl.arpa, SYSRUTH Subj: tcp info file, MAIL COMPRESS, and DLVJ1's Several things this time: 1. I could not reach the following people who requested a copy of my collection of TCP responses: R. Haslam, I. Ahn, D. Morgan, and S. Cavrak. Please send me a FULL address (some of it gets truncated or left out in the messages you send me) if you still want a copy. Preferably something not too far removed from BITNET if possible. 2. A note about the MAIL COMPRESS command - it does NOT lock the MAIL.MAI file, or at least it didn't in 4.3. I got a message once during a COMPRESS and had to use the SET FILE command to get at it - it was in MAIL.OLD. Maybe they have fixed this in 4.4 (did they FIX anything in 4.4?). I would be interested to know what sort of message it gives someone trying to send a COMPRESSor mail. "File locked by another user" would not be very helpful. 3. A plea for HELP! We have just received a DLVJ1-M 4-line asynch. terminal line Q-bus interface. It is covered in jumpers. According to the technical manual that came with it, some of the features (speed etc.) are software settable. It is my understanding that this device uses the DLDRIVER. Is this the case? Is it truly software settable or do we have to pick a speed, wire it, and stick to it? What device names do things show up as? Would the SET TERM commands work the way they do with DZQ lines, or would we be stuck with SET DEVICE? I would try some of these things out for myself, but it is a production machine being used exclusively by one group in our department, and I can't take it away from them for long to play with it. CSR's and vector's (ignore the last apostrophe) should not be a problem as the CSR is uniqie uniqUe (having problems today - got bitten by a squirrel this morning) and we have nothing else at vector 300. Which brings me to another question - since the driver comes with uVMS, will the device autoconfigure? Thanks for any help you folks can give on this one. I have no exposure to the original UNIBUS device this is based on, either, so you'll need to get down to reasonably basic points (this is what I get for being non- technical - but that's changing!). Ruth Milner System Manager University of Toronto Physics SYSRUTH@UTORPHYS (BITNET)
cetron%utah-ced@UTAH-CS.ARPA.UUCP (02/10/87)
DLVJ1's.....what I remember from a quick (disgusting) look at one: 1. They are not silo'd or DMA capable so you should have them up at the front of the backplane... 2. Some functions are software selectable, others are put in by hard jumpers.... it depends on the operating system (some have support for the software selectable features, others do not). 3. According to my Microvax hardware manual, microvms does NOT support the DLVJ1 yet.....in 1985.... and my newer 1986 manual doesn't even mention it..... 4. DLVJ1's are really 4 dlv11's on one board so you must consider it as 4 seperate devices with four seperate csr's and vectors not just the one at 300. 5. Since 1 above and other internal considerations, DL's are NOT ABLE TO RUN AT OVER 1200 BAUD RELIABLY!!!!!!!. If you do so, you will every so often lose the rx or tx interrupt enable and that channel will be useless until totally reset (on vms i think it requires a reboot, on rsx you can poke the csr through the I/O page from dcl....) 6. If you really need to know whether microvms supports the dlvj's let me know direct and I will peruse the 'fiche... -ed cetron univ of utah...