BUG LIST/FAQ for WinFBB 7.00a evaluation release. Compiled by KE0WO @ KE0WO.#WIA.IA.USA.NA Internet: dmadsen@iastate.edu Updated 960402. The following is an UNOFFICIAL bug list that I have been compiling from my system and from other WInFBB users on the Internet. The main purpose of this list is to funnel bug report through proper channels to where they might do some good, cut down on the duplicate bug complaints/reports and get those that do not see their "pet" bugs on the list to contact me and report them (I know I left some off the list). Remember, if you have a bug to report, be sure to give as much information as you can. A report of "I had a GPF when WinFBB was loading" could be improved by giving the GPF address too! For Windows 3.1 users, there is a DRWATSON.EXE program in your \WINDOWS directory. If you add that program to your Start Up group, then when WinFBB crashes, the file \DRWATSON.LOG will contain info on what the problem was (you won't have to write down the address while the error is on the screen). Also, reports for WinFBB 7.00 will do little good. Upgrade to WinFBB 7.00a, try things again and then send in your reports! Take this for what it is worth (whatever that is). ------------------------------------------------------------------------------ - I have had the following GPF's: WFBB had a 'Exceed Segment Bounds (Read)' fault at BIDS47 4:2833 $tag$WFBB$Exceed Segment Bounds (Read)$BIDS47 4:2833$push word ptr es:[bx+08 ]$Fri Mar 22 17:51:04 1996 **************************************************************************** WFBB had a 'Unknown' fault at WFBB 71:6465 $tag$WFBB$Unknown$WFBB 71:6465$les bx, [bp+fa]$Sun Mar 24 19:02:17 1996 $param$, Last param error was: Invalid handle passed to USER 7:17b2: 0x0000 **************************************************************************** WFBB had a 'Null Selector (Read)' fault at WFBB 71:6470 $tag$WFBB$Null Selector (Read)$WFBB 71:6470$push word ptr es:[bx+52]$Sun Mar 24 19:02:19 1996 **************************************************************************** WFBB had a 'Null Selector (Read)' fault at WFBB 61:07bf $tag$WFBB$Null Selector (Read)$WFBB 61:07bf$mov bx, es:[bx]$Tue Mar 26 19:0 1:15 1996 **************************************************************************** WFBB had a 'Unknown' fault at WFBB 61:07c2 $tag$WFBB$Unknown$WFBB 61:07c2$callf word ptr [bx+08]$Tue Mar 26 19:01:17 199 6 **************************************************************************** WFBB had a 'Null Selector (Read)' fault at WFBB 5:2571 $tag$WFBB$Null Selector (Read)$WFBB 5:2571$cmp byte ptr es:[bx+7c], 00$Tue Mar 26 19:08:08 1996 **************************************************************************** WFBB had a 'Null Selector (Read)' fault at WFBB 61:0777 $tag$WFBB$Null Selector (Read)$WFBB 61:0777$mov bx, es:[bx]$Tue Mar 26 18:2 9:35 1996 **************************************************************************** WFBB had a 'Exceed Segment Bounds (Read)' fault at BIDS47 4:2830 $tag$WFBB$Exceed Segment Bounds (Read)$BIDS47 4:2830$les bx, [bp+fc]$Thu Ma r 28 20:31:25 1996 **************************************************************************** WFBB had a 'Null Selector (Read)' fault at BC453RTL 1:14ed $tag$WFBB$Null Selector (Read)$BC453RTL 1:14ed$repne scasb$Thu Mar 28 20:31:2 8 1996 - Message rejection does not work during mail file imports and X-forwards. - The editor crashes when you try to "create" a text file that does not exist. - Still has the twinsock related errors. I have helped and talked to others that are using the TCP/IP-winsock interface. Evidently the quirks my system experiances ("can not create socket" and an error when exiting WinFBB) are due to problems with TWINSOCK.... - The BBS tends to hang when it tries to find a C_FILTER when there is other (winsock forward attempt, CRON.SYS processing) activity on the system. To get around this, after the BBS loads up, wait for it to process CRON.SYS. Then wait for all activity to ceased (no disk activity, etc), only then try to log in with F2. - WinFBB crashs when .EXE/.COM PG programs, servers, M_FILTERs, and C_FILTERs are run. - It has been reported that WinFBB will attempt to use FBB forwarding when a station has no [XXX- ] system identification. Evidently there are users out there with outdated personal mail boxes. - Various stations have mentioned that nothing is displayed in the monitor window. Solution: you must have MULTICH 0 for your BPQ channel and M1 in the inittnc1.sys - It has been reported CRON.SYS does not call programs and batch files. - Some stations report lockups (I suspect a .EXE might be invovled :-) - I suspect that the WinFBB editor will strip the "8th bit" from 7+ data when the insert function is used. Doing a SP VE4KV +\FILES.7PL works fine. - N1NFC noted that without a mouse, functions such as selecting a BBS to start a forward to and selecting items with the INSTWFBB program are impossible. - F9 doesn't save and exit in the FBB editor. - NX0R reports: Just had a crash with Wfbb 7.00a I had 3 stations connected forwarding, I was connected via 2m , I had a typo and gave it the command ftfg and it crashed. Here is the info.. . WFBB caused a general protection fault in module WFBB.EXE at 0048:00001ebb. - After Yapp upload from the local console to another FBB system, WinFBB send the SSID to the other system and prompts for it to enter its name instead of - WinFBB produces this error log in Trumpet Winsock: Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (-1) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (-1) by WFBB Error: WSAENOTSOCK (-1) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (-1) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (-1) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB Error: WSAENOTSOCK (4=nil) by WFBB