[comp.unix.xenix] EBADF when moving from Xenix to SCO Unix.

mla@enea.se (Mats L|fstr|m) (08/14/90)

A customer of mine has just moved from Xenix/386 to SCO Unix on the same
hardware (Compaq 386).
On the system, they are running an application written in Thuroughbred
(spelling?) Business Basic.

On the Xenix system, the application work just fine, but when running
the same basic programs on SCO Unix, they frequently gets EBADF when
trying to write files.

Questions are:

- Has anyone seen this before?
- What to do about it?

Thanks in advance!

	mla

----------------------------------------------------------------------------
International:			Domestic:
Mats Lofstrom			Mats L|fstr|m
ENEA Data AB			ENEA Data AB
Nytorpsvagen 5b			Nytorpsv{gen 5b
Box 232				Box 232
S-183 23 TABY			183 23  T[BY
Phone: (+46) 8792 - 2500	Tel: 08 - 792 25 00

		e-mail: mla@enea.se
----------------------------------------------------------------------------

barton@holston.UUCP (Barton A. Fisk) (08/17/90)

In article <1997@enea.se>, mla@enea.se (Mats L|fstr|m) writes:
> 
> On the Xenix system, the application work just fine, but when running
> the same basic programs on SCO Unix, they frequently gets EBADF when
> trying to write files.
> 
> Questions are:
> - Has anyone seen this before?
> - What to do about it?

Check the permissions on the files, EBADF means bad file number.
Either a file descripter refers to no open file or a read request
was made to a write only file or vice versa.

Hope this helps.
Bart
-- 
uucp: holston!barton