TIP: Click on subject to list as thread! ANSI
echo: bluewave
to: James Bradley
from: Dale Shipp
date: 2008-04-13 00:31:02
subject: Re: BlueWave in Linux/DO

-=> On 04-12-08  18:08,  James Bradley <=-
 -=> spoke to Dale Shipp about BlueWave in Linux/DOSBOX <=-

 DS> I have a new little computer for travel (Asus EeePC) which has a
 DS> version of Linux on it (Xandros).   I am trying to get BlueWave to
 .......
 DS> If I open a QWK packet, read messages, and change the marks on those
 DS> messages, the changes get recorded in a file called OWL.XTI (QWK
 DS> packet is OWL.QWK -- and it is unpacked into a WORK directory).
 >

 JB> What happens if you leave the files unzipped in bw/work, after making
 JB> OWL.REP? IOW, does BW blow out an existing OWL.REP? (I'm 

   Does not seem to have any effect on OWL.REP.

   A person on a DOSBOX forum has done some experimentation and isolated
   the problem -- *AND* issued a file to fix it using ASM compiled into
   a .COM program.   Here is a quote of what he said:
--  begin quote --
The problem was easier to find with the DOSBox debugger than I thought
it would be. Blue Wave appears to have a flaw where it uses the DOS
"FindFirst" function INT 21/4E with a malformed filespec. Using the
example mail packet the program comes with, it tries to find
"C:\BWAVE\WORK\WELCOME.XTI*.BAK". MSDOS 5/6 and the WinXP NTVDM are
unforgiving and return error code 3 (invalid path), leading to a benign
result. DOSBox is more lenient, and finds the "WELCOME.XTI" work packet,
which the program proceeds to delete. Maybe the intent was to clean out
.BAK files in the work folder; but that seems redundant because the
program deletes *.* from there when it finishes recompressing the
packet. It's probably just a mistake that wasn't noticed until DOSBox
shed some light on it.

I adapted a little interrupt watchdog program to work around this
situation in DOSBox. It monitors the FindFirst function, and if it sees
a filespec with an extension of XTI* it will override with an error code
3 result. Run BWAVEFIX.COM from the BWAVE folder; it runs BWAVE.EXE as a
child program. The child exit errorlevel is reflected through the
parent, and the parent command line is given to the child, so the
program is friendly to batch files. Assembler source code is included in
the attached archive.

BWAVEFIX.ZIP (1.55kB) - Downloaded 4 Time(s)
 -- end of quote --

  If any of you want the file, go to
 
http://vogons.zetafleet.com/viewtopic.php?t=18242&postdays=0&postorder=asc&start=20

                               Dale Shipp
                  fido_261_1466 (at) comcast (dot) net
                              (1:261/1466)


... Shipwrecked on Hesperus in Columbia, Maryland. 00:38:53, 13 Apr 2007
___ Blue Wave/DOS v2.30

--- Maximus/NT 3.01
* Origin: Owl's Anchor (1:261/1466)
SEEN-BY: 10/1 3 14/250 300 34/999 90/1 106/1 120/228 123/500 134/10 140/1
SEEN-BY: 222/2 226/0 236/150 249/303 261/20 38 100 1381 1404 1406 1410 1418
SEEN-BY: 266/1413 280/1027 320/119 396/45 633/104 260 267 285 690/682 734
SEEN-BY: 712/848 800/432 801/161 189 2222/700 2320/100 2905/0
@PATH: 261/1466 123/500 261/38 633/260 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™.