Forums / Support / Cannot Start BB

Cannot Start BB

by sdavies2720 @
I've been using BinaryBoy happily for a long time, and for a year on this computer. Yesterday when I went to start BB, nothing happened -- no start screen, nothing. Going into Task Manager, I see the BinaryBoy service has started, but no application.

I figured that something was corrupted in the install, so I uninstalled, downloaded the installer, and reinstalled. I also ran a full media scan on my hard disk -- no errors were found.

Still it's not starting. What else should I try?

Steve
 

BinaryBoy's reply to sdavies2720 #17236 @

The most common problem is that a file has been damaged during windows shutdown. In Windows 7 or earlier, click the Start button and type binboy.exe -log
In Windows 8, click the Windows key and type: binboy.exe -log then click the binboy.exe icon that pops up. The log.txt file in the "Documents\Binary Boy\logs" folder will show which file failed to load. You'll need to delete the damaged file.

Typically it's the history file, which is usually stored in C:\Users\YOUR_USERNAME\AppData\Roaming\Binary Boy\binboy.hst or similar location.
 

sdavies2720's reply to BinaryBoy #17237 @

I went ahead and deleted the hst file anyway. Here's what I'm getting in my log:
##-------------------------------------------------
## Binary Boy Log File
##
## Created: Feb 03, 2014 10:44:02:
##
Removing demo components if necessary.
Setting reg path for combo history.
10:44:02: WinMain(): Loading binboy.xml

So I renamed binboy.xml to binboyold.xml.old and reran binaryboy. I got essentally the same thing:
##-------------------------------------------------
## Binary Boy Log File
##
## Created: Feb 03, 2014 10:44:02:
##
Removing demo components if necessary.
Setting reg path for combo history.
10:44:02: WinMain(): Loading binboy.xml
Removing demo components if necessary.
Setting reg path for combo history.
10:47:40: WinMain(): Loading binboy.xml

BB recreated the xml but without any of my login information (which is fine).

Next thing to try?
 

BinaryBoy's reply to sdavies2720 #17238 @

10:47:40: WinMain(): Loading binboy.xml


Is that the last line of the log.txt file or was it edited down? I've never seen a crash there before.
 

BinaryBoy's reply to BinaryBoy #17239 @

A new build with more detailed logging in that area has been uploaded. If you want to try it: http://binaryboy.com/patch.php
 

sdavies2720's reply to BinaryBoy #17240 @

That was the whole log. I'll try to the build.

I guess I feel better that at least it's a more interesting problem ;(
 

sdavies2720's reply to BinaryBoy #17241 @

And here you go:
##-------------------------------------------------
## Binary Boy Log File
##
## Created: Feb 03, 2014 13:35:41:
##
Removing demo components if necessary.
Setting reg path for combo history.
13:35:41: WinMain(): Loading binboy.xml
13:35:41: WinMain(): Constructing xml paths
13:35:41: WinMain(): Loading settings from xml
13:35:41: WinMain(): Backing up xml file xml file
13:35:41: WinMain(): xml file has loaded. Processing settings.
13:35:41: WinMain(): Setting product id.
 

BinaryBoy's reply to sdavies2720 #17242 @

Looks like it's not the xml file causing problems. Which version of Windows are you running and is it 32-bit or 64-bit?
 

sdavies2720's reply to BinaryBoy #17243 @

64-bit Windows 7 Ultimate. Last update (to .net 4/5/1) was 1/29/2014
 

BinaryBoy's reply to sdavies2720 #17244 @

Ok. I don't see the specific problem yet but I've reverted some potentially buggy code in that general area and added more logging in case that doesn't fix it. Build 126 is available. http://binaryboy.com/patch.php
 

sdavies2720's reply to BinaryBoy #17245 @

It's just going to keep telling you it got further:

##-------------------------------------------------
## Binary Boy Log File
##
## Created: Feb 03, 2014 15:54:50:
##
Removing demo components if necessary.
Setting reg path for combo history.
15:54:50: WinMain(): Loading binboy.xml
15:54:50: WinMain(): Constructing xml paths
15:54:50: WinMain(): Loading settings from xml
15:54:50: WinMain(): Backing up xml file xml file
15:54:50: WinMain(): xml file has loaded. Processing settings.
15:54:50: WinMain(): Setting product id.
15:54:50: WinMain(): Product struct set.
15:54:50: WinMain(): Version object created.
15:54:50: WinMain(): Writing title.
15:54:50: WinMain(): Version info finished.
15:54:50: WinMain(): Posting wakeup.
 

BinaryBoy's reply to sdavies2720 #17246 @

Did you ever allow a trial version of Binary Boy to expire on this computer?
 

BinaryBoy's reply to sdavies2720 #17247 @

I see the problem now. There must be a second instance of Binary Boy running. Either close the first instance or run second instance with the following command line: -multi
 

sdavies2720's reply to BinaryBoy #17248 @

It's quite possible that another copy is running -- it never comes up with any screen, so I can't tell if there is one.

I'll restart the computer and try again. If that doesn't work I'll run -multi. Then I'll report back.

Steve
 

BinaryBoy's reply to sdavies2720 #17249 @

Someone asked about running Binary Boy silently at startup. If that was you, try looking in the system tray beside the clock for the Binary Boy icon. It should unhide the first instance.
 

sdavies2720's reply to BinaryBoy #17250 @

Wasn't me but I checked anyway. I don't see it.

I rebooted, checked that the log was not there, ran binboy.exe -log

Computer was working for a second or two (cursor had rotating circle), then the log file showed up in the directory. No sign of Binary Boy that I can see (no startup or other screen, no icon in the task bar, even checked customizations in the hidden icons -- no binary boy listed).

The log file is much longer though:

##-------------------------------------------------
## Binary Boy Log File
##
## Created: Feb 03, 2014 16:29:47:
##
Removing demo components if necessary.
Setting reg path for combo history.
16:29:47: WinMain(): Loading binboy.xml
16:29:47: WinMain(): Constructing xml paths
16:29:47: WinMain(): Loading settings from xml
16:29:47: WinMain(): Backing up xml file xml file
16:29:47: WinMain(): xml file has loaded. Processing settings.
16:29:47: WinMain(): Setting product id.
16:29:47: WinMain(): Product struct set.
16:29:47: WinMain(): Version object created.
16:29:47: WinMain(): Writing title.
16:29:47: WinMain(): Version info finished.
16:29:47: WinMain(): Logging version.


##### Binary Boy v1.97 build 126 running at Feb 03, 2014 16:29:47: #####
16:29:47 WinMain: Checking for outdated comctl32.dll
16:29:47 WinMain: Initializing Winsock 2.2.
16:29:47: Initialized winsock version 2.2
16:29:47 WinMain: Creating Critical Section object.
16:29:47 WinMain: Registering custom windows message.
16:29:47 WinMain: Initializing common controls.
WinMain: RICHED20.DLL loaded successfuly
16:29:47 WinMain: Creating main window classes.
16:29:47: Loading plugins from appdata folder
16:29:47: 0 plugins loaded
16:29:47: Loading plugins from local appdata folder
16:29:47: 0 plugins loaded
16:29:47: Loading plugins from install folder if available
16:29:47: 0 plugins loaded
16:29:47 WinMain: Creating main window.
16:29:47 OnCreate: InitMain()
16:29:47 OnCreate: Setting RAS notifications
16:29:47 OnCreate: Loading RAS DLL
16:29:47 OnCreate: InitUpdate()
16:29:47 OnCreate: Loading settings
16:29:47 OnCreate: Setting Dr. Mime and Dr. Binary log file paths.
16:29:47 OnCreate: InitStatusbar()
UPShowButton(): Already have newer build: 126 >= 124.
16:29:47 OnCreate: Assigning status bar to dialer.
16:29:47 OnCreate: InitToolbar()
16:29:47 OnCreate: InitChild()
Child WM_CREATE called
16:29:47 End: Main WM_CREATE.. Calling BB_LOADFILES directly
16:29:47 Begin: BB_LOADFILES
16:29:47 OnCreate: InitHistoryList()
16:29:47 OnCreate: InitScheduler()
16:29:47 OnCreate: Loading message-Id index list
16:29:47 message-id filename is "C:\Users\Steve\AppData\Roaming\Binary Boy\binboy.mdx"
16:29:47 OnCreate: Loading twit filter rules
 

BinaryBoy's reply to sdavies2720 #17251 @

The reason Binary Boy was shutting down those first few times was because it detected that the Binary Boy window still existed, possibly a crashed version. The log now shows that either twits.txt file isn't loading or your registration info in the registry has become corrupted or is missing. I'll send you information on the registry in an email. If your original email is no longer valid, please send the new one to support at binaryboy dot com.

As far as the twits.txt file, you can rename or delete if from "Documents\Binary Boy" if it exists. I'm guessing it's more of a registry issue though.
 

sdavies2720's reply to BinaryBoy #17252 @

I still use my original registration email.
Thanks for your help!
Steve
 

sdavies2720's reply to sdavies2720 #17496 @

It's me again, once again BB isn't loading and I don't see it anywhere (but after I try to run it, binboy.exe *32 shows up in Windows Task Manager.

I ran binboy.exe -log and this is what I got:

##-------------------------------------------------
## Binary Boy Log File
##
## Created: Feb 03, 2014 10:25:57:
##
10:25:57: Command-line: -log
10:25:57: Checking for duplicate uninstall keys
10:25:57: Checking for old Wise style uninstall key
10:44:02: Command-line: -log
10:44:02: Checking for duplicate uninstall keys
10:44:02: Checking for old Wise style uninstall key
10:47:40: Command-line: -log
10:47:40: Checking for duplicate uninstall keys
10:47:40: Checking for old Wise style uninstall key
10:53:57: Command-line: -log
10:53:57: Checking for duplicate uninstall keys
10:53:57: Checking for old Wise style uninstall key
10:55:10: Command-line: -log
10:55:10: Checking for duplicate uninstall keys
10:55:10: Checking for old Wise style uninstall key
23:43:35: Command-line: -log
23:43:35: Checking for duplicate uninstall keys
23:43:35: Checking for old Wise style uninstall key
23:47:53: Command-line: -log
23:47:53: Checking for duplicate uninstall keys
23:47:53: Checking for old Wise style uninstall key


I'm assuming it's a registry problem again -- I just ran a virus checker that found some spyware that it removed. I'm thinking it messed up BB's registry keys.

I'm still at the same email I registered with.
Steve
 

BinaryBoy's reply to sdavies2720 #17497 @

Check your email for some registry information. Also, that log above is only from the early stages of the startup. Try looking here: Documents\Binary Boy\Logs\log.txt for the full log. You can send the last few lines or the whole thing to support at binaryboy.com if you like.