From sasdxk@unx.sas.com Wed Nov 17 11:38:25 1993 Received: from lamb.sas.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP id AA27937; Wed, 17 Nov 1993 16:38:53 -0500 Received: from mozart by lamb.sas.com (5.65c/SAS/Gateway/10-28-91) id AA09985; Wed, 17 Nov 1993 16:38:52 -0500 Received: from skyhawk.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA14688; Wed, 17 Nov 1993 16:38:26 -0500 Received: by skyhawk.unx.sas.com (5.65c/SAS/Generic 9.01/3-26-93) id AA27228; Wed, 17 Nov 1993 16:38:25 -0500 From: Dave Kolb Message-Id: <199311172138.AA27228@skyhawk.unx.sas.com> Subject: segment boundaries To: winsock-users@sunsite.unc.edu Date: Wed, 17 Nov 1993 16:38:25 -0500 (EST) X-Mailer: ELM [version 2.4 PL20] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 575 Does the w16 winsock specification for send and recv dictate that the buffer ptr and length arguments do not cross a segment boundary? I.E. Is it up to the app to make sure that the offset and length never exceed 64K or does the winsock.dll handle this? Thanks, -- Dave Kolb Opinions are mine not SAS' SAS Institute, Inc. EMAIL: sasdxk@unx.sas.com SAS Campus Drive - R4306 Phone: (919) 677-8000 x6827 Cary, NC 27513-2414 USA FAX: (919) 677-8123 Compuserve: 72410,407@compuserve.com From jas@hostel.lincroftnj.ncr.com Thu Nov 18 03:03:00 1993 Received: from hostel.lincroftnj.ncr.com (h153-68-185-39.NCR.COM) by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP id AA01776; Thu, 18 Nov 1993 08:03:28 -0500 Date: Thu, 18 Nov 93 08:03 EST Message-Id: <9311180803.AA04048@hostel.lincroftnj.ncr.com> From: jas@hostel.lincroftnj.ncr.com To: winsock-users@sunsite.unc.edu Subject: DOS based version of Win Sock API? Content-Length: 297 Content-Type: text Is their a dos version of the Win Sock api available? I am trying to port UNIX based sockets code to windows using win sockets v 1.1 from Microsoft. I'm also interested in doing a similar port to DOS. Jim Shelton jas@hostel.att.com jashelton@attmail.att.com james.shelton@lincroftNJ.ncr.com From sokolsky@avalle.insoft.com Thu Nov 18 15:19:47 1993 Received: from netcomsv.netcom.com (uucp5.netcom.com) by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP id AA13474; Thu, 18 Nov 1993 10:30:16 -0500 Received: from localhost by netcomsv.netcom.com with UUCP (8.6.4/SMI-4.1) id HAA11206; Thu, 18 Nov 1993 07:30:12 -0800 Received: from avalle.insoft.com by insoft1.insoft.com (4.1/RHP-1.0) id AA00819; Thu, 18 Nov 93 10:03:18 EST Received: by avalle.insoft.com (5.0/SMI-SVR4) id AA04433; Thu, 18 Nov 1993 10:19:47 +0500 Date: Thu, 18 Nov 1993 10:19:47 +0500 From: sokolsky@avalle.insoft.com (Alexander V. Sokolsky) Message-Id: <9311181519.AA04433@avalle.insoft.com> To: sasdxk@unx.sas.com Cc: winsock-users@sunsite.unc.edu Subject: segment boundaries Content-Length: 1005 >>>>> Dave Kolb writes: > Does the w16 winsock specification for send and recv dictate that the > buffer ptr and length arguments do not cross a segment boundary? > I.E. Is it up to the app to make sure that the offset and length never > exceed 64K or does the winsock.dll handle this? My experience shows that at least some stacks (e.g. PC NFS) can't handle buffers crossing segment boundary. // // adjust the number of bytes to send/recv not to get into another segment // static int __near makeHugeAdjustment(HPSTR buf, int bufsiz) { WORD offset = OFFSETOF((DWORD)buf); if((LONG)offset + (LONG)bufsiz > (LONG)UINT_MAX + 1L) { bufsiz = (int)((WORD)UINT_MAX + 1L - offset); } return bufsiz; } Hope this helps -- Alexander (Sasha) Sokolsky phone: 717-730-9501 (day) Insoft, Inc 717-796-9642 (ev) Executive Park West 1 fax: 717-730-9504 Suite 307 sokolsky@insoft.com 4718 Old Gettysburg Rd. Mechanicsburg, PA 17055 From 100121.373@compuserve.com Fri Nov 22 01:38:20 1993 Received: from dub-img-1.compuserve.com by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.06) with SMTP id AA23911; Mon, 22 Nov 1993 06:41:12 -0500 Received: from localhost by dub-img-1.compuserve.com (8.6.4/5.930129sam) id GAA20483; Mon, 22 Nov 1993 06:41:11 -0500 Date: 22 Nov 93 06:38:20 EST From: Franck LEFEVRE <100121.373@compuserve.com> To: "INTERNET:winsock-hackers" Cc: "INTERNET:winsock-users@s" , "INTERNET:winsock@sunsite" Subject: WSDIR932 Message-Id: <931122113820_100121.373_BHJ47-1@CompuServe.COM> WSDIR the WinSock directory The WSDIR932 of November 17th, 1993 is now available. The first goal of WSDIR is to provide a regularly-updated directory of WinSock applications, implementations and development tools. It contains only, and will always only contain, data sheets that have been directly filled by poeple responsible for the product submitted. There are 3 official ways to get a copy of WSDIR : 1) K1's BBS (France) (33) 33.39.22.13 Files Area : TCP/IP 2) CompuServe Forum : MSNETWORKS 3) Anonymous FTP to ftp.demon.co.uk:/pub/ibmpc/winsock (thanks, Steve) Franck LEFEVRE K1 Informatique 100121.373@compuserve.com From ICH211@ZAM001.ZAM.KFA-JUELICH.DE Fri Nov 26 11:01:32 1993 Received: from ZAM001.ZAM.KFA-JUELICH.DE by SunSITE.unc.edu (SMI4.1/FvK 1.02) id AA05545; Fri, 26 Nov 93 11:01:32 EST Message-Id: <9311261601.AA05545@SunSITE.unc.edu> Received: from DJUKFA11 by ZAM001.ZAM.KFA-JUELICH.DE (IBM VM SMTP V2R2) with BSMTP id 8506; Fri, 26 Nov 93 17:00:35 +0100 Date: Fri, 26 Nov 93 16:56:40 +0100 From: Thomas Heil Organization: Forschungszentrum Juelich GmbH - Institut fuer Chemie 2 Subject: Announcing WLPRSPL 3.1, a WinSock based LPR print spooler To: winsock@sunsite.unc.edu, winsock-users@sunsite.unc.edu, FTP Software User's Group mailing list , Microsoft Windows Version 3 Forum , TCP/IP Protocol Implementations for PC Discussion Hello folks! I have finished a new version of my WinSock based LPR print spooler named WLPRSPL 3.1. Announcement text follows. Please note that ftp.cica.indiana.edu is closed for uploads until Tuesday, Nov. 30. >From then on you'll be able to get it from there. And the /uploads directory on sunsite.unc.edu cannot be listed with "dir", but if you cd to it, say "bin", and then "get wlprsp31.zip" you'll get it. /Thomas ---------------------------------------+-------------------------------------- Mail: Thomas Heil | EMail: BITNET: ICH211@DJUKFA11.BITNET Forschungszentrum Juelich - ICG2 | Internet: th.heil@kfa-juelich.de 52425 Juelich | Phone: +49 2461 61-6915 Germany | Fax: +49 2461 61-5346 ========================= Announcement follows ========================= WLPRSPL 3.1, a Windows Sockets 1.1 based print spooler for transparent printing to LPD print servers from Windows Applications WLPRSPL 3.1 allows you to print transparently from any Windows application to any remote printer that can be reached over a TCP/IP network and that is driven by an LPD (RFC1179) server (typically some UNIX host). Requirements: o Microsoft Windows 3.1 o Networking software that offers a Windows Sockets 1.1 DLL Changes since release 3.0: o Added the capability of viewing spool jobs that still are in a WLPRSPL local queue in more detail, and to selectively purge them. o Added the ability to suspend the spooler completely in addition to disabling individual queues by a menu option or hot key. o Now every time a local spool file is enqueued or dequeued, the queue state file WLPRSPL.SPL is written to the spool directory, instead of being written when the spooler is ended. This ensures that spool files are not lost even if Windows or the spooler dies. o Fixed a problem with the queue listbox. o Included is WLPR.DLL 1.1, which now does CRLF->LF translation for certain file types and which is more robust and configurable for certain TCP/IP stacks (I hope). For details see included documentation for this DLL. o Also included is WSOCKAID.DLL along with its documentation. This DLL now supports TCP/IP stacks that have a real Windows network driver offering the WNetGetUser function. Availability: The ZIP archive containing the packages is WLPRSP31.ZIP. The software was uploaded to the following Anonymous FTP sites: o sunsite.unc.edu in /uploads Final destination directory: /pub/micro/pc-stuff/ms-windows/winsock/apps o ftp.cica.indiana.edu in /pub/pc/win3/uploads Final destination directory: /pub/pc/win3/util or /pub/pc/win3/winsock The ZIP file contains the program and necessary DLLs as well as documentation in form of an MS Word for Windows 2.0 file and a plain ASCII file. For installation and operating instructions please refer to this documentation. A PostScript version can be sent by mail on demand. The program is Shareware.