Date: Wed, 1 Jul 1998 09:11:32 +0200 (MET DST) From: Federico Spinazzi To: Vic cc: djgpp AT delorie DOT com Subject: Re: NT compat (also Linux) In-Reply-To: <35994204.56A9@cam.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Precedence: bulk On Tue, 30 Jun 1998, Vic wrote: > I'm sorry if this question's in the FAQ. I know it's been asked a > hundred times before. I never bothered before :) > Now I want to get a new PC, a PII, and win 98 won't cut it anymore. So > I'll install NT and Linux. > Can I still run DJGPP and the progs created by it under NT? > What about Linux? how compatible is DOSEMU? > I'm using quite often NT and DJGPP developement environement at a time. I' would like to point out a little of my experience with it: 0 - I basically work with C with djdev 2.01, FAT drive, gcc 2.7.2.1, NT Workstation 4.0, service pack 3; 1 - symify often doesn't work: i.e. the stack traceback always being converted to nothing; 2 - memory allocation bugs are virtually impossible to catch (may be due to the different behaviour of the DPMI service provided by NT ? well, different from CWSDPMI ) 3 - SIGFPE (C) signals cannot be catched (well, I'm not able to catch them) by the program but are catched by the OS that calls Dr. Watson ..., well, I guess that is the sequence of events; when I say 'catch' I refer to the installation of a signal handler (I'm famous for bad code sent on this mailing list (there is a reason for that, other than my great distraction) so I don't try to explain that with an example) to handle it; 4 - often make, gcc, less, and so on crash (spelled right ?) with a SIGSEV signal; I've never tried to symify the traceback due to 1; 5 - profiling is virtually impossible (Eli's FAQs tell there is a patch for fixing it, but I've never searched it); 6 - Allegro works (or: NT works with Allegro): I've been able to see the demo and the examples but, as I don't have a VESA , a VESA what ? video, chipset, driver ? I don't know what VESA really should be...I'M SURE I HAVEN'T IT ; NT crashes (WOW !) if you try to switch from an allegro example or demo to, say, a WonderfulWord; here the crash is silent: you simply see nothing on the screen; 7 - RHIDE works fine using -M switch on the command line; somethimes it exit after stepping into a program and reaching the end ; sometimes rhgdb work debugging while rhide not (rhgdb -M too !) 8 - you often have said that from a windows box DOS programs cannot allocate more than 64Mb, right ?. I have seen djgpp programs using more than that memory (RAM + disk space): up to 130Mb, for example; go32-v2 always report 0Kb of swap space; how , for hell, go32-v2 sizes the memory avaiable ? (this last question doesn't match the main discussion at all). 9 - will follow a link to nt-lfn.com for long name support; I hope to find it; 10 - bye bye to you all. Thank you for you patience, work, suggestions, spirit and so on. federico