| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: EleBBS: DOOR.SYS Format Addition |
Re: Re: EleBBS: DOOR.SYS Format Addition By: Mike Ehlert to All on Tue Feb 14 2006 03:59 pm > > Not sure if EleBBS "knows" that a door is 32-bit or not, but it'd be cool > > if EleBBS supported this line for 32-bit doors too. > > EleBBS supports the Door32 standard (also used by Synchronet and Mystic), > http://grouty.org/door32.fmt > > Wouldn't it be better to add door32 support to OpenDoors rather then > changing the door.sys standard? :) It would be if the door32 format contained even a third of the information that door.sys did. The only missing bit of info I've found regarding door.sys is the sex of the user. I recently ported a door which requires the users name, handle, birthdate, number of rows on screen, and sex. Using door.sys means I only need to prompt for once piece of info. Using door32.sys means I need to prompt for two. Further, door32.sys doesn't have a stdio option. In the whole, the door32.sys format seems like it was rushed out the door where as door.sys has everything and the kitchen sink. On the whole, I'd rather use a standard that supports everything plus a lot of extra stuff than a format which supports less than the basics. However, OpenDoors supports door32 doors using both the "official" door32.dll and by reading the dropfile itself. For doors that care how much time is remaining in the call, the users screen length, the users birthday, if the user is an "expert", or the desired download protocol, door.sys is superior. ---This sig is not directed at Jazzman. --- SBBSecho 2.11-FreeBSD* Origin: (1:140/17) SEEN-BY: 633/267 270 @PATH: 140/17 1 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™.