Opened 17 years ago
Closed 17 years ago
#873 closed Bug (No Bug)
DLLCall crashes when characters \\.\ in parameters
| Reported by: | Owned by: | ||
|---|---|---|---|
| Milestone: | Component: | AutoIt | |
| Version: | 3.3.0.0 | Severity: | None |
| Keywords: | DLLCall Crash | Cc: |
Description
Hi,
tried to use DLLCall as follws:
$hdl = DllCall($drv,"int","ldv_open","str","
.\LegacyMIP12","int_ptr","LdiUSB_000-004")
The script crashes, it seems it depends at characters
.\
That worked in older versions. I have created the script two years ago without problems. Now would add some functions and have seen this problem.
I'm using Autoit V3.3.0.0 under Vista Sp1 x86
I attach you the dll which I'm using.
Thanks and BR Helmut
Attachments (1)
Change History (5)
by , 17 years ago
| Attachment: | ldv32_xx.dll added |
|---|
comment:2 by , 17 years ago
Should the line read?
$hdl = DllCall($drv,"int","ldv_open","str","
.\LegacyMIP12","int*",0)
The last parameter is described as:
Syntax: LDVCode ldv_open(LPCSTR id, short* handle) Element Description '''id:''' Identify the network interface to establish communication with by specifying its name as the id input parameter. For example, “x.Default.1MainStreet” could be used to identify an i.LON 10 that will be opened through xDriver. Or, “LON1” could be used to identify a PCLTA-10 or PCLTA-20 network interface. '''handle:''' This output parameter will contain a pointer to a short integer that you will use to identify the network interface with the other OpenLDV functions. This handle is only valid if the function returns LDV_OK.
follow-up: 4 comment:3 by , 17 years ago
Hi,
now works different from older versions, but works.
when I use:
$hdl = DllCall($drv,"short","ldv_open","str","
.\LegacyMIP12","short*","LdiUSB_000-004")
can open the driver to the device, send and receive messages.
It,s not the original openLDV, it's the one for LOYTEC devices.
BR Helmut
comment:4 by , 17 years ago
| Resolution: | → No Bug |
|---|---|
| Status: | new → closed |
Replying to helmut.hiller@…:
now works different from older versions, but works.
Gee, I wonder if reading the changelog and in particular the script-breaking changes portion would tell you that?

DLL for LonWorks driver