Well, I found a temporary solution. installing 32-bit Oracle libraries
didn't fix the problem, so I simply commented out the $linklib entry in
the culprit file. I didn't have any of the other files it listed anyway!
Gareth aka. Kit
On 25/11/2020 17:51, J. Gareth Moreton via fpc-devel wrote:
Am 25.11.2020 um 15:44 schrieb Tomas Hajny via fpc-devel:
On 2020-11-25 14:40, Sven Barth via fpc-devel wrote:
Tomas Hajny via fpc-devel schrieb am
Mi.,
25. Nov. 2020, 13:31:
On 2020-11-25 10:31, Nikolai Zhubr via fpc-devel wrote:
> 25.11.2020 1:52, Tomas Hajny via fpc-devel:
.
.
How
On Wed, Nov 25, 2020 at 1:31 PM Tomas Hajny via fpc-devel
wrote:
> I get the following result (regardless from the registry setting):
>
> dwMode = 3
> SCM: 87
> FALSE
C:\Users\Bart\LazarusProjecten\ConsoleProjecten>test
dwMode = 3
TRUE
Microsoft Windows [Version 10.0.19041.630]
--
Bart
Sure thing - I'll give that a try.
Looks like this is my first true experience with DLL Hell!
Gareth aka. Kit
On 25/11/2020 17:13, Marco van de Voort via fpc-devel wrote:
Op 2020-11-25 om 18:10 schreef J. Gareth Moreton via fpc-devel:
That's the only useful stuff I found. Sorry to sound
Op 2020-11-25 om 18:10 schreef J. Gareth Moreton via fpc-devel:
That's the only useful stuff I found. Sorry to sound like such a
novice. I have never come across this error before and am not sure
how to resolve it without breaking something critical.
Easiest: do an install of the
Damn - I never thought to fully confirm that.
So what I've found so far - there's a copy in the following directories:
-
C:\Windows\System32\DriverStore\FileRepository\xtucomponent.inf_amd64_614515f4e6eb21a1
- C:\Windows\SysWOW64
Both seem to be identical, unless one is a simple mirror of
On 2020-11-25 14:40, Sven Barth via fpc-devel wrote:
Tomas Hajny via fpc-devel schrieb am
Mi.,
25. Nov. 2020, 13:31:
On 2020-11-25 10:31, Nikolai Zhubr via fpc-devel wrote:
> 25.11.2020 1:52, Tomas Hajny via fpc-devel:
.
.
How current is your Windows 10? VT100 support was added only two
Tomas Hajny via fpc-devel schrieb am Mi.,
25. Nov. 2020, 13:31:
> On 2020-11-25 10:31, Nikolai Zhubr via fpc-devel wrote:
> > 25.11.2020 1:52, Tomas Hajny via fpc-devel:
>
>
>
>
> Hi Nikolai,
>
> >> No problem, thanks for testing. Unfortunately, it doesn't work for me
> >> under Windows (Win 10
On 2020-11-25 09:51, J. Gareth Moreton via fpc-devel wrote:
Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
while C:\Windows\System is 64-bit. Question is, what can I do to
resolve it? I'm not even sure what Common.dll is for.
Well, I don't think that it works this way
On 2020-11-25 10:31, Nikolai Zhubr via fpc-devel wrote:
25.11.2020 1:52, Tomas Hajny via fpc-devel:
Hi Nikolai,
No problem, thanks for testing. Unfortunately, it doesn't work for me
under Windows (Win 10 Pro 64-bit) either with the original version or
Have you also checked with this
J. Gareth Moreton via fpc-devel schrieb am
Mi., 25. Nov. 2020, 09:51:
> Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
> while C:\Windows\System is 64-bit. Question is, what can I do to
> resolve it? I'm not even sure what Common.dll is for.
>
Wrong.
System32 -> Host
Hi!
25.11.2020 1:52, Tomas Hajny via fpc-devel:
On 2020-11-24 19:17, J. Gareth Moreton via fpc-devel wrote:
Sorry for being a bit slow - I've been doing my own work on x86. I
gave your patch (and new file) a test run on x86_64-win64, and that
seems to work fine. At least the warning messages
Aah, typical! C:\Windows\System32 is supposed to be for 32-bit DLLs,
while C:\Windows\System is 64-bit. Question is, what can I do to
resolve it? I'm not even sure what Common.dll is for.
Gareth aka. Kit
On 25/11/2020 07:27, Marco van de Voort via fpc-devel wrote:
Op 2020-11-25 om 00:37
13 matches
Mail list logo
