Thread: Delphi 10 won't connect to an AD driver
 |
This question is answered.
Helpful answers available: 2.
Correct answers available: 1.
|
|
Replies:
2
-
Last Post:
Mar 21, 2018 11:37 PM
Last Post By: Flemming Barlach
|
Threads:
[
Previous
|
Next
]
|
|
Posts:
2
Registered:
1/18/18
|
|
|
Hi there,
I have developed an app that controls external hardware which are two AD converters from Data Translation
(DT9837). I have Delphi 7 and Delphi 10 Tokyo installed on my PC. The code from D7 executes without any
problems, but exactly the same D10 code keeps getting the same error: 'Can not open driver'. The external
hardware cannot be initialized. The operating system is Win10.
Does anyone have an idea as to why exactly the same app compiled on D7 and D10 Tokyo behave so differently?
I am out of ideas, so is there a fix out there?
Best Regards
Flemming Barlach
|
|
|
Posts:
1,227
Registered:
12/16/99
|
|
Flemming Barlach wrote:
Hi there,
I have developed an app that controls external hardware which are two
AD converters from Data Translation (DT9837). I have Delphi 7 and
Delphi 10 Tokyo installed on my PC. The code from D7 executes without
any problems, but exactly the same D10 code keeps getting the same
error: 'Can not open driver'. The external hardware cannot be
initialized. The operating system is Win10.
Does anyone have an idea as to why exactly the same app compiled on
D7 and D10 Tokyo behave so differently? I am out of ideas, so is
there a fix out there?
Unless you are trying to compile to 64 bit in Tokyo I would suspect a
Unicode/Ansi issue with parameters you have to pass to the driver for
initialization.
--
Peter Below
TeamB |
|
|
|
|
Posts:
2
Registered:
1/18/18
|
|
Flemming Barlach wrote:
Hi there,
I have developed an app that controls external hardware which are two
AD converters from Data Translation (DT9837). I have Delphi 7 and
Delphi 10 Tokyo installed on my PC. The code from D7 executes without
any problems, but exactly the same D10 code keeps getting the same
error: 'Can not open driver'. The external hardware cannot be
initialized. The operating system is Win10.
Does anyone have an idea as to why exactly the same app compiled on
D7 and D10 Tokyo behave so differently? I am out of ideas, so is
there a fix out there?
Unless you are trying to compile to 64 bit in Tokyo I would suspect a
Unicode/Ansi issue with parameters you have to pass to the driver for
initialization.
--
Peter Below
TeamB
I take my hat off to you.
I had tried all of the string types available - except the AnsiString type.
When I used the AnsiString type for the name of the external board, the
driver said hello to me and the code now runs without further complaints.
Thanks Peter for showing me that there was light after all.
Flemming |
|
|
|
Legend
|
|
Helpful Answer
(5 pts)
|
|
Correct Answer
(10 pts)
|
|
Connect with Us