============================================================ CoyoteBack - Coyote Linux Backup/Restore Utility for Windows ============================================================ CoyoteBack Copyright © 2001,2002 Dean Mills Portions Copyright © Blake Ramsdell CoyoteBack is free software. You may redistribute it and/or modify it under the terms of the GNU General Public License, as published by the Free Software Foundation; either version 2, or (at your option) any later version. CoyoteBack is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with CoyoteBack. See the file "COPYING". If not, write to: The Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. INTRODUCTION ============ CoyoteBack is a backup and restore utility for Coyote Linux floppies. Having said that, it could/should/would work for any floppy really, but the idea was to create a utility for backing up and restoring my Coyote Linux router floppies. CoyoteBack was developed using Borland C++ Builder v5.0 Enterprise, but I'm sure it's possible to use other flavors of BCB v5, and perhaps evern earlier versions as well, who knows. Let me know if it does and send me the project files and I'll add it in to the archive. CoyoteBack utilizes methods and code from another free software project, NTRawrite (Blake Ramsdell ) to read and write the image files. Given that, CoyoteBack currently will only run on Windows NT, Windows 2000, and apparently Windows XP as well, although I've not tested it on NT or XP. There should be no Borland dependencies in the executable, but you never know, so if it comes up complaing about a BPL, DLL, etc, send me the error and I'll fix it up. REQUIREMENTS ============ Borland C++ Builder v5.0 Enterprise * Dark sunglasses ** * As stated in the Readme.txt, CoyoteBack _might_ work on other flavors of BCB v5, and even earlier versions of BCB, but watch out, things changed a lot between BCB v3 and BCB v5, it might compile but the results could be rather unexpected :) ** To make the code look better :) COMPILING COYOTEBACK ==================== Dump the source files into a single directory somewhere. Create a directory in that folder named objs, since this is where the project will want to put the object files. Open the project in BCB and check the Options-> Directories/Conditionals and change any hard-coded references to my directory structure to yours. If you change anything, you'll probably want to set the project to Debug until your happy with the changes. In Release mode, don't be alarmed if you get 6 warnings about variables being assigned values that are never used. BCB is lying to you! :) Actually, I just hate leaving uninitialized variables around and had a rather bad experience with a rouge DWORD once, but that's another story! :) * If you do make additions, changes, etc, please send them to me at the address below, I love to see what others do with my crazy code, and who knows, it may just make it into the next release! Wow, just that thought of that sends tingles up and down your spine doesn't it!?!?! :) * As of v1.0.1.0, I've turned off two warning in the projects, the uninitialized variable warning and "Functions containing switches are not expanded inline", the latter of which is generated by Borlands own CSpinEdit control . Turn them back on at your leisure. ** As of v1.0.1.0, I'm including shlobj.h for ShellExecute in formAboutBox.cpp. As any of you who use BVB v5 know, shlobj.h and BCB v5 don't get along too well. I've added the required #define in CoyoteBack.cpp to keep Builder quiet, but once in a while it still complains. If it does for you, simply exit Builder, delete the object files from the .\objs directory and restart the project, it should build fine. BUGS, COMMENTS, ETC =================== Send comments, suggestions, bugs, *pizza, beer, etc, to me here... Dean Mills * One slice at a time, there's a space limit on my inbox :)