Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!sdcsvax!ucbvax!JASPER.PALLADIAN.COM!dp From: dp@JASPER.PALLADIAN.COM.UUCP Newsgroups: comp.os.vms Subject: Re: C RTL [again?] Message-ID: <870607223853.3.DP@BANFF.PALLADIAN.COM> Date: Sun, 7-Jun-87 22:38:00 EDT Article-I.D.: BANFF.870607223853.3.DP Posted: Sun Jun 7 22:38:00 1987 Date-Received: Tue, 9-Jun-87 03:58:00 EDT References: <552@unc.cs.unc.edu> Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: Jeffrey Del Papa Distribution: world Organization: The ARPA Internet Lines: 34 Date: 7 Jun 87 15:05:45 GMT From: unc!mcguffey@mcnc.org (Michael McGuffey) In article <12308535119.47.AWALKER@RED.RUTGERS.EDU> AWalker@RED.RUTGERS.EDU (*Hobbit*) writes: >Did I miss it back whenever, or is there really a bug in VAXCRTL that silently >limits the size of a read() to 65535 bytes? I found this the hard way, while >------- I have recently been having trouble doing reads of around 1/2M at a time I got around it by reading in sections of 1K chunks. Since I only needed the program once, I didn't fine tune itto see the largest read I could perform. I like DEC equipment and software but it seems funny that they would claim in the VAX C ref manual that they want to maintain compatibility with unix c but have such a glaring bug. Does anybody have a patch or fix? --mike mcguffey@dopey.cs.unc.edu mcguffey@csnet this is a holdover from pdp-11 days. The controllers could only transfer 64kb, so the restriction carried to the next layer, since not all devices could be supported uniformly. (of course vms was originally envisioned as fitting into 64kb, and the original 11/780 memory controller would only support 1mb, with a 2 controller per system limit. It really was originally intended as a slightly bigger pdp-11, and vms was rsx-11a with some help from the hardware.) I cannot tell you what the business programming language in use in the year 2000 will look like, but it will be called COBOL. Programmers never bury their dead.