From: vasco@icpnet.pl (Andrzej Popielewicz)
Subject: [TUHS] Irwin 285
Date: Thu, 21 Jan 2010 13:05:16 +0100 [thread overview]
Message-ID: <4B5842FC.6000407@icpnet.pl> (raw)
In-Reply-To: <48239d391001210226v7bc5208apf497cc74b54f5d4b@mail.gmail.com>
Sergey Lapin pisze:
> Hi, all!
>
> Once, I was dismantling very old very long dead rusty box, which once
> ran some version of SCO UNIX.
> And I've got a strange device I've seen nowhere else - floppy-attached
> tape drive, labelled Irwin, model 285. Drive looks
> OK visually, motor wiring is perfect, so I can't see why it won't work.
> I tried to make it run with old and new versions of Linux, but failed.
> Do anybody have any documentation
> regarding this?
>
> Also - how wide these devices were used? I've never met one before
> while I can't say I have little IT experience.
>
> All the best,
> S.
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs
>
> __________ Informacja programu ESET NOD32 Antivirus, wersja bazy sygnatur wirusow 4792 (20100121) __________
>
> Wiadomosc zostala sprawdzona przez program ESET NOD32 Antivirus.
>
> http://www.eset.pl lub http://www.eset.com
>
>
>
>
>
I have seen , I think 2 years ago, a company in California which still
offered these drives brand new and tapes for them.Try to google.
The only system I know, which supports these drives, is Coherent.
You can still find sources of the driver and eventually port it to SCO.
But probably the manufacturer of this drive offers drivers for SCO.
Andrzej
Andrzej
_______________________________________________
TUHS mailing list
TUHS at minnie.tuhs.org
https://minnie.tuhs.org/mailman/listinfo/tuhs
next prev parent reply other threads:[~2010-01-21 12:05 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 10:26 Sergey Lapin
2010-01-21 10:51 ` Brantley Coile
2010-01-21 11:19 ` Jochen Kunz
2010-01-21 11:32 ` Wilko Bulte
2010-01-21 12:07 ` Sergey Lapin
2010-01-21 12:37 ` Jason Stevens
2010-01-21 13:02 ` Wilko Bulte
2010-01-21 16:50 ` Jochen Kunz
2010-01-21 17:11 ` Jochen Kunz
2010-01-21 17:37 ` M. Warner Losh
2010-01-21 17:41 ` Sergey Lapin
2010-01-21 19:00 ` Jochen Kunz
2010-01-21 19:10 ` Al Kossow
2010-01-21 19:36 ` Jochen Kunz
2010-01-21 19:41 ` Wilko Bulte
2010-01-21 19:45 ` John Cowan
2010-01-21 18:59 ` Wilko Bulte
2010-01-21 19:48 ` Jochen Kunz
2010-01-21 19:56 ` Wilko Bulte
2010-01-21 19:58 ` Larry McVoy
2010-01-21 20:00 ` Wilko Bulte
2010-01-21 20:11 ` Larry McVoy
2010-01-21 20:26 ` Jason Stevens
2010-01-21 20:41 ` Wilko Bulte
2010-01-21 20:44 ` Larry McVoy
2010-01-21 21:00 ` Wilko Bulte
2010-01-21 21:01 ` Larry McVoy
2010-01-21 21:36 ` lyricalnanoha
2010-01-21 22:15 ` Larry McVoy
2010-01-21 22:22 ` M. Warner Losh
2010-01-22 9:14 ` Jochen Kunz
2010-01-22 9:34 ` Wilko Bulte
2010-01-22 10:15 ` Jochen Kunz
2010-01-22 10:46 ` Wilko Bulte
2010-01-22 11:06 ` Jochen Kunz
2010-01-22 11:12 ` Wilko Bulte
2010-01-22 15:38 ` Larry McVoy
2010-01-22 16:52 ` Jochen Kunz
2010-01-22 16:55 ` Wilko Bulte
2010-01-21 20:46 ` Jason Stevens
2010-01-21 22:15 ` Aaron J. Grier
2010-01-21 22:57 ` Wilko Bulte
2010-01-21 20:36 ` Wilko Bulte
2010-01-21 20:44 ` Corey Lindsly
2010-01-21 21:45 ` Wilko Bulte
2010-01-22 0:36 ` [TUHS] Backup software (was: Irwin 285) Greg 'groggy' Lehey
2010-01-22 0:48 ` Jason Stevens
2010-01-28 20:27 ` Brad Spencer
2010-02-12 17:03 ` Tim Bradshaw
2010-02-15 1:19 ` [TUHS] dump(8) compatibility (was: Backup software (was: Irwin 285)) Greg 'groggy' Lehey
2010-02-15 1:24 ` Jason Stevens
2010-02-15 1:30 ` [TUHS] dump(8) compatibility M. Warner Losh
2010-02-15 2:27 ` Larry McVoy
2010-02-15 5:05 ` Warner Losh
2010-02-15 5:18 ` Jason Stevens
2010-01-21 20:33 ` [TUHS] Irwin 285 Jochen Kunz
2010-01-21 20:44 ` Wilko Bulte
2010-01-21 20:47 ` Larry McVoy
2010-01-22 9:23 ` Jochen Kunz
2010-01-22 9:32 ` Wilko Bulte
2010-01-22 0:38 ` [TUHS] Tape backups? (was: Irwin 285) Greg 'groggy' Lehey
2010-01-21 20:18 ` [TUHS] Irwin 285 Jochen Kunz
2010-01-21 12:05 ` Andrzej Popielewicz [this message]
2010-01-21 12:12 ` Sergey Lapin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B5842FC.6000407@icpnet.pl \
--to=vasco@icpnet.pl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).