07-22-2002
SCO TCP/IP runtime System for SCO Unix
Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine the file type. i have tried wnidows and it wants to wipe it out (typical) and i have tried a plain old un partitioned disk. I have not tried my free bsd boot yet, but i dont think it will work either.
anyway the disk says:
SCO TCP/IP runtime System for SCO Unix
media: 135dshd
type: ku386
release: 1.2.1o
has a seriel # and it is a 3 floppy disk set... does any one know how i can get this up and running. maybe i am missing the point of the title where it says "for SCO unix" but my impression was that this was a light version of unix it self. if i am wrong lay it on me brothers!!! because i just am brain farting here. So any point in the right direction would be outstanding. thanks alot
Cerberus
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was just wondering if there is a way to recursive grep for something in this version of UNIX... so that I don't have to do it a directory at a time? (1 Reply)
Discussion started by: PBNOSGT
1 Replies
2. SCO
Hi Guys
I have got a problem and I would really be grateful if some1 could sort out the problem.
I have got a healthcare system named MEDISCAN, its SCO Unix based system, I need to convert the data files into ORACLE data.
The problem is that I have been unable to open the files, whatever... (1 Reply)
Discussion started by: Faysal_Mazhar
1 Replies
3. UNIX for Dummies Questions & Answers
I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based).
I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get... (2 Replies)
Discussion started by: Parkegio
2 Replies
4. SCO
Hi folks,
First of all, sorry about my english, isn't the best and thks for advance.
Here es my problem...
I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies
5. SCO
Hi
I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7.
I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies
6. SCO
Hi every body.
I am looking for TCP package under sco unix 3.2 or sco xenix system.
would you please help me? (7 Replies)
Discussion started by: javad1_maroofi
7 Replies
7. SCO
HI,
I have sco unix server currently i am trying to boot its not booting and giving error as HTFS error message contains -
Warning : can not identify block 496 for i number 438 on HTFS dev hd (1/42).
Warning : exit - /etc/init (PID 1) died, status 0x0000008B
server is not getting boot... (0 Replies)
Discussion started by: islamsk
0 Replies
8. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
9. SCO
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies
10. UNIX for Advanced & Expert Users
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies
UBT(4) BSD Kernel Interfaces Manual UBT(4)
NAME
ubt -- USB Bluetooth driver
SYNOPSIS
ubt* at uhub? port ? configuration ? interface ?
DESCRIPTION
The ubt driver provides support for USB Bluetooth dongles to the Bluetooth protocol stack.
USB Bluetooth dongles provide two interfaces, both of which the ubt driver claims. The second interface is used for Isochronous data and
will have several alternate configurations regarding bandwidth consumption, which can be set using the hw.ubtN.config sysctl(8) variable.
The number of alternate configurations is indicated by the value in the hw.ubtN.alt_config variable, and the isoc frame size for the current
configuration is shown in the hw.ubtN.sco_rxsize and hw.ubtN.sco_txsize variables.
By default, configuration 0 is selected, which means that no bandwidth is used on the Isochronous interface and no SCO data can be sent.
Consult the Bluetooth USB specification at https://www.bluetooth.org/ for complete instructions on setting bandwidth consumption. The fol-
lowing extract may be useful as a general guidance though details may differ between manufacturers.
0 No active voice channels
1 One voice channel with 8-bit encoding
2 Two voice channels with 8-bit encoding, or one voice channel with 16-bit encoding.
3 Three voice channels with 8-bit encoding
4 Two voice channels with 16-bit encoding
5 Three voice channels with 16-bit encoding
SEE ALSO
bluetooth(4), uhub(4), sysctl(8)
HISTORY
This ubt device driver was originally a character device written by David Sainty and Lennart Augustsson. It was rewritten to support socket
based Bluetooth access for NetBSD 4.0 by Iain Hibbert.
CAVEATS
Isochronous data is seemingly not well supported over USB in the current system and to get SCO working, you may have to calculate the SCO
packet size that the stack will use. This is the sco_mtu value reported by the btconfig(8) command, and when combined with the SCO header (3
bytes) should fit exactly into an integer number of Isochronous data frames where the frame size is indicated by the 'hw.ubtN.sco_txsize'
sysctl variable.
For example: I want one voice channel (which is all that is supported, for now) so am using configuration #2, with a frame length of 17
bytes. This gives possible values of:
(17 * 1) - 3 = 14
(17 * 2) - 3 = 31
(17 * 3) - 3 = 48
(17 * 4) - 3 = 65
(17 * 5) - 3 = 82
etc.
btconfig(8) shows the maximum SCO payload as 64 bytes, so I am using the next smaller size of 48, to minimize the overhead of the 3 header
bytes.
The SCO packet size can be changed using the 'scomtu' option to btconfig(8).
The failure mode is that the USB Bluetooth dongle locks up though generally removal/reinsertion will clear the problem.
BUGS
The Isochronous configuration can only be changed when the device is not marked up.
BSD
August 27, 2006 BSD