Nfl Game Package For Computer there. I can't believe this post has been 3 weeks with no reply? Though it flagged up on my system today 13th May 2014 ok. My ten pence worth.

Download the latest driver for CDC RS-232 Emulation Demo, fix the missing driver with CDC RS-232 Emulation Demo. Cdc rs 232 Emulation demo usb driver. COM Port Data Emulator - Emulates a device connected through or an Ethernet port how samsung android cdc driver.

1) The device simply may not work with windows 8. (bummer) Lots of references to NT in the config file. 2) You MAY need administrator access to load any driver in win 8 (Don't use it, so speaking from ignorance). 3) Contact the manufacturers and ask IF it works with win8 though it if does, this says more about Win8 than the authors of the PIC product as 6 years is a long time in Computing, then ask what you need to do as plug 'n' play, it isn't. 4) If win8 cannot locate a driver for you, then it might be a hard slog.

5) If it THAT important. Might a Win7 emulator work I wonder?

Sorry to give you nothing at all helpful but your post deserves a reply. I am sure there are Uber Users out there who might know better though you may also try posting your request on a Microsoft site though beware of 'Not Invented Here' Syndrome.

Firstly, above INF file lacks x64 (.NTamd64) sections - it never works for 64bit windows. Secondly, above INF file declares a device of VID/PID = 0x04D8 / 0x000A This VID/PID is originally assigned to Microchip CDC examples.

You may apply these INF files (and.cat file) on Microchip Library, instead of above flawed one. Microchip_solutions_v2013-06-15 USB Device - CDC - Basic Demo inf mchpcdc.inf and.cat OR microchip mla v2013_12_20 apps usb device cdc_basic utilities inf mchpcdc.inf and.cat For your convenience, I attached the INF and.cat file to this post Tsuneo. I apologise for not replying to the thread for so long.

I hadn't been notified of a reply. Thank you so much for replying. I have attempted to install the driver you linked by simply right clicking and then pressing 'install' but to no avail. My device still doesn't work. I'm a complete newbie here so any relevant guidance I may need would be very much appreciated. It's like feeling around in an unfamiliar room in the dark.

EDIT: In the device manager I get the device come up as 'USB Input Device' with error code 10 which apparently means that Windows can't start the device. EDIT 2: So last night I found that you can install the microchip driver through the 'Add legacy devices' option in device manager. I added the serial COM port option, but still to no avail. Even when I tried all the different COM port options I still couldn't get it to realise that there was a device attached. I'm starting to understand the driver files better now though. The only thing I observed that could be of issue in the driver file is that the PID when the device comes up as 'USB Input Device' its VID is '04D8' but its PID is 'D001'.

I've seen a PID of simply '00D' in the inf file but not 'D001'. 'Device USB VID_04D8&PID_D001 5&15c311e1&0&11 was configured.' Is what I get under the USB device. So I don't know a lot about INF files either, but a few weeks ago I needed a CDC/ACM INF file for my M-Stack library. After looking through a lot of sources and examples, I was able to come up with what I think is the right way to do it for at least Windows 7: The reason I post this here, knowing that your problem is with Win 8, is that this method makes a _lot_ of use of standard facilities included from a system INF file installed already in the system (see the include references to mdmcpq.inf). Looking now, I do see similar in what Tsuneo posted, so maybe this won't help you.

I will say though, that mine seems to be a lot more bare-bones, so maybe there's something in the Microchip files that's conflicting with what Windows 8 is trying to do. It's one more thing to try, and it's all I know about it:) I am far from an expert on the INF files. If it is a windows certified driver it will download if needed and install itself. But we're talking about CDC here. Windows will not automatically install a driver for a CDC device without a manual install of an INF file which binds the Windows CDC driver to the device. Reading over some of the terminology in the original posting, I'm now starting to wonder whether we're even looking at the right thing. Razyre, the INF file that you posted, where did you get that?

Did it come with the device? Did it come from the system manufacturer's webiste? You said you 'acquired a driver from 2008.' The VID/PID in the INF file you posted is from a Microchip demo: 04d8:000a. When you say it has a PIC18F2450, keep in mind that has no bearing on what driver may be necessary to interface with it, since a 2450 is programmable microcontroller and can be programmed for any USB device class. Since you say you're a complete newbie, it comes to my mind that you may not know that, and may have seen the part number on the chip, looked for a driver, found an INF from Microchip, and tried to install it to no avail. Having a driver automatically install on Windows 7 seems to indicate that the device has a custom WHQL driver (or at least an INF) in the Microsoft driver database.