Xref: utzoo comp.sys.intel:1754 alt.lang.asm:77 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!uunet!munnari.oz.au!deakin.OZ.AU!rand!grs From: grs@cocam.oz.au (Gary Raymond Schmidt) Newsgroups: comp.sys.intel,alt.lang.asm Subject: Re: Need help in porting 8088/286 assembly code to 386. Message-ID: <329@rand.mel.cocam.oz.au> Date: 26 Jun 91 04:04:25 GMT References: <1991Jun21.161443.13880@kofax.uucp> <1991Jun24.160828.6047@ima.isc.com> Sender: usenet@rand.mel.cocam.oz.au Followup-To: comp.sys.intel Organization: Co-Cam Computer Group, Melbourne, OZ Lines: 24 In article peter@ficc.ferranti.com (Peter da Silva) writes: >In article <1991Jun24.160828.6047@ima.isc.com> suitti@ima.isc.com (Stephen Uitti) writes: >> In article <1991Jun21.161443.13880@kofax.uucp> jdm@kofax.uucp (James D. Murray) writes: [ ... much stuff deleted ... ] Minor point - if he's porting to a Unix box, the only model available to him is the _flat_ 32-bit model. If he modifies the segment registers on the '386, his code will crash with a resounding thud, taking the machine with it. The Operating System, being an O/S, not a glorified program loader such as MesSy-DOS, handles _all_ memory protection considerations. The safest, and easiest way to port to a '386 is to ignore the segments and treat it as a pure 32-bit machine, a la M68000, and re-code the assembler stuff from scratch, or better yet, re-write it in C. -- | Gary R. Schmidt || MHSnet: grs@cocam.oz.au | || or: grs%cocamrd@cocam.oz.au | Co-Cam Computer Group, || I sees it, but I don' believes it !! | Melbourne, OZ || VOX +61 3 412 3431 FAX +61 3 417 7857