4.27.001 - Anyone having problems?

[Guest]

[fracTure]

Yes you are quite correct.  Thank you.

[techNOguy]

I have a problem. I've noticed that for a dual boot setup (Vista and XP), once I install it on XP (E: ) after it has been installed on Vista (C: ), the XP installer deletes the BOClean.dll from the Vista partition's BOClean program folder. I'm not sure if any other files are getting deleted as well. And of course, this deletion disables BOClean. As such, I'll only be able to use BOC on one OS, and perhaps Threatfire on the other. I don't like that Threatfire disables certain functionality without warning (like installing certain Firefox extensions), so I can only hope to replace it with a multiboot capable BOC release in the near future, or that Threatfire does away with its "do instead of warn or provide options" approach in a future release.

[Jrb]

Since I started this thread, I thought that I needed to reply too

(XP SP3, Dutch, IE6; Pentium 4, 3.0 Ghz, 512 MB RAM)

About a week ago, when I came home at the end of the weekend, I saw that 4.27 was released.
I quickly installed the new version (wanting to know how it was).
It completely locked my system, and I had no other option than to put back a backup-image.
In fact I was surprised that it locked my system because (as far as I remember) that never happened and I had already running the test version 4.26 which Kevin released a few weeks ago.

I didn't have the time to try it again.

A day or two ago I installed it again, and now I had more time to do it instead of doing it in a rush.

The new version is now doing OK. Somehow I must have made an error when I installed it the first time in a rush.

I think that I noticed that the initial scan after reboot takes a few seconds more, but it could be that that is only my imagination.

Thanks Kevin and crew !

[Jrb]

An additional note:

In case you had for version 4.26 mutually excluded some apps in BOClean and BOClean itself in one or more of your other security apps, don't forget to check whether you need to make the appropriate changes for BOClean 4.27.

[fracTure]

About a week ago, when I came home at the end of the weekend, I saw that 4.27 was released.
I quickly installed the new version (wanting to know how it was).
It completely locked my system, and I had no other option than to put back a backup-image.
In fact I was surprised that it locked my system because (as far as I remember) that never happened and I had already running the test version 4.26 which Kevin released a few weeks ago.

Totally and completely scares the crap out of me!  BOClean locking up a system?  What a nightmare.  I would do like you did and make sure I had a fresh disk image handy for a system recovery.

So this brings up the question, what process must we follow to upgrade to 4.27?  I forget.  Close down BOClean then uninstall the exisiting version? 

It's been awhile since I upgraded, and most of us have more than a few security applications, most of which have specific installation requirements.  Anyone remember the rather intricate instructions Kevin used to issue for BOClean installs?  Drag and drop something into something else, and so on.

I think that whenever new version updates are posted in a forum, the upgrade instructions should be posted alongside.

[PiCo]

Do you remember Jrb the security applications you used (AV, firewall, HIPS, AS, etc) when the lock up occured?

[Jrb]

The only thing I was trying to say, was that I was too much rushing to upgrade.
That was my fault.
I wished that I had not posted at all ....

[SiberLynx]

The only thing I was trying to say, was that I was too much rushing to upgrade.
That was my fault.
I wished that I had not posted at all ....

Hi Jrb,

Don't blame yourself too much... Your initial request was fine. It was accepted  as you want to know before installation. Why not?
At the same time if you had that locking problem it would be nice to describe that in more details.
Probably there is some specific glitch in install procedure???
How did you performed installation? was it according to the manual?

I am using BOClean for a long time and never experienced anything like that.
For all time of use I had just 2 FPs and an issue with Miro crashing BOC... which was not dramatic because you just restart BOC after the session with Miro. As I said above it looks like that was fixed in this version because it is the same version of Miro I'm having here.

[at] techNOguy

Hi techNOguy,

I thinks that it would be good idea to create a thread with your request.
It can be lost in here meaning that Kevin may find it easily in a new thread and reply.
Many have dual (and more) boots (and other shoes  ) systems nowadays so it will be interesting to report as a problem and get an answer.

My regards

[Kevin McAleavey]

The only thing I was trying to say, was that I was too much rushing to upgrade.
That was my fault.
I wished that I had not posted at all ....

 Sorry for the headache there, have no idea what would cause a lockup though XP does have some memory issues of its own which I will describe over in the "resources" thread ... glad all's better now!

[Kevin McAleavey]

I have a problem. I've noticed that for a dual boot setup (Vista and XP), once I install it on XP (E: ) after it has been installed on Vista (C: ), the XP installer deletes the BOClean.dll from the Vista partition's BOClean program folder. I'm not sure if any other files are getting deleted as well. And of course, this deletion disables BOClean. As such, I'll only be able to use BOC on one OS, and perhaps Threatfire on the other. I don't like that Threatfire disables certain functionality without warning (like installing certain Firefox extensions), so I can only hope to replace it with a multiboot capable BOC release in the near future, or that Threatfire does away with its "do instead of warn or provide options" approach in a future release.

 Sorry about that ... that one's actually occurring in the installer itself, and unfortunately for "good reason" as well as "whoops, didn't expect that." The BOCLEAN.DLL is a critical connection between the GUI pieces and the kernel driver and it's crucial that the correct version of the DLL be in there or BOClean is unlikely to receive notifications from the kernel. So when you go to install, the install portion has been designed over many versions to remove old registry keys, and to ensure that the BOCLEAN.DLL file on the C drive is removed to ensure that an older version isn't somehow left behind. That's why that's happening.

 I haven't done a "dual boot" with two versions of windows since the days of NT ... my method of running multiples has been "disk drive drawers" on my machines, and would insert the drive for what I wanted to boot, so I'm not quite sure of the trick to make that C drive "invisible" to the E drive. I remember that whatever booted once upon a time long ago BECAME the C drive. That's how long it's been.

 We're hoping to FINALLY move along to the long-promised 5.0 version, along with a "Legacy version 4.something" of BOClean for "Older systems. Currently, BOClean has to support everything from Win95 to Vista, and that's getting more and more difficult. I can definitely deal with this when we do an "XP/Vista ONLY" version, but for now about all I can suggest is copying the file from E back to C after doing that install or start with the E drive for install, then do the C which will also avoid that. An unexpected situation and unfortunately, making sure that the DLL on the C drive is cleared before the new version goes in is necessary to ensure the correct DLL (and no others) exist.

[fracTure]

Sorry about that ... that one's actually occurring in the installer itself, and unfortunately for "good reason" as well as "whoops, didn't expect that." The BOCLEAN.DLL is a critical connection between the GUI pieces and the kernel driver and it's crucial that the correct version of the DLL be in there or BOClean is unlikely to receive notifications from the kernel. So when you go to install, the install portion has been designed over many versions to remove old registry keys, and to ensure that the BOCLEAN.DLL file on the C drive is removed to ensure that an older version isn't somehow left behind. That's why that's happening.

 I haven't done a "dual boot" with two versions of windows since the days of NT ... my method of running multiples has been "disk drive drawers" on my machines, and would insert the drive for what I wanted to boot, so I'm not quite sure of the trick to make that C drive "invisible" to the E drive. I remember that whatever booted once upon a time long ago BECAME the C drive. That's how long it's been.

 We're hoping to FINALLY move along to the long-promised 5.0 version, along with a "Legacy version 4.something" of BOClean for "Older systems. Currently, BOClean has to support everything from Win95 to Vista, and that's getting more and more difficult. I can definitely deal with this when we do an "XP/Vista ONLY" version, but for now about all I can suggest is copying the file from E back to C after doing that install or start with the E drive for install, then do the C which will also avoid that. An unexpected situation and unfortunately, making sure that the DLL on the C drive is cleared before the new version goes in is necessary to ensure the correct DLL (and no others) exist.

and...

Thanks guys! Here's where things are going ... 4.25 is about to run out of internal memory space VERY soon and will be taken out before it hits the top. A notice will be given when we reach that time and a week or two later, we will stop updating it.

 4.26 is something we also want to kill off, but we'll give it a little more time. Now that 4.27 is looking VERY stable, we'll want to do that as soon as is practical as well, and everybody is encouraged to move up to 4.27 as soon as it's convenient.

 As to the XVU file version, the data buried within is the same for each (so far until older ones stop being updated) but the coding of the information within is different for security purposes.

 As to the timestamp, the timestamp shown on the screen is the specific actual time when the database was generated for BOClean by our lab. Back in the days when updates were done by FTP, that date and time stamp was within a minute or two of the upload to our servers from the lab because FTP downloads will carry the timestamp of the file on the server. Now that we have to do it by means of a WEB download, the browser library which downloads it does not make note of the date and time so what you see there is the time that the file was downloaded. So the "system date" when looking at the file itself unfortunately has nothing to do with the actual update time any longer since we're not doing FTP updates now. But there's why ...

Asks again...  what process must we follow to upgrade to 4.27?

[Kevin McAleavey]

and...Asks again...  what process must we follow to upgrade to 4.27?

 Good timing! Was just headed out ... the procedure is as follows:

1. Shut down BOClean. If you forget, you'll be reminded during uninstall.
2. If running Win2000 or later, be SURE you're the administrator first (or you might get errors).
3. Run the uninstaller for what you have - either "Add/Remove" on control panel, or "uninstall" from the program group.
4. Once the old one has been cleaned up, then install 4.27.

 We've tried to make it easier than the early days when our customers were IT folks. 

[techNOguy]

Sorry about that ... that one's actually occurring in the installer itself, and unfortunately for "good reason" as well as "whoops, didn't expect that." The BOCLEAN.DLL is a critical connection between the GUI pieces and the kernel driver and it's crucial that the correct version of the DLL be in there or BOClean is unlikely to receive notifications from the kernel. So when you go to install, the install portion has been designed over many versions to remove old registry keys, and to ensure that the BOCLEAN.DLL file on the C drive is removed to ensure that an older version isn't somehow left behind. That's why that's happening.

 I haven't done a "dual boot" with two versions of windows since the days of NT ... my method of running multiples has been "disk drive drawers" on my machines, and would insert the drive for what I wanted to boot, so I'm not quite sure of the trick to make that C drive "invisible" to the E drive. I remember that whatever booted once upon a time long ago BECAME the C drive. That's how long it's been.

 We're hoping to FINALLY move along to the long-promised 5.0 version, along with a "Legacy version 4.something" of BOClean for "Older systems. Currently, BOClean has to support everything from Win95 to Vista, and that's getting more and more difficult. I can definitely deal with this when we do an "XP/Vista ONLY" version, but for now about all I can suggest is copying the file from E back to C after doing that install or start with the E drive for install, then do the C which will also avoid that. An unexpected situation and unfortunately, making sure that the DLL on the C drive is cleared before the new version goes in is necessary to ensure the correct DLL (and no others) exist.

Thanks Kevin. I appreciate your detailed response.

I haven't tried simply copying the BOClean.dll file from E to C because I didn't know if any other deletions or modifications were made or if the file would be compatible. Also, I don't know how the deletion was implemented so I just figured installing on E first and then C would again result in the non-used BOClean.dll from being deleted. But I'll give it a shot. No other files beside BOClean.dll are being removed/modified, correct?

Edit: I recall that during installation of BOC in XP, the installer did properly (automatically) detect the appropriate drive to install itself on (E). Perhaps you can modify the installer to check for previous files only on the same auto detected partition, or to warn and query removal if it detects files outside of that partition?

Edit2: I went ahead and uninstalled BOC from Vista, installed on XP, and reinstalled on Vista. Everything seems to be working okay now. Both program file directories seem to be identical in size so hopefully there aren't any other missing/modified files to be worried about. Thanks.

[Kevin McAleavey]

Thanks Kevin. I appreciate your detailed response.

I haven't tried simply copying the BOClean.dll file from E to C because I didn't know if any other deletions or modifications were made or if the file would be compatible. Also, I don't know how the deletion was implemented so I just figured installing on E first and then C would again result in the non-used BOClean.dll from being deleted. But I'll give it a shot. No other files beside BOClean.dll are being removed/modified, correct?

Edit: I recall that during installation of BOC in XP, the installer did properly (automatically) detect the appropriate drive to install itself on (E). Perhaps you can modify the installer to check for previous files only on the same auto detected partition, or to warn and query removal if it detects files outside of that partition?

Edit2: I went ahead and uninstalled BOC from Vista, installed on XP, and reinstalled on Vista. Everything seems to be working okay now. Both program file directories seem to be identical in size so hopefully there aren't any other missing/modified files to be worried about. Thanks.

 Once again, sorry about that ... unexpected situation ... have already made notes to myself in the code for the installer to see what I can do to prevent that in the next build! Over the years, we had a lot of folks who would just go to the program folder, delete the files, and then complain about "leftovers" and that's why we built that "cleanup of the old" into the installer ... you did something I hadn't originally expected. Whoops! 

[dwax]

When did the version 4.27.001 come out? And what changes are there compared to version 4.27.000 thats what I have,4.27.000

[Tags:]