[Beowulf] Joe Blaylock's notes on running a MacOS cluster, Nov. 2007
Many of your questions may have already been answered in earlier discussions or in the FAQ. The search results page will indicate current discussions as well as past list serves, articles, and papers.
Peter St. John peter.st.john at gmail.comFri Nov 23 19:48:53 PST 2007
- Previous message: [Beowulf] Joe Blaylock's notes on running a MacOS cluster, Nov. 2007
- Next message: [Beowulf] Joe Blaylock's notes on running a MacOS cluster, Nov. 2007
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Well it was the 286 I meant; DOS 3.2 on the 286 stopped at 640K, I used ramdisk, no problem with SVr4. That's all. I'm not blaming M$ for everything. I'm sure DOS would have been hard to keep backward compatible, the unix didn't have to be, it was ported to the 286. DOS caught up later. Peter On 11/23/07, Mark Hahn <hahn at mcmaster.ca> wrote: > > > XP?) but used all 1.5 MB naturally with the unix (making it clear to > > me, btw, that the "640K RAM Barrier" was MS's fault, not Intel's). > > I'm the last to defend msft, but this 640k thing irks me. > > 640k is the physical hardware address of the graphics buffer; > IBM put it there. on the 8086/8088, there is no kind of memory > virtualization, so this is a hard limit on contiguous user memory. > the 286 is very, very different in memory model (16:16 segmentatation - > you don't want to know more about it unless you like pain) > so this location no longer matters to user-space. of course, code > assuming only the 8086/8088 model is still 640K-aware. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.scyld.com/pipermail/beowulf/attachments/20071123/c68eee10/attachment.html
- Previous message: [Beowulf] Joe Blaylock's notes on running a MacOS cluster, Nov. 2007
- Next message: [Beowulf] Joe Blaylock's notes on running a MacOS cluster, Nov. 2007
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Beowulf mailing list
