| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Squish progress |
> How about updating the actual Squish executible itself, so that it's a > true 32-bit aplication, instead of a 386 extended DOS app? Would it make you feel any better if I told you I had it running in 64 bit mode under Alpha/Linux, and am working on 64-bit Sparc/Solaris? I have no plans to make any changes to released DOS versions. The primary reasons being that I have no interest in doing so, do not own a suitable development platform, and have very little experience coding under DOS, Windows, or OS/2. That said, some enterprising soul may be able to get my version to run under djgpp, cygwin, or EMX. But it won't be me. There exists a vague possibility that I might do a native Win32 version, but that won't be for a long, long time. Getting this stuff working under UNIX is far more important to me. However, I appreciate you pointing out the limits in the older products; I need to make a checklist of "limits to remove". Message size limits are a big one; I firmly believe I should be able to handle messages which are at least half as big as the amount of virtual memory available. One limit I will not be removing is the node number limit (255), as that will break many third-party utilities. Wes --- Maximus/2 3.01* Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000) SEEN-BY: 633/267 270 @PATH: 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.