1. Drivers & Software Updates Search. Do you have the latest drivers for your device? Our engineering team is constantly adding, updating and improving our drivers to ensure optimal performance.
2. Lo and behold after much surfing and fretting, switching machines and reconfiguring, bluetoothing and blue-swearing, I found a 64-bit USB driver that works with PalmDesktopWin62 on a Treo 755p. I installed the Palm software; plugged the phone's sync cable into the PC USB port; and manually added the new USB driver. Works like a champ.

For certain Universal Serial Bus (USB) devices, such as devices that are accessed by only a single application, you can install WinUSB (Winusb.sys) in the device's kernel-mode stack as the USB device's function driver instead of implementing a driver. This topic contains these sections: Automatic installation of WinUSB without an INF file. Download usb driver - Best answers Spvd-012.1 usb driver for windows 10 - Forum - Drivers Sony psp usb driver windows 10 - How-To - PSP.

• August 22, 2019 2.9.8

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.8	Released August 22, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added several internal interfaces for particular sensors (J003).

• January 25, 2019 2.9.6

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.6	Released January 25, 2019	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added missing Tonemapping Auto property.

• May 4, 2018 2.9.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.5	Released May 4, 2018	Type ZIP	Filesize 3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 controller Graphics card with 24 or 32 bit Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Enabled tonemapping for 8bit video formats, e.g. Y800, RGB24 and RGB32.

• November 21, 2017 2.9.4

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.4	Released November 21, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Repaired not working J003 mono sensor pattern fix on particular video formats. This driver version is the last that works in Windows XP.

• January 9, 2017 2.9.3

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.3	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added a pattern fix for J003 mono sensors.

• January 9, 2017 2.9.1

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.9.1	Released January 9, 2017	Type ZIP	Filesize 3.2MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed the driver signature Code 52 error on new Windows 10 v1607 systems.

• January 15, 2016 2.8.9

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.9	Released January 15, 2016	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Changed certificates so that the driver can also be installed in Vista.

• November 9, 2015 2.8.7

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.7	Released November 9, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed an error which can appear when using sharpness on older CPUs.

• October 20, 2015 2.8.5

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.5	Released October 20, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed a bug which can appear on LivePause call.

• July 15, 2015 2.8.0

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.8.0	Released July 15, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support of DFK ECU010-L34 with serial number property. Added tone mapping.

• February 17, 2015 2.7.33

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.33	Released February 17, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog The Auto Focus Onepush Running flag now resets correctly after the auto focus has finished.

• February 5, 2015 2.7.32

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.32	Released February 5, 2015	Type ZIP	Filesize 2.4MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Video format MJPG (2592x1944) of DFK AFU050-L34 camera can now be used.

• January 14, 2015 2.7.31

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.31	Released January 14, 2015	Type ZIP	Filesize 2.3MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Support for IMX236 based cameras. Support for RGB64 color formats. Several performance improvements.

• June 6, 2014 2.7.9.1152

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.7.9.1152	Released June 6, 2014	Type ZIP	Filesize 2.1MB
  Requirements Intel Core i3 or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Added new properties: Brightness, sharpness, de-noise, saturation, hue and contrast. Added new property: Highlight reduction. Added new property: White balance temperature controls. Pixelfix for Y16 cameras now works as expected. VideoControl_ExternalTrigger (DirectShow property) can now be set as expected.

• January 1, 2014 2.6.5.1014

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.6.5.1014	Released January 1, 2014	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog Fixed missing auto-gain for DFK AFU130. Fixed focus when start value is out of auto_focus_range. Fixed problem with AUTOFOCUS_ROI_RIGHT: minimum possibly wrong. Fixed auto focus ROI not working for 21*UC cameras. Fixed crash on load/connect with certain cameras 22/72xUC. Fixed previous exposure settings not being loaded on reconnect. Complete reworking of internal property system. Fixed Windows XP driver load crash. Fixed drop counter to be accessible from DirectShow. Fixed Windows 8 problem with certain video formats needing converters with standard DirectShow filters (e.g. Y800, capturing to an Y800 avi file was not possible). Fixed a problem with Windows 8 usbxhci driver not allowing transfers larger then 4 MB.

• February 26, 2013 2.4.14.851

  Device driver for all The Imaging Source USB cameras except the 33U, 37U, 38U and AFU auto focus series.
  Version 2.4.14.851	Released February 26, 2013	Type ZIP	Filesize 1.9MB
  Requirements Intel Pentium IV or similar, 2 GB RAM USB 3.0 or USB 2.0 controller (depends upon camera model) Graphics card with 24 or 32 bit Windows XP, Windows Vista, Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit) DirectX 9.0c or higher
  Changelog WHQL certification.

• News
• Reviews
  • Smartphone & PDA Reviews
• RSS
• About
  • GlassWave

Ruggedized PDA manufacturer Aceeca has done what many thought impossible by releasing USB drivers for users of 64-bit Windows and Palm OS Garnet devices.

Aceeca Usb Devices Driver Download For Windows 10 64

While the driver is primarily intended to work with the company's Garnet-based handhelds such as the new PDA32, Aceeca is encouraging unsupported testing on other Palm OS devices running some version of Garnet (i.e. Palm OS 5.4 or higher). Compatible Palm Inc. devices, in theory, should be the T5, E2, LifeDrive, Z22 and TX handhelds along with the Treo 650, 700p, 755p, and Centro smartphones.

The driver is digitally signed so as not to cause any unsigned device drive alerts in Windows. Thus far, users reports from the community indicate that the older Palm Inc. 4.1.4 version of Palm Desktop from 2004 intended for Windows XP has a higher success rate working with this 64-bit driver than the newer Vista-compliant Palm Desktop 6.2 released in 2008.

Aceeca's Hotsync drivers currently only officially supports Microsoft Windows 7 64-bit, which is by far the most popular and compatible 64-bit version of Windows to date. A stickied thread on the HP Palm support forums giving advice on driver installation and Hotsync setup is here, while Aceeca's forum thread detailing the driver release is here.

Article Comments

(24 comments)

The following comments are owned by whoever posted them. PalmInfocenter is not responsible for them in any way.
Please Login or register here to add your comments.

Yes!!

RE: Yes!!

what's next? cave paintings and stone tablets?

RE: Yes!!

Gekko, you are wrong on this one. This is FANTASTIC news!

RE: Yes!!

RE: Yes!!

RE: Yes!!

The driver works on os4 and os 5 palm devices also

RE: The driver works on os4 and os 5 palm devices also

will it interface with a VHS player and 8 track too?

please go call that hooker you were looking at the other night. you need it.

RE: The driver works on os4 and os 5 palm devices also

in other news - Commodore is providing new support for the 1541 5.25' floppy drive.

RE: The driver works on os4 and os 5 palm devices also

Well done, Aceeca!

Download For Windows 10 Free

I wonder why our little buddies at Access didn't do this a LOOOOOOOOOOOOOONG time ago.

Thanks for nothing, Schlesinger. How's that ALP OS hanging? How many phones sold with ALP OS so far? Idiot.

FJH

RE: Well done, Aceeca!

RE: Well done, Aceeca!

When time permits, I am going to round up all of the remaining USB Palm OS devices in my stable (TX, Treo 755p, Zire 72) and post my findings as well as any pertinent install or configuration info here in a how-to article. All of the PIC faithful can respond with their own tips, questions and experiences.

Ironic how Win 7 (in both 32-bit and 64-bit flavors) hit the market when there were still a number of new Centros out in the market and being sold/activated. If a small operation like Aceeca can release this as an act of goodwill to the Palm OS community (I can assure you there are more late-model Palm Inc Garnet device users installing this driver than there are Aceeca PDA users), Palm or Access definitely could have done it with their far greater available resources. What a shame but kudos again to Aceeca!

This might be the final chapter in a long saga but it's definitely not the first instance of the 'Palm companies' twiddling their thumbs while 3rd parties and the user/dev community scramble to address a glaring flaw or product shortcoming. Softick Audio Gateway & Card Export, TealScript for the G1 fans, Dmitri's PowerSDHC, FAT32 driver and all the other 'PowerUps', Aeroplayer on the T|T etc etc etc etc)

Pilot 1000->Pilot 5000->PalmPilot Pro->IIIe->Vx->m505->T|T->T|T2->T|C->T|T3->T|T5->Zodiac 2->TX->Verizon Treo 700P->Verizon Treo 755p->Verizon Moto Droid + Verizon Palm Centro-> Verizon Moto Droid X + Palm TX

RE: Well done, Aceeca!

Centro is still a hell of a bargain for a PDA. I keep an unlocked GSM Centro around for travel + some PDA purposes, but the power of my 400 iPhone apps has made PalmOS less crucial to me over the past year. PalmOS PIM, speed and 20 of my all time favorite PalmOS apps will keep me using PalmOS devices forever though. I have a really nice collection of devices that can be pressed into service at whim.

FJH

RE: Well done, Aceeca!

'They did not believe there was money enough in it for them.'

Smart companies don't shaft longtime customers. Palm lived off the goodwill of the Palm name for the past decade during which time they foisted crap like Lifedrive and Pre upon unsuspecting victims. (Read the horribly inaccurate, never-updated Palminfocenter fluff 'review' of the Lifedrive to see how the media played a role in deceiving customers.)

Having ACCESS to the sourcecode, both Palm and Access should have been able to fix the desktop issues within a few weeks and at minimal expense. Instead they said 'Screw you!' to the millions of people who have purchased PalmOS devices over the years. Palm abandoned PalmOS users and developers when they transitioned to webOS. HP/Palm screwed the developer that had released the PalmOS emulator for webOS. HP/Palm abandoned owners/early adopters/victims of the original Pre. Access LIED repeatedly about its ability to get its tragic ALP OS onto shipping hardware. Access changed its OS and strategy/business plan yearly for 3 years, the entire time releasing nothing but fetid VAPOR(ware) from the mouth of its chief shill, David 'Lefty' Schlesinger. See a pattern with these companies? History repeats and eventually customers and developers that have been burned in the past will wise up and move on to more reliable/trustworthy platforms.

So yes, maybe there would be no DIRECT financial gain to Palm or Access from supporting legacy products, but the goodwill such a move would have generated would have been worth the trivial cost of providing the support.

FJH

RE: Well done, Aceeca!

RE: Well done, Aceeca!

Aceeca Usb Devices Driver Download For Windows 10 32 Bit

Someone somewhere (Brighthand, perhaps?) commented on what a good e-book reader the PDA32 was with its gargantuan battery life and the brightness turned down to the lowest level.

I'd like to see Aceeca introduce a refreshed PDA32 in the future (perhaps to coincide with the availability of 802.11g & BT options) in a black case. Adding 4GB SDHC card support to it would be icing on the cake. Hell, I bet Dmitry Grinberg could really give them a hand for stuff like FAT32 and SDHC support.

Back to Palm: The LifeDrive, with its initial shipping ROM, remains the single worst product I ever purchaed at a substantial pricepoint with reasonly expections of performance and reliability. In fact, I returned the first one, waited a mont hor two, then bought another hoping I just got an early production dud the first timea round. It was just as bad. What a horrible, horrible device. Some of its flaws were addressed in future ROM updates but there was simply no reason to release a Microdrive-based device with such a feeble amount of RAM in 2005. I'd rather have seen a refreshed T5 with 512mb or 1gb of internal flash than that nasty 4GB Microdrive.
Pilot 1000->Pilot 5000->PalmPilot Pro->IIIe->Vx->m505->T|T->T|T2->T|C->T|T3->T|T5->Zodiac 2->TX->Verizon Treo 700P->Verizon Treo 755p->Verizon Moto Droid + Verizon Palm Centro-> Verizon Moto Droid X + Palm TX

RE: Well done, Aceeca!

RE: Well done, Aceeca!

Why did Ryan publish such a B.S. 'review' of the LifeDrive? Did he actually use the device or did he just have someone from Palm write the review for him? Probaby one of the all time low points for Palminfocenter.

The Tapwave Zodiac makes a decent book reader if you can still find them. I bought a couple back when they were being blown out for around $100 apiece when the company announced they were giving up on the market and liquidating all of their remaining stock. It was definitely ahead of its time.

FJH

RE: Well done, Aceeca!

RE: Well done, Aceeca!

Will Gekko realize his comments aren't funny?

Between his shrill pom pom cheerleading for Android and his increasingly strident whining about why he wishes PalmOS was no longer still a useful OS it's obvious that he's just a mailroom clerk with control issues living out his fantasies online. Whatever.

OK, we get that you're in love with Android an want everyone to stop using PalmOS and instead join you in the Google Collective. But that's not going to happen. So go back to your circle jerks with the other mailroom clerks on the Android sites. If you find you need to post here try to at least string together a cogent paragraph or two... if your tiny brain is actually capable of such a feat. Save the tiresome photo and YouTube links for your Android Reach Around Buddies. Perhaps you need some more snuggle time with a certain craven member of Colligan's BoyToys? Mmmmmmmmkay.

FJH

Aceeca Usb Devices Driver Download For Windows 10 64

Android Reach Around Buddies (ARABs) fear the Ugly Truth

Google is spending hundreds of millions of dollars developing a mobile OS to give away 'for free', but they STILL don't get it. Android is an OS designed by geeks for geeks. It isn't an OS for regular, normal people. Normal people don't spend several hours a week rooting thrir phones, downloading and installing hacked custom ROMs and tweaking 100 different near useless widgets cluttering up their home screen.

Android is an utter mess in terms of its User Interface and ironically may have gotten even worse since the Google Collective's acquisition/assimilation of webOS UI guru Matais Duarte. The ONLY reason Android has become the most commonly used smartphone OS is because almost every manufacturer is using it, so consumers are forced to use Android whether they want to or not. And the only reasons manufacturers are using Android are because it's 'free' and they're too shortsighted, stupid and moneyhungry to realize why using Android and entrusting their future to Google is a big mistake.

A mobile OS should be all about speed, simplicity, ease of use, rapid presentation of data, stability, flexibility, and ease of application development. Android fails in most of these aspects. Compare iOS, webOS, Windows Phone 7, the new BlackBerry OS and even Meego and Symbian to Android and it becomes obvious how poorly designed Android is.

Aceeca Usb Devices Driver Download For Windows 10 Free

Android clearly needs a COMPLETE redesign of its User Interface. Copying the webOS UI (as RIM did) would be the a good idea. Or else just mimicing the UI of a jailbroken iPhone running Infinidock, Infiniboard and Infinifolders. Another option would be to create a Launcher X UI (or at least provide this as a user-selectable option ). Upcoming CPUs are so powerful that it soon won't matter that Android is a sluggish, poorly optimized OS. Security and the rampant problems with rogue apps stealing user data needs to be addressed immediately. That issue alone should be enough for wise consumers to stay away from Android phones.

Android has quickly become a blight upon the smartphone world and should be avoided at all costs until it is fixed. Just say no to Android.

FJH

RE: Android Reach Around Buddies (ARABs) fear the Ugly Truth

Latest Comments

• I got one -Tuckermaclain
• I got one -Tuckermaclain
• RE: Don't we have this already? -Tuckermaclain
• RE: Palm brand will return in 2018, with devices built by TCL -richf
• RE: Palm brand will return in 2018, with devices built by TCL -dmitrygr
• Palm phone on HDblog -palmato
• Palm PVG100 -hgoldner
• RE: Like Deja Vu -PacManFoo