Thread View: comp.lang.pascal.borland
4 messages
4 total messages
Started by Robert AH Prins
Sat, 01 Sep 2001 20:47
TPL60N20 & BLP70N17, any interest in them?
Author: Robert AH Prins
Date: Sat, 01 Sep 2001 20:47
Date: Sat, 01 Sep 2001 20:47
77 lines
3814 bytes
3814 bytes
Hi all, From a private email: ... >I'm also still working on a 386+ only TURBO.TPL - I've increased the >granularity of the DOS unit by splitting most files into two "get"/"set" >parts, and in one case, TIME.ASM, into four parts, TIMEGDAT.ASM, >TIMESDAT.ASM, TIMEGTIM.ASM & TIMESTIM.ASM! I've also changed the code >for Intr/MsDos to the BP7 version, issuing a real interrupt, so that it >will work under windoze. I've also done some work on CRT, most notably >I've removed the Delay initialisation to Delay (it's done on the first >call (or a Delay(0)) so that Delay can be smartlinked out completely. >I've extracted Pedt S' code using TWU1, and I like his use of a detected >enhanced keyboard, but rather than his way of detecting it, I think I >will use one of the newer interrupts for it, Any comments on this remark? >given that the code will only run on at least a 386! > >I've also added a small amount of 386 code to OVERLAY and made some >minimal optimizations to it, but as yet I haven't split it up - which >should give some smartlink-savings, as I guess that some procedures in >it are used very infrequently! > >As for the SYSTEM unit itself, sofar I've modified and/or added 386 >instructions to 41 of the files and I've also decided to add the last of >BP7's files, appropriately named "LAST.ASM", which clears out the unused >portion of the datasegment. It's also very likely that I will (try to) >remove the re-entrancy problems in the original RTL FPU code and >heapmanager! ... Q1) How much interest would there be in such a unit, or a similar one for BP7? (TPL60N20 will be based on the TPL60N19 code by Norbert Juffa and a tiny bit of SYS60A code by Eagle Performance Software (aka Jim LeMay)) Q2) My disassemblies of TPC.EXE (TP 6.00 & TP 6.01) are complete and assemble, after some massaging to byte-4-byte equivalent versions (except for the relocation table). I'm ready to create a VER65 version, where BASM will be able to assemble a lot of 386(+) instructions. I could do the same for BP7's compilers, but except for the command line compiler this will be a lot harder. Would there be any interest in such a hacked compiler? BTW, I will create two versions of some (or all?) of the units, a normal one and a test/debug one that has NOPs before most and after some RTL routines, allowing you to patch in FAR JUMPS for user exits, like Andy Cooper's HeapChk routine (MEMORY.SWG, file 85) and my own MyWrite unit that intercepts the Longint write routine to emulate procedures/functions with a variable number of parameters. Regards, Robert -- Robert AH Prins prino@bigfoot.com PS: Does anyone know how I can get TLINK to remove the uninitialized datasegment from a linked file, it's included as lots of zeroes in my reassembled versions of TPC.EXE and I don't like them one bit!
Re: TPL60N20 & BLP70N17, any interest in them?
Author: Franck Pissotte
Date: Sun, 02 Sep 2001 18:46
Date: Sun, 02 Sep 2001 18:46
22 lines
2182 bytes
2182 bytes
Robert AH Prins a οΏ½crit : > From a private email: > Q2) My disassemblies of TPC.EXE (TP 6.00 & TP 6.01) are complete and > assemble, after some massaging to byte-4-byte equivalent versions > (except for the relocation table). I'm ready to create a VER65 > version, > where BASM will be able to assemble a lot of 386(+) instructions. I > could do the same for BP7's compilers, but except for the command line > compiler this will be a lot harder. Would there be any interest in > such a hacked compiler? interesting but i prefered D1 command line or BP7. there was a dissasembled version of TP6 and it dissapeared from web site without explication. i suspect you should get borland authaurization before distributing the source. -- http://www.pascaland.org/ compilateurs, sources et liens langage pascal, delphi http://franck.pissotte.free.fr/ mon vide grenier: vieux materiels, logiciels, livres et revues
Re: TPL60N20 & BLP70N17, any interest in them?
Author: Jason Burgon
Date: Mon, 03 Sep 2001 03:03
Date: Mon, 03 Sep 2001 03:03
53 lines
3444 bytes
3444 bytes
Robert AH Prins <prino@bigfoot.com> wrote in message news:ed6d5b69.0109011247.3fcfa670@posting.google.com... > Hi all, > > From a private email: > > ... > >> I'm also still working on a 386+ only TURBO.TPL - I've increased the >> granularity of the DOS unit by splitting most files into two >> "get"/"set">parts, and in one case, TIME.ASM, into four parts, TIMEGDAT.ASM, >> TIMESDAT.ASM, TIMEGTIM.ASM & TIMESTIM.ASM! I've also changed the >> codefor Intr/MsDos to the BP7 version, issuing a real interrupt, so that >> it will work under windoze. Take a look at my GDOS unit. This is a 386+, TP7/BP7 unit with many enhancements over the standard DOS unit, including: Better interrupt support Long file name support Much better DPMI support http://www.jayman.demon.co.uk/gv/download.htm > >I've also added a small amount of 386 code to OVERLAY and made some > >minimal optimizations to it, but as yet I haven't split it up - which > >should give some smartlink-savings, as I guess that some procedures > in it are used very infrequently! I would be most interested in a dissassembly of the Overlay unit, as I would like to allow it to use XMS instead of EMS, but Borland in their infinite wisdom did not include the source code for Overlay (or Graph) in their "Open Source" BP7 distribution. > Q1) How much interest would there be in such a unit, or a similar > one for BP7? I really see no point in doing a TP6 version, since this compiler was superceeded by TP7 and BP7 nearly 10 years ago. However, I would be most interested in a BP7 version. It must be able to handle DPMI properly though. > Q2) My disassemblies of TPC.EXE (TP 6.00 & TP 6.01) are complete and > assemble, after some massaging to byte-4-byte equivalent versions > (except for the relocation table). I'm ready to create a VER65 > version, where BASM will be able to assemble a lot of 386(+) instructions. I > could do the same for BP7's compilers, but except for the command line > compiler this will be a lot harder. Would there be any interest in > such a hacked compiler? I'd be very interested in a BPC.EXE (BP7 command line compiler) that was somewhat better at code optimizing. Some of the code generated by BP7 is pretty awful.
Re: TPL60N20 & BLP70N17, any interest in them?
Author: Pedt
Date: Mon, 03 Sep 2001 13:36
Date: Mon, 03 Sep 2001 13:36
26 lines
2259 bytes
2259 bytes
Jason Burgon <jason@jayman.demon.co.uk> said the following: >Robert AH Prins <prino@bigfoot.com> wrote in message >news:ed6d5b69.0109011247.3fcfa670@posting.google.com... >> Hi all, >> >> From a private email: >> >I've also added a small amount of 386 code to OVERLAY and made some >> >minimal optimizations to it, but as yet I haven't split it up - which >> >should give some smartlink-savings, as I guess that some procedures >> in it are used very infrequently! > >I would be most interested in a dissassembly of the Overlay unit, as I would >like to allow it to use XMS instead of EMS, but Borland in their infinite >wisdom did not include the source code for Overlay (or Graph) in their "Open >Source" BP7 distribution. > I know Robert's done a disassembly of the overlay unit but not sure if he's done XMS support. The XMS unit via <URL:http://www.pedt.demon.co.uk/usenet/xms.zip> has an OvrInitXMS procedure which functions like the OvrInitEMS procedure from Borland if that's any help to you. -- Pedt
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads