HDTenEightyP/NetNews huggingface dataset:
From: duane@anasazi.com (Duane Morse)
Subject: TCP/IP t_close/close blocks when data is outstanding -- any relief?
Organization: Anasazi, Inc.  Phoenix, Arizona USA
Date: Tue, 10 Nov 1992 02:00:15 GMT

Under the latest release of 386/IX, we have found that t_close (under
TLI) and close (under Berkeley sockets) both block the calling processes
for about 2 minutes if there's data waiting to be sent or acknowledged.
In our test scenario, we unplug one machine from the Ethernet LAN after
having established a connection from another machine.  If we send data
after the connection has been dropped and then decide to close the
connection, the program blocks.

The sockets version is using the SO_LINGER option with 0 as the timeout,
and I've tried an ioctl(fd, I_FLUSH, FLUSHW) on the TLI version before
calling t_close, all to no avail.

The TLI version of the same test software also blocks under NCR's Sys V R 4
OS on a 3433 and under SCO Unix unless I use the I_FLUSH trick, in which
case they don't block.  I haven't worked on the sockets version long enough
on those platforms to perform the same test.

Has anyone encountered this problem under 386/IX and figured out how
to get around it?  The primary application using TCP/IP at our company
is supposed to be non-blocking because it handles multiple connections,
and it's very rude for it to block when trying to close a connection.
-- 

Duane Morse	e-mail: duane@anasazi.com
(602) 861-7609
Newsgroups: comp.unix.sysv386,comp.unix.xenix.misc
From: mcvey@mprgate.mpr.ca (Iain McVey)
Subject: ODT and XENIX compatibility
Organization: MPR Teltech Ltd., Burnaby, B.C., Canada
Date: Thu, 12 Nov 92 23:36:12 GMT

I am having a hard time compiling xenix binaries on our new ODT 2.0 
system.  The problem is that there seems to be no Slibsocket.a on the
ODT machine.  At first we thought that the library had simply been 
merged into the standard libraries, but this is not so.

There is a COFF version of the socket library, just no x.out (or xenix)
supported socket library.

Anyone????

- Iain -


-- 
Iain McVey (mcvey@mpr.ca)      | "Join the army, they said, see the next
Software Designer              |  world..." - Carry on up the Khyber
MPR Teltech Ltd.               | "This bottle of whisky is awful.  I'll be
8999 Nelson Way, Burnaby, BC   |  glad when it's done" - One Scot to another
Newsgroups: comp.unix.sysv386,comp.unix.sys5.r4
From: gerg@netcom.com (Greg Andrews)
Subject: Re: Performance of UUCP under DELL Unix (SVR4 issue 2.2)
Organization: Netcom Online Communications Services (408-241-9760 login: guest)
Date: Tue, 10 Nov 1992 00:09:07 GMT

In article <1992Nov8.235526.1476@jeck.amherst.nh.us> coffler@jeck.amherst.nh.us (Jeff Coffler) writes:
>
>At work, I have a DECstation 5000/200 that talks UUCP to my home system.  The
>modem at work is a T-2500.  The modem at home is a Worldblazer.
>
>At work, during a transfer, the CTS modem indicator goes on and off (as one
>would expect); the system transfers as much data as possible to the modem, and
>then the modem uses flow control to moderate it.
>
>At home, while I'm transferring to another site, CTS *NEVER* flickers.  That
>is, I have CTS/RTS always on solid.  One would think that I wasn't feeding data
>to the modem fast enough, but this isn't the case (the Worldblazer serial rate
>is 115k bps, fed by a Digiboard EPC/X).  Given this, it seems that the modem is
>most likely not transferring at it's maximum capacity ...
>

Looking just at the CTS light can be a red herring.  These are two
different model modems you're looking at.  Different modem, different
CTS light behavior.

The WorldBlazer's spoofing simply doesn't let the buffer fill up enough
to trigger flow control.  The T2500's spoofing does.  That doesn't mean
you're not giving the modem enough data to transfer efficiently.  You're
giving the modem as much as it wants.  If it wanted another packet, it
would return an ACK.

There is one and only one gauge of whether your transfers are moving at
maximum capacity:  Measure them (preferably with a stopwatch) and compare
the results with the expected throughput from the modem link.  Over a
Turbo-PEP connection on good lines (S70/S72 read 25000 or higher),
you should get uucp throughputs in the 1900-2100 cps range.  Higher,
if your data can be compressed.  Remember that data errors in the
receiving system can slow throughput down, and make you think it's
the modem's fault.  Make sure you measure transfers that don't register
any errors on the receiving system.


-- 
 .------------------------------------------------------------------.
 |  Greg Andrews   |       UUCP: {amdahl,claris}!netcom!gerg        |
 |                 |   Internet: gerg@netcom.COM                    |
 `------------------------------------------------------------------'
From: ignatz@chinet.chi.il.us (Dave Ihnat)
Newsgroups: comp.unix.sysv386
Subject: Re: DELL sysvr4 console buggs out on boot
Summary: Try zapping (or moving) /etc/ioctl.syscon
Date: 6 Nov 92 06:04:26 GMT
Article-I.D.: chinet.BxA67F.Awr
Organization: Chinet - Public Access UNIX

In article <1992Nov04.173517.718@openage.openage.com>
gryphon@openage.openage.com (The Golden Gryphon) writes:
>A client of mine has a DELL 486/50 DX/EISA, running DELL UNIX SVR4.  They
>had a previous consultant come in to do some work, and when she was done
>their console bugged out.  By bugged out I mean this.  
>
>When you start to boot, or boot DOS, the video is OK.

I needn't be as cautious as the Dell person who asked for info--try moving
/etc/ioctl.syscon aside before booting.  To get to that point, try booting from
floppy; perhaps first, trying to login blind, then do a "setcolor -n" to get
to a sane color combination, if that's what's hosed.

If it doesn't work, well, fine.  Otherwise, you may have solved the problem...
Newsgroups: comp.unix.sysv386
From: herbert@crunch.ikp.physik.th-darmstadt.de (Tobias Herbert)
Subject: ISC 3.0 and Tandberg TDC 3800/4100 Taperstreamer
Date: Thu, 12 Nov 1992 14:02:49 GMT
Organization: TH Darmstadt

Using the followin Hardware:

-BusTek BT742 SCSI Controller
-Tandberg Data Mod. 3800 Tapestreamer (525MB)
 or Tandberg Data Mod. 4100 Tapestreamer

I encounter the following problems with ISC 3.0(1):

Writing (and reading) 1GB or 525 MB Tapes everything works fine,
but when we use older  150MB Tapes we are unable to write
with cpio or tar to them. We get the error:

"write error, error 5" 

What is wrong with the configuration or are additional
command options necessary to write with tar or cpio.
(Must I Switch to 18 sector tapes ??)

Can anybody help ?
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: anyone get XV working with ISC?
Organization: American Micro Group, Ft. Lee  NJ
Date: Sun, 8 Nov 1992 04:05:52 GMT

In article <1992Nov07.072134.19212@gremlin.muug.mb.ca> charles@gremlin.muug.mb.ca (Charles) writes:
>
>Has anyone gotten xv to compile on an ISC 2.2.1 system?  
>If so, I'd like to know how you did it...
>
>
>I'm using the X11R3 that came with ISC but would upgrade to the Xfree86 if
>I need to.
>
>Thanks..Charles

See, the way you get help is, you do the work. You post the error
messages you get when you try to compile and ask specific questions
and then the people you're asking don't have to break their backs.

We have xv compiled here, and if you post the specifics of
your failed make by redirecting standard output and standard error to a
a file and posting the relevant parts, we'll help.
-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
Newsgroups: comp.unix.sysv386
From: mju@mudos.ann-arbor.mi.us (Marc Unangst)
Subject: Re: starting X in SCO ODT
Date: Thu, 12 Nov 1992 02:12:19 GMT
Organization: The Programmer's Pit Stop, Ann Arbor MI

In article <1dpl5jINNkjn@rave.larc.nasa.gov> jka@windshear.larc.nasa.gov (J. Keith Alston) writes:
>   open event driver failed: no such file or directory

This means that your mouse is not configured correctly.

-- 
Marc Unangst, N8VRH         | "There are two ways to solve this problem:
mju@mudos.ann-arbor.mi.us   | the hard way, and the easy way.  Let's start
                            | with the hard way."
                            |   - W. Scheider, from a Physics lecture
Newsgroups: comp.unix.sysv386
From: frigo@asiago.med.ge.com (Fred Frigo 5-5806)
Subject: Re: DTK BIOS/Chipset systems...
Reply-To: frigo@opustech.com
Organization: Opus Technologies, Inc. 
Distribution: usa
Date: Fri, 6 Nov 92 23:35:12 GMT

In article <1992Oct09.174320.11511@attics.rn.com> rdr@attics.rn.com (Dean Riddlebarger) writes:
|> >>For 386 UNIX and/or Windows 3.1 installations, has anyone noticed any
|> >>major compatibility problems with systems based on the DTK BIOS and
|> >>chipset?  Especially 486 machines?
|> >
|> >There have been some problems with dtk machines. Usually they are fine
|> >for dos but may be flaky when pushed to run windows or unix-like os's.
|> >I prefer to use Technology Power motherboards.

I have a 25 MHz DTK FEAT 2506 (or something like that).  I run
SCO Unix / Xsight with no problems.  I have an ESDI WD10007
card and a Micropolis 1664 hard disk.  I have no problems
whatsoever under Unix.   When I run under MS Windows or DOS
occcasionally I hang for almost exactly 60 seconds (sometimes
with an error message indicating a disk drive problem) and if I just
wait everything work fine after the 60 second wait....

I have replaced IO cards, checked interrupts, and tried several
different versions of proms to fix the problem, but have
kept the originals.
--
Fred Frigo    Opus Technologies, Inc.                 (__)
Voice: (414)-521-0400   FAX: (414)-549-9744           (oo)
E-mail: frigo@opustech.com                    /--------\/  
US-mail: PO Box 717,  Brookfield, WI 53008   * ||-----||
Newsgroups: comp.unix.sysv386
From: liuwu@acuson.com (Wu Liu)
Subject: Re: Installation problems with ODT 2.0
Organization: Acuson; Mountain View, California
Date: Wed, 11 Nov 1992 18:42:10 GMT

kbs@ccr-p6.ccr.jussieu.fr (SMUP7 Administrator) writes:
>Hi netters,
>
>I've just got SCO ODT 2.0 out of the box and have problems
>in installing it (tape version).
>
>Here's my config: Tandon 486DX, 487, 16Mb Ram, 630Mb SCSI disk,
>SCSI Adaptec adapter, Archive compatible drive, SMC Ethernet.
>
>So I boot with N1 and then N2...and got on the screen
>
>		address		vector	dma
>fpu				13		type=387
>serial		0x03f8-0x03ff	4		unit=0 type=standard
>						nports=1
>floppy		0x03f2-0x03f7	6	2	unit=0 type=135ds18
>         					unit=1 type=96ds15
>console					unit=vga type=0 12 screens=68K
>
>cannot install intr vecno=4, type 1, IPL=5
>vector 4 is private
>
>tape						type=S ha=0 id=2 lun=0
>						ht=ad
>(probably my adaptec, but not my Archive tape)

Nope.  This is your tape drive.  The "type=S ha=0 id=2 lun=0" string
above indicates that the kernel found a SCSI tape drive on host adapter
0, at SCSI ID 2, LUN 0.  That's the default configuration for a SCSI
tape drive in both SCO Unix and Open Desktop.

>eisarom					eisa (1.3.0)
>adapter	0x0330-0x332	11	5	type=ad ha=0 id=7 fts=s
>(my SMC ethernet card I presume!)

Nope again.  This is your Adaptec SCSI host adapter.  The "type=ad ha=0
id=7 fts=s" string indicates that the kernel found an Adaptec (or clone)
configured as the initial SCSI host adapter (ha=0), with the adapter
using SCSI ID 7 for itself.

>Then I enter all the parameters (key...), gave I/O=200, IRQ 5, DMA 3
>for the Archive-tape anf chosen "overwrite".

Don't do this unless you have a non-SCSI Archive (clone) tape drive.
If you have a SCSI tape drive that's not set up in the expected default
configuration, you can specify the real settings on the Boot: line.
See the Installation Notes for how to do so.

>So it asks me the size...UNIX, DOS partitions...
>and after a while (creating partitions...) it prints:
>
>couldn't create the root division
>couldn't divvy the active UNIX partition
>
>the following installation program has failed
>/inst2/hdinit
>
>And, I have the feeling SCO doesn't see my tape, do I have
>to link the driver at the boot or something.

The kernel found your tape drive just fine (assuming it's a SCSI tape
drive, that is).  It looks more like it didn't find your *disk* drive.
Does the initial boot screen (with all the hardware configuration values)
have a line that has "Sdsk" on it somewhere?  The kernel expects the
boot hard disk (if SCSI) to be configured as ID 0, LUN 0 (unless you've
got a MicroChannel system with an IBM SCSI host adapter), so if it's not,
the kernel won't find it.

Hope this helps.  Good luck.
-- 
Wu Liu                          Software Engineer, User Interface Group
liuwu@acuson.COM                Acuson
From: keithb@reed.edu (Keith Brown)
Newsgroups: comp.unix.sysv386
Subject: Re: accessing NOVELL from SCO-ODT
Date: 12 Nov 92 08:00:23 GMT
Article-I.D.: reed.1992Nov12.080023.8681
Organization: Reed College, Portland, OR

In article <1dpl8bINNkjq@rave.larc.nasa.gov> jka@windshear.larc.nasa.gov (J. Keith Alston) writes:
>
>Hi,
>   I'm running SCO ODT. I need to know if there is any way that
>   ODT's DOS under unix can access a novell network? Or is there any
>   way that the novell net can be accessed directly from SCO unix?
>   any ideas/information would be greatly appreciated. Thanks.
>
>-Keith Alston
> jka@windshear.larc.nasa.gov

SCO is now shipping a IPX/SPX product that lets your Unix machine
act like just another server on the Novell net.  The list price is
under $500.  Much better than the $5000.

-Keith
-- 
Keith Brown
INTERNET: keithb@reed.edu || keithb@pdx.com   UUCP: ...!tektronix!reed!keithb 
(voice: +1 503 635-5055)   CSNET: reed!keithb@Tektronix.CSNET   CIS: 72615,216
Newsgroups: comp.unix.sysv386,comp.unix.question,comp.unix.sysvr4
From: nll@cbnewsb.cb.att.com (neal.l.leitner)
Subject: ttydefs and Port Setup
Organization: AT&T
Date: Wed, 11 Nov 1992 18:00:36 GMT


Anyone know if there is a size limitation to the /etc/ttydefs file???

I am using Unix SysV rel 4.0.2.1.  My ttydefs file, after adding some
entries, is 134 lines long.  Using the pmadm command to configure a port,
the port will not configure properly.  The term entry I want to use in
the ttydefs file is on line 124, so I moved it to the top of the ttydefs
file and configured the port and it configured ok.  After playing around
a while line 115 of the ttydefs file seems to be the limit.  The port
would configure with the entry on line 115, but not 116.  Anyone
else have any experience with this????

Neal Leitner
..att!emdbl1!nll

Newsgroups: comp.unix.sysv386,misc.forsale,misc.forsale.computers,misc.forsale.computers.other,comp.unix.pc-clone.32bit,comp.windows.x
From: herbert@crunch.ikp.physik.th-darmstadt.de (Tobias Herbert)
Subject: ISC 3.01 and TDC 3800/4100 TAPESTREAMER
Date: Wed, 11 Nov 1992 18:52:43 GMT
Distribution: comp
Organization: TH Darmstadt

Using the following Hardware:

-BusTek BT742 SCSI Controller
-Tandberg Data Mod. 3800 Tapestreamer (525MB)
 or Tandberg Data Mod. 4100 Tapestreamer

I encounter the following problems with ISC 3.0(1):

Writing (and reading) 1GB or 525 MB Tapes everything works fine,
but when we use older  150MB Tapes we are unable to write
with cpio or tar to them. We get the error:

"write error, error 5" 

What is wrong with the configuration or are additional
command options necessary to write with tar or cpio.
(Must I Switch to 18 sector tapes ??)

Can anybody help ?

Newsgroups: comp.unix.sysv386
From: k2ph@dxis.att.com (Bob Schreibmaier)
Subject: Re: Performance C News on Release 3.2
Organization: QRM Central, Kresgeville, PA
Date: Mon, 9 Nov 1992 17:14:19 GMT

>Has anybody successfully compiled the performance release of
>C News on a System V/386 Release 3.2 box?  I'm running AT&T
>Release 3.2 Version 2.3 and am getting nowhere fast.  The
>first problem is it expects a /usr/include/sys/vfs.h file
>that doesn't exist.  It goes downhill from there.  :-(

Thanks to everybody who responded.  The bottom line seems to
be when build asks you what type of df you have say sysv, even
though you have ustat.  This required a little playing with
spacefor, but everything else builds without a hitch.

-- 
-------------------------------------------------------------------
| Bob Schreibmaier K2PH | UUCP:     att!dxis!k2ph     |   Free    |
| (a.k.a. "The QRPer")  | INTERNET: k2ph@dxis.att.com |    the    |
| Kresgeville, PA       | ICBM:     40o55'N 75o30'W   | Intel 386 |
-------------------------------------------------------------------
Newsgroups: comp.unix.sysv386,comp.sys.att,alt.sources
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: Latest Fixdisk for ISC3.0
Organization: American Micro Group, Ft. Lee  NJ
Date: Mon, 9 Nov 1992 15:40:04 GMT

In article <566@rri.UUCP> tim@rri.UUCP (Tim Buck) writes:
>In article <Bx4FsG.Dv@maxed.amg.com> ed@maxed.amg.com (Ed Whittemore) writes:
>>
>>Just upgrade to 3.01. It's only $95.
>>-- 
>>Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
>>American Micro Group, Inc.   201-944-3293
>
>Can someone post a list of things that ISC 3.01 fixes from ISC 3.0 so I
>can decide how important it is to upgrade?  Thanks.
>
>Timothy Buck   --   rri!tim@vtserf.cc.vt.edu OR timbuck@borg.lib.vt.edu
> Recognition Research, Inc. (703) 231-6500	++ NeXTmail accepted ++
>------------------------------------------------------------------------
> Borger King:  Special orders are irrelevant. You will have it our way.

It's been done many times. Just cal SunSoft at 1-800-346-7111, ask for
Interactive Teleservices Upgrades who can tell you or fax you a list.
-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
Newsgroups: comp.unix.sysv386
From: ed@maxed.amg.com (Ed Whittemore)
Subject: Re: ISC 3.0 multiple FDISK partitions?
Organization: American Micro Group, Ft. Lee  NJ
Date: Fri, 13 Nov 1992 02:40:34 GMT

In article <1992Nov12.062326.19981@timesink.chi.il.us> mikebo@timesink.chi.il.us (Michael Borowiec) writes:
>In article <BxKEKD.v0@ad4su1.rsre.mod.uk> druid%caercn@ajax.rsre.mod.uk (ad4su1) writes:
>>On my hard disk I have three *real* partitions---i.e., created with FDISK.
>>The first is for DOS, the second for ISC 3.0, the third is spare.
>>I would also like to use the third partition for ISC, as a home partition.
>>
>>Is this possible?
>
>Yes, use /dev/dsk/0p3
>
>>
>>It seems to me that ISC only ever looks at the first UNIX partition,
>>which it divides into several of what it calls partitions. I am not
>>able to re-FDISK at this stage and thus merge the second and third
>>partitions.
>>
>>Can anyone suggest how I can make use of my third partition from UNIX?
>>
>>	Regards and thanks,
>>		Mark.
>
>Here is the poop on using DOS fdisk partitions in ISC UNIX >= 2.2 from
>the 2.2 release notes:
>/dev/dsk/...
>np0	Entire physical drive n
>np1	1st fdisk partition on drive n
>np2	2nd "
>np3	3rd "
>np4	4th "
>np5	1st extended DOS partition on drive n
>np6	2nd "
>... etc, etc, through
>np15	11th extended DOS partition on drive n
>
>Additional info:
>ns0	Entire UNIX system partition on drive n
>	(not the entire disk as it meant in 1.x releases of 386/ix)
>ns1	1st "soft" UNIX partition in the UNIX fdisk "hard" partition
>	(usually root)
>
>The spec changed from 2.2.x to 3.0.x in that:
>/dev/dsk...
>c0d0s3	<= 2.2.x syntax for Controller 0, Disk 0, Slice 3 (usually /usr)
>c0t0s3	>= 3.0.x syntax for Controller 0, Target 0, Slice 3
>
>I had configured my 2nd fdisk partition as a 64MB DOS partition. Since
>I didn't need it as a DOS parition any longer, I simply did a mkfs,
>labelit and mount and, voila... I have a new 64MB UNIX partition I
>mount as /dev/dsk/0p2. Works like a champ... 
>- Mike
>
>PS> Get 3.0.1 or 3.0 Update disk FD3.0S.3 to be able to mount DOS 4/5
>    (or Compaq DOS 3.31) partitions greater than 32MB under UNIX like:
>    mount -f DOS /dev/dsk/0s? /dos
>
This is very interesting, and appears to work with some disks as the
first or second physical drives, but not all, or 3rd drives. But in some
instances, while mkfs, and fsck seem to work, mount does not giving
the error message:

mount: /dev/dsk/c0t2p1 no such device

We also get complaints from the disk controller:

NOTICE: free block read error on Bustek 742 SCSI HBA Controller <bt742> DISK Target 2, LUN 0 partition 17

Partition 17, hmmmm...:)

Too bad. I suppose the advice would have to be--if it works for you
great, if not...

I wouldn't like to rely on this for file storage.
-- 
Ed Whittemore   uunet!maxed!ed   ed@maxed.amg.com
American Micro Group, Inc.   201-944-3293
From: vec@sunshine.Kodak.COM (Vance Cochrane)
Newsgroups: comp.unix.sysv386
Subject: ISC on an ALTEC Box
Date: 5 Nov 92 14:27:34 GMT
Organization: Eastman Kodak Co., Rochester, NY

hi,
I am considering buying an Altec box on which to run the latest version 
of ISC.  
I was wondering if there was any wisdom out on the net regarding this and
if there are any problems associated with this company.
thanks in advance.

vec

-- 
+------------------------------------------------------+
+ Vance Cochrane                Email: vec@Kodak.COM   +
+ Research Laboratories	        Voice: (716) 722-3709  +
+ Eastman Kodak Company	        Fax:   (716) 477-8681  +
+ Rochester, NY 14650-1826                             +
+ USA                                                  +
+------------------------------------------------------+
From: marrevola@iris-dcp.es
Newsgroups: comp.unix.sysv386
Subject: Re: starting X in SCO ODT
Date: 12 Nov 92 14:38:56 GMT
Organization: REDIRIS, Red Nacional de I+D

In article <1dpl5jINNkjn@rave.larc.nasa.gov>, jka@windshear.larc.nasa.gov (J. Keith Alston) writes:
> 
> Hi,
>   I'm running SCO ODT (not sure which version). When I attempt to
>   start the X window system, with startx, I get the following
>   message:
>    open event driver failed: no such file or directory
> 
>   does anyone out there have any idea what might be causing
>   this problem?????

Check for the file .startxrc at your home directory. Also check files in
/usr/bin/X11 and /usr/lib/X11. If all this is fine, try to start the X
processes manually (X, mwm, odtterm , etc ...) from a remote terminal to
 your default display and check if there is any failure.

manolo@taf.fundesco.es
Newsgroups: comp.unix.sysv386
From: kbs@ccr-p6.ccr.jussieu.fr (SMUP7 Administrator)
Subject: Installation problems with ODT 2.0
Organization: Laboratoire d'Electrochimie - Paris 7, FRANCE.
Date: Tue, 10 Nov 1992 19:55:34 GMT

Hi netters,

I've just got SCO ODT 2.0 out of the box and have problems
in installing it (tape version).

Here's my config: Tandon 486DX, 487, 16Mb Ram, 630Mb SCSI disk,
SCSI Adaptec adapter, Archive compatible drive, SMC Ethernet.

So I boot with N1 and then N2...and got on the screen

		address		vector	dma
fpu				13		type=387
serial		0x03f8-0x03ff	4		unit=0 type=standard
						nports=1
floppy		0x03f2-0x03f7	6	2	unit=0 type=135ds18
         					unit=1 type=96ds15
console						unit=vga type=0 12 screens=68K

cannot install intr vecno=4, type 1, IPL=5
vector 4 is private

tape						type=S ha=0 id=2 lun=0
						ht=ad
(probably my adaptec, but not my Archive tape)
eisarom						eisa (1.3.0)
adapter		0x0330-0x332	11	5	type=ad ha=0 id=7 fts=s
(my SMC ethernet card I presume!)

Then I enter all the parameters (key...), gave I/O=200, IRQ 5, DMA 3
for the Archive-tape anf chosen "overwrite".
So it asks me the size...UNIX, DOS partitions...
and after a while (creating partitions...) it prints:

couldn't create the root division
couldn't divvy the active UNIX partition

the following installation program has failed
/inst2/hdinit

And, I have the feeling SCO doesn't see my tape, do I have
to link the driver at the boot or something.

Thanks in advance for any help.

Au revoir,
-- 
=============================================================================
Laboratoire d'Electrochimie - Universite Paris 7  |Khac Binh Su
4, place Jussieu, Tour 44/45, 75005 PARIS. FRANCE |e-mail: kbs@ccr.jussieu.fr
=============================================================================
Newsgroups: comp.unix.sysv386