G-spy Driver

So I had a Arch Linux installed last year (using the Wiki's beginner's guide) on my laptop and I didn't use it up until yesterday. Yesterday I was just messing around when I stumbled upon some Nvidia settings thing installed, decided to check it out, clicked it and it said something like update you nvidia. So I ran pacman -S nvidia, which I assume went well and said that I'll be able to use nvidia after reboot. So I rebooted and there it hung up on me, it 'got stuck' on Starting LXDE display manager, started LXDE display manager, stopped LXDE display manager. This would repeat a few times, then it would say that few other things started up until Network, and there it would just get stuck. Also when I go to ctrl+alt+F2 it goes back to ctrl+alt+F1 automatically after a few seconds which I guess it means it's still trying to load something up without success. I assumed that my video drivers got screwed, so I did pacman - R nvidia; same for nvidia-utils.
After a reboot the booting process would be the same except for some weird noaveau spam.
Something like [123123] noaveau [P SOMETHING 123123].
So what I did after that is reinstall LXDE and LXDM, didn't help. I reinstalled the nvidia again, didn't help. Then I decided to reinstall xorg and xorg-server, didn't help. My laptop has 2 video cards, one nvidia and one intel. So I downloaded intel drivers using commands from the Wiki, still didn't do the trick. Basically I spent whole night doing a combination of pacman -R and pacman -S for nvidia; xorg; intel, and lxde/lxdm. When I disable lxdm and reboot, it just asks me for my credentials and I can do my thing, just without the GUI. When I enable it, depending if I have currently nvidia installed, it would either do nothing (just the _ blinking) or it would spam the noveau thing.

I know that I'm describing this kind of vague, and 'thingie' or 'thing' isn't a sufficient explanation, it's just that I really don't exactly remember each line or whatever.

So what we have:


Had fairly fresh install of Arch Linux using a begginer's guide from last year.
Ran LXDE with it, everything was wonderful.
Decided to update the nvidia, rebooted, everything went to hell.
I spent whole last night and half of today trying to google and Wiki my problem, it's just that I can't really find a solution on my own, hence I'm asking on a forum. Any help would be appreciated. If there's any more info needed, I will gladly provide it.

E: Solved by removing /etc/X11/xorg.conf

My search for G-Spy turned up some kind of cam recording software. I would scan my computer with MalwareBytes and what ever other security software I had available. Check your Device Manager panel for unknown devices or yellow triangles. In Device manager explore the details of the mouse driver. See if G-Spy is mentioned. Shop for Mini Wireless Security Cameras at Walmart.com. Apr 06, 2012 So got a new mouse today, iv used Razor mice products in the past but never got this would you like to install this device software name Razor Razer device Publisher G-SPY Co, Ltd Iv never heard of that G-SPY thing and sounds pretty dodgy.

Last edited by NumeroSMG (2016-08-23 20:40:14)

Typical Windows CU-SeeMe configurations

A variety of Windows system configurations that are used for running CU-SeeMe, courtesy of Bill Ryan of White Pine. If you're running CU-SeeMe on a setup not noted here (but is interestingly different), please let Bill know.

From: [email protected] (Rich Kennerly)

We now have available, via FTP, the updated ComputerEyes RT capture drivers that work with CU-SeeMe.

To get it, FTP to bearcat.cit.cornell.edu and log in as:

login: computereyes
password: cu-seeme

Get the readme.txt and rtvidcp.exe (binary self-extracting ZIP file). This driver is now shipping with new RT cards and is also available from Digital Vision's dialup download service.

I'd like any feedback on how this works with CU-SeeMe; this board (as well as the ProMovie Spectrum & Studio) has potential for being as good as the discontinued Video Spigot card and we'd really like to be able to recommend a board or two instead of just saying which ones apparently work or don't.

From: [email protected] (Rich Kennerly)

We have a driver written by Michel Carleer that does work with the Pro-Movie Spectrum (and I expect will work with the Pro-Movie Spectrum) that we're having integrated into CU-SeeMe by a third party developer. There is also a new driver that takes care of the palette problem but still results in the image being upside down (available from Media V.).

This being a nice, popular, inexpensive card should be perfect for the philosophy behind CU-SeeMe and we expect to be able to support it.

From: [email protected] (Rich Kennerly)

The new version of CU-SeeMe will have PAL support, tested already with the Video Spigot. It should work for any capture card whose VidCap has a PAL input option.

From: [email protected] (Scott Rasmussen)

Problems and solutions:

Can't use more than 16 meg ram on my system.

From: anonymous

Problems and solutions:

The camera type seems to matter for the ComputerEyes/RT card, its unsteady with my tiny electronic camera.

From: [email protected] (arvell hairston)

Problems and solutions:

1. reverse polarity image (neg image) with cuseeme; soon to solved by exteral codec or by using a capture brd that has overlay functions or a built in tvtuner (feature connector).

2.no audio with cuseeme ;rescued by iphone.

3.no icons on cuseeme window;unable to access human interface files at ncsu.

4.Half video transmited:cuseeme does not like PPP connections.

From: [email protected] (Chuck Elliot)

Problems and solutions:

occasional 'bind to udp port' error usually after crash

From: [email protected] (Alain Caillet)Salary

Problems and solutions:

Waiting for a more advanced version as this one does not support audio.

Error messages during transmission, require manual closing of the window where they display. Their existance or number should be made to display but they shouldn't interrupt the peration of the program. Splendid application!

From: [email protected] (Steve Loboyko)G-spy

Problems and solutions:

G-spy Driver License

PMS board driver shipped with product yields 4 bit negative image. New driver from their bulletin board yields 8-bit negative image. Cornell says board will be supported in next version; I may have a fix sooner. MediaVision will not fix problem.

I am working on software that will allow CU to be easily used over POTS.

G-spy driver license testFrom: [email protected] (Richard Collins)

Problems and solutions:

None reported.

From: [email protected] (Bennett Frankel)

Problems and solutions:

Config my autoexec and config files.

From: [email protected] (John Allain)

Problems and solutions:

Indeo is not an 8-bit palletized card. Apply for CU-SeeME alpha test copy.

CU-SeeME error: 'WSAAsyncSelect() blew chow. (10035)'. Apply for CU-SeeME alpha test copy. -or- get a subdomain name set for myself.

From: anonymous

Problems and solutions:

Works great... I just want SOUND!

From: [email protected] (Ian Simmins)

Problems and solutions:

Soon to have Mac PowerBook 520 with 28.8K PPP

From: [email protected]

Problems and solutions:


Since the Laptop is portable over half the time, I need to wait until the video codec is in place to get support for a PCMCIA based video card.

Problems and solutions:

None reported.

From: Anonymous

Problems and solutions:

Get Video for Windows from somewhere.. Get targa drivers...do not run targa windows program concurrently... CUSeeMe can handle it alone...Amiga's video out and nintendo video out seem to have horizontal rolling problem

From: [email protected] (gordon whelpley)

Problems and solutions:

Get loads of 'sendto' errors if I set max rate above 14K.

From: [email protected] (Byron Thomason)

Problems and solutions:

For error, Write Packet sendto (10050) I lowered the kbps to 15 max.

From: [email protected] (Gary)

G-spy Driver Updater

Problems and solutions:

Warp includes an Internet Access Kit, which is a subset of the full TCP/IP product (SLIP only, no servers). Otherwise they are functionally identical. OS/2 makes it's TCP services available to virtual DOS machines via a number of interfaces, including Winsock for Windows sessions.

After installing the most recent set of patches (aka CSDs), host name resolution was not working reliably from Winsock apps. In my case I ran the DNS product that is an addon to TCP, but name resolution SHOULD work if th host and resolv files are setup correctly in tcpip/etc and tcpip/dos/etc.

It is also possible to run Trumpet from a Windows session, although the network is only available to apps running in that session, and not to native OS/2 apps. I have run CuSeeMe with Trumpet in this environment, but there is noticeably more overhead than when using the OS/2 TCP code.