Update: 2.1.0

Fixes a few bugs and crashes with the program. Stop button is actually usable.

update: Version 2.0.0

It's been a while, but I finally decided to release the latest version of BCSearch. This version incorporates quite a number of new features. The intended "actionfilters" functionality is disabled currently (you may uncomment the appropriate portions of the Menu XML file to re-enable the feature) I also added an easter egg that I'm sure will be quite amusing to those who find it.

I also added the "simple" filter mode. At the moment it provides a file mask and the ability to use a regular expression for that file mask in a search, but that's it.

I also added a splitter bar that splits the upper and lower panes and allows one to size them as desired. No doubt this has added about 500 new bugs to the program.

When trying to create a working setup, I found issues whereby the program crashed on Vista nad earlier but crashed on XP. since I haven't yet tested this on 2000, it's fully possible it still crashes there, as well. I managed to hunt down the problem (or more precisely, I haphazardly changed things until it seemed to work) and it no longer crashes on startup.

update: Version 1.9.00

This version has seen the squashing of several listview related bugs, culminating in a major "fix" for the VBAccelerator listview. Technically, the way it was originally allowed for a few predetermined sorting modes. Since BCSearch "formats" the size data as KB MB, and so forth, sorting numerically on that column would not be desirable. What I was doing was placing the size in a certain "itemData" field of each listitem. This worked. Except that itemData cannot hold a number larger then around 2 billion, or about 1 GB. files larger then this still displayed properly, but the overflow error meant they were sorted as 0. I popped open the VBAccelerator ListView control and plopped in a new Event for custom sorting, which I now use for the size column. (not the size on disk column, which is simply something I forgot until just now.

Note: Some users have reported errors regarding already present copies of dll and ocx files the installer tries to copy. Any OS that has System File Protection (2000 and up) should have the proper versions of these files already installed- therefore, this error can be safely ignored.

UPDATE: Version 3.4.2: no longer chokes on quoted filenames. tidied up /h output.

DirectSound was a tough one; the main reason I decided to switch was that, for some reason, I was causing playsound() to leak. This often ended up with my audiodg.exe process consuming over 4GB of RAM whereby it should only get around 10 or 12K.

Update, Version 1.1:

Fixed a bug that broke function parsing. Not sure how I missed it the first time.

ANOTHER Update:

BCDodger is a simple game written in C#. Your mouse controls a group of spinning objects, which represent your possumist comrades. You must move them to protect them from the flying mercedes logos, which represent various features of mercedes automobiles.

When a mercedes Logo touches a possum follower, it converts that possum follower to the dark lord mercedes, and you lose them as a comrade.

It might be best to not have a story....

To run this, run the EXE in the "debug" folder (BCDodger\BCDodger\Bin\Debug\BCDodger.exe)

This is because I'm lazy and all the resources are in that folder.

the code already supports an APPDATA folder containing said resources, but that would mean there is an installation step, and at the moment I'd rather not have to deal with the woes of MSI installers.

Also: I recommend running the "demo" (from the file menu) before you play a game. if you play a game, get game over, and then play the demo, the background stays red and the timing is off. (easy fix, but I figured I had been postponing releasing it for long enough).

UPDATE: Thanks to Tux2 (of http://www.jrtechsupport.com/) there is now a Mono compatible version. This can be downloaded here.

The main reason changes were required was that I opted to use a sound library that is only works on windows. More annoying is the general lack of sound support in the otherwise pretty complete .NET framework (to my understanding .NET 4 adds Sound capabilities). Oh well.

BASeCamp JobClock is an Application- or, rather, a suite of applications, that facilitates the management of employees in a Assignment-based scenario. Examples of such a situation includes repair shops or IT departments. It is designed for use in a moderately distributed scenario, where one person- or a small group of people- add jobs to the list of those that need to be done. Employees/techs then sign in to work on those tasks, and clock out when their work concludes. This allows for the tracking of how much time is spent on a given task by each employee as well as how many man-hours went into the task in total, for use in billing. It consists of three parts: the Administration program, which is used for management of users, orders, and general database maintenance. A "Monitor" program, designed to be used for a supervisor to keep track of when techs are available and who is working on what, as well as what Jobs require attention. lastly, the "Client" Application, which is designed for use on a touchscreen system, allowing employees to enter their own ID to clock into and out of a given order. Orders can be scanned (via a barcode reader that uses keyboard input) or 'typed' using an on-screen keypad.

BCDodgerX is my "rewrite" of the older BCDodger. BCDodger was my first serious foray into C# Programming and .NET, and it has a lot of issues. Since I hadn't dealt with XNA much and the concept of the game was simple, I decided I would rewrite it using XNA. I originally started it in XNA 3.0 with VS2008, but at some point swapped over to VS2010 and XNA 4.0, even though I don't use any XNA 4.0 features to my recollection. Oh well.

The "Installer" program is actually a self-extracting executable which extracts the files that were created from the XNA publish tool and runs the XNA setup program.

• Requires the .NET framework, version 4.
• Resolution is "locked" at 800x600. This will be an option. Eventually. main issue is that different sizes could change the difficulty, though.
• High scores are saved. The High-Score handing is done by the exact same code that handles High-Scores in BASeBlock, but some of the features (such as managing different score lists which is used for levelset-based handling in BASeBlock) are not used. The highscore file can be found in %appdata%\BCDodgerX.
• Since I haven't dealt with XNA before I'm not 100% sure what is needed to properly install it, so I just used the XNA publish tool.

Where we CAN fix the broked stuff Is your computer giving you the "Blue Screen of Death"!?
Do you have viruses?
Do you need to know how to use a program for that Boss presentation tomorrow?
Wanna have a nice shiny website, but don't want to pay a fortune?
Just wanna know how to turn the blasted thing on?!
You have come to the Right place!