As many people suggested, I now use usbser.sys to map USB to COM port (Win2k/XP).
But I could not figure out if there is a similar possibility to use on older Windows versions (Win9x/Me, Win95 is only "nice to have").
So does anybody know such a possibility or how to install usbser.sys on the system to have the same end solution as under Win2k/XP?
Many thanks for any hints and advices
Holi
il_renato
October 19th, 2004, 06:29 AM
Hi, send me a mail replace ooo with o, let me know how it turns out.
Find on google cdciden.inf edit an change hw and prod id.
This might help:
http://homepages.wmich.edu/~r1slone/work/iDEN%20Update/USB%20Compatibility/INF%20Files/cdc/
also you can change some names and strings, will have to do this myself
too.
Next look at:
http://ddrnation.com/idenusb/usb/mdmiden.inf
and change it too your likes, not changing the functionality
Now your product must be working according to the usb cdc class and thus
working in xp or 2000 as a com port. I have mine working here no prob.
Connect your product to usb, it will say composite device, but have it use
the cdciden.inf file. Next it will install but point again for a driver
file, have it use mdmiden.inf. A modem will be installed, and a com port
will be added.
I tested this all today for the first time as I am currently apperantly
doing the same as you do, so there, some help.
I have contact now on a win 98 laptop with only supplying the inf files
and no driver files!
regards revo
It seems it only works with the WDM driver, I found a file called
ymhusb.inf with the contents alike cdciden.inf
; Windows USB CDC ACM Setup File
; Copyright (c) 2000 Microsoft Corporation
; Copyright (c) 2000 YAMAHA Corporation
;
; Manufacturer: YAMAHA Corporation Wed Jun 27 2001
;
[Version]
DriverVer = 06/27/2001,1.01.0000.1 ; mm/dd/yyyy[,x.y.v.z]
Signature = $CHICAGO$
Class = WDM
Provider = %Mfg%
LayoutFile = layout.inf,layout1.inf,layout2.inf
Now with this and the standard mdmiden.inf it works without changing
anything but the hw and prod id.
revo
Holi the Rob
January 4th, 2005, 03:57 AM
Hi Revo
I'm back now into this work again. And I had success with your files - with slight modifications (besides the ones you mentioned: VID/PID stuff):
In the cdciden.inf file I changed the following:
remove the "CatalogFile" entry in [Version] section (I don't have it)
[USBIDEN]
;CopyFiles=USB.Drvrs,USB.VxD
AddReg=USBIDEN.AddReg
--> remove the ';' so the installation process will work (it didn't without this line) and automatically invoke the installation for the second file.
To have only an additional COM port and not a modem (the device isn't a modem) I changed the following in the mdmiden.inf:
change Class to Ports (section [Version]):
Class = Ports
ClassGUID = {4D36E978-E325-11CE-BFC1-08002BE10318}
in the [All] section:
from:
HKR,,FriendlyDriver,0,Unimodem.vxd
HKR,,DevLoader,0,*vcomm
HKR,,ConfigDialog,0,modemui.dll
HKR,,EnumPropPages,0,modemui.dll,EnumPropPages
to:
HKR,,FriendlyDriver,0,serialenum.vxd
HKR,,DevLoader,0,*vcomm
HKR,,ConfigDialog,0,serialui.dll
HKR,,EnumPropPages,0,serialui.dll,EnumPropPages
This works for getting a COM port. Unfortunately the port number isn't shown in the device manager and I don't get the "Port Settings" tab in the property dialog. But I see another COM device I can open and read/write as on a normal port.
So, thanks for this great hint!
Regards
Holi
Holi the Rob
January 4th, 2005, 04:15 AM
I encountered a bug: when I disconnect the device (COM port was not connected) and conect it again, I get a blue screen as soon as I want to open the COM port. It says:
Error: 0E : 028 : C1543907
I have to restart the PC in order to connect to the COM port again.
codeguru.com
Copyright 2007 Jupitermedia Corporation All Rights Reserved.