From healyzh at aracnet.com Sat Jan 1 02:07:53 2000 From: healyzh at aracnet.com (Zane H. Healy) Date: Sun Feb 27 18:48:31 2005 Subject: Happy 0-|99 to all!!! Message-ID: Happy 0-|99 to all!!! I might be working, but I'm working from home, so just watched my PDP-11/73 roll over about 7 minutes ago, which means the first Y2K bug I've seen is it's date function :^( Zane | Zane H. Healy | UNIX Systems Adminstrator | | healyzh@aracnet.com (primary) | Linux Enthusiast | | healyzh@holonet.net (alternate) | Classic Computer Collector | +----------------------------------+----------------------------+ | Empire of the Petal Throne and Traveller Role Playing, | | and Zane's Computer Museum. | | http://www.aracnet.com/~healyzh/ | From kyrrin at bluefeathertech.com Sat Jan 1 02:24:21 2000 From: kyrrin at bluefeathertech.com (Bruce Lane) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? Message-ID: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> We have at least five PeeCees active here at any one time. Of those five, only ONE got confused about the date rollover. It was a 1994-vintage 486 system running DOS 6.22. I use it as one of my testbed systems. EVERY other system, including my old 486-based server, which any industry "expert" would happily sneer at as "obsolete," handled the flip-over without so much as an electronic hiccup. Ah, me... all that hype, and the only glitches I've heard of this evening were only minor annoyances (like Auckland's airport web page reporting flight dates of 1900). Methinks we're going to hear about an awful lot of annoyed paranoid people and survivalists over the next couple weeks. Happy New Year, gang! Keep the peace(es). ;-) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner and head honcho, Blue Feather Technologies http://www.bluefeathertech.com // E-mail: kyrrin@bluefeathertech.com Amateur Radio: WD6EOS since Dec. '77 "Our science can only describe an object, event, or living thing in our own human terms. It cannot, in any way, define any of them..." From geoffrob at stmarks.pp.catholic.edu.au Sat Jan 1 02:55:30 2000 From: geoffrob at stmarks.pp.catholic.edu.au (Geoff Roberts) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <002701bf5435$f5342b60$de2c67cb@stmarks.pp.catholic.edu.au> ----- Original Message ----- From: Bruce Lane To: Discussion re-collecting of classic computers Sent: Saturday, 1 January 2000 6:54 Subject: What Y2K glitch? > We have at least five PeeCees active here at any one time. About the same at the cafe here. > Of those five, only ONE got confused about the date rollover. It was a > 1994-vintage 486 system running DOS 6.22. I use it as one of my testbed > systems. Similar experience. I have a P75 with the buggy Award 4.50G bios. I deliberately didn't load the y2kure.sys on it to see what would happen. It got terribly confused (2094!) until I rebooted it with Y2KURE.SYS loaded. It uses a date offset to ensure the O/S gets a real date, despite the buggy bios that won't accept dates not in the 90's. Only other way to fix these suckers is to replace the bios. (BTW, this is freeware if you have machines with a 'replace the bios' type bug.) The machine is still in service in the cafe - so much for the "you have to replace your computer" sales pitch..... Only thing it couldn't fix was an XT that has a real problem with the GETCLOCK.exe program that only deals in two digits. The o/s doesn't directly speak to the clock in an xt, it has to use the getclock program. y2kure loaded the offset driver ok, but the o/s couldn't get the correct date through the usual system calls, and getclock bypasses the y2kure driver... Manual date setting works if you don't mind setting the clock every restart, but it was a bit painful for them. It's a LASER Turbo (10mhz) XT clone with a RTC board & RLL drive if someone knows of a Y2K happy version of getclock for it...... I replaced it with a 286 board circa 1987 that only required a pivot driver for the rollover to make the customer happy. (long story - not a lot of money) I also had to remember all I thought I'd forgotten about formatting & configuring MFM drives in a pc, since the RLL xt 'smart card' controller wouldn't work in the 286, (It pinches interrupt 8, a Bad Thing to do to an AT) so I resurrected a 1988 40mb Miniscribe and 16 bit MFM card to shift the software onto. That plus the y2kure.sys sorted it all out. As a bonus, I kept his genuine IBM full length CGA card and monitor and gave him an ega card and monitor I had laying about. They're happy and so am I. (they mostly wanted some games for the kids, and I'm very short of stuff that will run on a) an XT and b) CGA.) > EVERY other system, including my old 486-based server, which any industry > "expert" would happily sneer at as "obsolete," handled the flip-over > without so much as an electronic hiccup. My Novell 3.12 server required that I manually set the date after a reboot, to roll the century over in the hardware clock, but the (y2k patched) Novell had no probs. The 4.11 server was fine, it has an sntp client, which saved me having to do the reboot and manual reset bit, (Oldish P100 board) as it set the century for me. > Ah, me... all that hype, and the only glitches I've heard of this evening > were only minor annoyances (like Auckland's airport web page reporting > flight dates of 1900). Methinks we're going to hear about an awful lot of > annoyed paranoid people and survivalists over the next couple weeks. A lot of people made a lot of money out of Y2K paranoia. Some of them may have upset people to deal with shortly. So be it. The 11 year old Vax 6000 mini at the school here happily rolled over to 2000. Despite the fact that it's running a 1993 version of VMS (6.0) which is supposedly not compliant. (It breaks in a couple of obscure places under obscure conditions - none of which occur on this system) Everything here was fine. No problems that I am aware of anywhere in the country. > Happy New Year, gang! Keep the peace(es). ;-) Amen. Cheers Geoff Roberts Computer Systems Manager Saint Mark's College Port Pirie, South Australia. Email: geoffrob@stmarks.pp.catholic.edu.au netcafe@pirie.mtx.net.au ICQ #: 1970476 From jhfine at idirect.com Sat Jan 1 10:47:11 2000 From: jhfine at idirect.com (Jerome Fine) Date: Sun Feb 27 18:48:32 2005 Subject: Questions on HD: extensions for RT-11? References: Message-ID: <386E2F8F.69F5BB16@idirect.com> >Zane H. Healy wrote: > Happy 0-|99 to all!!! I might be working, but I'm working from home, so > just watched my PDP-11/73 roll over about 7 minutes ago, which means the > first Y2K bug I've seen is it's date function :^( Jerome Fine replies: Why were you beside your PDP-11/73 at midnight? Yes, I remember - there are great at night to cuddle up with (humour). Let's not get back to that thread!! Which version of RT-11? I had thought I would get enough time to make Y2K patches for a number of different versions, but there was never enough interest and too little time based on the lack of interest. Maybe now that there is actually a possible use, there may be more interest. I just spent the last few days making some kludges to the HD: device driver for E11 to allow UNIT=0 to have 8 partitions (0 => 7) in a BIGFILE.DSK (256 MBytes) on a hard drive. Not really much use at this stage, but the first step on the road to allowing a full mapping table with 64 partitions. Now that the technical details are proven, I thought I would ask this list for their thoughts regarding the range of variables. (a) Should the mapping table allow for "n" controllers? I thought a maximum of 4? (b) Should the mapping table allow for "u" units per controller? I thought a maximum of 4 different units (not the actual unit numbers)? (c) How many different partitions should the mapping table allow per drive? I thought a maximum of 4096 (only 64 could be active at one time - this allows for a drive up to 128 GBytes - a larger drive would be allowed if the number of controllers and/or different units per controller is reduced - up to 65536 partitions or 2 TBytes for one controller and one unit - would 128 GBytes be enough for the next 10 years - or more to the POINT can anyone ever keep track of 4096 partitions - Tim how do you manage with 256 partitions on that 9 GByte SCSI drive?). (d) Should all 64 partitions from H00: to H77: be bootable? (e) Is as small an HDX.SYS as possible essential - i.e. place as much code and tables as possible into high memory? (f) Is a "SET HD: SHOW" command essential and is an enhancement to RESORC to initiate that command in a way that is transparent to the user (after "SHOW DEVICE:HD:") also considered essential? NOTE: While DU(X).SYS is used as a comparison, I am discussing the features that would be in HD(X).SYS for a version of E11 which allows more than 32 MBytes of hard drive disk space to be mounted. If this discussion results in these features also being added (eventually) to DU(X).SYS, that aspect can be looked at later. Note that DU(X).SYS allows up to four controllers. That seems a reasonable maximum. Note that DU(X).SYS allows up to 256 different units from 0 to 255. Does any controller that anyone knows about (except for host adapters) allow any more than four units per controller? And is four drives a reasonable maximum even for a host adapter? The limit of four drives per controller is not meant to say that the UNIT numbers would be limited to the range 0 to 3. A SET command would provide an additional mapping to allow any UNIT value from 0 to 65535, such as: "SET HD: CSR3=160334,UNIT32=8192." where "UNITpu" is used as UNIT32 for PORT=3,UNIT=2 If anyone has a better suggestion, it would be appreciated. Thereafter: "SET H30: PORT=3,UNIT=2,PART=1024." "SET H34: PORT=3,UNIT=2,PART=1028." "SET H37: PORT=3,UNIT=2,PART=1031." might be what one user would require - assuming that a drive of the appropriate size (about 40 GBytes or larger) was available. It would be appreciated if anyone who uses V5.5, V5.7 or V5.7 of RT-11 (or will in the future) cares to comment on these questions? If your comments are even on just one question, that would be helpful. HAPPY NEW YEAR TO EVERYONE ON THE LIST! I hope that the actual start of the millennium next year in 2001 will be just as smooth. Sincerely yours, Jerome Fine From cisin at xenosoft.com Sat Jan 1 11:07:58 2000 From: cisin at xenosoft.com (Fred Cisin (XenoSoft)) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: D'ya mean that it's now safe to come out of the fallout shelter? > Ah, me... all that hype, and the only glitches I've heard of this evening > were only minor annoyances (like Auckland's airport web page reporting > flight dates of 1900). Methinks we're going to hear about an awful lot of > annoyed paranoid people and survivalists over the next couple weeks. Watch. The news media will tell you that THEY SAVED you, by all of their hysterical warnings. From rhblake at bigfoot.com Sat Jan 1 11:53:21 2000 From: rhblake at bigfoot.com (Russ Blakeman) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? References: Message-ID: <386E3F11.25AF11D5@bigfoot.com> Fred Cisin (XenoSoft) wrote: > D'ya mean that it's now safe to come out of the fallout shelter? > > > Ah, me... all that hype, and the only glitches I've heard of this evening > > were only minor annoyances (like Auckland's airport web page reporting > > flight dates of 1900). Methinks we're going to hear about an awful lot of > > annoyed paranoid people and survivalists over the next couple weeks. > > Watch. The news media will tell you that THEY SAVED you, by all of their > hysterical warnings. I can see that coming Fred....we're in the middle of a wood burning society here and with alll the older technology not even one traffic light freaked nor did the power companies fail. You don't think all this Y2K stuff could have been a way to make money huh? Naw, just ask anyone that retired over the last 4 years from reworking machines or selling "compliant" systems or writing software fixes (the non-free ones). The local computer dealer (1 of 2) just closed up - not from bankruptcy but from getting rich enough to retire at 32 yrs old and move on to where he wants to be. From kyrrin at bluefeathertech.com Sat Jan 1 12:08:51 2000 From: kyrrin at bluefeathertech.com (Bruce Lane) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> At 09:07 01-01-2000 -0800, you wrote: >D'ya mean that it's now safe to come out of the fallout shelter? Well, nothing fell out so I assume it's OK. ;-) >Watch. The news media will tell you that THEY SAVED you, by all of their >hysterical warnings. Oh, it already started. Someone on Prezzy Clinton's staff already started huffing and puffing about how we won't know the "full impact" of the problem until the end of January. I wager 4,000 Quatloos that, when that point comes, they'll claim they won't know the "full impact" for at least another month. And then another, and another, and... well, you get the idea. Oh, and the MicroVAXen and Sun boxes here, the oldest of which was designed and built in 1990, rolled right over to 2000 without a single protest. Lord above, what a non-event... too bad that people chose to focus their energies towards a bunch of hype instead of something worthwhile, like, say, a manned mission to Mars. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner and head honcho, Blue Feather Technologies http://www.bluefeathertech.com // E-mail: kyrrin@bluefeathertech.com Amateur Radio: WD6EOS since Dec. '77 "Our science can only describe an object, event, or living thing in our own human terms. It cannot, in any way, define any of them..." From ethan_dicks at yahoo.com Sat Jan 1 12:15:48 2000 From: ethan_dicks at yahoo.com (Ethan Dicks) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? Message-ID: <20000101181548.29178.qmail@web601.mail.yahoo.com> --- Geoff Roberts wrote: > A lot of people made a lot of money out of Y2K paranoia. Some of them may > have upset people to deal with shortly. So be it. Locally, certain store policies made the news: no returns on generators at the farmer's supply stores (Quality Farm and Fleet, for those in the U.S. who have heard of them). The same store chain was also asking city residents not to buy generators because there weren't enough to go around for their usual rural customers who buy them from time to time, anyway, Y2K-notwithstanding. -ethan ===== Infinet has been sold. The domain is going away in February. Please send all replies to erd@iname.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com From thompson at mail.athenet.net Sat Jan 1 12:27:30 2000 From: thompson at mail.athenet.net (Paul Thompson) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: <20000101181548.29178.qmail@web601.mail.yahoo.com> Message-ID: Watch for generators on Ebay popping up like mushrooms after a spring rain. Like many I spent last night watching our VMS and Unix systems pass to 2000 uneventfully. At the time there was a rumor flying about that there was a Y2k problem detected at one of our (Wisconsin) nuclear plants which was corrected before any problems resulted. I have not seen or read the news yet today. Myth or fact? If myth, was there a similar myth flying about in your locality? Paul On Sat, 1 Jan 2000, Ethan Dicks wrote: > > > --- Geoff Roberts wrote: > > A lot of people made a lot of money out of Y2K paranoia. Some of them may > > have upset people to deal with shortly. So be it. > > Locally, certain store policies made the news: no returns on generators at > the farmer's supply stores (Quality Farm and Fleet, for those in the U.S. > who have heard of them). The same store chain was also asking city residents > not to buy generators because there weren't enough to go around for their > usual rural customers who buy them from time to time, anyway, > Y2K-notwithstanding. From rigdonj at intellistar.net Sat Jan 1 15:06:44 2000 From: rigdonj at intellistar.net (Joe) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <3.0.1.16.20000101150644.452f4b30@mailhost.intellistar.net> At 10:08 AM 1/1/00 -0800, Bruce wrote: > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was >designed and built in 1990, rolled right over to 2000 without a single >protest. Hell! So did my 17 year old Zenith Z-100 with MS-DOS 1.2! Joe From kyrrin at bluefeathertech.com Sat Jan 1 13:23:41 2000 From: kyrrin at bluefeathertech.com (Bruce Lane) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.1.16.20000101150644.452f4b30@mailhost.intellistar.net> References: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> Message-ID: <3.0.5.32.20000101112341.00930260@mail.bluefeathertech.com> At 15:06 01-01-2000, you wrote: >At 10:08 AM 1/1/00 -0800, Bruce wrote: > >> Oh, and the MicroVAXen and Sun boxes here, the oldest of which was >>designed and built in 1990, rolled right over to 2000 without a single >>protest. > > Hell! So did my 17 year old Zenith Z-100 with MS-DOS 1.2! Am I surprised? No! ;-) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner and head honcho, Blue Feather Technologies http://www.bluefeathertech.com // E-mail: kyrrin@bluefeathertech.com Amateur Radio: WD6EOS since Dec. '77 "Our science can only describe an object, event, or living thing in our own human terms. It cannot, in any way, define any of them..." From cisin at xenosoft.com Sat Jan 1 14:05:02 2000 From: cisin at xenosoft.com (Fred Cisin (XenoSoft)) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: <386E3F11.25AF11D5@bigfoot.com> Message-ID: > ones). The local computer dealer (1 of 2) just closed up - not from bankruptcy but > from getting rich enough to retire at 32 yrs old and move on to where he wants to be. Professor Harold ("Music Man") Hill made a living inciting panic and peddling solutions. But Y2K was his "career" opportunity. I hope that the e-bay watching collectors here realize that soon, the most "RARE! VALUABLE!" collectibles will be the Y2K NON-compliant machines. -- Grumpy Ol' Fred cisin@xenosoft.com From dwollmann at puttybox.com Sat Jan 1 14:09:38 2000 From: dwollmann at puttybox.com (David Wollmann) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <20000101140938.E9349@puttybox.com> On Sat, Jan 01, 2000 at 12:24:21AM -0800, Bruce Lane wrote: > We have at least five PeeCees active here at any one time. > > Of those five, only ONE got confused about the date rollover. It was a > 1994-vintage 486 system running DOS 6.22. I use it as one of my testbed > systems. > > EVERY other system, including my old 486-based server, which any industry > "expert" would happily sneer at as "obsolete," handled the flip-over > without so much as an electronic hiccup. > We experienced only one oddity. One of our older Linux boxes, a 486-66 VLB running Linux 2.0.38, told me that my last login was in 1969. I logged out, logged back in again and it got it right that time. No problems since, although I've yet to reboot anything since the rollover. -- David Wollmann DST / DST Data Conversion http://www.puttybox.com/ ICQ: 10742063 From bpechter at monmouth.com Sat Jan 1 15:18:10 2000 From: bpechter at monmouth.com (Bill Pechter) Date: Sun Feb 27 18:48:32 2005 Subject: What Y2K glitch? References: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> Message-ID: <00010116270604.35175@pechter.dyndns.org> On Sat, 01 Jan 2000, Bruce Lane wrote: > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was > designed and built in 1990, rolled right over to 2000 without a single > protest. > > Lord above, what a non-event... too bad that people chose to focus their > energies towards a bunch of hype instead of something worthwhile, like, > say, a manned mission to Mars. Yup... I went nuts patching the blasted SunOS 4.1.x boxes (because management required "Certification" on all hardware and software. The problems were stuff like troff macro packages that didn't get date/time headers right. Real critical stuff, eh. Well, I wish I could've stayed with the old stuff. The Suns worked. The biggest problem I had was the time I spent patching Windows boxes. It took 5 times the overtime patching the Win95/98/NT stuff than any of the Sun stuff. The Suns were easy. Apply patch to one Sun of each architecture under SunOS 4.1.4, make tar patch. Untar over machine to install new kernel and all the patches. The PC's were much worse. Bill ----------------------------------------------------------------- bpechter@.monmouth.com|pechter@pechter.dyndns.org|pechter@pechter.bsdonline.org Three things never anger: First, the one who runs your DEC, Theone who does Field Service and the one who signs your check. From edick at idcomm.com Sat Jan 1 15:53:03 2000 From: edick at idcomm.com (Richard Erlacher) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? Message-ID: <001601bf54a2$94fff220$0400c0a8@winbook> Well, thatsurprises me! I've got NT3.51, NT4,Win98, and Win 95 in several boxes some dating back a few years, and not a one had the wrong date or any other apparent ill efects to show for the rollover. My Netware server was off by 11 months, but that was due to a typo last August. That was the last time I rebooted more than one of my boxes. Dick -----Original Message----- From: Bill Pechter To: Discussion re-collecting of classic computers Date: Saturday, January 01, 2000 2:29 PM Subject: Re: What Y2K glitch? On Sat, 01 Jan 2000, Bruce Lane wrote: > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was > designed and built in 1990, rolled right over to 2000 without a single > protest. > > Lord above, what a non-event... too bad that people chose to focus their > energies towards a bunch of hype instead of something worthwhile, like, > say, a manned mission to Mars. Yup... I went nuts patching the blasted SunOS 4.1.x boxes (because management required "Certification" on all hardware and software. The problems were stuff like troff macro packages that didn't get date/time headers right. Real critical stuff, eh. Well, I wish I could've stayed with the old stuff. The Suns worked. The biggest problem I had was the time I spent patching Windows boxes. It took 5 times the overtime patching the Win95/98/NT stuff than any of the Sun stuff. The Suns were easy. Apply patch to one Sun of each architecture under SunOS 4.1.4, make tar patch. Untar over machine to install new kernel and all the patches. The PC's were much worse. Bill ----------------------------------------------------------------- bpechter@.monmouth.com|pechter@pechter.dyndns.org|pechter@pechter.bsdonline. org Three things never anger: First, the one who runs your DEC, Theone who does Field Service and the one who signs your check. From rhblake at bigfoot.com Sat Jan 1 16:10:04 2000 From: rhblake at bigfoot.com (Russ Blakeman) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> <3.0.1.16.20000101150644.452f4b30@mailhost.intellistar.net> Message-ID: <386E7B3C.A8CDC070@bigfoot.com> As did my 1982 (I think) IBM 5170 AT...The Sanyo MBC-55x was the bad one, hung on the RTC program until I went in and edited a string in the code (only by luck actually) Joe wrote: > At 10:08 AM 1/1/00 -0800, Bruce wrote: > > > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was > >designed and built in 1990, rolled right over to 2000 without a single > >protest. > > Hell! So did my 17 year old Zenith Z-100 with MS-DOS 1.2! > > Joe From healyzh at aracnet.com Sat Jan 1 02:07:53 2000 From: healyzh at aracnet.com (Zane H. Healy) Date: Sun Feb 27 18:48:33 2005 Subject: Happy 0-|99 to all!!! Message-ID: Happy 0-|99 to all!!! I might be working, but I'm working from home, so just watched my PDP-11/73 roll over about 7 minutes ago, which means the first Y2K bug I've seen is it's date function :^( Zane | Zane H. Healy | UNIX Systems Adminstrator | | healyzh@aracnet.com (primary) | Linux Enthusiast | | healyzh@holonet.net (alternate) | Classic Computer Collector | +----------------------------------+----------------------------+ | Empire of the Petal Throne and Traveller Role Playing, | | and Zane's Computer Museum. | | http://www.aracnet.com/~healyzh/ | From kyrrin at bluefeathertech.com Sat Jan 1 02:24:21 2000 From: kyrrin at bluefeathertech.com (Bruce Lane) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? Message-ID: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> We have at least five PeeCees active here at any one time. Of those five, only ONE got confused about the date rollover. It was a 1994-vintage 486 system running DOS 6.22. I use it as one of my testbed systems. EVERY other system, including my old 486-based server, which any industry "expert" would happily sneer at as "obsolete," handled the flip-over without so much as an electronic hiccup. Ah, me... all that hype, and the only glitches I've heard of this evening were only minor annoyances (like Auckland's airport web page reporting flight dates of 1900). Methinks we're going to hear about an awful lot of annoyed paranoid people and survivalists over the next couple weeks. Happy New Year, gang! Keep the peace(es). ;-) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner and head honcho, Blue Feather Technologies http://www.bluefeathertech.com // E-mail: kyrrin@bluefeathertech.com Amateur Radio: WD6EOS since Dec. '77 "Our science can only describe an object, event, or living thing in our own human terms. It cannot, in any way, define any of them..." From geoffrob at stmarks.pp.catholic.edu.au Sat Jan 1 02:55:30 2000 From: geoffrob at stmarks.pp.catholic.edu.au (Geoff Roberts) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <002701bf5435$f5342b60$de2c67cb@stmarks.pp.catholic.edu.au> ----- Original Message ----- From: Bruce Lane To: Discussion re-collecting of classic computers Sent: Saturday, 1 January 2000 6:54 Subject: What Y2K glitch? > We have at least five PeeCees active here at any one time. About the same at the cafe here. > Of those five, only ONE got confused about the date rollover. It was a > 1994-vintage 486 system running DOS 6.22. I use it as one of my testbed > systems. Similar experience. I have a P75 with the buggy Award 4.50G bios. I deliberately didn't load the y2kure.sys on it to see what would happen. It got terribly confused (2094!) until I rebooted it with Y2KURE.SYS loaded. It uses a date offset to ensure the O/S gets a real date, despite the buggy bios that won't accept dates not in the 90's. Only other way to fix these suckers is to replace the bios. (BTW, this is freeware if you have machines with a 'replace the bios' type bug.) The machine is still in service in the cafe - so much for the "you have to replace your computer" sales pitch..... Only thing it couldn't fix was an XT that has a real problem with the GETCLOCK.exe program that only deals in two digits. The o/s doesn't directly speak to the clock in an xt, it has to use the getclock program. y2kure loaded the offset driver ok, but the o/s couldn't get the correct date through the usual system calls, and getclock bypasses the y2kure driver... Manual date setting works if you don't mind setting the clock every restart, but it was a bit painful for them. It's a LASER Turbo (10mhz) XT clone with a RTC board & RLL drive if someone knows of a Y2K happy version of getclock for it...... I replaced it with a 286 board circa 1987 that only required a pivot driver for the rollover to make the customer happy. (long story - not a lot of money) I also had to remember all I thought I'd forgotten about formatting & configuring MFM drives in a pc, since the RLL xt 'smart card' controller wouldn't work in the 286, (It pinches interrupt 8, a Bad Thing to do to an AT) so I resurrected a 1988 40mb Miniscribe and 16 bit MFM card to shift the software onto. That plus the y2kure.sys sorted it all out. As a bonus, I kept his genuine IBM full length CGA card and monitor and gave him an ega card and monitor I had laying about. They're happy and so am I. (they mostly wanted some games for the kids, and I'm very short of stuff that will run on a) an XT and b) CGA.) > EVERY other system, including my old 486-based server, which any industry > "expert" would happily sneer at as "obsolete," handled the flip-over > without so much as an electronic hiccup. My Novell 3.12 server required that I manually set the date after a reboot, to roll the century over in the hardware clock, but the (y2k patched) Novell had no probs. The 4.11 server was fine, it has an sntp client, which saved me having to do the reboot and manual reset bit, (Oldish P100 board) as it set the century for me. > Ah, me... all that hype, and the only glitches I've heard of this evening > were only minor annoyances (like Auckland's airport web page reporting > flight dates of 1900). Methinks we're going to hear about an awful lot of > annoyed paranoid people and survivalists over the next couple weeks. A lot of people made a lot of money out of Y2K paranoia. Some of them may have upset people to deal with shortly. So be it. The 11 year old Vax 6000 mini at the school here happily rolled over to 2000. Despite the fact that it's running a 1993 version of VMS (6.0) which is supposedly not compliant. (It breaks in a couple of obscure places under obscure conditions - none of which occur on this system) Everything here was fine. No problems that I am aware of anywhere in the country. > Happy New Year, gang! Keep the peace(es). ;-) Amen. Cheers Geoff Roberts Computer Systems Manager Saint Mark's College Port Pirie, South Australia. Email: geoffrob@stmarks.pp.catholic.edu.au netcafe@pirie.mtx.net.au ICQ #: 1970476 From jhfine at idirect.com Sat Jan 1 10:47:11 2000 From: jhfine at idirect.com (Jerome Fine) Date: Sun Feb 27 18:48:33 2005 Subject: Questions on HD: extensions for RT-11? References: Message-ID: <386E2F8F.69F5BB16@idirect.com> >Zane H. Healy wrote: > Happy 0-|99 to all!!! I might be working, but I'm working from home, so > just watched my PDP-11/73 roll over about 7 minutes ago, which means the > first Y2K bug I've seen is it's date function :^( Jerome Fine replies: Why were you beside your PDP-11/73 at midnight? Yes, I remember - there are great at night to cuddle up with (humour). Let's not get back to that thread!! Which version of RT-11? I had thought I would get enough time to make Y2K patches for a number of different versions, but there was never enough interest and too little time based on the lack of interest. Maybe now that there is actually a possible use, there may be more interest. I just spent the last few days making some kludges to the HD: device driver for E11 to allow UNIT=0 to have 8 partitions (0 => 7) in a BIGFILE.DSK (256 MBytes) on a hard drive. Not really much use at this stage, but the first step on the road to allowing a full mapping table with 64 partitions. Now that the technical details are proven, I thought I would ask this list for their thoughts regarding the range of variables. (a) Should the mapping table allow for "n" controllers? I thought a maximum of 4? (b) Should the mapping table allow for "u" units per controller? I thought a maximum of 4 different units (not the actual unit numbers)? (c) How many different partitions should the mapping table allow per drive? I thought a maximum of 4096 (only 64 could be active at one time - this allows for a drive up to 128 GBytes - a larger drive would be allowed if the number of controllers and/or different units per controller is reduced - up to 65536 partitions or 2 TBytes for one controller and one unit - would 128 GBytes be enough for the next 10 years - or more to the POINT can anyone ever keep track of 4096 partitions - Tim how do you manage with 256 partitions on that 9 GByte SCSI drive?). (d) Should all 64 partitions from H00: to H77: be bootable? (e) Is as small an HDX.SYS as possible essential - i.e. place as much code and tables as possible into high memory? (f) Is a "SET HD: SHOW" command essential and is an enhancement to RESORC to initiate that command in a way that is transparent to the user (after "SHOW DEVICE:HD:") also considered essential? NOTE: While DU(X).SYS is used as a comparison, I am discussing the features that would be in HD(X).SYS for a version of E11 which allows more than 32 MBytes of hard drive disk space to be mounted. If this discussion results in these features also being added (eventually) to DU(X).SYS, that aspect can be looked at later. Note that DU(X).SYS allows up to four controllers. That seems a reasonable maximum. Note that DU(X).SYS allows up to 256 different units from 0 to 255. Does any controller that anyone knows about (except for host adapters) allow any more than four units per controller? And is four drives a reasonable maximum even for a host adapter? The limit of four drives per controller is not meant to say that the UNIT numbers would be limited to the range 0 to 3. A SET command would provide an additional mapping to allow any UNIT value from 0 to 65535, such as: "SET HD: CSR3=160334,UNIT32=8192." where "UNITpu" is used as UNIT32 for PORT=3,UNIT=2 If anyone has a better suggestion, it would be appreciated. Thereafter: "SET H30: PORT=3,UNIT=2,PART=1024." "SET H34: PORT=3,UNIT=2,PART=1028." "SET H37: PORT=3,UNIT=2,PART=1031." might be what one user would require - assuming that a drive of the appropriate size (about 40 GBytes or larger) was available. It would be appreciated if anyone who uses V5.5, V5.7 or V5.7 of RT-11 (or will in the future) cares to comment on these questions? If your comments are even on just one question, that would be helpful. HAPPY NEW YEAR TO EVERYONE ON THE LIST! I hope that the actual start of the millennium next year in 2001 will be just as smooth. Sincerely yours, Jerome Fine From cisin at xenosoft.com Sat Jan 1 11:07:58 2000 From: cisin at xenosoft.com (Fred Cisin (XenoSoft)) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: D'ya mean that it's now safe to come out of the fallout shelter? > Ah, me... all that hype, and the only glitches I've heard of this evening > were only minor annoyances (like Auckland's airport web page reporting > flight dates of 1900). Methinks we're going to hear about an awful lot of > annoyed paranoid people and survivalists over the next couple weeks. Watch. The news media will tell you that THEY SAVED you, by all of their hysterical warnings. From rhblake at bigfoot.com Sat Jan 1 11:53:21 2000 From: rhblake at bigfoot.com (Russ Blakeman) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? References: Message-ID: <386E3F11.25AF11D5@bigfoot.com> Fred Cisin (XenoSoft) wrote: > D'ya mean that it's now safe to come out of the fallout shelter? > > > Ah, me... all that hype, and the only glitches I've heard of this evening > > were only minor annoyances (like Auckland's airport web page reporting > > flight dates of 1900). Methinks we're going to hear about an awful lot of > > annoyed paranoid people and survivalists over the next couple weeks. > > Watch. The news media will tell you that THEY SAVED you, by all of their > hysterical warnings. I can see that coming Fred....we're in the middle of a wood burning society here and with alll the older technology not even one traffic light freaked nor did the power companies fail. You don't think all this Y2K stuff could have been a way to make money huh? Naw, just ask anyone that retired over the last 4 years from reworking machines or selling "compliant" systems or writing software fixes (the non-free ones). The local computer dealer (1 of 2) just closed up - not from bankruptcy but from getting rich enough to retire at 32 yrs old and move on to where he wants to be. From kyrrin at bluefeathertech.com Sat Jan 1 12:08:51 2000 From: kyrrin at bluefeathertech.com (Bruce Lane) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> At 09:07 01-01-2000 -0800, you wrote: >D'ya mean that it's now safe to come out of the fallout shelter? Well, nothing fell out so I assume it's OK. ;-) >Watch. The news media will tell you that THEY SAVED you, by all of their >hysterical warnings. Oh, it already started. Someone on Prezzy Clinton's staff already started huffing and puffing about how we won't know the "full impact" of the problem until the end of January. I wager 4,000 Quatloos that, when that point comes, they'll claim they won't know the "full impact" for at least another month. And then another, and another, and... well, you get the idea. Oh, and the MicroVAXen and Sun boxes here, the oldest of which was designed and built in 1990, rolled right over to 2000 without a single protest. Lord above, what a non-event... too bad that people chose to focus their energies towards a bunch of hype instead of something worthwhile, like, say, a manned mission to Mars. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner and head honcho, Blue Feather Technologies http://www.bluefeathertech.com // E-mail: kyrrin@bluefeathertech.com Amateur Radio: WD6EOS since Dec. '77 "Our science can only describe an object, event, or living thing in our own human terms. It cannot, in any way, define any of them..." From ethan_dicks at yahoo.com Sat Jan 1 12:15:48 2000 From: ethan_dicks at yahoo.com (Ethan Dicks) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? Message-ID: <20000101181548.29178.qmail@web601.mail.yahoo.com> --- Geoff Roberts wrote: > A lot of people made a lot of money out of Y2K paranoia. Some of them may > have upset people to deal with shortly. So be it. Locally, certain store policies made the news: no returns on generators at the farmer's supply stores (Quality Farm and Fleet, for those in the U.S. who have heard of them). The same store chain was also asking city residents not to buy generators because there weren't enough to go around for their usual rural customers who buy them from time to time, anyway, Y2K-notwithstanding. -ethan ===== Infinet has been sold. The domain is going away in February. Please send all replies to erd@iname.com __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com From thompson at mail.athenet.net Sat Jan 1 12:27:30 2000 From: thompson at mail.athenet.net (Paul Thompson) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: <20000101181548.29178.qmail@web601.mail.yahoo.com> Message-ID: Watch for generators on Ebay popping up like mushrooms after a spring rain. Like many I spent last night watching our VMS and Unix systems pass to 2000 uneventfully. At the time there was a rumor flying about that there was a Y2k problem detected at one of our (Wisconsin) nuclear plants which was corrected before any problems resulted. I have not seen or read the news yet today. Myth or fact? If myth, was there a similar myth flying about in your locality? Paul On Sat, 1 Jan 2000, Ethan Dicks wrote: > > > --- Geoff Roberts wrote: > > A lot of people made a lot of money out of Y2K paranoia. Some of them may > > have upset people to deal with shortly. So be it. > > Locally, certain store policies made the news: no returns on generators at > the farmer's supply stores (Quality Farm and Fleet, for those in the U.S. > who have heard of them). The same store chain was also asking city residents > not to buy generators because there weren't enough to go around for their > usual rural customers who buy them from time to time, anyway, > Y2K-notwithstanding. From rigdonj at intellistar.net Sat Jan 1 15:06:44 2000 From: rigdonj at intellistar.net (Joe) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <3.0.1.16.20000101150644.452f4b30@mailhost.intellistar.net> At 10:08 AM 1/1/00 -0800, Bruce wrote: > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was >designed and built in 1990, rolled right over to 2000 without a single >protest. Hell! So did my 17 year old Zenith Z-100 with MS-DOS 1.2! Joe From kyrrin at bluefeathertech.com Sat Jan 1 13:23:41 2000 From: kyrrin at bluefeathertech.com (Bruce Lane) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.1.16.20000101150644.452f4b30@mailhost.intellistar.net> References: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> Message-ID: <3.0.5.32.20000101112341.00930260@mail.bluefeathertech.com> At 15:06 01-01-2000, you wrote: >At 10:08 AM 1/1/00 -0800, Bruce wrote: > >> Oh, and the MicroVAXen and Sun boxes here, the oldest of which was >>designed and built in 1990, rolled right over to 2000 without a single >>protest. > > Hell! So did my 17 year old Zenith Z-100 with MS-DOS 1.2! Am I surprised? No! ;-) -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Bruce Lane, Owner and head honcho, Blue Feather Technologies http://www.bluefeathertech.com // E-mail: kyrrin@bluefeathertech.com Amateur Radio: WD6EOS since Dec. '77 "Our science can only describe an object, event, or living thing in our own human terms. It cannot, in any way, define any of them..." From cisin at xenosoft.com Sat Jan 1 14:05:02 2000 From: cisin at xenosoft.com (Fred Cisin (XenoSoft)) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: <386E3F11.25AF11D5@bigfoot.com> Message-ID: > ones). The local computer dealer (1 of 2) just closed up - not from bankruptcy but > from getting rich enough to retire at 32 yrs old and move on to where he wants to be. Professor Harold ("Music Man") Hill made a living inciting panic and peddling solutions. But Y2K was his "career" opportunity. I hope that the e-bay watching collectors here realize that soon, the most "RARE! VALUABLE!" collectibles will be the Y2K NON-compliant machines. -- Grumpy Ol' Fred cisin@xenosoft.com From dwollmann at puttybox.com Sat Jan 1 14:09:38 2000 From: dwollmann at puttybox.com (David Wollmann) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? In-Reply-To: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> Message-ID: <20000101140938.E9349@puttybox.com> On Sat, Jan 01, 2000 at 12:24:21AM -0800, Bruce Lane wrote: > We have at least five PeeCees active here at any one time. > > Of those five, only ONE got confused about the date rollover. It was a > 1994-vintage 486 system running DOS 6.22. I use it as one of my testbed > systems. > > EVERY other system, including my old 486-based server, which any industry > "expert" would happily sneer at as "obsolete," handled the flip-over > without so much as an electronic hiccup. > We experienced only one oddity. One of our older Linux boxes, a 486-66 VLB running Linux 2.0.38, told me that my last login was in 1969. I logged out, logged back in again and it got it right that time. No problems since, although I've yet to reboot anything since the rollover. -- David Wollmann DST / DST Data Conversion http://www.puttybox.com/ ICQ: 10742063 From bpechter at monmouth.com Sat Jan 1 15:18:10 2000 From: bpechter at monmouth.com (Bill Pechter) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? References: <3.0.5.32.20000101100851.0092fd70@mail.bluefeathertech.com> Message-ID: <00010116270604.35175@pechter.dyndns.org> On Sat, 01 Jan 2000, Bruce Lane wrote: > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was > designed and built in 1990, rolled right over to 2000 without a single > protest. > > Lord above, what a non-event... too bad that people chose to focus their > energies towards a bunch of hype instead of something worthwhile, like, > say, a manned mission to Mars. Yup... I went nuts patching the blasted SunOS 4.1.x boxes (because management required "Certification" on all hardware and software. The problems were stuff like troff macro packages that didn't get date/time headers right. Real critical stuff, eh. Well, I wish I could've stayed with the old stuff. The Suns worked. The biggest problem I had was the time I spent patching Windows boxes. It took 5 times the overtime patching the Win95/98/NT stuff than any of the Sun stuff. The Suns were easy. Apply patch to one Sun of each architecture under SunOS 4.1.4, make tar patch. Untar over machine to install new kernel and all the patches. The PC's were much worse. Bill ----------------------------------------------------------------- bpechter@.monmouth.com|pechter@pechter.dyndns.org|pechter@pechter.bsdonline.org Three things never anger: First, the one who runs your DEC, Theone who does Field Service and the one who signs your check. From edick at idcomm.com Sat Jan 1 15:53:03 2000 From: edick at idcomm.com (Richard Erlacher) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? Message-ID: <001601bf54a2$94fff220$0400c0a8@winbook> Well, thatsurprises me! I've got NT3.51, NT4,Win98, and Win 95 in several boxes some dating back a few years, and not a one had the wrong date or any other apparent ill efects to show for the rollover. My Netware server was off by 11 months, but that was due to a typo last August. That was the last time I rebooted more than one of my boxes. Dick -----Original Message----- From: Bill Pechter To: Discussion re-collecting of classic computers Date: Saturday, January 01, 2000 2:29 PM Subject: Re: What Y2K glitch? On Sat, 01 Jan 2000, Bruce Lane wrote: > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was > designed and built in 1990, rolled right over to 2000 without a single > protest. > > Lord above, what a non-event... too bad that people chose to focus their > energies towards a bunch of hype instead of something worthwhile, like, > say, a manned mission to Mars. Yup... I went nuts patching the blasted SunOS 4.1.x boxes (because management required "Certification" on all hardware and software. The problems were stuff like troff macro packages that didn't get date/time headers right. Real critical stuff, eh. Well, I wish I could've stayed with the old stuff. The Suns worked. The biggest problem I had was the time I spent patching Windows boxes. It took 5 times the overtime patching the Win95/98/NT stuff than any of the Sun stuff. The Suns were easy. Apply patch to one Sun of each architecture under SunOS 4.1.4, make tar patch. Untar over machine to install new kernel and all the patches. The PC's were much worse. Bill ----------------------------------------------------------------- bpechter@.monmouth.com|pechter@pechter.dyndns.org|pechter@pechter.bsdonline. org Three things never anger: First, the one who runs your DEC, Theone who does Field Service and the one who signs your check. From rhblake at bigfoot.com Sat Jan 1 16:10:04 2000 From: rhblake at bigfoot.com (Russ Blakeman) Date: Sun Feb 27 18:48:33 2005 Subject: What Y2K glitch? References: <3.0.5.32.20000101002421.00928540@mail.bluefeathertech.com> <3.0.1.16.20000101150644.452f4b30@mailhost.intellistar.net> Message-ID: <386E7B3C.A8CDC070@bigfoot.com> As did my 1982 (I think) IBM 5170 AT...The Sanyo MBC-55x was the bad one, hung on the RTC program until I went in and edited a string in the code (only by luck actually) Joe wrote: > At 10:08 AM 1/1/00 -0800, Bruce wrote: > > > Oh, and the MicroVAXen and Sun boxes here, the oldest of which was > >designed and built in 1990, rolled right over to 2000 without a single > >protest. > > Hell! So did my 17 year old Zenith Z-100 with MS-DOS 1.2! > > Joe From manney at hmcltd.net Sun Jan 16 18:50:15 2000 From: manney at hmcltd.net (PG Manney) Date: Sun Feb 27 18:53:45 2005 Subject: Diablo Hytype II Printer Ribbons References: <3.0.5.32.20000615065708.009653a0@pop.sttl.uswest.net> fromBruce Lane at "Jun 15, 2000 06:57:08 am" Message-ID: <000c01bf6084$d55796a0$27e3cfd8@pavilion> I have (6) Global Diablo Hytype II printer ribbons, 4 new in plastic envelopes. Shipping fee will take 'em. Anyone? P Manney From manney at hmcltd.net Sun Jan 16 18:52:47 2000 From: manney at hmcltd.net (PG Manney) Date: Sun Feb 27 18:53:45 2005 Subject: Symphony References: <14666.30391.344696.968138@phaduka.neurotica.com> <14666.47480.254777.476342@phaduka.neurotica.com> Message-ID: <000d01bf6085$2cb77280$27e3cfd8@pavilion> Some time ago I discussed, with someone on the list, Symphony for the DEC Rainbow. It's still available. Would the person please contact me? Failing that, anoone else want to buy? P Manney From manney at hmcltd.net Sun Jan 16 18:50:15 2000 From: manney at hmcltd.net (PG Manney) Date: Sun Feb 27 18:54:40 2005 Subject: Diablo Hytype II Printer Ribbons References: <3.0.5.32.20000615065708.009653a0@pop.sttl.uswest.net> fromBruce Lane at "Jun 15, 2000 06:57:08 am" Message-ID: <000c01bf6084$d55796a0$27e3cfd8@pavilion> I have (6) Global Diablo Hytype II printer ribbons, 4 new in plastic envelopes. Shipping fee will take 'em. Anyone? P Manney From manney at hmcltd.net Sun Jan 16 18:52:47 2000 From: manney at hmcltd.net (PG Manney) Date: Sun Feb 27 18:54:42 2005 Subject: Symphony References: <14666.30391.344696.968138@phaduka.neurotica.com> <14666.47480.254777.476342@phaduka.neurotica.com> Message-ID: <000d01bf6085$2cb77280$27e3cfd8@pavilion> Some time ago I discussed, with someone on the list, Symphony for the DEC Rainbow. It's still available. Would the person please contact me? Failing that, anoone else want to buy? P Manney