test-drb April 2002

test-drb@ccmp.vtda.org

280 participants
1162 discussions

by mranalog＠attbi.com

I really need a copy of the manual for a Data Systems Design DSD-440. If I knew what I was doing I would just ask for the switch and jumper settings, but that's not the case. I would like to get a copy of the entire manual. If someone has the manual scanned already, I can take 2MB email attachments. --Doug ========================================= Doug Coward @ home in Poulsbo, WA Analog Computer Online Museum and History Center http://dcoward.best.vwh.net/analog Analogrechner, calculateur analogique, calcolatore analogico, analoogrekenaar, komputer analogowy, analog bilgisayar, kampiutere ghiyasi, analoge computer. =========================================

22 years, 9 months

OT: Dell Quality

by dquebbeman＠acm.org

> PS: Oh, Your dept who bought up that 25 dells made serious > *mistake*. Only way dept can depend on them running w/ replacement > parts is dell's especially their power supplies and few oddball > boards. PSUs are totally non-standard pinouts. Oh, your dept also > didn't choose AMD and let dell know everybody else wanted > quality but flexible choices in different brands of CPUs instead > of Intel-only. Oh, I pitched MicronPC, but no one here has ever heard of them... But anyway, it's irrelevant. Every machine will be obsolete in three years, and every machine has a three-year next-day- response service contract. When the three years is up, we buy new ones and give the old ones to employees. Oh, and the only thing we've ever had go bad in Dells: * company president drops laptop and kills it * construction administrator packs one in overhead storage on plane and crushes screen * Western Digital Hard Drive failed in a new Dimension * Sony tape library jammed and replaced with another Sony * Seagate SCSI drive in PowerEdge Server RAID 5 array *will* fail * user killed mouse and lied, Dell replaced anyway * sysadmin ordered white keyboard for black computer, asked for swap, Dell sent back keyboard free And while Micron's would be nice, I'll do *anything* to avoid buying Hewcom Pacqward... -dq -Douglas Hurst Quebbeman (DougQ at ixnayamspayIgLou.com) [Call me "Doug"] Surgically excise the pig-latin from my e-mail address in order to reply "The large print giveth, and the small print taketh away." -Tom Waits

22 years, 9 months

Shoddy Hardware (Was: Re: WW fixtures (was Re: "New" PDP-8))

by dquebbeman＠acm.org

> -> I assume everyone knows what casting flash is... these screws > -> have casting flash... > > Look closely. It is not casting flash. Screws aren't cast. > As mentioned in an earlier post, the heads and threads are > made by pressing (deformation) of a rod. > > When the form dies wear, are improperly secured, or are misaligned, > the result is "extruded squish", not "casting flash". <insert Ewok worship sound emoticon here> I stand corrected. -dq -Douglas Hurst Quebbeman (DougQ at ixnayamspayIgLou.com) [Call me "Doug"] Surgically excise the pig-latin from my e-mail address in order to reply "The large print giveth, and the small print taketh away." -Tom Waits

22 years, 9 months

Computers Manufactured in 1986

by mcguire＠neurotica.com

On April 2, Christopher Smith wrote: > > What wonderful machines these are. The first ones, though, shipped > > with 10MB drives, not 40MB, and it was SYSVR2, not 3. > > I don't doubt the 10M disk, but I've never seen anything below 3.0 for it. > > I have 3.5 on mine, with a 3.0 dev kit. That's not the UNIX SysV "release" number, that's the UnixPC 7300 OS version number...like Solaris2.x is SysVR4, but there's version 2.7, 2.8, 2.9, etc. The UnixPC 7300/3B1 OS base is definitely SysVR2. -Dave -- Dave McGuire "I thought it would go quickly, St. Petersburg, FL that rubberized bottom..." -Sridhar

22 years, 9 months

some what OT: FW: Adios, Internet Radio

by rigdonj＠cfl.rr.com

More US Government running amok! Joe >Subject: Adios, Internet Radio > > >========================================================= >-------- ENEWS AND VIEWS -------- >========================================================= >Delivering breaking news, as well as analysis and >commentary, from eWEEK.com > >April 3, 2002 // Volume 2, Issue 41 > >========================================================= >In This Edition >========================================================= >--OUR TAKE >Adios, Internet Radio > >========================================================= >Our Take >========================================================= >ADIOS, INTERNET RADIO > >-- By Chris Gonsalves -- > >I'm a fan of Stardog, personally. Maybe you like CelticGrove >or BlueCityJazz. Doesn't matter. In a few weeks, listening >to music on Internet radio will be dead as a mackerel. > >Shame really. The Internet radio business has been growing >at something like 100 percent annually and is thriving in >genres underrepresented on FM stations, such as classical, >blues, jazz and gospel. Doesn't matter. The government, >acting once again in the special interest of the music >industry, is about to crush the idea. > >In the latest example of groundless regulation and greed >interfering with free commerce, the U.S. Copyright Office is >considering a proposal that would force Internet radio >stations to pay exorbitant royalties to record companies and >performers, something their over-the-air counterparts are >not required to do. > >Where AM and FM radio stations pay a small fee to music >composers, Internet radio stations are facing fees of up to >14 cents per listener per song. That fee would bankrupt >nearly all of the Web broadcasters operating today, >according to the group saveinternetradio.org. > >Copyright officials have until May 21 to make the call, but >considering that the recommended shakedown came from the >advisory group they created--the Copyright Arbitration >Royalty Panel (CARP for short)--it's clear the rubber stamp >is warmed up and waiting. > >How did we get to this point? Even if you thought Napster >and others of their ilk were the bad guys, how did Internet >radio become to the target of the Harry Fox crowd? It began >in October 1998, when Congress passed the "Digital >Millennium Copyright Act" (DMCA), which gave record >companies the green light to collect royalties when music >was played via "digital media" such as Internet radio. > >It's an interesting departure from a music industry >standpoint. Record companies and performers don't get >royalties from AM and FM radio play because the copyright >folks consider the promotional value of the airplay payment >enough. So why the switch for the Internet? The theory >bought by Congress is that Internet listeners can make >"perfect copies" of the songs being streamed, and those >copies could hurt CD sales. That would be a good argument, >except that, as anyone who listens to Internet Radio knows, >you can't make "perfect copies." You can't easily make >copies at all. And if you can, they are of too low a sound >quality to be useful in creating your own CDs. What you get >sounds pretty much like those cassette tapes you used to >make off the FM radio. Not great. > >Never ones to let facts stand in their way, the solons >assigned to the CARP published their recommended royalty >schedule in late February. As the basis for the outrageous >fee schedule, the CARP report cites a $5 billion deal >between Yahoo! and Broadcast.com. The result was a figure >that would leave most Internet broadcasters, who have >attracted precious little advertising, liable for between >200 and 300 percent of their gross revenues. And, oh, by the >way, the fees are retroactive to October 1998. According to >Internet radio industry figures, a midsize independent >Webcaster with an average audience of 1,000 would owe >$525,600. > >See you later Stardog. It was nice knowing you. > >To e-mail eWEEK Deputy News Editor Chris Gonsalves, >click here: >mailto:chris_gonsalves@ziffdavis.com > >========================================================= >News >========================================================= >1. ADDITIONAL IE/APACHE PROBLEMS SURFACE > >eWEEK Labs' Timothy Dyck last month advised readers to use a >combination of HTTPS and basic authentication to get secure >log-in functionality that works with all browsers and Web >servers. It turns out that this approach won't work all the >time, either. To read the story, click here: >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gLO0A2 > >------------------------------------------------------------ >2. PAIR OF OFFICE XP BUGS UNCOVERED > >A well-known security researcher has released an advisory >about--and exploit code for--two new unpatched flaws in >portions of Microsoft Corp.'s Office XP application suite. >The two bugs are closely related and, if used in concert, >could enable an attacker to gain complete control over a >vulnerable machine. To read the story, click here: >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJj0AS > >------------------------------------------------------------ >3. INTEL TO CUT CHIP PRICING BY 57 PERCENT > >Intel is set to cut prices on its top-performing Pentium 4 >chips by as much as 25 percent this month and up to 57 >percent this spring. To read the story, click here: >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJm0AV > >========================================================= >Now at eWEEK.com >========================================================= >1. PETER COFFEE: THE LONG ROAD TO SIMPLE SYSTEMS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gLP0A3 > >2. NETWORK APPLIANCE TARGETS REMOTE ACCESS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gLQ0A4 > >3. A SECURITY EXTENSION FOR MICROSOFT OPERATIONS MANAGER >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gLR0A5 > >4. SUN BUILDS OUT JAVA TOOL SETS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJn0AW > >5. HP BOARD BALKS AT HEWLETT RENOMINATION >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0fva0A1 > >6. NAI TOOL SCANS FOR NETWORK CRACKS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJk0AT > >========================================================= >Elsewhere on Ziff Davis >========================================================= >1. JOHN C. DVORAK: NANODRIVE USES INSECT PARTS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJr0Aa > >2. ULTRAPORTABLES: HOW LOW CAN THEY GO? >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJq0AZ > >3. ARE SERVER APPLIANCES RIGHT FOR YOUR BUSINESS? >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJs0Ab > >4. LINUX X WINDOWS FLAW LETS INTRUDERS IN >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gJt0Ac > >5. BILL MACHRONE: XML SECURITY RISKS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gLS0A6 > >6. A CHEAT SHEET FOR CRM SUCCESS >http://eletters1.ziffdavis.com/cgi-bin10/flo?y=ePOu0BzN6x0DUm0gLT0A7 > >Copyright (c) 2002 Ziff Davis Media Inc. All Rights >Reserved. >

22 years, 9 months

Core Memory Interfacing?

by ajp166＠bellatlantic.net

From: Loboyko Steve <sloboyko(a)yahoo.com> To: classiccmp(a)classiccmp.org <classiccmp(a)classiccmp.org> >been mentioned before. Without those, its a heck of a >lot of discretes, and there's no way around it. Too There are pther parts out there. >a wall. I also suspect that because of all of the >unknowns involved regarding the magnetic properties of >the core that you use, the way to go about it is to If you read the article ALL of those parameters are can be tested and defined, before building the whole core plane. >of core is that there are thermistors involved also, >and that core had a very narrow range of temperature >operation. There were even programs designed >specifically to cause "hot spots" in the core in order >to test it (you'd have to know the physical layout of >the core to pull this trick off). Actually when doing that you'd also vary the slice level or the power supply levels to see where the edges are. FYI: I checks my notes and a 64x64 array needs 65 drivers and something like 192 diodes to drive the select lines. Allison

22 years, 9 months

Strange idea in VAX

by Antonio.Carlini＠riverstonenet.com

>One thing that might be interested is to see if I can find a PCI hose for >it, find source code for the PCI hose driver for a free OS (I'm pretty >sure that there is one out there somewhere), and try to write a VMS driver >for the PCI hose on OpenVMS/VAX? Can you get a PCI hose for it? I forget. If you can then you could also get one of those 3rd party PCI<->Q-bus boards and create a loop :-) >Then I could try to get a PCI >framebuffer working, but then how would I go about attaching a keyboard >and mouse? PCI->USB? Antonio

22 years, 9 months

Core Memory Interfacing?

by ajp166＠bellatlantic.net

From: Joe <rigdonj(a)cfl.rr.com> drivers and sense amps on it so that might make things easier. However there are some things that you have to do with core and I don't know if they handled in hardware or if the OS had to take care of it. For example, reading core is destructive, that is it erases the contents so you have to store the contents back into it before you do anything else (unless you don't care if it's lost). That seems like it wou! > ld be easy enough to do in HW but I don't know if that's what they did. Not an OS task. It's usually handled in hardware either in the CPU microcode or as a synchronous timing with the cpu such that if the cpu is going to alter the data at the location it's already started the cycle. Some will stop the memory cycle after the read to see if it should write the old data back or alter it, this is usually signaled by the cpu before it outputs a new address. That would be ideal as you have something you may have data on, most of the circuits and even a clue on the timing. I'd love to play with something like that rather than a scratch build. Allison > > Joe > >At 11:41 AM 4/3/02 -0600, you wrote: >>Right off, let me say that I know next to nothing about the realities of >>using core memory. I only know that it looks like pretty cool stuff to >>play with. Would I be completely off my tree to try to build a core >>memory interface from scratch, assuming I had a pre-strung core frame with >>all the cores and wires intact? When I say "interface", I mean basically >>something that will let me talk to the core from a PC or from my >>recently-completed Mark-8 using TTL or CMOS levels. If I have a 64x64 >>frame, would I just need something on the order of 256 driver transistors >>(one to drive each of the X and Y wires in either direction) plus some >>kind of op-amp or comparator circuit to monitor the sense wire (is there >>just one of these per frame?) and determine whether or not a bit has >>flipped during a read pulse? Or are there all sorts of ghosts and goblins >>lurking in core memory that I don't want to confront? >> >> >> >> >

22 years, 9 months

some what OT: FW: Adios, Internet Radio

by csmith＠amdocs.com

> -----Original Message----- > From: Lawrence Walker [mailto:lgwalker@mts.net] > classical stations. I guess I'll have to settle for Radio > Cuba on SW. :^) At least that way you're acting in support of a more honest organization than RIAA (the Cuban government)! > The US corporate beast is getting VERY greedy. They may bite > off more > than they can chew, if they wake up enough of the US populace. They may, but it's just about as likely as them deciding that McDonalds isn't a good place to go out for food. Chris Christopher Smith, Perl Developer Amdocs - Champaign, IL /usr/bin/perl -e ' print((~"\x95\xc4\xe3"^"Just Another Perl Hacker.")."\x08!\n"); '

22 years, 9 months

IBM PS/1 Recovery/Install diskettes available

by SUPRDAVE＠aol.com

In a message dated 4/3/2002 8:33:45 AM Central Standard Time, r_beaudry(a)hotmail.com writes: > >><< A bit too new to be on topic, but... I was scrounging through some > >> >>stuff > >>yesterday, and unearthed a set of original diskettes for an IBM PS/1. > >> >> > > > >do you know what model PS/1? > > Well.... I only have the disks, and not a PS/1. They were part of another > lot of stuff that I got... > > Is there a way to tell from a file on the disk, or some number on the > outside of the disk? > > Unfortunately, I've been away from IBM for several years now. The early models used 9 or so, and the later more standard models used ~14 or more. If not claimed, I will take them.

22 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

test-drb April 2002