Received: by cthulhu.engr.sgi.com (941129.SGI.8.6.9/911001.SGI)
	for tiff-list id CAA17812; Thu, 1 Dec 1994 02:34:30 -0800
Return-Path: <owner-tiff>
Received: from sgi.sgi.com by cthulhu.engr.sgi.com via ESMTP (941129.SGI.8.6.9/911001.SGI)
	for <tiff-relay@cthulhu.engr.sgi.com> id CAA17807; Thu, 1 Dec 1994 02:34:24 -0800
Received: from daimi.aau.dk by sgi.sgi.com via SMTP (941129.SGI.8.6.9/910110.SGI)
	for <tiff@sgi.com> id CAA05448; Thu, 1 Dec 1994 02:34:20 -0800
Received: from tuborg (tuborg.daimi.aau.dk) by daimi.aau.dk with SMTP id AA22486
  (5.67b8/IDA-1.5 for <tiff@sgi.com>); Thu, 1 Dec 1994 11:33:57 +0100
Date: Thu, 1 Dec 1994 11:33:57 +0100
Message-Id: <199412011033.AA22486@daimi.aau.dk>
X-Sender: pingel@daimi.aau.dk
X-Mailer: Windows Eudora Version 1.4.3
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: tiff@sgi.sgi.com
From: pingel@daimi.aau.dk (Soren Pingel Dalsgaard)
Subject: Re: DOS port
Sender: owner-tiff@sgi.sgi.com
Precedence: bulk

>Hello all,
>
>Apologies if this is a FAQ -- I looked in the archives and the sources 
>mentioned there, but could not find what I was after...

I don't think it is a FAQ.

>1) Has anyone ported the latest libtiff to MSDOS, specifically using MSC 
>7.0, 6.0 or the Visual C++ compiler?

Well I tried to see if it was possible. A major problem is that LibTIFF was
written for UNIX computers with unlimited memory resources :-). A port to DOS
will need some dos extender because huge amount of memory *may* be needed in
order to read an image.
You need to change the tif_msdos.c file so that all functions, i.e. file read
and file write will work even if they have to write more than 64Kb data. The
same goes for the memcpy, memset, memcmp, malloc, realloc and free functions
(_TIFF prepended).
Also you need to compile it so that all pointers are HUGE by default. The
library may cast tdata_t pointers to pointers to any data type. So the
default pointer type must be able to address more than 64Kb.

>2) Do you have a make file for one of the above, &/or notes on 16 vs 32 
>bit issues and which routines might need to be omitted or reworked?

There is a makefile but it is old and I don't think it can be used for much.
The porting problem is not in the makefile but the machine specific module.

>3) If anyone has comments on some other DOS C compiler (32 bit?) that eases 
>any of the potential problems, I'd love to hear about that too.

I know that gcc for dos will work. I compiled the tools some time ago and
they worked for me. One good thing about this compiler is that it is free
(available from oak.oakland.edu in pub/msdos/djgpp)

>Much thanks,
>
>Mickey Feldman
>Spatial Insights, Inc.  

You are welcome!

/Soren
--
Soren Pingel Dalsgaard, Computer Science Department  )\._..--....,---,
Aarhus University, Ny Munkegade 116, DK-8000 Aarhus /,   _.. \   _.. ,`._ ,.
DENMARK, email:pingel@daimi.aau.dk, ph:+45 89423284`._.-(___.'..(___.'`-.;.'


