RE: [BPQ32] BPQ32_410f_2008Nov19 Just released!
What I noted looked like normal installation… I did not shutdown BPQ32.. I installed it and after it said I needed to reboot….
Which is what I would expect with BPQ32 running… So that the files could be placed over the old ones..
So after reading your alert I did some tests…
If I shutdown BOQ32 it would not require a reboot. If I did not.. a reboot was always required.. After each install everything has always appeared to be working correctly..
I may be dead wrong… I have been very busy… But had to at least test that much..
What I did not do is try to see which versions were and were not copied???
Maybe I can do that this weekend…
73 jerry n9lya
From: BPQ32@yahoogroups.com [mailto: BPQ32@yahoogroups.com ] On Behalf Of Ron Stordahl N5IN
Sent: Wednesday, November 19, 2008 5:14 PM
Subject: [BPQ32] BPQ32_410f_2008Nov19 Just released!
Perhaps so much fanfare is unwarranted as the only change from the
release of 48 hours ago is that I have added documentary changes to
the installer and installation document warning about the necessity of
closing BPQ32 before attempting an update. This 'hitch' has always
been in the installer, but the first KNOWN trip up occurred yesterday.
In brief, you must be sure BPQ32 is closed before you do an update.
Now that more application programs are available which themselves
start BPQ32 it might not always be obvious that BPQ32 is running.
That little 'BPQ' in the notification area, it's located on the lower
right hand bottom of your screen, is a clue that BPQ is alive!
You must close all such applications that themselves start BPQ32 as
well as any BPQ32 utilities such as BPQTerminal, AGWtoBPQ,
BPQTelnetServer, etc before proceeding with running the installer to
update your current version.
Should you fail to heed this warning, all is not lost. You need only
reboot your system, close BPQ32 as you should have as described above,
and rerun the installer. The update will be correct and nothing will
be lost other than your time.
I intend to add code to the installer to test for a running BPQ32,
issue a warning and abort without making any changes. This will take
a bit of study to accomplish.
The links on the BPQ32 Yahoo Group home page are to the 2008Nov19 version.
Ron Stordahl, N5IN
The reboot message is an indication that bpq32.dll in the system folder was assigned and could not be replaced. A replacement to the new dll was queued to be performed after a reboot as you observed. However there are other, non system folder files, which could be assigned and would not be replaced even though they are in need of update.
So you should be sure BPQ32 is cancelled, then rerun the installer just to be sure. Your configuration files will not be lost.
In the future I will add code to the installer so it will warn and not do an update in the instance when BPQ32 is still active.
I would recommend that everyone who has updated in the past, but is not positive that BPQ32 was closed, should run the installer again with BPQ32 definitely closed down. That is the only way to guarantee a consistent file set.
- Ron Stordahl N5IN wrote:
> Perhaps so much fanfare is unwarranted as the only change from theHi Ron and others,
> release of 48 hours ago is that I have added documentary changes to
> the installer and installation document warning about the necessity of
> closing BPQ32 before attempting an update. This 'hitch' has always
> been in the installer, but the first KNOWN trip up occurred yesterday.
A question that is not related to this particular version, but ...:
Recently I realized that I have some issues with BPQ+FBB under WinXP
that do not happen under Win2k (the same type of installation both).
Well, regardless BPQ32 is already active or not, an activation of FBB
causes opening a small window entitled 'Program to hold BPQ32.dll in
memory' (that does not happen uder Win2k). When I close FBB manually
that window does not close. When I re-start FBB again (or after the
housekeeping), another window entitled 'Program to hold BPQ32.dll in
memory' appears, so they are two, etc.
Besides that, after some 5-10 minutes of telnet forwarding via the
Internet, it seems that FBB somehow loses its dirmes.sys file and asks
me if I want it to create another one (which, again, does not happen
under Win 2000). But whatever I answer (Y/N), in the next minute or two
the bbs failures and closes. After the next activation, it starts with
an empty dirmes.sys file, so the number of available messages is set to
Any explanation of those funny things? Btw, my WinXP and Win2k is a
dual-boot system, where each of them have their own installation of
BPQ32 (C:\BPQ32 and D:\BPQ32 respectively), as well as their own
installations of FBB, (though they share FBB's system files on D disk,
which is W2k's FAT32 partition). Btw, generally speaking, what folder is
better for BPQ: ..\Program Files\BPQ32, or in the root of a partition
(like C:\BPQ32). Under W2000 I can start BPQ32 from within
non-administrative account but under WinXP it asks for admin. rights to