hackyremaster-v3.1.pet
hackyremaster-v3.1.pup
HackyRemaster-v3RC.pup - Release Candidate (now missing...)
|UPDATE| April 8, 2006 - v3RC: Added teminal echos; improved installer; is a Release Candidate.
|UPDATE| April 4, 2006 - v3iv: Fixes many bugs introduced by last versions; adds Xdialog interface; eliminates terminal (can still be seen through a right click on the dotpup); looks spiffy.
|UPDATE| April 2, 2006 - v3iii: Automatically creates loop-back devices when needed and possible.
|UPDATE| April 2, 2006 - v3ii: Functionized scripts; new icons; added readmes to control panel.
|UPDATE| April 1, 2006 - v3i.1: Corrected size calculations.
For those who don't know, HackyRemaster is a way to remaster Puppy. I call it "Hacky" because I hacked it out of Barry's old remaster script, and it wasn't originally very friendly (still isn't, really, but it's much better). I'm working on smoothing it out, giving it more functionality, and making it more foolproof. Rather than wait until I get the whole thing done, I'm going to be putting it up in stages. The "i" at the end of the version is like the lower-case Roman numerals in the begginning of a book. When I finish it, it will be 3.0.
So far I've finished many of the bug fixes I've been wanting to do. The image.gz file is now four to five megabytes smaller than the last version's (bad typo, bad ). It also doesn't delete the filesystem if you try unmounting while rox is open to the directory (bad lack of error checking, bad). This is the stuff I've finished from my To-Do list:
- update isolinux.cfg settings
- add HackyPupBeGone
- fix cleanup bug (Important)
- add ability to use isos in addition to cds
- fix image.gz buffer size (Important)
- integrate burniso2cd
- upgrade integrated burniso2cd to blank cdrw's
My next stage is to put all the little scripts into functions. While I'm in there I'll fix any bugs people find, and clean up some things. I'm also going to add some more error checking. Then I'm probably going to re-do the frontend to be more friendly.
I'm hoping the instructions in the readme will be sufficient. If not, complain so I know what to add to. I'm going to have to re-write it anyways when I do the new interface, so I didn't double check it hard for this release. Knowing what is intuitive or obvious and what isn't will come in handy, though.
So, go ahead and test this. Or don't. Doesn't matter to me. I'll do it anyway, and posting this gives me more incentive to finish quickly, since now I'll feel guilty if I delay.
Also, tomorrow is Tuesday, so as usual I'll be busy writing an essay. Depending on how fast I get done, I might or might not get over here. So don't think I'm ignoring you or anything.