Re: AlphaServer 2100s available
On Fri 15. Apr 2022 at 11:43, Alan Perry via cctalk wrote: > > On 4/15/22 9:53 AM, Dave Wade G4UGM via cctalk wrote: > >> -Original Message- > >> From: cctalk On Behalf Of Alan Perry > via > >> cctalk > >> Sent: 15 April 2022 16:00 > >> To: cctalk@classiccmp.org > >> Subject: Re: AlphaServer 2100s available > >> > >> I wouldn't expect commercial value to come into the discussion on this > list. I > >> am wondering what other hobbyists pay in order to gauge whether the > price > >> that a local recycler is asking for one (which was around > >> $100) is fair. > > If its working and boots up I would say that is very reasonable. > > > Oh, don't say that. My garage is filling up with sun3 desksides and > drive pedestals :) > > The note on it says that it doesn't boot, but they had the same note on > the Axil 320 (SS20 clone) that I got from them and it booted up fine > once I put a HDD in it. Unrelated to the current discussion, but since you mention your Axil 320: do you have a way of reading the OBP PROM for that? I have been looking for that! Cheers, Malte >
Re: Sun-2 and Sun-3 mice (eBay)
Hi, On Thu, Oct 28, 2021 at 05:00:26PM -0400, Ethan Dicks via cctalk wrote: > On Thu, Oct 28, 2021 at 10:00 AM Alan Perry wrote: > > Aside from the posts on the side of the connector, what is unique about the > > cable and connector? What’s the deal with those posts? Aside from them, it > > looks like a 6P4C with only three leads connected. > > AFAIK, the posts are there so you don't plug your mouse into a phone > jack or a modem port. There are cutouts on the back of the Sun3 > keyboard to admit that connector. > > One could almost certainly start with a 6P4C cable and fix up the > mouse end and re-use a Sun4 mouse, but for show/display purposes, it > would be clearly a substitute. I am using a MiniDIN-8(F) to 6P4C (without those posts) cable I made to connect a type 4 mouse to my type 3 keyboard. Works perfectly. I think I found the pinouts for type 3 and type 4 mice in the SUN Hardware Reference? If anyone has trouble figuring it out I can measure the connections on my adapter and post them. Cheers, -- Malte Dehling
Looking for older versions of MatLab for Unix / VMS
Dear List, I am looking for older versions of MatLab (3.x, 4.x, and 5.x) for Unix and (Open)VMS. I'm happy to pay a reasonable price for media kits, or, alternatively, images of the installation media would suffice. The media for Windows or Mac can be found on the various abandonware sites, but I've had no luck finding MatLab for Unix / VMS so far. Cheers Malte -- Malte Dehling
Re: Wanted: Sun Sparcstation Classic/LX PS Fan
Hi Kurt, did you see the reply you got on the res...@sunhelp.com mailing list? The fan is a 12v 60x25mm 14cfm according to the Nidec TA225DC datasheet. Cheers, Malte On Mon, Sep 13, 2021 at 3:17 AM Kurt Nowak via cctalk wrote: > Hi All, > > Does anyone by chance have a collection of fans? The one in my Sun Sparc > Classic died and I am having a hard time finding a replacement with the > same specs. Or can anyone recommend a good source? > > It's a Nidec BetaV, TA225DC, Model M33402-55 > > Thanks! > > -Kurt >
Re: Mounting ULTRIX CDROMs on Linux
On Thu, May 20, 2021 at 04:11:18PM -0400, John-Paul Stewart via cctalk wrote: > On 2021-05-20 4:01 p.m., Warner Losh via cctalk wrote: > > On Thu, May 20, 2021 at 1:56 PM Antonio Carlini via cctalk < > > cctalk@classiccmp.org> wrote: > > > >> I'm running Linux Mint (an ubuntu derivative) and I want to mount ULTRIX > >> CDROM discs to see what I can see. > >> > >> (I'm eventually going to image these, but I presume that will "just > >> work" with dd or ddrescue). > >> > >> They are supposed to be UFS format (according to the net) and that > >> usually means you have to tell mount exactly which option to use (as not > >> all UFS implementations are compatible). > >> > >> I've tried (all the options I can find) and failed: > >> > >> $ sudo mount -t ufs -o ufstype=44bsd /dev/sr1 /tmp/mount > > > > 44bsd is likely too new. ufstype=old or =sunos or =sun might work. > > Setting ufstype=sun will indeed work for loopback mounting Ultrix CD images. > > With physical CDs, the Linux CD-ROM driver expects the filesystem to use > 2048 byte blocks but the UFS CDs have 512 byte blocks. So you'll also > have to add "loop" to the options: > > sudo mount -t ufs -o ro,ufstype=sun,loop /dev/sr1 /tmp/mount > > That will mount the physical CD using a loopback device so you can > access the 512 byte per block filesystem. (FWIW, I learned that trick > with IRIX EFS CDs, which have the same problem.) Wow! I never expected to learn something new about mounting CDs tonight :-) Thanks! -- Malte Dehling
Re: Mounting ULTRIX CDROMs on Linux
On Thu, May 20, 2021 at 02:01:21PM -0600, Warner Losh via cctalk wrote: > On Thu, May 20, 2021 at 1:56 PM Antonio Carlini via cctalk < > cctalk@classiccmp.org> wrote: > > > I'm running Linux Mint (an ubuntu derivative) and I want to mount ULTRIX > > CDROM discs to see what I can see. > > > > (I'm eventually going to image these, but I presume that will "just > > work" with dd or ddrescue). > > > > They are supposed to be UFS format (according to the net) and that > > usually means you have to tell mount exactly which option to use (as not > > all UFS implementations are compatible). > > > > > > I've tried (all the options I can find) and failed: > > > > > > $ sudo mount -t ufs -o ufstype=44bsd /dev/sr1 /tmp/mount > > > > 44bsd is likely too new. ufstype=old or =sunos or =sun might work. I just tried on an Ultrix 4.5 ISO and I was able to mount it with ufstype=old or without a ufstype option. Cheers, Malte -- Malte Dehling
Re: VAXstation 4000 Mice?
On Thu, May 20, 2021 at 05:58:22PM +, Jonathan Stone wrote: > > > On Thursday, May 20, 2021, 10:38:56 AM PDT, Malte Dehling via cctalk > wrote: > > > The VSXXX-GA mouse or VSXXX-AB tablet is the correct model for the 4000 > > series, but the older puck mouse (VSXXX-AA) will work as well. > > Exactly, since the -GA is compatible with the -AA. And the MoseTrack > model M5 DEC trackball should work too, if you can find one in working > condition. The Service Guide really does say "VSXXX-AA mouse or > VSXXX-AB tablet" EK-V48VB-SV.001, p. 1-1. Interesting. I looked it up in the "VAXstation 4000 Model 60 and VLC Condensed Service Information" (EK-V466H-PS.A01), and on page D-4 (for the Model 60) and page D-8 (for the VLC) it lists the VSXXX-GA (and the tablet, but only for the Model 60,) but not the VSXXX-AA :-) > I've never owned a VLC, so I don't know what was actually delivered. I > can't find EK-VAXVL-OG. Neither do I. -- Malte Dehling
Re: VAXstation 4000 Mice?
On Thu, May 20, 2021 at 05:22:05PM +, Jonathan Stone via cctalk wrote: > On Thursday, May 20, 2021, 10:16:03 AM PDT, Zane Healy via cctalk > wrote: > > What sort of mice does a VAXstation 4000 (vlc/60/90) take? I’m > > pretty sure they don’t need a DEC “hockey puck” mouse. > > It does indeed need a VSXXX-AA mouse (the round puck) or a VSXXX-AB > tablet (or compatible). \ I recently checked both installation guide > and service guide, whilst looking at eBay offerings. The VSXXX-GA mouse or VSXXX-AB tablet is the correct model for the 4000 series, but the older puck mouse (VSXXX-AA) will work as well. -- Malte Dehling
Still looking for VAXSET <= v7.0
Dear list, through Antonio's efforts, we have now archived ISOs for a number of early CONDIST CDs. Unfortunately, this did not help me find a version of the VAXSET Software Engineering Tools for VMS 4.x that I was looking for: - CONDIST 1989-07 contains VAXSET v8.0, which requires VMS 5.0/5.1. - CONDIST 1989-05 does not contain any VAXSET components. So my hope now is that someone may still have old TK50 or 9-Track distribution tapes stored away for VAXSET v7.0 or earlier, or for some of its components: - LSE Language Sensitive Editor v2.2 or earlier - SCA Source Code Analyzer v1.2 or earlier - PCA Performance Coverage Analyzer v2.0 or earlier - DTM DEC/Test Manager v2.3 or earlier (I already have CMS and MMS.) Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Mon, May 17, 2021 at 12:46:31PM -0700, Zane Healy wrote: > > On May 16, 2021, at 5:51 AM, Malte Dehling via cctalk > > wrote: > > I have now generated a contents listing for the CONOLD CDs: > > > > https://archive.org/details/vms-conold-1989-03 > > https://archive.org/details/vms-conold-1989-07 > > Did you read these on a VAX? I’m trying to use MGBOOK (based on > VTBOOK), to read the files from > CDROM-AG-NC67C-RE-1989-07-VMS-CONOLD.iso. I’m on a system running > VAX/VMS 5.5-2, and I am able to read the DECW$BOOKSHELF files, but not > the DECW$BOOK files. > > I’m able to read the Bookreader documentation installed with VAX/VMS > 5.5-2 just fine using MGBOOK. I just did a TYPE *.DECW$BOOKSHELF in a simulated vax and wrote a little python script to generate the contents listing. I don't know MGBOOK, so I can't help you there. On my VAXstation 3100 running VMS 5.5-2, I can read the documentation using the standard DECW$BOOKREADER application after doing: DEFINE/SYSTEM DECW$BOOK DKA400:[DECW$BOOK] Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Fri, May 14, 2021 at 11:47:09AM +0200, Malte Dehling wrote: > I plan on updating the description for the CONOLD CDs with a list of > the books included. That probably means writing a script to extract > that information from the DECW$BOOKSHELF files. I have now generated a contents listing for the CONOLD CDs: https://archive.org/details/vms-conold-1989-03 https://archive.org/details/vms-conold-1989-07 Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Thu, May 13, 2021 at 08:18:33PM +0100, Antonio Carlini wrote: > On 12/05/2021 13:58, Malte Dehling wrote: > > > > Here are the links to the relevant archive.org uploads: > > > > https://archive.org/details/vms-conold-1989-07 > > https://archive.org/details/vms-ad-condist-1989-07 > > https://archive.org/details/vms-condist-1989-07 > > https://archive.org/details/vms-condist-1989-11 > > https://archive.org/details/digital-standards-1993-03 > > > > Let me know what you think! > > Thanks. Nice work, particularly grouping them together, pulling out the > JPEGs and seemingly mounting them to suck out the CD_CONTENTS.DAT! > > As a reward for your hard work here are a few more for you :-) > > I've now uploaded ag-nc67a-re.tar.xz, ag-mn36d-re.tar.xz and > ag-pcy4c-xe.tar.xz. > > These are: > > AG-NC67A-RE - VMS Online Documentation Library 1989-03 Disc 1 of 1 > AG-MN36D-RE - VMS Consolidated Software Distribution 1989-05 Disc 1 of 1 > AG-PCY4C-XE - InfoServer V2.0 Software Base Level 10 1991-11 Disc 1 of 1 Perfect! Thanks so much :-) The first two are now also on archive, the InfoServer CD will follow soon: https://archive.org/details/vms-conold-1989-03 https://archive.org/details/vms-condist-1989-05 I plan on updating the description for the CONOLD CDs with a list of the books included. That probably means writing a script to extract that information from the DECW$BOOKSHELF files. > AG-MN36D-RE in particular took over 5 days to rescue. In the end it managed > 99.41% and couldn't get any more data off the CDROM when run with -R. So, > despite the internet saying use 2000 and 3000 grit sandpaper, I went against > all the advice and recklessly tried a seven minute does of 1500 frit > sandpaper, followed by the usual vigorous polishing. I've included a > "before" image of the rear (non-label) side of the CDROM and a triangular > "blemish" is clearly visible near the centre and extending out into the data > region. 2000 grit didn't touch it, I could still feel it afterwards with my > fingernail. 1500 grit wiped it away completely and ddrescue got to work > immediately and took just 10 minutes or so to recover the missing data > (apart from 4096 bytes). Wow, thanks a lot! You are putting in some serious effort here! I'm glad this worked so well :-) Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Fri, May 14, 2021 at 09:40:34AM +0100, Antonio Carlini via cctalk wrote: > On 14/05/2021 00:19, Matt Burke via cctalk wrote: > > You might want to have a look at http://de.openvms.org/spl.php > > Thanks, that looks really useful. I'll have to work out which updates to > send him. I talked to him a while ago and I've sent him the cd_contents.dat files for your first round of uploads already (which is what he needs to update the database.) I'll send him the newer ones, too. Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Wed, May 12, 2021 at 02:52:26PM +0200, Malte Dehling wrote: > > On 10/05/2021 10:05, Malte Dehling wrote: > > > I think uploading them to archive.org would be a good long-term > > > solution. I can take care of it if you don't have an account. > > > > Please do. Thanks. > > Will do. I'll let you know. Here are the links to the relevant archive.org uploads: https://archive.org/details/vms-conold-1989-07 https://archive.org/details/vms-ad-condist-1989-07 https://archive.org/details/vms-condist-1989-07 https://archive.org/details/vms-condist-1989-11 https://archive.org/details/digital-standards-1993-03 Let me know what you think! Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
(I had accidentally sent my reply below only to Antonio. I'm resending it to the list.) > On 10/05/2021 10:05, Malte Dehling wrote: > > Thanks a lot, Antonio, these are very valuable to have! > I've only checked a couple of them under SIMH, so it would be helpful to > know if I need to check my workflow or not. > > I think uploading them to archive.org would be a good long-term > > solution. I can take care of it if you don't have an account. > > Please do. Thanks. Will do. I'll let you know. > In other news, I polished the MAR-1989 CONOLD, which looked very bad, to > start with. Amazingly it buffed up quite nicely and then read surprisingly > well: > > [ > > $ ddrescue -r5 -v /dev/sr1 CDROM-AG-NC67A-RE-1989-03-VMS-CONOLD.iso > CDROM-AG-NC67A-RE-1989-03-VMS-CONOLD.map > GNU ddrescue 1.23 > About to copy 205199 kBytes from '/dev/sr1' to > 'CDROM-AG-NC67A-RE-1989-03-VMS-CONOLD.iso' > Starting positions: infile = 0 B, outfile = 0 B > Copy block size: 128 sectors Initial skip size: 128 sectors > Sector size: 512 Bytes > > Press Ctrl-C to interrupt > ipos: 205198 kB, non-trimmed: 0 B, current rate: 0 B/s > opos: 205198 kB, non-scraped: 0 B, average rate: 637 kB/s > non-tried: 0 B, bad-sector: 2048 B, error rate: 170 B/s > rescued: 205197 kB, bad areas: 1, run time: 5m 22s > pct rescued: 99.99%, read errors: 25, remaining time: n/a > time since last successful read: 2m 1s > Finished > ] > > > So I went ahead and tried the CONDIST from MAY-1989. That too now can be > read, although it is proving a somewhat tougher nut to crack: > > [ > > $ ddrescue -r5 -v /dev/sr1 CDROM-AG-MN36D-RE-1989-05-VMS-CONDIST.iso > CDROM-AG-MN36D-RE-1989-05-VMS-CONDIST.map > GNU ddrescue 1.23 > About to copy 623247 kBytes from '/dev/sr1' to > 'CDROM-AG-MN36D-RE-1989-05-VMS-CONDIST.iso' > Starting positions: infile = 0 B, outfile = 0 B > Copy block size: 128 sectors Initial skip size: 128 sectors > Sector size: 512 Bytes > > Press Ctrl-C to interrupt > ipos: 5919 kB, non-trimmed: 0 B, current rate: 0 B/s > opos: 5919 kB, non-scraped: 11127 kB, average rate: 14694 B/s > non-tried: 0 B, bad-sector: 2843 kB, error rate: 85 B/s > rescued: 609276 kB, bad areas: 445, run time: 11h 31m 2s > pct rescued: 97.75%, read errors: 5884, remaining time: 5d 23h 43m > time since last successful read: 2m 45s > Scraping failed blocks... (forwards) ] > > > On the plus side, that's 97.75% more data than I had before :-) but the > "remaining time" looks like it could be the rest of the week (it varies > quite a bit). > > > I think, from reading the manual, that I can use CTRL-C and restart this > again later and it will pick up where it left off using the map file. Is > this right? Very nice, this worked much better than I had expected! And you're right, you can simply CTRL-C and restart ddrescue with the same command (i.e., with the iso and map file; different options should work.) I would make a copy of the files before restarting, just in case. > Are there any other options I should consider trying? Can you try with "-b 2048 -d" for direct disc access and maybe once more with "-R" for reverse? > Another thought is that perhaps a shade more polishing might help. If I > polish the CDROM a little more and then resume the ddrescue, I think I won't > be any worse off than I am now, i.e. all existing data will still be there > and all I'll be risking is data that maybe would have eventually read before > but now may not read at all. Is that right? Successful reads are now ~20m > apart, so I suspect that the remaining data will be quite difficult to > recover. After trying the various options on the disk in its current state, I see no harm in trying this approach. With the map file, ddrescue should never overwrite already-read data. Again, I would make a copy to be safe. Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Sun, May 09, 2021 at 10:23:19PM +0100, Antonio Carlini via cctalk wrote: > I've now uploaded: ag-mn36e-re.tar.xz, ag-nh37b-re.tar.xz and > el-cdrom-01-rev-L.tar.xz. > > The full set now available are: > > AG-MN36E-RE - VMS Consolidated Software Distribution 1989-07 Disc 1 of 1 > AG-NC67C-RE - VMS Online Documentation Library 1989-07 Disc 1 of 1 > AG-NH36B-RE - VMS AD Software Consolidation 1989-07 Disc 1 of 2 > AG-NH37B-RE - VMS AD Software Consolidation 1989-07 Disc 2 of 2 > AG-MN36G-RE - VMS Consolidated Software Distribution 1989-11 Disc 1 of 2 > AG-PASMA-RE - VMS Consolidated Software Distribution 1989-11 Disc 2 of 2 > EL-CDROM-01 - Digital Standards and Related Documents 1993-03-19 Rev L Thanks a lot, Antonio, these are very valuable to have! > If anyone wants to offer them a permanent home, that's fine by my (I > don't need the space on the google drive just yet, but I will have to > remove some images if I start to image a lot more (and I do seem to > have a fair few more). I think uploading them to archive.org would be a good long-term solution. I can take care of it if you don't have an account. Cheers, Malte -- Malte Dehling
Re: That VAXStation4000vlc 3W3 video connector
I used CONEC 131J20019X to build my 3w3 to vga cable. Here's the datasheet with dimensions: https://cdn-reichelt.de/documents/datenblatt/C120/MIXSTGCO.pdf On Tue, May 4, 2021 at 1:23 AM Adam Thornton via cctech < cct...@classiccmp.org> wrote: > I assume it would be way too much to hope that HD BNC would fit it? Does > anyone have a pointer to the actual physical dimensions of the itty-bitty > BNC-ish connector in the video port of the VAXStation4000vlc? If I can get > red, green, and blue out (assuming since there are only 3 connectors it's > sync-on-green) I can put together a sync splitter and turn it into VGA. I > have at least one decent multisync VGA monitor still, although none with > the RGB BNC inputs. > > Adam >
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Wed, Apr 21, 2021 at 09:53:26PM +0100, Antonio Carlini via cctalk wrote: > I've managed to reconstitute my SIMH config and I've checked out a few > of the ISO files I managed to generate using ddrescue. > > The Mar 89 CONOLD and May 89 CONDIST do not even show up as media > under Linux. If I get the chance I'll try out the Oxford GAME store > polisher for one at least of them. As a backup I'll dig out my 3000 > grit sandpaper and try that out. I have to say I'm a little worried about the sandpaper... do you have a spare CD to test the effect on? Another option might be to send the CD to someone who does have a store nearby with a CD polisher. Either way, I guess the first step would be to find out whether the Oxford GAME store has one. Thanks again for your effort! > I've only looked at a few CONDIST volumes and none of the > corresponding CONOLD volumes. > > The oldest working one is the 1989 July CONDIST, which read 99.99% > with ddrescue. It mounts quite happily and I can see the directory. > > [...] > > Anyway, it looks like it is all there. However (and there's always a > "however") the VAXSET kit that started this all off is VAXSET*080* and > not the hoped for *070*. Interestingly the [.LINE] subdirectory does > contain some doc files but the [.KIT] directory is empty. I've > included the CD_CONTENTS.DAT below. From that you can see: > > "VAXSET" N V8.0 SUB N Y VAXSET080 NO_BINARIES > > which would suggest that the kit didn't ship although the SPD and so > on did. No idea why. Until I saw that I assumed that this was the one > set of files to get whacked, but that seems very unlikely. Especially > since the 1989 JUL AD CONDIST is the same. VAXSET is just a combined package consisting of CMS, LSE, SCA, MMS, PCA, and DTM. Here's a table of corresponding version numbers I've compiled from various sources (likely not 100% correct): |=== | VAXSET | v5.0 | v6.0 | v7.0 | v8.0 | v9.0 | v10.0 | CMS | v2.3 | v3.0 | v3.1 | v3.2 | v3.3 | v3.4 | LSE | v2.1 | v2.2 | v2.2 | v2.3 | v3.0 | v3.1 | SCA | v1.1 | v1.2 | v1.2 | v1.3 | v2.0 | v3.0 | MMS | v2.2 | v2.3 | v2.4 | v2.5 | v2.5 | v2.6 | PCA |?v1.2 | v2.0 | v2.0 | v2.1 | v2.2 | v3.0 | DTM | v2.2 | v2.3 | v2.3 | v3.0 | v3.1 | v3.2 | Release | 1987 | 1988 | 1988 | 1989 | 1990 | 1990 | Minimal VMS |?v4.4 | v4.6 | v4.6 | v5.1 | v5.3 | v5.3 |=== It looks like the individual components of VAXSET v8.0 are on the 1989-07 CONDIST even if VAXSET is listed as NO_BINARIES. While VAXSET v8.0 requires VMS v5.1, I'm not sure about its components. Some of them may run on (Micro)VMS 4.7. > I also ran up the MENU.EXE that is included and VAXSET is listed under > "New Products" and not "Updated Products". My interpretation would be > that it is not on any earlier CONDIST CDROMs. But it would be nice for > earlier ones to get flushed out and published! That's entirely possible, I have no reason to believe VAXSET was on earlier CONDIST CDs. Either way, I'm very interested in the older CONDISTs, too! This one already contains a few other things I have been looking for for a while. > Anyway, over the next few days I'll package up these early CDROMs and > put them up on either google drive or dropbox. I'll post a link here > and whoever wants them can grab them. If Al wants them for bitsavers > that's OK by me. > > I plan to include the ISO, a README.TXT that explains that these are > all incomplete and I'll attach the ddrescue output, a scan of the CD, > a SHA256 of the files. I'll tar it up and compress with xz. > > If anyone would prefer some other format or compression or whatever, > I'm open to suggestions. Maybe a ZIP file is easier for some people? Otherwise this sounds good! Cheers, Malte -- Malte Dehling
Re: DEC LK201-AA removable feet dimensions?
On Mon, Apr 19, 2021 at 09:33:42AM -0700, Seth J. Morabito via cctalk wrote: > Sort of an odd request, but I have some LK201-AA keyboards that have (of > course) not got their little black riser feet any more. I don't think > they've ever had them while in my possession, in fact. > > If anyone has one, and has the time and interest, could you do me a big > favor and take measurements of them for me? I would like to 3D print > some replacements, so getting the outer dimension is the most critical > part (though I can always measure the inner dimension of the hole they > fit into, too), along with the protrusion of the two clips that fit into > the key of the hole on the bottom of the LK201 keyboard. > > I have good pictures of them, just not dimensions, so I think once I > know the size of the critical bits, designing and printing them > shouldn't be too difficult. I have one (yes, one) of these little feet. Let me see if I can find it... Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Sat, Apr 17, 2021 at 08:33:59PM +0100, Antonio Carlini via cctalk wrote: > On 17/04/2021 19:35, Al Kossow via cctalk wrote: > > On 4/17/21 11:30 AM, Antonio Carlini via cctalk wrote: > > > > > So far I've just tried using dd to recover the data but perhaps I > > > should try to find something that won't give up when the OS reports > > > an unreadable sector. Anyone have any suggestions? > > > > > > ddrescue > > > > I guess I should've remembered that one, thanks! > > > So has this just lost ~3KiB? "pct rescued" suggests that it did quite well. > Does "bad areas" mean one bad sector (2048 bytes)? > > > $ ddrescue -r5 -v /dev/sr1 JUL89DIST.iso JUL89DIST.map > GNU ddrescue 1.23 > About to copy 623247 kBytes from '/dev/sr1' to 'JUL89DIST.iso' > Starting positions: infile = 0 B, outfile = 0 B > Copy block size: 128 sectors Initial skip size: 128 sectors > Sector size: 512 Bytes > > Press Ctrl-C to interrupt > ipos: 623246 kB, non-trimmed: 0 B, current rate: 0 B/s > opos: 623246 kB, non-scraped: 0 B, average rate: 1303 kB/s > non-tried: 0 B, bad-sector: 4096 B, error rate: 73 B/s > rescued: 623243 kB, bad areas: 1, run time: 7m 58s > pct rescued: 99.99%, read errors: 49, remaining time: n/a > time since last successful read: 5m 11s > Finished > > This is what ls sees (I renamed the ISO to match what it actually is): > > > -rw-rw-r-- 1 antonioc antonioc 623243264 Apr 17 20:14 > CDROM-AG-MN36E-RE-1989-07-VMS-CONDIST.iso > > (That happens to be exactly the same result as dd). That looks pretty good already! Can you try with "-b 2048 -d" for direct disc access and maybe once more with "-R" for reverse? Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
On Sat, Apr 17, 2021 at 11:35:41AM -0700, Al Kossow via cctalk wrote: > On 4/17/21 11:30 AM, Antonio Carlini via cctalk wrote: > > > So far I've just tried using dd to recover the data but perhaps I should > > try to find something that won't give up when the OS reports an > > unreadable sector. Anyone have any suggestions? > > > ddrescue I agree with the suggestion. I think it's worth trying this before anything else. If anything can be read without further work, ddrescue should do the trick. Of course it helps to test with different drives, too, like you already did. Sorry this turned into more work than expected, and thanks again for your effort! -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
Hi Antonio, On Fri, Apr 16, 2021 at 06:03:45PM +0100, Antonio Carlini via cctalk wrote: > On 16/04/2021 14:11, Malte Dehling via cctalk wrote: > > If anyone has an early 1990 (or older) Consolidated Software > > Distribution CD: that should contain VAXSET v7.0 and I would love to > > obtain a copy. > > Just to check that my memory wasn't playing tricks I went and looked > for it. I stopped looking before finding int because I found > > AG-MN36D-RE VMS Consolidated Software Disk May 1989 > > and > > AG-NC67A-RE VMS Online Documentation Library May 1989 thanks a lot for checking, that looks great! I didn't even know _such_ early versions existed :-) > I'll check them out in SIMH later on tonight, but if they look suitable I > can probably make the ISOs available via dropbox or similar. Whether VAXSET is on there or not, I would be very interested in ISOs of both of these either way! Cheers, Malte -- Malte Dehling
Re: Looking for VAXSET Software Engineering Tools for VMS 4.x
Dear all, On Thu, Apr 08, 2021 at 02:13:58PM +0200, Malte Dehling wrote: > I am looking for a version of the VAXSET Software Engineering Tools to > run on (Micro)VMS 4.7. The oldest version I have found so far is > VAXSET010 which requires VMS 5.3 to run (this was on CSD 1991/05.) I was informed of a typo: the version I have is VAXSET100, so v10.0. I am still looking for earlier versions (v8.0 already requires VMS 5.x.) If anyone has an early 1990 (or older) Consolidated Software Distribution CD: that should contain VAXSET v7.0 and I would love to obtain a copy. Or maybe someone still has an old VAXSET TK50 tape? I have working TK50 drives and am happy to pay a reasonable price and deal with tape baking etc if needed. Cheers, Malte -- Malte Dehling
Looking for VAXSET Software Engineering Tools for VMS 4.x
Dear all, I am looking for a version of the VAXSET Software Engineering Tools to run on (Micro)VMS 4.7. The oldest version I have found so far is VAXSET010 which requires VMS 5.3 to run (this was on CSD 1991/05.) VAXSET is a bundle of the following components (and more in newer versions): - CMS (Code Management System) - LSE (Language Sensitive Editor) - SCA (Source Code Analyzer) - MMS (Module Management System) - PCA (Performance Coverage Analyzer) - DTM (DEC/Test Manager) I have found versions of CMS and MMS seperately that run on VMS 4.x. If anyone has old versions of the other components and is willing to share, that would be much appreciated :-) Cheers, Malte -- Malte Dehling
Re: VAXstation 2000 network & hardware guides (English & German)
I'd be interested in the guides if you're located in Germany, and I do have access to a book scanner. Best, MalteOn Mar 14, 2021 19:08, David Brownlee via cctalk wrote: > > I have acquired a tiny slice of Orange Wall, and wondered if anyone would > be interested - preference for anyone who is setup to scan and upload the > missing bits to bitsavers or similar :) > > These seem to already be generally available online > EK-NETAB-UG-002 Workstations and MicroVAX 2000 Network Guide > EK-VAXAB-OM-002 VAXstation 2000 Owner's Manual (Covers how to replace your > mouse balls, and details exciting options such as LN03, LN03 PLUS, LPS40, > LA210, LA100, LA75, LA50. LGC01, LVP16, DF224, DF124, DF112, VSXXX-AB :-p) > > These I cannot immediately find > EK-NETAA-UG-001 VAXstation 2000, MicroVAX 2000 and VAXmate Network Guide > EK-VAXAB-IN-002 VAXstation 2000 Hardware Installation Guide > > Likewise these German versions > EK-NETGA-UG-001 VAXstation 2000, MicroVAX 2000 und VAXmate > Netzwerk-Anleitung > EK-A0305-IN 001 VR160 Installations-und Bedienungsanleitung > EK-A0355-OG-001 Grafikkoprozessor (8 Bildebenen) fur die VAXstation 2000 > Installations- und Bedienungsanleitung > > Thanks > > David
