[Freedos-devel] IDE-type code editor
Is there a particular code editor (ideally, with IDE-type features like: being able to bind the maker/compiler to a keystroke, capturing of compiler errors into a separate window, etc.) that people here are using to work on the packages they maintain? Given that there are some really nice features that we have available nowadays (like CVS/SVN) which probably aren't available in a true DOS-based editor, is it a better idea to use a Windows editor/IDE and just instruct the compiler to build for DOS? What is everyone else using to develop/debug their DOS apps here? - Joe smime.p7s Description: S/MIME Cryptographic Signature -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] IDE-type code editor
FreeDOS Edlin! (Actually, I use the joe editor under Cygwin to do a lot of my programming, and then make sure it compiles under MSVC 6.0 and OpenWatcom with a DOS target before sending it out.) Gregory Pietsch Joe Emenaker wrote: Is there a particular code editor (ideally, with IDE-type features like: being able to bind the maker/compiler to a keystroke, capturing of compiler errors into a separate window, etc.) that people here are using to work on the packages they maintain? Given that there are some really nice features that we have available nowadays (like CVS/SVN) which probably aren't available in a true DOS-based editor, is it a better idea to use a Windows editor/IDE and just instruct the compiler to build for DOS? What is everyone else using to develop/debug their DOS apps here? - Joe -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] IDE-type code editor
On Thu, 5 Nov 2009, Gregory Pietsch wrote: FreeDOS Edlin! (Actually, I use the joe editor under Cygwin to do a lot of my programming, and then make sure it compiles under MSVC 6.0 and OpenWatcom with a DOS target before sending it out.) xDDD; Gregory Pietsch Joe Emenaker wrote: Is there a particular code editor (ideally, with IDE-type features like: being able to bind the maker/compiler to a keystroke, capturing of compiler errors into a separate window, etc.) that people here are using to work on the packages they maintain? Given that there are some really nice features that we have available nowadays (like CVS/SVN) which probably aren't available in a true DOS-based editor, is it a better idea to use a Windows editor/IDE and just instruct the compiler to build for DOS? What is everyone else using to develop/debug their DOS apps here? - Joe For the record, I use gedit for most stuff, but then go into DOS and do the compilation with a DOS compiler. -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] IDE-type code editor
Joe Emenaker wrote: Is there a particular code editor (ideally, with IDE-type features like: being able to bind the maker/compiler to a keystroke, capturing of compiler errors into a separate window, etc.) that people here are using to work on the packages they maintain? Try http://www.bttr-software.de/forum/board_entry.php?id=5355 or http://www.bttr-software.de/products/fed/. What is everyone else using to develop/debug their DOS apps here? Notepad2 on Windows plus some batch files. Robert Riebisch -- BTTR Software http://www.bttr-software.de/ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
Re: [Freedos-devel] Fw: Re: About my driver, HIMEM/EMM386 and interrupts
but then virtual-86 mode is set and I can no loger use 32bit real-mode pointers! IF you need PM from V86 there is VCPI. Protected mode isn't the same as flat real mode. NO, but there is no absolute need to use flat [un]real mode. flat-real mode, VCPI and DPMI work and how they deal with other previously loaded systems to avoid collisions? DPMI is not very relevant for real mode drivers. The important quetions are: - Do we have a 32-bit CPU ? - Real or V86 mode ? - Do we have an XMS host, version 2 or 3 ? - If V86, do we have VCPI at least (if not, we are most likely inside NTVDM) ? mentioned if you want PM, you have VCPI, I think, meaning if I wanted to access PM memory. NO. You need VCPI if you want to run your own PM code but find yourself in V86. The XMS host as well as BIOS or EMM386 will temporarily switch to PM or unreal for you when memcopying for you. Only I wish I knew more about VCPI. Google for VCPI.DOC or VCPI.ZIP or VCPI spec or so. FYI: VCPI is the award winning standard from 1988 :-D FYII: forget or postpone VCPI, get your driver working using XMS and INT $15 first. it will probably be enough to just rely on XMS functions for now. Exactly. One doubt I have about XMS functions is this: the XMM specification states that if I lock some memory, I must unlock it as soon as possible. How soon is that? Just before unhogging it should be fine. would be important to keep it locked for as long as the driver is running Do it, hog and lock your XMS at driver start, and unlock and unhog just before driver removal. Can I keep memory locked like for the whole time one process is running (i.e.: half an hour)? Even 1 year :-D How bad is that? NOT at all. can read Assembly, you can also look at the source code of HIMEMX, JEMM and HDPMI. And FASM of course (hogging physical memory from BIOS or XMS host), beware that the unreal mode used by it is VERY special and unique. :-) -- ~~~ wow ~~~ -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
[Freedos-devel] WATCOM http://wiki.fdos.org/Main/OpenWatcom
What version of WATCOM is the most recommended one ? Almost 1 year elapsed since 1.8 release, there were some complaints by Japheth about JWASM doesn't compile with 1.8 anymore in the past, but latest releases report to compile fine with both 1.7a and 1.8, although nothing has been fixed in WATCOM since then. Author of MPXPLAY still uses 1.3 and warns about newer versions (possibly he didn't test anything after 1.6). How does 1.8 compare to 1.7a or 1.3 or other C compilers? Bugs, efficiency (optimization)? The features I might be interested are: - 16-bit code generation: COM, MZ, OBJ, FreeDOS kernel - 32-bit code generation: LE, PE, OBJ http://wiki.fdos.org/Main/OpenWatcom is desperately obsolete, anyone dares to update or delete this page ? Also 1.8 reportedly is able to compile itself on DOS again, anyone can confirm this ? Any info around (what to download, how to start) ? http://groups.google.com/group/openwatcom.contributors/browse_thread/thread/cbd0a556f8623386 I'll eventually document all of the above somewhere when I get a chance. http://japheth.de/Download/jwlink_090910.zip JWLink (improved OW WLink v1.8) binary (Win32) Several enhancements, but not a single bugfix - is 1.8 WLINK really bugfree ? -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july ___ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
