Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!saimiri.primate.wisc.edu!sdd.hp.com!swrinde!elroy.jpl.nasa.gov!decwrl!csus.edu!nic.csu.net!vax.sonoma.edu!levinson Newsgroups: comp.unix.bsd Subject: Re: [386bsd] Colorado Jumbo tape drive device driver. Message-ID: <1992Nov10.153518.1@vax.sonoma.edu> From: levinson@vax.sonoma.edu Date: 10 Nov 92 15:35:18 -0800 References: <raz.720786927@ultima> <1992Nov5.153537.1@vax.sonoma.edu> <1dchecINN4pk@hpsdlss3.sdd.hp.com> Distribution: world Organization: Sonoma State University Nntp-Posting-Host: vax.sonoma.edu Lines: 47 In article <1dchecINN4pk@hpsdlss3.sdd.hp.com>, mattb@sdd.hp.com (Matt Bonner) writes: > In article <1992Nov5.153537.1@vax.sonoma.edu>, levinson@vax.sonoma.edu writes: > |> In article <raz.720786927@ultima>, raz@socs.uts.edu.au (The Inimitable Raz) writes: > |> > Has anyone developed, is anyone working on, has anyone worked on a > |> > 386bsd driver for utilising Colorado Jumbo 250M, floppy controller > |> > attached, tape drives? > |> > > |> > Does anyone have any info or code at all for driving these items? > |> > > |> > raz@socs.uts.edu.au (Roland Turner) (OH) 61 2 906 4681 > |> > |> > |> It is amazing, that with all the Jumbo systems sold, only you and I are asking > |> about a driver for this tape drive! > |> > |> If you happen to find one, let me know. If I find one, I will let you know. > |> > |> I am still waiting for Colorado Memory Systems to respond to a message I sent > |> to their Compuserv address. It has been about 3 weeks. > |> > > This was discussed a few months ago, I believe the final answer was > that something in Colorado drive I/O was proprietary, and Colorado > wouldn't share, so you can't write the driver for them. I could be > wrong though, I didn't follow the thread too intently. > > Regards, > Matt > -- > > Matt Bonner | Email: mattb@sdd.hp.com > Hewlett-Packard Company | Snail: 16399 West Bernardo Drive > Ink-jet Components Division | San Diego, CA 92127-1899 -- Yes, you are correct. I think the proprietary part lie in the compression routines, however I am not interested in that aspect. I could always compress with COMPRESS or something like that. I think it is very unprofessional for them simply not to respond. -- Eric Levinson rcisnet2!root@moon.nbn.com | Home computer (UUCP) levinson@vax.sonoma.edu | Vax I can also be reached on my BBS system, Color Galaxy Milky Way (415) 883-0696