Newsgroups: comp.os.msdos.djgpp From: "Hoogenraad, dr. J.H." Subject: Re: 32bit memcpy function? Sender: news AT natlab DOT research DOT philips DOT com (USEnet Subsystem) Message-ID: <347927B4.7DAB@natlab.research.philips.com> Date: Mon, 24 Nov 1997 07:07:32 GMT Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii References: Mime-Version: 1.0 Organization: Philips Research Lines: 19 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk Eli Zaretskii wrote: > > On Sat, 22 Nov 1997 wolfman AT cedar DOT alberni DOT net wrote: > > > I was wondering if DJGPP has a 32bit memcpy function (memcpy uses > > 8bit right?) > > Wrong. `memcpy' in DJGPP uses 32-bit move instructions. Furthermore, The Pentium processor does its own optimisations: Even movsbs are done using 32 bit automatically, I read somewhere in the Intel docs (don't ask me where). So no more reason to try to redo things done in microcode. -- Jan Hoogenraad Philips Research Laboratories Building: WB 2-007 Prof. Holstlaan 4 (WB21) Phone: +31 40 2742074 5656 AA Eindhoven Fax: +31 40 2745002 The Netherlands E-mail: hoogenrd AT natlab DOT research DOT philips DOT com mode user >screen, but the text mode user screen instead. > (How is it supossed to debug a graphic module whitohut seeing what it >does?!! Maybe it's a useful exercise to improve abstract thinking, >uh?) > Anyway, if you knew why it happens, or knew how to solve it, please do >tell me about. > > >2) The thing is that if I try *ANY* SVGA graphic mode under a >WINDOWS 95's MSDOS window (even in whole screen mode) the system gets >hanged up (you know, a only-cold-reboot-solution crash). > It all happens just as I initgraph() with a SVGA mode (just like a >*simple* 640x480x256colors). I know the .exe is ok because it DOES >work in PLAIN MSDOS. > > Is this *normal*? I mean, is grx expected to be used only on plain >MSDOS or is there something wrong in my system configuration? > > > >Thanx in advance for reading this ugly-mess-idea text! > > >==> Diego Dominguez <== diegodc AT arrakis DOT es > > The second problem.... in my belief anyways... MUST be with the way certain "switches" are set while your WIN95 is running.... I've been building & running programs under win95 (that are DOS apps) for quite a while.... and something I installed recently has now jumped up and bit me HARD! When I goto run DOS apps... it's as though I'm not using my computer's MATH COPROCESSOR anymore.... I've checked the registry... and the inis.... damn! it stinks! As far as your FIRST problem.... I'm not sure BUT: - are you talking about completely separate runnings of your program? are you running it by going to the "DOS Shell" first? Perhaps you aren't freeing up your resources.... they should be freed whenever your program ends execution... but I've found it necessary to EXPLICITLY free the memory associated with look-up tables... etc... before exiting a program... Jim the loiterer http://members.aol.com/qball1723/index.htm (wannabe PC game/graphics developer)