Migration and life

Life has gotten in the way of my plans to migrate the site in a timely fashion. Luckily, I made time for it today and made some headway. The site is back up and running to a point. I need to restart the whole download repository idea from scratch, but that’s another day/week/month away from now.

I’ll be sending out password resets once the site is further along. For now, you may bask in the knowledge that:

  • 7-Zip finally has a new stable release! version 15.12 came out this past week.
  • BootZilla development is NOT dead, it’s just hiding on a couple flash drives and computers
  • Lots of updates to how the whole toolkit works and updates are in the works
  • Re-teaching myself how to maintain a linux server takes a lot of time
  • SSL isn’t enabled yet – this is the one thing I want to get done before re-enabling user signups and accounts.
  • ???
  • Profit!

Site migration in progress

BootZilla.org is currently being migrated to the new web host. It will take a couple days to get everything going. We’re moving away from an apache backend to a private server running nginx. As such, there’s a handful of wacky issues that need attention before migration will be completed.

As of writing, BootZilla updates should still work, regardless of the state of the site. The few dependencies that BootZilla does not ship with can be downloaded through the normal scripted means — there exists a hidden directory that contains mirrored files that are only accessible via direct linking/downloads – these are already migrated and intact. The rest of the downloads will follow.

Major Changes Ahead!

I’ve begun adding all the tool categories and files that BootZilla grabs to the main site. As time goes on, more and more tools will be grabbed and mirrored on BootZilla’s server, to help keep a local repository with proper documentation for each file. This in turn makes BootZilla not only a toolkit, but also a tools website. In turn, development continues on the toolkit and its various scripts. Several changes have been made in the direction this whole project is taking.

Initially, the idea for BootZilla was an easily update-able toolkit that would require the least amount of configuration from the end-user to operate. Earlier versions of the toolkit provided easy to understand documentation for each tool. That’s still the goal, and going forward with the new mirror direction is going to help a whole lot.

The descriptions for the files on this mirror will be scraped together and used in the final build of BootZilla’s documentation. One of the biggest flaws with the current version of BootZilla is the lack of this critical documentation. This new feature will correct this. Not only that, but it will protect against losing some tools that have gone missing from the internet. There’s a handful of these tools that either are no longer available, or completely removed from their respective author’s sites. If this project is to thrive, these types of problems need to be addressed.

One last bit that this will help with is continuity – some files will obviously be updated from the original author’s sites, but others, like Universal Virus Sniffer, which is currently made available through a self-hosted dyndns site will be mirrored to help the author out. I mention this tool in particular, as it’s the first tool to be made fully mirrored on BootZilla.org. The links will be added when the time is right.

As for the next ‘beta’ — It would make more sense to focus on a final release sooner rather than later. As such, the second version of the CMDLet design will have to wait. A lot of work still needs to be done in order for the toolkit to be considered release-quality. A bit of this work was done over the last weekend. ISO-creation will not be a feature this time around, as employing USB drives seems to be the standard means of using this type of toolkit.

BootZilla will include the awesome Easy2Boot toolkit, which supports booting directly from ISO’s, disk images, and various other neat formats. You can dump in practically ANY ISO, ANY disk image, and have it boot without much fuss. It’s what I personally use to boot Windows Installation media on PC’s – and it’s free, too. It’s written by the same people behind the RMPrepUSB format tool, which will be utilized to help create a bootable USB drive, if the user so wishes, with the contents of BootZilla onboard.

Minor beta update release

Very minor updates to the CMDLets that should resolve a bunch of problems in the last release.

The last release was -ahem- buggy. A handful of tools need to be re-sourced and re-implemented, but will likely have to wait until template2 is fully re-written.

BootZilla Beta 2.1

Just a minor update for the interim. Consider this Beta 2.1.

July 7, 2015 –
Removed Old Timer’s Temp File Cleaner (need to find a mirror)
Removed Amphetamine (URL no longer resolves, tool no longer listed on foolishIT.com)
Updated Display Driver Uninstaller to latest release and fixed URL issue
Updated PeStudio to latest version
Fixed ADWCleaner cmdlet

June 2015 Beta released

I’ve released the latest beta, updated thru June 2015. Lots of small changes, and development changes in the pipeline. Some examples of these changes can be seen in the newer template2.cmd that’s included. More work needs to be done, but at least this has some updates that were needed.

BootZilla Beta – June 2015

The latest beta release with updated CMDLets. There’s a changelog now!

Includes current work on template2, as well as a few other bits and pieces.

Minor update

I’ve done some minor updates and released a stop-gap beta  on the downloads page. Changelog can be found here: https://www.bootzilla.org/sdm_downloads/beta-1-5/

I’m still in the process of rewriting the template that all the cmdlets are based off of. There’s a handful of changes I have planned. I don’t have much time allocated to the project at the moment, due to life and stuff. There’s a few other projects out there that I spend time on, and have been working on learning Arduino stuff in the little free time I devote to hobbies as of late.

Feel free to contact me via the site for any additional tools you’d like to see. I’m planning on adding a few more bits and pieces (bells and whistles) to the kit before it’s considered done. Not to mention some sort of updating functionality, which is still missing – I may decide on implementing a git repository for the cmdlets in the end, so that it can be easily built upon and rebuilt on as time goes on. That, and making the project more public is a good idea in the grand scheme of things. Too many projects like this one are closed source, with all the downloading functionality hidden within either a .NET control, or some proprietary file host that only responds to the client software that the developer pushes. Ideally, all the data that I process into scripts could be all scraped into a database and linked on a single page – which I may end up doing in the end, as a devblog post.

That’s enough words for today I think. I’m running out of time for leisure activities on this weekend day.

Work, work, work…

The months seem to be passing by at an alarming rate. As such, development and refactoring development is going on at a slow pace.  Typically, the cmdlet files themselves that need to be cleaned up and re-written in their entirety are updated as-needed, bi-weekly. For now, I’m going to release a slightly updated set of scripts as another Beta release. Be on the lookout for that soon.

As for update functionality in the future, I’d like to get that in sooner rather than later. It shouldn’t be too hard to get that function written and implemented in the next release. Since development has taken far longer than originally anticipated, it makes sense to postpone the so-called Winter release, and in turn, clean up the current codebase for a Spring-Summer 2015 release instead.

The Spring/Summer 2015 release will include all the missing features from the beta releases so far – Updating, Boot CD, USB image creation, and maybe a few more bells and whistles I can scrape together.

Refactoring towards a release

While tracking down some issues in some of the cmdlets, I came to the conclusion that it may be a good idea to rebuild all the scripts prior to a release. There’s a lot of missing bits and pieces in various cmdlets, which came about due to the nature of the project. Initially, a cmdlet was going to be very simple, but over time, the template became 8kb in size. From here on out, I can either keep the 8kb template and rebuild each script, or extract the necessary bits from each script and strip all comments out so each script is only the necessary bits to grab that particular set of files. In any case, one of these will be needed in order to complete the current release.

There’s also the boot functionality that needs to be fully implemented and utilized.

For the time being, BootZilla is in a ‘refactoring’ period of development. A final build is likely to be out by April 2015.

HTTPS support!

While doing some mandatory domain updates, it was decided to invest in an SSL/TLS certificate for the site, for both security and peace of mind. I’ll be changing to few minor things in the next release to utilize https for downloads from the site. Additional work is being done to make logging more useful, and will likely include the use of Awk in the next release to parse logs for errors, which will in turn give better reasons to users as to why a download may have failed or why an extraction may have ended badly (corrupt archive, for instance).

First release of the new year is now available

After a long hiatus, work has begun on finishing what was started late last year. The latest release is mostly updated CMDLet files, and a few added tweaks to make debugging bad downloads easier to resolve. This release also introduces an internal-use build script that makes it easy to deploy new builds of BZ, so as to stop procrastinating on releases….

Grab the latest update here –