| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Long `unzip` time |
MG> Hpt has proven that Squish doesn't need this limit in MG> 32-bit environments, because it's Squish compatible and MG> it doesn't have the limit. It'll process anything as MG> long as you have enough memory on your system. BS> Huh? Actually what does 32-bit environment has to do with a buffer size? In a 16-bit environment, all data structures have to fit within 64Kbytes. With some compilers (or switches used by the compiler) the code has to keep all data within 64K bytes or maybe 2 or so blocks of 64K bytes. Remember, Squish and Maximus were running on 16-bit systems that had the intel 64K byte segment limits, that resulted in certain compiler restrictions. In a 32-bit environment, you can have a flat (non-segmented) memory structure. While it has been a while since the nodelist was above the version 6 index limits, which were based on 64K byte data segment limits, the 32-bit environments could have junked some of those limits..... Some of the 16-bit limits haven't been raised, or significantly raised, in the 32-bit versions of the code.... Scott coded for compact code. At one point in time, I believe you could run two copies of Max/Bink/Dos on a 640Kb computer with Desqview for the multi-tasker..... Take care..... Bob Jones, 1:343/41 --- Maximus/2 3.01* Origin: Top Hat 2 BBS (1:343/41) SEEN-BY: 633/267 270 @PATH: 343/41 10/345 106/1 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™.