T h e   F i d o G a z e t t e!   Volume III Number VI  August      2009    
    | .----------------------. |      dr.debug: dr.debug @ filegate.net   |
    | | A monthly E-Zine     | |      bbslists: bbslists @ filegate.net   |
    | | published by Fidonet | |      articles: fidogazette @ filegate.net|
    | | to promote BBSing    | +------------------------------------------+
    | |          ____________. |                                          |
    | |         /  __          | "Anyone who has never made a mistake     |
    | |        /  /  \         |  has never tried anything new."          |
    | | WOOF! (  /|oo \        |                      Albert Einstein     |
    |  \_______\(_|  /_)       |                                          |
    |             \@/ \        |          Got Something To Say?           |
    |             .---.\    _  |              Say it in the               |
    | (jk)  _     |usb| \   \\ |           =The FidoGazette=              |
    |      / |    .___.  \   ))|                                          |
    |     /  |    /_ |  /  \// |         Editor: Janis Kracht             |
    |    |___|   // || _\   /  |         janis @ filegate . net           |
    |    .--`-. (_|(_|(____/   |         janis kracht 1:261/38            |
    |    |____| (jm)           |                                          |

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009

    Important Region 11 News!..................................(1)
    New SysOps!................................................(2)
    FidoGazette BBSList........................................(2)   	 
    The Slightly Crusty Sysop..................................(5)
    The Old School Toolbox: Mailers ...........................(6)                              
    D'Bridge EMAIL System......................................(7)
    FidoGazette: ..............................(9) 
    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009

    Important Region 11 News!
    By Janis Kracht, Z1C, 1:1/0
    The following email was sent out to each NC in Region 11 that I could
    connect with.  Unfortunately I was not able to connect with a great
    number of them.  See the results in the polling section of this
    article below.  If you are in Region 11, please read the
    following, and contact me if you have not been able to reach your NC.
    You can email me at janis (at) filegate.net or netmail via binkp at
    filegate.net on port 24554 (standard port). No password is necessary,
    I'll get you netmail :)  If you are an NC, I'll have mail waiting for
    you here :)  This is the post:

    === cut here === start post ===
	As I was informed last evening by R11C Don Plesky, he is unable to
	continue as RC of Region 11 at this point.  Since it has been so long
	since Don was appointed RC and I did ask him then to hold an
	election, I think now would be a good time for one, however I look at
	the Regional segment and I see a number of the network coordinators
	in Region are MIA...

	I would like the "living" NCs and RINs to contact me in reply to this
	message asap so we can see if an election is feasible.  I'll wait a
	week or so for a reply given vacations, etc.  If you know one of the
	NCs or RINs is "live" but out of town, please let me know! .

	Failing a response from people, I will appoint another RC as I have
	done in the past.

	Take care,
      ====== cut here ====  end post ===

    I also posted a message in Z1_SYSOP and Z1C to all members of Region
    11 regarding this issue today, July 31st, 2009:

    =======cut here===start of echomail post=====
      fido.Z1_SYSOP message #740 from Janis Kracht to All.
      Entered on 31st July, 2009 at 16:56, 8 lines.
      Subject: R11 NCs and RINs
      If you are one of the above in the Subj., I am trying to poll your
      systems to send some important netmail.  Please try to connect to my
      system with no password enabled if we've never set one up here before.

      Thanks :)
	=====cut here====end of echomail post===

    Saturday Morning/Afternoon Polling Results:  July 31st, 2009
    This is the result of some of the polling from earlier today for RINs
    and NCs, Bad Poll counts exceeded due to 'No Carrier'.  Keep in mind
    if your system is one of these, that this may be due to systems only
    allowing passworded accounts to connect (something I don't have a big
    problem with, but if you do, you should contact me in netmail (1:261/38
    or 1:261/100) or email, please. No password is necessary.

	   Warning: Bad poll count exceeded for 1:11/600.0
	   Warning: Bad poll count exceeded for 1:11/2202.0
	   Warning: Bad poll count exceeded for 1:11/229.0
	   Warning: Bad poll count exceeded for 1:11/340.0
	   Warning: Bad poll count exceeded for 1:11/304.0
	   Warning: Bad poll count exceeded for 1:11/202.0
	   Warning: Bad poll count exceeded for 1:2320/0.0
	   Warning: Bad poll count exceeded for 1:220/0.0
	Page 1

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009
     New & Returning Members
     By Janis Kracht

     In the Works:
     Brian McSweeney Florida, Region 18
     Allen Snodgrass, Region 18
     Z3: New Zealand
     James Kelly
     Returning SysOps:
     Welcome Back!
     Mike Miller     Wisconsin, Region 11         

	Page 2

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009

	!!!        G A Z E T T E   B B S   L I S T        !!!
	By bbslist @ filegate.net    
	Send updates, changes to address above or to janis @
	System.......<  I'm still not sure /why/ I run
    a BBS.  I get my regular callers and such but I know there's other
    things I could be doing with my time.  I think it's because BBSing
    still gives me a special satisfaction that very few other things in 
    life seem to give me.

    I have an understanding wife that allows me to spend a little more
    time on the computer than I do with her, but I try to make up for
    it.  I really don't spend much time on the BBS any more due to my
    work schedule and health but I'm trying to fix up the board and
    actually get some new BBS doors out (much to my very patient and
    very bored beta team's relief).

    How about you?  What's your first memory of BBSing?  Do you even
    remember this joyful event?   I'd like to hear from you and
	if it's a good story, I might even put it in my next column.

	You can contact me via netmail at 1:18/200 - if you do send me a
	story, please put it inline with the netmail message and do not
	attach it as attachments with routed netmail don't mix.  If you
	prefer, you can email it to me at sean@nsbbs.info with the
	subject line of "Favorite BBS Memories".  As always, comments,
	suggestions, kudos and such are welcome.  Flames will go
	immediately into the bit bucket.

	See you next month.

    Page 5

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009
                              The old school TOolbox

                       By RIchard Webb, 1:116/901

                 Improving wireless network performance

	"Setting  up  a  network  of machines has never been easier," says the
	salesman and the glossy advertisements.  THE  salesman  at  the  local
	electronics  and  computer imporium has "just what you need" to do it.
	IT sure seems to you that he's giving you  the  straight  dope.  After
	all,  pulling  that  cable  through  walls  ceilings  and  crawlspaces
	wouldn't be much fun, and this is simple, probably  cheaper  than  all
	that cable too.

	"Hey  I  can  even  use  it out on the patio sipping a margarita," you
	think to  yourself.  Pictures  of  doing  spreadsheets  on  the  patio
	listening  to  the crickets and sipping that cool libation on a summer
	evening dance in your head.  son's  pc  in  the  bedroom  is  wireless
	networked,  your  laptop  connects  to  your printer from anywhere, no
	cumbersome umbilicals. What's not to like?

	Or, like many, you bought a new laptop  and  it  had  this  capability
	built  in  and  you suddenly want to use it. SO you went to the store,
	bought the  requisite  hardware  to  make  your  server(s)  wirelessly
	accessible.  But,  things didn't quite turn out as you'd planned. THat
	envisioned relaxation on  the  patio  with  your  laptop  and  a  cool
	beverage isn't so great, because your laptop loses its connection with
	the server, and your daughter can't access it from the family room  in
	the basement.  What's wrong with this picture?  YOur laptop on the
	patio is only a few feet from your wireless router.  WHat's the matter

	Worst of all, your neighbor next door has been hitchhiking a free ride
	on your  internet  connection.  DOg  gone  it!  Time  to  change  some
	configuration to lock him out. But still range isn't quite what you've
	been told you can expect. FUnny though that your freeloading  neighbor
	was able to get in before you changed some passwords and rights.

	YEs  VIrginia  you  can  increase your range, you can install a better
	antenna at the router. some strategies to do this are  even  available
	at  the  same friendly merchandiser that sold you the gear. SHould you
	do this? Maybe you should, and maybe  you  don't  need  to  spend  the
	money.  IF  you should decide to do some modification to increase your
	range you might find yourself not  reaping  as  much  benefit  as  you
	thought  you  might.  Hmmm,  think  I just mentioned that when talking
	about your original wireless installation.

	First, change the channel! YOur wireless network can operate  on  more
	than  one  channel.  shut down your system, use your laptop's wireless
	connection facilities to look at other channels near your home and see
	what's  in  use. FInd one that isn't. HEy, that's how your freeloading
	neighbor found yours! I'd bet you dollars to doughnuts that  when  you
	switch  off  that default main channel your range might improve a bit.
	Hmmm, no upgrade dollars spent, just a bit of time.  FUnny  how  those
	things  work.  OFten  they're  the best performance increases whatever
	your endeavor I find. At this point maybe you've gotten all you expect
	from  your wireless network, and you can go on to other activities and
	cease reading this bit of dry text. But, before  you  decide  to  exit
	this  text view and go back to exciting stuff offering 3d graphics and
	markup stuff stay with me a bit longer, because tomorrow your  mileage
	may vary, quite literally.  AFter all, another neighbor might switch
	from 2.4 to 5 ghz just as you did to get more range.

	All  this  data  that you ship around on your wireless network goes by
	microwave instead of by cat-5 cable or coaxial cables.  THat's  right,
	microwaves,  just  like  those  that  baked  the casserole you had for
	dinner or warmed up your sandwich or soup for lunch.

	Microwaves don't act like other radio frequencies you're accustomed to
	thinking of. You're used to thinking about that long  drive  home  and
	spinning  the  dial  on your car radio to keep awake, signals from all
	over bouncing into your car. YOu might be listening to a  radio  drama
	from  a station in CAlifornia, or KAAY in LIttle ROck ARkansas playing
	the best progressive rock, or the Road gang from WWL New ORleans.  OR,
	you'll  remember  spinning  the  tuner  on that old television set and
	seeing a TV channel from a distant city coming in like a local.

	YEs, TV is vhf and uhf, but the lower TV channels still  were  subject
	to  phenomena  that  enabled  transmission further than line of sight.
	Microwaves, on the other hand are limited in most instances to line of
	sight,  especially  with the small compromise antenna systems provided
	with your laptop or wireless router.

	Microwaves  in fact have some very strange characteristics compared to
	the radio waves you're used to thinking about.  Just  the  human  body
	between  the  transmitting  antenna  and  the  receiving  antenna  can
	attenuate that signal to the point of rendering it unusable.  this  is
	why microwave relays using terrestrial paths use big dish antennas and
	lots of brute force in the form  of  power.  A  terrestrial  microwave
	relay   system   operated  by  your  telephone  company  might  employ
	transmitters transmitting at several thousand  watts,  and  high  gain
	antennas  giving  that 5000 watts the relative power of 20,000 watts in
	its direction of travel.

	Remember a bit ago  we  told  you  that  even  bodies  can  mess  with
	microwave  paths.  INdeed  meat isn't good for propagating microwaves.
	MEat, and most  foodstuffs  contain  some  moisture,  and  this  water
	content  is what enables the microwaves in your microwave oven to cook
	your food. the microwaves vibrate the water molecules in your  bowl  of
	soup  or  cup  of  coffee.  AS the water molecules vibrate they create
	friction as they bump against each other, and friction,  as  you  know
	from  rubbing your hands together to warm them creates heat. THere are
	many urban legends about  the  microwave  facility  techs  who  cooked
	themselves by sitting inside the big microwave dish.

	This  still  isn't telling you why you can't get into the darned thing
	reliably from the patio but your freeloading neighbor could access it.
	YOu'd  have  never known he could if you'd taken the time to configure
	your wireless network for proper security. But, hey, you're a  fidonet
	sysop, you knew this part (I hope.)

	BUt,  you  didn't,  and  your  neighbor  has  sure  been enjoying your
	wireless internet and it's sure a bummer  that  you  can't  kick  back
	where  you'd  like  and use your system you paid for. THink about what
	stands between your freeloading neighbor and  your  router's  antenna,
	and  then consider what might be between your router and your favorite
	spot on the back patio.

	Remember how they're always telling you not to  use  metal  dishes  or
	certain stoneware in your microwave oven? OF course you do. MIcrowaves
	don't pass through metal very well. SO, if those microwaves can't  get
	inside  they  can't  vibrate  those water molecules and your casserole
	won't get hot. So, what's between your router and that  favorite  spot
	on  the  patio?  YOur  kitchen  appliances  maybe? A wall with lots of
	wiring and copper plumbing? Ah yes, and between your router and farney
	Freeloader  there's  a  window  and  the usual outer wall construction
	materials. Hmmmm, so he's got a better signal than you have.

	Vhf and uhf, as well as the microwave frequencies only travel line  of
	sight  as we noted earlier. so, you might gain some benefit by getting
	that router and its antenna up higher, say  on  a  shelf  or  cabinet.
	Maybe  then  it  can  look over the top of your refrigerator and reach
	your patio. AFter changing frequencies this might be all you  need  to

	MOst of us who work with this radio stuff every day are accustomed to
	thinking of height as our friend when it comes to signal  improvements
	on  vhf  and  uhf.  but,  there  are  a few problems with getting more
	skyhook for your router's antenna.

	FIrst and foremost, separating the antenna from the hardware itself is
	a  bit  of a daunting task. regular coaxial cable isn't that efficient
	at the frequencies you'll be using, in fact, its losses would probably
	offset  any gains you'd make with more height. Therefore, you've got to
	move the whole thing higher. MIcrowave relay systems and  many  others
	who  utilize  vhf  and  uhf utilize "hard line" as a feed instead of a
	cable. ONe of the most common varieties of hard line is  7/8  inch  in
	diameter,  and  not easy to work with. But moving that whole server up
	high might not be real practical either.

	Even though you've locked out Farney Freeloader next door you'll still
	possibly  hear  his  signals, and the signals of other neighbors using
	their wireless network systems, even if they can't access yours.  WHen
	you raised that antenna you increased its range, both for its receiver
	and its transmitter. YOur laptop and other computers  still  have  the
	same  range for transmit and receive, but your router's antenna is now
	higher, reaches out farther, and receives  more  signals.  THat  clear
	channel now isn't so clear.

	But,  a  little bit of height might just be the solution you need, and
	if it can be done without having to  go  buy  some  more  hardware  or
	reroute  a  bunch of cables it's sure worth a try. But, those few feet
	might not make a difference.

	IF your router only has one whip antenna  you  might  think  about  an
	upgrade  to  a  router using what is called a diversity system for its
	receiver. IF it does the label will usually  tell  you  this.  A  good
	indicator  of  this  is  a  router with multiple antennas. A diversity
	receiver system is one that uses these multiple antennas, and possibly
	receivers  to listen for signals on its frequency, and routes the best
	signal to the rest of the system. the technology  was  popularized  by
	broadcasters  and  live  productions using wireless microphones. THese
	microphones were often deployed by performers and presenters who  move
	about  quite  a bit, and even in theaters and auditoriums the wireless
	microphone  receiver  deployed  couldn't   reliably   pick   them   up
	consistently.  Hence,  diversity  receivers were employed to solve the
	problem. THe ubiquitous cellular phone uses diversity reception  on  a
	large scale to keep you connected with the network.

	Still  not enough improvement? well my friend, you're on your own, but
	there are resources out there. Start  doing  some  hunting  around  on
	google  and  specialty  ham radio web sites, especially those for weak
	signal vhf uhf and microwave enthusiasts. YOu can find numerous  plans
	for directional antennas which will cover your bands of interest, many
	which would appear to be simple to fabricate. IF you go  with  one  of
	these  plans  from  the web or the books, remember that these are very
	small wavelengths,  this  is  why  they  call  them  "microwaves"  and
	tolerances  are  very  fine.  A small error in measurement will render
	your antenna useless, and you'd do better then  to  go  back  to  your
	stock router with its stock antenna.

	Then,  when  rolling  your  own  there's  the matter of connecting the
	antenna to your router.  Unless  the  cable  run  is  extremely  short
	remember  that  standard coaxial cable presents a high degree of loss,
	and must be carefully terminated with the proper connectors.  But,  if
	you  must  proceed, and don't have the technical skills necessary then
	make nice with a local  ham  radio  afficionado  who  is  really  into
	antenna building for the uhf and microwave bands.

	To recap, small changes make big differences. Don't just think higher,
	think left or right. Draw some  imaginary  lines  from  your  router's
	antenna  to  your  favorite  kick  back and use your laptop spot which
	gives you trouble currently.  COnsider  where  the  wiring  and  pipes
	travel through the walls; dad's favorite spot at the dining room table
	to sit and read the paper, etc. THat slight shift to the  left  a  few
	inches  might  just  allow you to get a clear microwave path from your
	router to that laptop on the patio that avoids dad's  head.  All  that
	meat in your dad's body doesn't do great things for microwaves remember.

	IF you must upgrade, try a diversity receive system before you go the home brew
	antenna route.

	Finally,  remember  that old proverb? IT went something like
	this. "Be careful what you wish for, you just might get it."
	YOu  could even maybe move the main antenna for your server,
	along with the server itself up high, say in your attic, and
	just  run  your  broadband  hard  wired connection up there,
	power it up and you're ready to go, instant improved  range.
	But,  remember, you're working with frequency bands where no
	license is required. Sure  this  limits  you  to  low  power
	levels,  but  it almost means that you're going to encounter
	more interference as you improve your  receive  range.  But,
	try some experiments before you throw money at the problem.

    Page 6

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009


                           D'Bridge EMAIL System                
                         (c) by Nick J. Andre, Ltd.

	VERSION 3.32 - JULY 22 2009

	This is a major release and it has significant and fundimental changes
	done internally to the source code. A lot of work was done to simplify
	or improve the functionality of several elements of D'Bridge.

	Please try only to report any problems once 3.32 has been installed. The
	source code for 3.31 and prior versions has been archived/moved off the
	workstation. I will not be able to quickly diagnose any problems in 3.31
	and prior versions. Thats not to say I can't do it; its just going to
	take more time if you are reporting stuff from 3.31.

	WARNING: If thats not possible or if this release does not perform as
		desired, then rollback to 3.31 or prior releases and send a report
		accordingly, ASAP to my attention via Internet Email. DO NOT send
		regular Fido NETmail.

	The release notes for this version are lengthly; so I've broken it up
	into several sections, and for posting in the Fidonet DBRIDGE echo:

	REDESIGNED SETUP WIZARD - Explains the install/upgrade improvements.
	FIDO PLUG AND PLAY - Allows new users to automatically obtain 
	UPDATES NOTIFICATION - Explains the new auto-updates 
   						notification feature.
	CORRECTIONS/FIXES/ETC - The largest section; 
	  						outlining the obvious.


	The Setup Wizard has been rewritten from scratch; functioning exactly as
	it did in the version 1.xx series. This was done for a few reasons, but
	the end result is a more simplified procedure. And most important: Less
	code used.  

	The Setup Wizard will do a fair amount of "cleanup" of your DB directory
	when you upgrade from 3.31 or prior versions. There may be a
	considerable amount of disk-activity during this process. A fair amount
	of files will be permanently DELETED from your directory. These are:

	- ANY and ALL "leftovers" from terminated Soupgate/VSOUP sessions.
	- DB07*.3 and DB08*.3; obsolete/retired code from 3.31 
	  and prior versions.
	- COMM.CFG, obsolete from version 1 and version 2 series.
	- DBRIDGE.MSG, obsolete from version 2.
	  removed either for obsolescence or because of possible conflicts 
	  after upgrading to 3.32.
	- The infamous empty "Queu" directory.

	There may be a problem if you decide to rollback to 3.31 or prior
	versions when these files are missing, however it would (theoretically)
	be more of a cosmetic/minor problem than major.


	This was a past topic you may remember discussion on in the Fidonet
	DBRIDGE echo.  

	A completely redesigned Wizard in 3.32 now gives the end-user the option
	of either manually configuring their address, uplink and routing
	information or to have that automatically-obtained. This is done via
	Fido Plug and Play, or FPNP for short. FPNP is a way to
	dynamically-assign Fidonet/FTN addresses to systems who connect to you
	for the first time.

	When prior versions of D'Bridge were installed for the first time, a
	Wizard would appear, asking the user to enter in their network address
	and that of their Fidonet uplink/provider. And of course DB would
	configure itself accordingly.

	FPNP is now fully functional, works properly across "othernets", and is
	a major step in allowing newcomers to join our hobby.  

	WARNING: This is an advanced feature. You should not enable FPNP unless
	you are an experienced administrator with a very thorough knowledge of
	how Fido/FTN addressing, routing and hubbing works.

	When a remote system is assigned an address by you, they are given a
	POINT ADDRESS and can optionally be connected to Echomail areas of your
	choice.  All of the complicated routing, scheduling and packet/mail
	settings are automatically configured on both your side and the user's.

	The Wizard will ask if the user already has a Fido/FTN address. If so,
	then the system will be auto-configured with their address and uplink
	info, the same way it worked in prior versions. However, if not, then
	FPNP works to obtain the address.

	The way it works is a new installation of 3.32 (and higher) connects
	first with nickandre.com (1:1/130). The 1:1/130 address on Fidonet is a
	"primary directory" of all known D'Bridge installations worldwide that
	are offering FPNP services to end-users; along with which networks (ie.
	Fidonet, DBNET, etc) and their corrosponding geographical locations.

	The data exchanged with nickandre.com is your address and FPNP
	information as configured in this screen. No other information is sent
	to that site.

	WARNING: Systems who do not refresh themselves within a one-week period
	are automatically purged from the database at 1:1/130; to help present a
	most-recent list of available systems that an end-user can exchange mail

	By carefully manipulating BinkD on the end-user side, a short query is
	done and a list of available "hubs" is downloaded from 1:1/130 and
	presented to choose from. The user can then choose one (usually whoever
	is closest geographically) and optionally choose which networks to
	connect to.

	A request is then sent to your system to obtain an address. D'Bridge
	then computes and sends back the address along with special commands
	that automatically configure that remote end-user with the proper
	address, routing, Echomail areas and so forth.

	The questions in the new FPNP SETUP screen control how it works:

	ZONE:NET    This is where you specify the network Zone and Net where 
				the addressing should start. For example, 1:229 means 
				that I will	auto-assign addresses in Zone 1, Net 229. 
				The ZONE:NET must match at	least one of your network 
				addresses specified in the BASIC CONFIGURATION	screen. 
				The first matching ZONE:NET will be the one that addresses are
				auto-assigned from.

        	    WARNING: Be very careful with the deligation of Fidonet ZONE
        	            and NET properties. If you are not the Network 
        	            Co-Ordinator (NC) of your local "net", you should 
        	            ask permission to use FPNP first.

	NETWORK ID  A unique ID to assign for this network. Up to 8 letters and
	            numbers only. For example, FIDONET or DBNET. The network ID is
    	        presented to the remote system.

	NODELIST    D'Bridge will send the specified nodelist to the remote system.
    	        Do not enter an extension; it will send whatever matches.

	DEFAULT     Specifies the default security criteria to apply for new systems
	SECURITY    and this should match the criteria in the PACKET/MAIL CONTROL
    	        screen. For example: A,50 means assign group A, security 50.

	START       The starting "scope" for address assignment. For example, if
    	        you enter 50 and your network address is 1:229/426, then D'Bridge
        	    will assign addresses from 1:229/426.50 and onward.

	END         The ending "scope", as per above, D'Bridge will assign addresses
    	        up to this criteria.

	OPTIONAL    You may send an optional "infopack", usually a ZIP file that
	INFOPACK    would contain an official application, rules and list of areas.
    	        Specify that name of the file here (*with* an extension)

	FPNP updates and controls the points via the POINTS.LST control file.

	D'Bridge is smart enough to figure out if the POINTS.LST already exists and
	if its in that "Boss-node" format as discussed recently (as of this writing)
	in the FIDOGAZETTE echo.

	Originally it was my intention to provide NODE addressing and full support
	for MakeNL-compliant segments, however, there are a few "political"
	drawbacks of offering this service. Internally however, the code can be
	adjusted fairly easily to provide NODE addressing.


	When D'Bridge 3.32 is installed for the first time, a Wizard appears,
	asking you if you wish to be automatically notified when new updates are
	available.  If you answer YES to this question, D'Bridge will check with
	nickandre.com approximately once per week, to see if a new version is
	available. If so, then a message is flashed on the MAILER screen


	As explained earlier, a significant amount of work was done behind the
	scenes to help improve the way certain fundimental components operate.
	In addition:

	- The overall installation/upgrade process should be several times
      faster than before.

	- The overall operation of the mailer should be anywhere from 5% to 25%
 	  faster now.

 	- The overall operation of the BinkD subsystem should be anywhere from
      10% to 75% faster now and use less disk access/swapping.

	- D'Bridge will unpack any received mail immediately after a BinkD
	  transaction if running in "client only" mode.

	- D'Bridge uses slightly less memory when running now.

	- A serious stability/reliability problem with the way D'Bridge handles
	  COM ports has been resolved.

	- A serious stability problem with Error 23 relating to COMM/MODEM setup
	  should be resolved. The problem is in the length of the MCF files.

	- A serious problem with the way BinkD stopped polling remote systems
	  upon installation of some recent versions of D'Bridge should be 
	  resolved	now. This version underwent serious testing to ensure that problem did
	  not happen again.... but if it does, let me know.

	- A serious problem with DBUTIL SORT AREAS has been resolved.

	- A serious longstanding problem with DBUTIL CHANGE on alias-addresses
	  (non-Fidonet) has been resolved.
	- A minor improvement was done to the code of DBUTIL PURGE.

	- The nightly "cleaning" of the system log files is now done internally
	  in D'Bridge.

	- A problem with a malfunctioning COM port-status in the menu system has
	  been fixed, and no, it wasn't something I botched before... it was 
	  a new thing I botched.

	- The internal editor should no longer duplicate the MSGID kludge on
	  NETmail destined for multiple recipients.

	- The internal editor's "Custom tear line" is no longer Wildcat.

	- DBUAFIXI is no longer included in D'Bridge, I rewrote that entire program
	  and all the code to function during the tossing of mail; internally.

	- USENET.BBS is properly auto-generated on all transactions from the
	  NNTP SOUP gateway that update the NEWSRC source file.

	- AUTORUN.INF is no longer included in D'Bridge; for security reasons, and
	  Microsoft has recently released a series of "patches" to their OS's to
	  change the behavior of AUTORUN.INF. It is fairly simple to create your own
	  if you decide to burn D'Bridge to CD-R to share with others.

	I also rewrote a few sections of code to be less dependant on Assembler and
	be a bit more compiler-friendly instead of just hammering the DOS session
	with assembler calls.

	After working on 3.32, I am inspired to start work on eliminating ALL of the
	assembly-language calls out of D'Bridge entirely. There are two fundimental
	problems in the code that I may need help on. Those are ZMODEM and the B-
	Tree database system used by the Nodelist, Costbase and system Queue.

	Eliminating the assembler code means that I can compile cross-platform DB
	that will work natively in Linux, OS/2, Unix, FreeBSD, Win32/Win64, etc etc.

	Depending on what feedback I get from that, I may just release that as
	the version 4 series.

	Nick Andre


    Page 7

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009

    Where to Send Your Articles

    Unlike most editors, I surely do not  mind running my mouth when
    there is a sparcity of articles for the 'zine.  I'd MUCH rather
    you sent in material but I think until someone starts a
    discussion you feel like commenting about, you evil dullards
    (just kidding!!!) will no doubt complain about "no issues" 
    So I will fill these issues with my meanderings and thoughts and
    hopefully we will grow into something of consequence here :)
    Don't be offended.. write an article!

    If you WOULD like to submit an article and prove me wrong about
    the dullard aspect of you guys and gals , feel free to drop
    your article off at:

    By email attach to address: janis@filegate.net
    Fidonet attach: Janis Kracht 1:261/38 Modem: 607-655-5652

                   1:261/100 filegate.net via telnet mailer
                   filegate.net via binkp mailer (don't send 
                   articles as routed attaches, send them
                   direct to filegate.net).

    Give it a title, sign your name and network address if you have
    one and send it along!

    Don't worry about the format, I can take anything you send me
    and mutilate it further as you can see above.  Linux is nice
    that way .  Spell checking your own work will help though
    (something I'm typically guilty of ).

     More specifics with this issue :)

     To send a question to Dr. Debug, email a question to
     dr.debug@filegate.net or post in the fidogazette echo! :)

     To send a listing to the fidogazette internet bbs list, send your
     bbs listing to bbslist@filegate.net or post it in the fidogazette
     echo!  :)

    Page 8

    T h e   F i d o G a z e t t e!   Volume III Number VI August       2009