TOPIC:

I installed CT 1.7 today and have the following observations:

1. Norton did not like the file syngutterchanges.ppu. (mad5011 risk). File was quarantined. Any comments?

2. I opened an existing project and could not view the forms. The lfm file was there but pressing the unit/form toggle button did nothing. Any solution?

3. 64 version installed ok despite 1. above. Could not install 32 version with bigIDE.

In any case, thank you for your work.

Can you give us more info Sir

What additional info do you require?

1. from Norton: The file c:\lazarus\components\synedit\units\i386-win32
is reported as infected with risk Mad.5011.

2. Project has 2 pas units and 2 forms. I can see the lfm files in the source editor but pressing the button unit-form toggle does nothing while lfm file tab is on top.

3. I can run later the build 32 with bigIDE and send you the log...

Again, I have used CodeTyphon 1.6 and this is a great piece of work. thanks for your support.

Same problem here.
c:\lazarus\components\synedit\units\i386-win32\syngutterchanges.ppu is infected with mad.5011 virus.
Reported by:
Symantec Endpoint Protection 11.0.5002.333
Virus definitions 22. mai 2011 r2

/Elfrom

I ran the 32bit build bigIDE. It fails because file syngutterchanges.ppu is not found. Not surprising. It has been quarantined by Norton.

forgot to add the name of the file above in my second posting. the sentence should have read:
The file syngutterchanges.ppu in c:\lazarus\components\synedit\units\i386-win32 is reported as infected with risk Mad.5011.

Let me know if you need any additional information.

I think all these are "False alarm" from Antivirus Software
CodeTyphon Build from source all *.ppu files...
But, I will check this

Hi

The Change Log 1.7 says "Port pl_Indy to WinCE".
Use Indy in project WinCE / arm does not causes any compile or linking errors, but when you run the application on the mobile device shows the error: "Error on call to Winsock2 library function WSAStartup. I think the problem is related to defective compilation of library Indy for WinCE / arm by not spelling out the symbol "UNDER_CE. The result is a reference to the non-specific to WinCE ws2.dll

DUDUS

Thanks. Any ideas regarding point 2?

Hi,

Any news on this issue? I got the same error message.

Can you verify if there are any changes done to the given file from 1.60 to 1.70?
Going back to 1.60 and the problem is gone.

Error message on file in Symantec Endpoint Protection

Regards,

Bjørn

hi

After many hardships, I found a solution to the problem of compiling Indy for WinCe-arm

1. The source files:
IdGlobal.pas
IdGlobalProtocols.pas
IdStackWindows.pas
IdWinsock2.pas
Everywhere where there is a projection onto PWideChar Yoy have to use addition UTF8Decode function. For example:
IdGlobal.pas
OutputDebugString(PWideChar(WsAText))
need to replace the
OutputDebugString(PWideChar(UTF8Decode(WsAText)))

2. In the file IdStackWindows.pas you need to modify functions:
HostByAddress
HostByName
In both functions You need to force entry to the block executed past instruction:
if not then GIdIpv6FuncsAvailable
begin
...
end
Of course, you must also define a variable
LHost: PHostEnt

These changes can be implemented only for compiling wince-arm.

For me everything compiles and runs correctly on the device.

DUDUS

Regarding the report from Symantec/Norton - this looks like a false positive.

The file in question (syngutterchanges.ppu) is a generated file from bulding the Lazarus IDE (Synedit is the actual code editor) - i.e. it's compiled by FPC as part of the process of making Lazarus and so doesn't come directly from CodeTyphon.

It's mentioned here;

lists.lazarus.freepascal.org/pipermail/l...11-April/062444.html

In theory, if you installed Lazarus manually (i.e. didn't use CodeTyphon to do this) the FPC compiler will generate the same compiled code for syngutterchanges.pp and you'd still be in the same boat. They suggest suspending your AV until after Lazarus has been built although I guess you'll need to do that every time you install new components beacuse that will require a rebuild of the IDE.

Avast doesn't report an issue with this file and I've rebuilt the IDE in 1.70 about 20 times in the last few days. Have you tried updating the Symantec engine/definitions to see if that makes it stop complaining.

Can't suspend Symantec AV (Office PC) + updating Symantec didn't resolved this "Mad 5011" issue.
=> Back to CodeTyphon 1.60...

woma1 wrote: hi

After many hardships, I found a solution to the problem of compiling Indy for WinCe-arm

1. The source files:
IdGlobal.pas
IdGlobalProtocols.pas
IdStackWindows.pas
IdWinsock2.pas
Everywhere where there is a projection onto PWideChar Yoy have to use addition UTF8Decode function. For example:
IdGlobal.pas
OutputDebugString(PWideChar(WsAText))
need to replace the
OutputDebugString(PWideChar(UTF8Decode(WsAText)))

2. In the file IdStackWindows.pas you need to modify functions:
HostByAddress
HostByName
In both functions You need to force entry to the block executed past instruction:
if not then GIdIpv6FuncsAvailable
begin
...
end
Of course, you must also define a variable
LHost: PHostEnt

These changes can be implemented only for compiling wince-arm.

For me everything compiles and runs correctly on the device.

DUDUS

Thanks Sir,
can you post the fixed units in a zip file?

Of course.

I'm glad I could help.

Attached changed source files.

DUDUS.

Thanks Sir
We will test your MODs
if all OK, we will put this to next release...