DSMTalk Forums: Mitsubishi Eclipse, Plymouth Laser, and Eagle Talon Forum banner
1 - 1 of 21 Posts
If you have not solved this problem, while I dont have a dsmlink, I am a cerified network tech.

You issue is that serial interfaces are legacy technology (OLD and less FLEXIBLE). If it were truly a USB interface through and through, the USB API would handle that for you. That may have been gibberish to some, but OH WELL.

Anyhow, it doesnt matter which COM the dsmlink is on or the USB port is set to, so long as they are both the SAME. If setting the above value in the .dll file did not work, it is:
A) because that is not the port DSMLINK wants to communicate on, or
B) Yo shit is FUCKED UP!

To fix this, simply do this in vista (very similer in XP, but Im not a fucking GeekSquad employee, so use Google)

Hit the windows key or orb (start menu or windows key in XP)
go to "control panel"
go to device manager (called system bleh bleh bleh in XP, and has a tab labled "hardware" which contains a button labeled "device manager")
Eyeball the PORTS section of the tree display
the port you want will be listed, and without having to click on any particular one, should say (COM##) next to it

edit the dsmlink.prefs file as state before using the com## you saw in the device manager

You should be good to go, but if not, restart; legacy hardware often times requires a restart for changes to take effect. (windows 95/98 anyone?)
 
1 - 1 of 21 Posts