Re: I-concepts Webcam Drivers Setup Free
Edel Dieringer
I've tried everything to get these things to work with no success...of any kind. I've followed the instructions to the letter and still nothing. It's obviously not plug and play, the drivers on the disk do nothing. Perhaps this product was made only for Dell computers made in August, 2003 with Intel chipsets and silver case screws...it's the only thing I can think of. I've tried manually setting up the device with no success. I just downloaded the drivers someone posted earlier on this thread and they seem to be the same drivers included on the disk. I think we've all been had. Return this product asap and buy something else! Do it now! For the love of god do it now! Don't waste your precious time on this inferior product! I beg you! We are all doomed.
Alright...frustrated as hell at this thing I cracked it open with a very large and heavy bowie knife. (I bought it clearance and lost the receipt...might as well have fun, no?) I plugged it in and began shorting out the circuit board with a piece of metal and VOILA! the sucker was instantly recognized by windows and began to function. SO! If it collecting dust because they won't let you return it...pop the bottom screw out, pull the circuit board and start touching metal bits with a screwdriver until windows recognizes it. The drawback of course is that the stand is broken...but there's always duct tape. :) It just crappy construction! The drivers are fine!
I'd like to first thank everyone for trying out the Webcam for Dummies. I was alerted to this website by one of our customers and was hoping I could address some of the questions that I see on this page regarding our webcam.
Many of you have noticed that on page nine of the camera's manual there is a reference to a toggle switch on the camera. This is actually an error in the manual which we only caught after the product was released to stores. We have since corrected the manual, and the new version is offered on our website and can be downloaded by going to the web address below:
Another issue discussed has been this camera's compatibility with the Windows Vista operating system. This camera originally hit stores before the initial release of the Windows Vista operating system, and thus unless specifically listed, the camera will not work with Vista. However, the new cameras that we are currently sending to stores do include Vista compatibility. Additionally, we are working on a driver that will allow all versions of this camera to be used with Vista. Within the next few weeks that driver will be posted on our web site, and I will post a link here too.
I will be checking this website periodically and will do my best to answer as many questions as possible. If anyone would like to e-mail me questions directly, feel free to e-mail me at [email protected]. I will do my best to answer any questions as quickly as possible.
Also, we do apologize for any delays and long hold times you might have had on our toll free technical support phone number (877 397 8200). However, we are excited to say that we will be offering 24/7 phone service with a larger staff of technicians on digital cameras starting immediately.
I've called two different toll free numbers, and have succeeded to getting routed to the worst possible elevator music you could imagine. You could break terrorists with this stuff. I've sent email, both on the online form at www.sakar.com, as well as directly emailing [email protected] (supposed to be tech service there).
49152 DM driver does not have problem. But
maybe the connecter has problem.
If you claim your webcam does not work,
what you have to do is to try USB hub!!
AVOID CONNECTING WEBCAM INTO YOUR COMPUTER DIRECTLY.
No TrackBacks yet. TrackBack can be used to link this thread to your weblog, or link your weblog to this thread. In addition, TrackBack can be used as a form of remote commenting. Rather than posting the comment directly on this thread, you can posts it on your own weblog. Then have your weblog sends a TrackBack ping to the TrackBack URL, so that your post would show up here.
Thin clients occur as components of a broader computing infrastructure, where many clients share their computations with a server or server farm. The server-side infrastructure uses cloud computing software such as application virtualization, hosted shared desktop (HSD) or desktop virtualization (VDI). This combination forms what is known as a cloud-based system, where desktop resources are centralized at one or more data centers. The benefits of centralization are hardware resource optimization, reduced software maintenance, and improved security.
Thin client hardware generally supports common peripherals, such as keyboards, mice, monitors, jacks for sound peripherals, and open ports for USB devices (e.g., printer, flash drive, webcam). Some thin clients include (legacy) serial or parallel ports to support older devices, such as receipt printers, scales or time clocks. Thin client software typically consists of a graphical user interface (GUI), cloud access agents (e.g., RDP, ICA, PCoIP), a local web browser, terminal emulators (in some cases), and a basic set of local utilities.
In using cloud-based architecture, the server takes on the processing load of several client sessions, acting as a host for each endpoint device. The client software is narrowly purposed and lightweight; therefore, only the host server or server farm needs to be secured, rather than securing software installed on every endpoint device (although thin clients may still require basic security and strong authentication to prevent unauthorized access). One of the combined benefits of using cloud architecture with thin client desktops is that critical IT assets are centralized for better utilization of resources. Unused memory, bussing lanes, and processor cores within an individual user session, for example, can be leveraged for other active user sessions.
The simplicity of thin client hardware and software results in a very low total cost of ownership, but some of these initial savings can be offset by the need for a more robust cloud infrastructure required on the server side.
An alternative to traditional server deployment which spreads out infrastructure costs over time is a cloud-based subscription model known as desktop as a service, which allows IT organizations to outsource the cloud infrastructure to a third party.
Thin client computing is known to simplify the desktop endpoints by reducing the client-side software footprint. With a lightweight, read-only operating system (OS), client-side setup and administration is greatly reduced. Cloud access is the primary role of a thin client which eliminates the need for a large suite of local user applications, data storage, and utilities. This architecture shifts most of the software execution burden from the endpoint to the data center. User assets are centralized for greater visibility. Data recovery and desktop repurposing tasks are also centralized for faster service and greater scalability.
While the server must be robust enough to handle several client sessions at once, thin client hardware requirements are minimal compared to that of a traditional PC laptop or desktop. Most thin clients have low-energy processors, flash storage, memory, and no moving parts. This reduces the cost and power consumption, making them affordable to own and easy to replace or deploy. Numerous thin clients also use Raspberry Pis.[2] Since thin clients consist of fewer hardware components than a traditional desktop PC, they can operate in more hostile environments. And because they typically don't store critical data locally, risk of theft is minimized because there is little or no user data to be compromised.
Modern thin clients have come a long way to meet the demands of today's graphical computing needs. New generations of low energy chipset and CPU (Central Processing Unit) combinations improve processing power and graphical capabilities. To minimize latency of high resolution video sent across the network, some host software stacks leverage multimedia redirection (MMR) techniques to offload video rendering to the desktop device. Video codecs are often embedded on the thin client to support these various multimedia formats. Other host software stacks makes use of User Datagram Protocol (UDP) in order to accelerate fast changing pixel updates required by modern video content. Thin clients typically support local software agents capable of accepting and decoding UDP.
Some of the more graphically intense use cases remain a challenge for thin clients. These use cases might include applications like photo editors, 3D drawing programs, and animation tools. This can be addressed at the host server using dedicated GPU cards, allocation of vGPUs (virtual GPU), workstation cards, and hardware acceleration cards. These solutions allow IT administrators to provide power-user performance where it is needed to a relatively generic endpoint device such as a thin client.
To achieve such simplicity, thin clients sometimes lag behind desktop PCs in terms of extensibility. For example, if a local software utility or set of device drivers are needed in order to support a locally attached peripheral device (e.g. printer, scanner, biometric security device), the thin client operating system may lack the resources needed to fully integrate the required dependencies (although dependencies can sometimes be added if they can be identified). Modern thin clients address this limitation via port mapping or USB redirection software. However, these methods cannot address all scenarios. Therefore, it is good practice to perform validation tests of locally attached peripherals in advance to ensure compatibility. Further, in large distributed desktop environments, printers are often networked, negating the need for device drivers on every desktop.
While running local productivity applications goes beyond the normal scope of a thin client, it is sometimes needed in rare use cases. License restrictions that apply to thin clients can sometimes prevent them from supporting these applications. Local storage constraints may also limit the space required to install large applications or application suites.
7fc3f7cf58