Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-pascal / 2001-07

SSockets + NT + CRT

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Thomas Schatzl

Hi,

I was searching for some useful socket related source and found the ssockets unit in the fcl. My question about it is whether it is available / has been tested for the windows platform too.

Is there any unit common for all platforms supporting sockets to resolve host names for inet - type sockets ? These calls seem to be missing in the sockets units ? Which units do I have to use for which platforms to accomplish that ?

FPC programs still behave somewhat weird in a NT command shell when the crt unit is used. Text output always seems to start at line 0 of the virtual screen regardless of where the actual cursor was at program start and always seems to use a fixed screen buffer area (80x50 ??) regardless of actual window dimensions....
Are there any plans to fix this in the future ?
I thought I made some crt patches available which fixed all previous problems, what's their current state ?

I hope somebody can help,
Thomas

Thomas Schatzl

Hi,

I was searching for some useful socket related source and found the ssockets unit in the fcl. My question about it is whether it is available / has been tested for the windows platform too.

Is there any unit common for all platforms supporting sockets to resolve host names for inet - type sockets ? These calls seem to be missing in the sockets units ? Which units do I have to use for which platforms to accomplish that ?

FPC programs still behave somewhat weird in a NT command shell when the crt unit is used. Text output always seems to start at line 0 of the virtual screen regardless of where the actual cursor was at program start and always seems to use a fixed screen buffer area (80x50 ??) regardless of actual window dimensions....
Are there any plans to fix this in the future ?
I thought I made some crt patches available which fixed all previous problems, what's their current state ?

I hope somebody can help,
Thomas

Thomas Schatzl

Hi,

I was searching for some useful socket related source and found the ssockets unit in the fcl. My question about it is whether it is available / has been tested for the windows platform too.

Is there any unit common for all platforms supporting sockets to resolve host names for inet - type sockets ? These calls seem to be missing in the sockets units ? Which units do I have to use for which platforms to accomplish that ?

FPC programs still behave somewhat weird in a NT command shell when the crt unit is used. Text output always seems to start at line 0 of the virtual screen regardless of where the actual cursor was at program start and always seems to use a fixed screen buffer area (80x50 ??) regardless of actual window dimensions....
Are there any plans to fix this in the future ?
I thought I made some crt patches available which fixed all previous problems, what's their current state ?

I hope somebody can help,
Thomas

Unknown author
to Thomas Schatzl
Thomas Schatzl wrote 5 lines
Hi, I was searching for some useful socket related source and found the ssockets unit in the fcl. My question about it is whether it is available / has been tested for the windows platform too.

Not yet. The functions have not even been implemented for the windows platform. This should be done, but lack of time prevented me from doing this. It should not be to hard to do this.

Show quoted text 5 lines
Is there any unit common for all platforms supporting sockets to resolve host names for inet - type sockets ? These calls seem to be missing in the sockets units ? Which units do I have to use for which platforms to accomplish that ?

No.
The idea was that the inet unit should handle this for all platforms, but at the moment, I think these calls reside in the sockets unit for Windows. They should be removed and moved to the inet unit.

Show quoted text 6 lines
FPC programs still behave somewhat weird in a NT command shell when the crt unit is used. Text output always seems to start at line 0 of the virtual screen regardless of where the actual cursor was at program start and always seems to use a fixed screen buffer area (80x50 ??) regardless of actual window dimensions....

This is a known problem.

Are there any plans to fix this in the future ?

If you have a fix, we'll be glad to apply it.

I thought I made some crt patches available which fixed all previous problems, what's their current state ?

:/ I don't know about that. Florian or Peter look after the crt unit on windows, I think...

Michael.

Peter Vreman
to Unknown author
> Are there any plans to fix this in the future ? If you have a fix, we'll be glad to apply it.

I tried to download it, but it was already gone. Please attach the patch in an email to me, then i can try to apply it in the 1.1 branch

Show quoted text 5 lines
> I thought I made some crt patches available which fixed all previous > problems, what's their current state ? :/ I don't know about that. Florian or Peter look after the crt unit on windows, I think...

I only fixed the 255x255 limit and a clreol bug.

Peter