Hi, sorry for replying the same thread twice... Thanks to Bernd for the very verbose testing and pointing out so many corner cases, impressive :-)
>> * Suppose I'd be a complete newbie to DOS: how do I know what to type >> there? (a.k.a what's valid input). >> * Absolute paths required? Relative paths seem to be supported, in which >> case there's attempts to create subdirectory structure in current >> directory. Which won't work ofcourse from cdrom >> * Path isn't checked/created before starting unzipping, depending on >> UNZIP itself instead to create directories? Or rather you're not >> returned to initial inputfield. >> * Try typing NUL into that field >> * Try typing C:\DUMMY\FDOS in there if C:\DUMMMY doesn't exist > > For the above: I'm thinking about simplifying the input even further, > asking for just the install *drive* and not a a full path. We can > assume installing to \FDOS (such as C:\FDOS). How about accepting both, and assuming a default directory name when only a drive letter is given? Then you still give the users freedom to call FreeDOS DOS, FDOS, FREEDOS etc. Of course that will need some checks - the target must not be a device or file, the target directory must exist or be createable, it must be writeable, the target drive must be writeable, existing and preferrably FAT (otherwise no SYS) and it should have enough space and fully use 8.3 syntax. > I'll add some level of confirmation of values before installing, and > an easy way to "gracefully" abort the install if the user chooses to. Thanks :-) >> SCREEN: DONE >> * No input on how to proceed/finish (pressing any random key?) > > I will add a "press any key" message. I'll borrow the NLS string from > the CHOICE program. Depending on what happens next, INSTALL could exit with a big (visible from across the room) and nice message without wait. > But I wonder if anyone really installs FreeDOS from floppies in 2011? As said, not many, and those can XCOPY a floppy distro or read a howto for mounting a DOS ISO which they downloaded directly to their FAT partition from within Windows anyway for the case where booting is the only part using floppy. >> * INSTALL expects/assumes user has validated that the input is >> 1) a directory (try C:\KERNEL.SYS as input if it exists as file) >> 2) on an existing driveletter >> 3) on a drive >> 4) FAT12/16/32 >> 5) with enough free diskspace >> 6) valid input Makes sense for INSTALL to check all those for the target. >> Question: can PACKAGES\subdirs\*.LSM now be deleted? Install doesn't >> give descriptions anymore of individual packages anyway. > > Correct, the LSM files are no longer required. Actually I liked knowing the version numbers of everything that way, but one file which concats all LSM info will be fine for me, saving lots of cluster overhead space compared to using many separate tiny LSM files. Probably INSTALL can have the LSMs in the package ZIP but copy the text to a big file and remove the individual ones after installing... ;-) >> scripting possibilities for: >> 1) source directory >> 2) destination directory >> 3) automation (accepting source input by default, and finish last screen Sounds useful. >> 3 seconds or so after being all done) Not useful imho. >> 4) /ALLSETS or /BASEONLY ; /NOSOURCE ; /QUIET Shrug. >> Yes, usable, will integrate it. Thanks for the work so far. >> (and I'll throw UPX over it to reduce size of binaries) > > If you do, please use UPX-UCL instead of NRV. Nice idea :-) Eric ------------------------------------------------------------------------------ AppSumo Presents a FREE Video for the SourceForge Community by Eric Ries, the creator of the Lean Startup Methodology on "Lean Startup Secrets Revealed." This video shows you how to validate your ideas, optimize your ideas and identify your business strategy. http://p.sf.net/sfu/appsumosfdev2dev _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
