Login or Register to Ask a Question and Join Our Community


UNIX and Linux RSS News

Another SCO Creditor Sells Its Claim to Argo

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Another SCO Creditor Sells Its Claim to Argo
# 1  
Old 10-13-2010
Another SCO Creditor Sells Its Claim to Argo
Tech Marketing Ink of Orem, Utah, a creditor in the SCO bankruptcy, has sold its claim to Argo Partners. I guess it figured a bird in the hand and all that. At this point, the company may feel that there's no getting blood from a stone and the likelihood of getting paid by SCO in bankruptcy court is slim. You can sell your claim if anyone will buy it, usually for a price that may be less than you are owed, but at least you have something. In real money. In a real world.
The company does presentations, among other things. I can't help but wonder if they did the presentations that SCO used with analysts. That would be ironic, to have it all end up like this.
But why would Argo buy this claim? I can't imagine, so let's research possibilities. The claim is modest, in the bigger picture, for $3,000. But we've seen Argo before.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question

LEARN ABOUT NETBSD

btsco

BTSCO(4)						   BSD Kernel Interfaces Manual 						  BTSCO(4)

NAME

     btsco -- Bluetooth SCO Audio

SYNOPSIS

     btsco*    at bthub?
     audio*    at audiobus?

DESCRIPTION

     The btsco driver provides support for Bluetooth SCO Audio devices through the audio(4) driver.

     The btsco driver must be configured at run time with the btdevctl(8) program.  The following properties are used by the btsco driver during
     autoconfiguration:

     local-bdaddr
	       Local device address.

     remote-bdaddr
	       Remote device address.

     service-name
	       The btsco driver matches the 'HF' and 'HSET' services.  For the 'HF' service, the btsco device will, on open(2), listen for incom-
	       ing connections from the remote device.	Otherwise, btsco will attempt to initiate a connection to the remote device.

     rfcomm-channel
	       This integer value is not used directly, but will be stored and passed via the BTSCO_INFO ioctl as below:

     SCO connections require a baseband connection between the two devices before they can be created.	The btsco driver does not create this, but
     can provide information to facilitate an application setting up a control channel prior to use, via the BTSCO_INFO ioctl(2) call on the mixer
     device, which returns a btsco_info structure as follows:

     #include <dev/bluetooth/btsco.h>

     struct btsco_info {
	     bdaddr_t	     laddr;	     /* controller bdaddr */
	     bdaddr_t	     raddr;	     /* headset bdaddr */
	     uint8_t	     channel;	     /* RFCOMM channel */
	     int	     vgs;	     /* mixer index speaker */
	     int	     vgm;	     /* mixer index mic */
     };

     #define BTSCO_INFO      _IOR('b', 16, struct btsco_info)

     The btsco driver can be configured to act in Connect or Listen mode.  In Connect mode, the btsco driver will initiate a connection to the
     remote device on an open(2) call, whereas in Listen mode, open(2) will block until the remote device initiates the connection.

SEE ALSO

     bthset(1), ioctl(2), audio(4), bluetooth(4), bthub(4), btdevctl(8)

HISTORY

     The btsco driver was written for NetBSD 4.0 by Iain Hibbert under the sponsorship of Itronix, Inc.

BUGS

     btsco takes no notice of the HCI Voice Setting in the Bluetooth controller, and this must be 0x0060 (the default) as alternate values are
     currently unsupported.

BSD
								  October 4, 2006							       BSD