SCO OPENSERVER5.0.7 Problem

10 More Discussions You Might Find Interesting

1. SCO

SCO OpenServer 5.0.5 Problem

I am currently having a problem with my SCO OpenServer 5.0.5 / 3.2v5.0.5 system. Running smoothly for the past 3 years, at random on March 16, 2010 the system crashes. I reboot it. Everything is normal again. 9 hours later it crashes again. This cycle has repeated itself ever since then. System...

2. SCO

Mouse problem in sco 5.0.6

hello i have a problem with mouse in vmware with sco 5.0.6 in graphic mode X11 my mouse move to corner after a while do you have any idea about this problem vmware 6.5.2 vmware 7

3. UNIX for Dummies Questions & Answers

vi problem, sco -> redhat

I rlogin from a sco box to a redhat box and run /bin/vi. Pgup, Pgdn, and arrow up/down keys don't work. I enter "export TERM=ansi80x25" and run vi again.Everything works just like I like it. Except the cursor turns into a blinking overscore. When I exit vi and close the connection to redhat,...

4. SCO

Small Problem with SCO

Help Please , how to shutdown SCO v. 5.0.5 from client pc ( windows xp or 2000 ) ? i have full access from client and i need to shutdown SCO from windows

5. SCO

Sco 6 copying problem

We are using GTAR for daily copies of our database using Travan cartridges (Tapestor drive)and are having intermittent problems. Some days it does not copy and we can't figure out why. Sometimes it seems to be hanging and a tape status command doesn't return anything. Other times it doesn't copy...

6. SCO

sco openserver 5.07 installation problem

Hi everyone, We r installing sco openserver 5.07 on dell poweredge 2800 but we are facing problem when installing SCSI-raid drivers. Dell provide Perc4 raid card and we dont found raid drivers for this specific raid card. So we r stuck up on primary stage and we also dont know the...

7. SCO

Problem while installing Unixware 7 SCO

Hi All, I just tried to intall Unix ware SCO version 7 on my computer but when system first boots from the CD The terminal Emulator does not shows texts in correct form; it shows all the text in Obnoxious form which is unable to read. I have ATI Radeon 9000 Graphics card installed on my...

8. UNIX for Dummies Questions & Answers

SCO 5.0.6 installation problem

I tryed to install SCO 5.0.6 OpenServer on P4 2.0 GHz 384 MB ram 40 GB HDD. It booted from the floppy disk, and when it comes to hd_config I got this error: unexpected trap in kernel mode: PANIC: K_trap - kernel mode trap 0x0000000E ** Safe to power off ** Please, what should I do?

9. Filesystems, Disks and Memory

SCO openserver 5 install problem

Hello all, I'm trying to install SCO openserver 5 on a 2.5 Gig hard drive, and I tried fdisk and a low-level format of the drive. When I insert the boot diskette all seems fine, and it asks me to set the cd-rom and it sees it and reads from it. Well, I'm thinking all is well until right after I...

10. UNIX for Advanced & Expert Users

SCO 5.05 partition problem

Hardware: IBM 300PL 32MB RAM 60Gig HDD During the phase in SCO installation where I get to partition my hard disk, SCO only seems to see 8Gig out of the 60 that I have. Does anyone out there know of a utility or what I need to do to make the the whole 60Gig available. Thanks

LEARN ABOUT NETBSD

ubt

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

SCO