It is currently Fri Jun 22, 2018 6:40 am

All times are UTC + 1 hour




Post new topic Reply to topic  [ 11 posts ] 
Author Message
 Post subject: Polink: fatal error: Es wurde versucht auf eine unzulässige
PostPosted: Tue Feb 20, 2018 6:20 pm 
Offline
New User
New User

Joined: Tue Feb 20, 2018 6:04 pm
Posts: 6
Hello,

sorry for my poor English, I normally write in the german section.
I am member of windows-insider-program on the slow ring.
That means I will get only the new Versions of Windows, which are quite stable.
I now installed Build 17074 from win10 prof 64bit
From now the PB-Compiler does not work any more. The error-code is:

Polink: fatal error: Es wurde versucht auf eine unzulässige Adresse zuzugreifen.

I tried severeal PB-sources, which were compiled previously without any problems.

For testing I installed PB 5.62 on a machine where Build 17025 i.e last FAll-Creators-Update is running.
The compiler works without problems.
Therefore I think it's clear that PB won't run on the upcoming release of win 10 in March or April
I reported that Problem to MS but I don't think, they'll take care.
Have you already heard about that error ??


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Tue Feb 20, 2018 10:55 pm 
Offline
User
User

Joined: Mon Apr 10, 2017 6:17 pm
Posts: 94
Location: Germany
Did you try if it works with a manually updated POLINK? That might fix it.

Klappt es wenn Du die POLINK version manuell updatest?

Check viewtopic.php?f=13&t=70191


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 8:52 am 
Offline
New User
New User

Joined: Tue Feb 20, 2018 6:04 pm
Posts: 6
Bitblazer wrote:
Did you try if it works with a manually updated POLINK? That might fix it.

Klappt es wenn Du die POLINK version manuell updatest?

Check viewtopic.php?f=13&t=70191


I'm sorry. I don't Know, how to update polink manually. After running into the fault, i updated the whole PB
from 5.51 to 5.62, but the result was the same.

I found polink.exe in the compilers path of the PB-Installation. But what to do with it ?

Edit:
I looked for details of the polink version: it is 5.0.1.0 from 04.02.2018 10:39


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 11:00 am 
Offline
User
User

Joined: Mon Apr 10, 2017 6:17 pm
Posts: 94
Location: Germany
I have 5.62 beta myself and the same polink 5.00.1 but that was released 2008 and works fine with my win7 x64. The current version of POLINK seems to be version 8 here - so i would try to install the latest version and see if it that fixes your win10 problem. If it does, you could report it here and request a POLINK update for PB 5.62 final :)


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 11:15 am 
Offline
Always Here
Always Here

Joined: Fri Oct 23, 2009 2:33 am
Posts: 5774
Location: Wales, UK
Well, it could be as simple as your Anti-Virus interrupting Polink, especially if it been recently updated. This is a common issue, AV sees app development as being suspicious.

_________________
IdeasVacuum
If it sounds simple, you have not grasped the complexity.


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 1:03 pm 
Offline
New User
New User

Joined: Tue Feb 20, 2018 6:04 pm
Posts: 6
IdeasVacuum wrote:
Well, it could be as simple as your Anti-Virus interrupting Polink, especially if it been recently updated. This is a common issue, AV sees app development as being suspicious.


That's definitely not the reason.
1. I said the antivir pb-paths to be an exception
2. I tried tor run while having antivir off-line.


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 1:05 pm 
Offline
New User
New User

Joined: Tue Feb 20, 2018 6:04 pm
Posts: 6
Bitblazer wrote:
I have 5.62 beta myself and the same polink 5.00.1 but that was released 2008 and works fine with my win7 x64. The current version of POLINK seems to be version 8 here - so i would try to install the latest version and see if it that fixes your win10 problem. If it does, you could report it here and request a POLINK update for PB 5.62 final :)


Another user in the german Forum tried pelle's c8 version. He said; problem not solved.
I downloaded Version 8 through your link and i'll give it a try

Edit: I tried it for my own, but I don't know how to bind it to PB.
Only copying polink.exe, porc.exe porc.dll and polib.exe to the Compiler-path of
PB does not work. There are several other faults which polink reports.


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 9:43 pm 
Offline
User
User

Joined: Mon Apr 10, 2017 6:17 pm
Posts: 94
Location: Germany
Diogenes wrote:
I tried it for my own, but I don't know how to bind it to PB.
Only copying polink.exe, porc.exe porc.dll and polib.exe to the Compiler-path of
PB does not work. There are several other faults which polink reports.


I would proceed with one of the two following solutions to get more informations about the problem:

Use Rohitab's API-Monitor to trace what happens. It is one of the most important universal tools for windows to understand problems.

API Monitor

You have another universal tool in your hands. Replace polink.exe with your personal compiled PureBasic program and use it to dump any passed program parameters before passing them to a renamed "polink_.exe".

After you did that and probably fixed the problem - the "many other" polink errors might point you to another problem and its solution. This might be a polink problem, a purebasic problem of using polink or (most likely) a change of the upcoming windows 10 security policies to make windows 10 more "safe" (more of a consumer system which instead of a homebrew development platform - remember that homebrew also includes the ability to create malicious software and worst of all - free software ;)
Might be their next step to a "locked up" consumer system.


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Wed Feb 21, 2018 10:43 pm 
Offline
New User
New User

Joined: Tue Feb 20, 2018 6:04 pm
Posts: 6
Sorry Bitblazer,

those things I can't do. I'm only a Hobby-Coder. I hope the developpers of PB will fix that error,
when the next win-update will be rolled out and all PB-Users will have that Problem.


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Mon Feb 26, 2018 10:19 am 
Offline
Addict
Addict

Joined: Mon Feb 16, 2015 2:49 pm
Posts: 1423
Diogenes wrote:
I hope the developpers of PB will fix that error

It's not a PureBasic problem, and not a confirmed bug. Disable your AV totally and try again, or try when your PC is booted in Safe Mode. It'll work.


Top
 Profile  
Reply with quote  
 Post subject: Re: Polink: fatal error: Es wurde versucht auf eine unzuläss
PostPosted: Mon Feb 26, 2018 10:39 am 
Offline
New User
New User

Joined: Tue Feb 20, 2018 6:04 pm
Posts: 6
Dude wrote:
Diogenes wrote:
I hope the developpers of PB will fix that error

It's not a PureBasic problem, and not a confirmed bug. Disable your AV totally and try again, or try when your PC is booted in Safe Mode. It'll work.


even with av disabled the error occurs; I wrote that previously.
It's not yet a confirmed bug, but it will be in March or April. I wrote, that in win10 Build 17025 it's all ok !!
Since Build 17074 the error occurs. In March or April the spring-update of windows ,then
probably Build 17101, will be rolled out to public.
And probably then the error will happen to all pb-Users.
In german forum, one User who has installed Build 17101 already says that the error is yet there.
Another user from french forum has the same problem. He opened a new thread in this board
I returned on this PC to Build 17025 and the compiler runs well even with av running, as i whitelisted the pb-paths.
As I go again further to 17074 the error occurs again (with or without av: the error occurs).
Now I returned again to Build 17025 and there is no problem.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 11 posts ] 

All times are UTC + 1 hour


Who is online

Users browsing this forum: No registered users and 4 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  

 


Powered by phpBB © 2008 phpBB Group
subSilver+ theme by Canver Software, sponsor Sanal Modifiye