Anthony Williams

As a workaround you can probably do something like this: mem /c | find "ANSI" >NUL if errorlevel 1 goto loadansi Or you could use NNANSI, which is an unloadable TSR. Tom Almy's DOS page (look for NNANS593.ZIP, GPL w/ src)

Here are a few links to Pascal tutorials and related sites. Tao Yue's Basic Pascal tutorial Wikibooks' Pascal Programming Standard Pascal FAQ and Rules Modern Object Pascal FreePascal From Square One You may also wish to check some example programs included with FPC (e.g. fpctris and samegame).

Thank you again, Tomas, for all your years spent working on such a wonderful project. (FYI, I believe he is the OS/2 maintainer who also sometimes helps Go32v2/DOS target since it's unmaintained.) You can use LFNs in FreeDOS (e.g. DOSLFN), and it's not that problematic on FAT(12/16/32), esp. under VM. If you insist on being like Turbo Pascal exactly and thus "more" DOS compatible, just use freeware TP 5.5 (or one of many other Pascal compilers). For casual usage questions like that or programming...

Is that all it says, just a generic "file access error"? Try to load this TSR first, and then check C:\HISTORY.DAT to see what files it tries to load. KGB TSR This is kernel 2043, right? What memory (XMS EMS) drivers are loaded? Is mouse loaded? SHARE? Is it in the same named dir that you installed to? Any specific environment variables needed? Any idea what kind of DOS extender (if any) was used? Also, this is a graphical app, right? VirtualBox is far from perfect. You could also try QEMU. What...

I've found the IDE interface is slow in Borland TurboC with FreeDOS (haven't looked into why) so it might be the same with the IDE in Borland C/C++. I believe we discovered that the Borland IDEs are noticeably slower when FDAPM (APMDOS??) is loaded.

If you want a small external calculator, try Eric Auer's calcfixp or Oleg Chukaev's resident FDRC.

The 16-bit real mode unzipper can be found on the iBiblio archives: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/util/file/info-zip/unzip/6.0/

Rarely does anyone need a linker without a compiler. Most compilers come with their own linkers. We do have several 16-bit OMF linkers. Although none is 100% compatible in the most extreme cases, they do work for average use. Some of the ones I've used recently (in small ways): Warplink, JWlink, VAL, DJLink, ALink. If there is specific functionality needed that is not supported here, I'm sure someone on the mailing list could point you in the right direction.