Whenever I attempt to use my standard Win32::SerialPort, it croaks in CommPort.pm at CreateFile.
From what I could find, the problem* seems to be the way the FileHandle is called in kernel32...
(from another forum discussing this driver): "I know that all of the Win32 API dlls, such as kernel32.dll, use the _stdcall convention. It is my understanding that any non-C programs linking to a dll require the _stdcall parameter passing convention.
BTW, the difference betweeen the two calling conventions is that when using _cdecl, the calling program cleans up the stack after the call, but with _stdcall, the called (dll) program does the cleanup."
Bottom line, has anyone had such an issue before and can they share the code modifications on how they made it work?
-------------------------------------------------- The error I get when I run is from CommPort.pm, sub CreateFile and says:
....The system cannot find the file specified. can't open device: COM10
In reply to Perl->Win32::CommPort->COM ports->Kernel32->ftdi driver by gluphus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |