I have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.

As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!

Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

I think Microsoft writes some drivers but not many.

I suspect the only "drivers" that Microsoft writes are the INF files todefine classes of generic devices (i.e., their miniport drivers).

This was the same idea as when Microsoft provided DirectX, so gameauthors would have a consistent interface to which they could codeinstead of each author having to design from scratch. In some cases,all that is needed is the INF "driver", like for mass storage devices(e.g., hard disks).

There have been problems in the past with hardware vendors doling out adriver to Windows and then finding their driver has a flaw. I rememberwhen Promise (probably for a SCSI controller) pushed out a driver toMicrosoft, found it had a flaw that caused data loss, and tried to yankit within the same week; however, they couldn't get Microsoft to pullthe driver for something like 3 months. For the corrected driver, youhad to use the newest one at Promise's site.

I've had Windows Update try to push a driver that was for a differentmodel within the same family of products from a vendor. For example, aWinmodem had 3 different versions (A, B, C) for the same model and Ineeded the driver for the C model, not the earlier ones. But WU wantedto push a driver for the earlier versions. If I used the old drivers,most of the Winmodem would work but a couple features would've beenlost. Although it was "just" a version change, the board vendor hadchanged which chip was on the PCB so a new driver was required to fullysupport it.

I *never* get driver updates via Windows Update. Their detection schemewon't catch the problem with the wrong driver as mentioned above for theWinmodem and the hardware vendor might already have a newer, improved,or fixed version of their driver, so using an old one could result inloss of function, or worse loss of data.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

I think Microsoft writes some drivers but not many.

I suspect the only "drivers" that Microsoft writes are the INF files todefine classes of generic devices (i.e., their miniport drivers).https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/minidrivers-and-driver-pairsThis was the same idea as when Microsoft provided DirectX, so gameauthors would have a consistent interface to which they could codeinstead of each author having to design from scratch. In some cases,all that is needed is the INF "driver", like for mass storage devices(e.g., hard disks).There have been problems in the past with hardware vendors doling out adriver to Windows and then finding their driver has a flaw. I rememberwhen Promise (probably for a SCSI controller) pushed out a driver toMicrosoft, found it had a flaw that caused data loss, and tried to yankit within the same week; however, they couldn't get Microsoft to pullthe driver for something like 3 months. For the corrected driver, youhad to use the newest one at Promise's site.I've had Windows Update try to push a driver that was for a differentmodel within the same family of products from a vendor. For example, a

When there is no other driver Windows is only option. The Webcam is thatold :)

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

I think Microsoft writes some drivers but not many.

I suspect the only "drivers" that Microsoft writes are the INF files todefine classes of generic devices (i.e., their miniport drivers).https://docs.microsoft.com/en-us/windows-hardware/drivers/gettingstarted/minidrivers-and-driver-pairsThis was the same idea as when Microsoft provided DirectX, so gameauthors would have a consistent interface to which they could codeinstead of each author having to design from scratch. In some cases,all that is needed is the INF "driver", like for mass storage devices(e.g., hard disks).There have been problems in the past with hardware vendors doling out adriver to Windows and then finding their driver has a flaw. I rememberwhen Promise (probably for a SCSI controller) pushed out a driver toMicrosoft, found it had a flaw that caused data loss, and tried to yankit within the same week; however, they couldn't get Microsoft to pullthe driver for something like 3 months. For the corrected driver, youhad to use the newest one at Promise's site.I've had Windows Update try to push a driver that was for a differentmodel within the same family of products from a vendor. For example, a

When there is no other driver Windows is only option. The Webcam is thatold :)

Cameras are split into two groups.

The older cameras didn't follow a standard.

Newer cameras are UVC (USB Video Class) compatible.They work up to about 960*??? or so. If you wanta higher resolution choice, or custom features(pan/tilt/zoom), then a custom driver is needed forthe extra features.

The camera consists of two parts. A CMOS or CCD sensorwith a glass top. And a "digital bus" to USB packetchip to get to the computer. Even if you detectedthe conversion chip via its plug and play information,that doesn't tell you what sensor is being used. If, onthe other hand, the conversion chip accepts an SPDchip off to the side, then a custom declaration canbe used to state what camera it is. And then PNPcould be used to track down a driver.

Now, if you went to the Linux side, you might find sourcecode for basic operation. You might even be able totrack down a jumbo Windows driver, based on whatyou discover using the enumeration. A tool likeUwes USBTreeView can be used for this purpose.

https://www.uwe-sieber.de/usbtreeview_e.html

Using the info from USBTreeView, you can look upthe device here. For example, your webcam could bea Sonix non-UVC camera.

http://www.linux-usb.org/usb.ids

0c45 Microdia62c0 Sonix USB 2.0 Camera

Then you'd head off to Linux land, andsee what materials they used to make the FOSSdriver for the thing.

Note that a few of the Chinese sites hosting a driverfor a Sonix, may harbor malware, so be careful. You canuse Virustotal.com to attempt a scan of a downloader sitelike that. Some camera I was working on here, had mesearching in places like that. Because a lot of these"$5 dental cameras", there's *no* fancy website to getdriver materials. You're left to collect floor sweepingsto make your new purchase work.

That's one reason why vanilla UVC is a useful option.Even if you cannot "Skype" at 1920x1080, a UVC with640x480 mode may be sufficient for a connection.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

I think Microsoft writes some drivers but not many.

I suspect the only "drivers" that Microsoft writes are the INF files todefine classes of generic devices (i.e., their miniport drivers).

No there are actual drivers written by Microsoft.

I use Microsoft drivers for the SATA ports on my Intel Z87 chipset basedmotherboard because I find them more reliable and compatible than theIntel "rapid storage" drivers.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Probably because the last driver provided by Creative (Microsoft doesn'twrite the drivers, they just included them in later versions of Windows)was a 32-bit driver. Unless Creative created a 64-bit driver, thereisn't one for Microsoft to bundle with a later version of Windows.

I think Microsoft writes some drivers but not many.

Microsoft writes "Class" drivers, which take intoaccount the "quirks" of various commercial offerings.

There would be Class drivers for USB2 and USB3 and Firewire.USBStor or UASPStor would be examples of layers abovethe physical layer.

I couldn't tell you whether Bluetooth has sufficientstandards to have a "standard register set" on a dongle,so a single driver can handle all of them.

USB has class declarations so the device can bedeclared as "Custom", and then nobody but thedevice manufacturer can offer a driver. As only theyknow what functions the registers perform.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Are these on the catalog server ?https://www.catalog.update.microsoft.com/Home.aspxPaul

Appear to be, least Broadcom Bluetooth shows up as both 32 % 64 bitversions. I'll try again as perhaps it was simply a network connectionissue. I have the driver to install 64 bit but hopefully it's notneeded.

Biggest issue is I have no bluetooth device to check it works, donglekinda just fell into lap so to speak.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Are these on the catalog server ?https://www.catalog.update.microsoft.com/Home.aspxPaul

Appear to be, least Broadcom Bluetooth shows up as both 32 % 64 bitversions. I'll try again as perhaps it was simply a network connectionissue. I have the driver to install 64 bit but hopefully it's notneeded.Biggest issue is I have no bluetooth device to check it works, donglekinda just fell into lap so to speak.

With two dongles, in theory you can do a piconet(Internet Connection Sharing). When I did an experimenthere, I think I managed to get one or two ping packetsthrough two dongles, before the connection died. Windows 10didn't seem to be prepared in any way, for a user to wanta Bluetooth piconet. The datarate would be about as fastas one of the old dialup modems. Not exactly screaming fast.

Finding a Bluetooth peripheral, if you're not a Bluetoothperson, might well be more difficult. I couldn't find anythinghere to buy, that didn't look like pure rubbish. So likeyou, I can't test the "high runner case" (A2DP).

https://en.wikipedia.org/wiki/List_of_Bluetooth_profiles

One of the problems I have with the stores here now,is there's nothing in stock for an "impulse buy". Itlooks like the stores, when they want to go bankrupt,will have a "very small clearance sale". Even a year ago,things looked a little bit better. Now all the stores justwant to run mail order outfits. Where is the servicedifferentiation ? If they want my business, how willthey demonstrate superior attributes to customers ?

Post by Stan BrownThis particular subgenre of phoneme switch is a Spoonerism.https://www.ahdictionary.com/word/search.html?q=spoonerism

Although "fobile moan" and "mucking foron" might not qualify, come tothink of it. think the rule is that the new "words" formed must beactual words. "Our queer old dean" is a common example, and the abovelink gives "/Let me sew you to your sheet/ for /Let me show you toyour seat./"

Post by Stan BrownThis particular subgenre of phoneme switch is a Spoonerism.https://www.ahdictionary.com/word/search.html?q=spoonerism

Although "fobile moan" and "mucking foron" might not qualify, come to

It's probably less common in the US, where I understand the common termis cellophane, or cell for short; in the UK, it's mobile 'phone, ormobile for short. The term "foible" on its own (or, though even less so,"moan") also has _some_ currency. [Incidentally, on a similar note: thenavigational aid that uses satellites, UK generally calls a "SatNav",whereas I gather the US calls it a "GPS". Neither, strictly, beingtechnologically correct on their own but that's how the languageevolves. Like "microwave".]

Post by Stan Brownthink of it. think the rule is that the new "words" formed must beactual words. "Our queer old dean" is a common example, and the abovelink gives "/Let me sew you to your sheet/ for /Let me show you toyour seat./"

Though "I get my wicking MusD fuddled" has a definite appeal (-:. Andthe full form of your "dean" one _does_ obey the rule - it's the loyaltoast: "Let's glaze Ruhr arses to the queer old dean".

Apparently, the reverend Sponger after whom they're named didn'tactually do the transpositions quite so rigorously as has become thedefinition, perhaps announcing the hymn "Greenland's icy mountains" as"Iceland's greasy mountains". But the name has stuck, and their use,deliberate or (often better) accidental, will continue to provide muchamusement, I hope.

Now, for those with their head in their hands over this thread drift: Ihope, if the original poster is still with us, that s/he was able to usea mobile/cell 'phone to test whether their Bluetooth adapter (or itsdriver) was working. Though since it probably involves arcane settingson the 'phone, borrowing a bomb from a nearby teenager - or an earpiece(or possibly car!) from a nearby businessman - might be easier.

Post by Stan BrownThis particular subgenre of phoneme switch is a Spoonerism.https://www.ahdictionary.com/word/search.html?q=spoonerism

Although "fobile moan" and "mucking foron" might not qualify, come to

It's probably less common in the US, where I understand the common termis cellophane, or cell for short; in the UK, it's mobile 'phone, or

cellphone!

Post by J. P. Gilliver (John)mobile for short. The term "foible" on its own (or, though even lessthe navigational aid that uses satellites, UK generally calls a"SatNav", whereas I gather the US calls it a "GPS". Neither, strictly,being technologically correct on their own but that's how the languageevolves. Like "microwave".]

Post by Stan Brownthink of it. think the rule is that the new "words" formed must beactual words. "Our queer old dean" is a common example, and the abovelink gives "/Let me sew you to your sheet/ for /Let me show you toyour seat./"

Though "I get my wicking MusD fuddled" has a definite appeal (-:. And

wucking murds

Post by J. P. Gilliver (John)the full form of your "dean" one _does_ obey the rule - it's the loyaltoast: "Let's glaze Ruhr arses to the queer old dean".

Post by J. P. Gilliver (John)actually do the transpositions quite so rigorously as has become thedefinition, perhaps announcing the hymn "Greenland's icy mountains" as"Iceland's greasy mountains". But the name has stuck, and their use,deliberate or (often better) accidental, will continue to provide muchamusement, I hope.Now, for those with their head in their hands over this thread drift: Ihope, if the original poster is still with us, that s/he was able touse a mobile/cell 'phone to test whether their Bluetooth adapter (orits driver) was working. Though since it probably involves arcanesettings on the 'phone, borrowing a bomb from a nearby teenager - or an

We need a reversal of the old saying: "DON'T do unto others as you would havethem NOT do unto you." (Paraphrase from "The Moral Maze", 1998-11-21: it was anattempt - quite good I thought - to get a modern [and non-specific] version.)

A common, cheaper alternative to PVC is low-density polyethylene (LDPE).It is less adhesive than PVC, but this can be remedied by adding linearlow-density polyethylene (LLDPE), which also increases the film'stensile strength.

In the US and Japan, plastic wrap is sometimes produced usingpolyvinylidene chloride (PVdC) ... environmental concerns."

Better life through chemistry. The LDPE sounds nicer. All dependson what plasticizer was added I suppose.

I was about to disagree with your "phonemes" comment, but realized Ihad misread "fobile" a "foible". I very nearly made myself out to bea mucking foron.This particular subgenre of phoneme switch is a Spoonerism.https://www.ahdictionary.com/word/search.html?q=spoonerism

I also picked "phonemes" because the joke involved a "phone".

The "spoonerism" bit, completely slipped my faulty memory.I've heard of the term before, but it didn't bubbleforth from the dim recesses when needed.

spoonerism (plural spoonerisms)A play on words on a phrase in which the initial (usually consonantal)sounds of two or more of the main words are transposed.REF: <https://en.wiktionary.org/wiki/spoonerism>

Yes, but in good spoonerisms, the result of the transposition is twoactual words, preferably with a humorous result.

The tits, chickadees, and titmice constitute the Paridae, a large familyof small passerine birds which occur mainly in the Northern Hemisphereand Africa. Most were formerly classified in the genus Parus.

Post by pjpI have an old Creative Webcam Gen3. Under XP it required a driver andthat's the last one available. Driver is very old, basically unuasablein todays OS's.As a curiousity I plugged it into a couple of Win7 32 bit pcs and theyall saw the camera, downloaded a driver and it was seen as a WindowsImaging Device and it worked. Under 64 bit Win7 it can't locate adriver!!!Same thing happened in last 24 hours, 64 bit Windows with a bluetoothdongle and it's go looking yourself. 32 bit downloads a driver thatappears to work properly.Is this a common occurence?

Yes, drivers not being available for old hardware and newer operatingsystems is a common occurrence.