Op 2-8-2011 14:28, dos386 schreef: > Test of "1.1test3" CD : > > http://jafile.com/uploads/dos386/fd11t3.png
Now that's some quite usable feedback, thank you very much DOS386. > > Issues: > > [-3.] many messages running over the screen but too fast to read Yeah file info from LSM files is displayed. Unfortunately the old installer wasn't smart enough to start on a new line after the DESCRIPTION part. You won't see this in the next installer anymore though as it's more limited (not handling individual packages and descriptions anymore, only entire sets). > [-2.] not prominently documented what's going to be installed (for > example "FreeDOS distro 1.1test3 2011-07-10 with kernel 2040 > 2011-06-26 and FreeCOM 0.81pl999 2002-12-31" Good point, not even sure which old INSTALL textfile it is, would have to research that if it's worthwile changing. As soon as the new installer supports 'switch to target directory after installation' I'll swap the old installer out (though I'll have to document the syntax and inner workings for it somewhere as it's pretty cryptic). > [-1.] it does install files (with some luck) but doesn't update the > bootsector, attempt to launch my new FreeDOS ends up > in "NTLDR missing" I'll have to look into how to deal with bootsectors anyway. Right now all SYS actions are commented out with exception for the 'FORMAT a partition from FreeDOS menu'. I'm not sure how to handle this at all. Generating bootsectors of the current operating system, of FreeDOS and of Syslinux all seem like good ideas. Actually writing these bootsectors from saved file to bootsector-area is an entirely different matter, I require a SYS with full capabilities [ described at http://www.freedos.org/kernel/sys.txt ] as is located in A:\FREEDOS\SYS.COM in the 1.0 distro (FDBOOT.IMG). Even then it's a question of 'is SYS simply writing 512 bytes, or is it analyzing the bootsector and patching in geometry data properly?' It's an issue I'm currently experiencing with that ReactOS loader bootdisk and its 16KB clustersize which I fail to reduce (using NFORMAT or FDFORMAT). How do I find a bootsector that I can safely override? I don't know what MS FORMAT puts there by default, nor what FreeDOS FORMAT puts there. In ideal case I could dump the bootsector to disk, followed by a search for 'NO OPERATING SYSTEM FOUND'. Any succesful search of this string and I'd be safe to overwrite. > [0.] (see shot) "no persistent changes possible" is strange That's likely for the LiveCD, and doesn't consider any other FAT volumes in your system (be they floppy, usb flash drives or harddisk partitions). I'll see if I can rephrase this somehow. > > [1.] (see shot) should be "volume" not "drive" (M$-$lang $uck$), what's worse, > it just shows me 4 letters with NO information on them (location of the > volumes, fs (FAT16/FAT28/Former-EX-FAT-64), total size, free space, > existing files or OS, ...), even worse, ot offers me letters > already having > an OS or those having ZERO free space ... It gets mighty interesting to use 4DOS with all of its scriptability at this time, or FDISK /INFO. Ideally you'd see: [Drive:] - [Label] [Total capacity][Used Capacity][Free Capacity] and maybe even some filesystem info (FAT12/16/32), primary partition or logical, etc. > [2.] (see shot) Marginally outdated As mentioned, once old installer supports switching to target directory, I'll use that. Meanwhile everyone can test it already, simply start SETUP with a dummy argument, or a valid directory name which contains the [DRIVE:\DIRNAME]PACKAGES\BASE\*.ZIP structure: D:\SETUP.bat C:\FDSETUP > [3.] (see shot) Subminor text formatting problems See above, i could maybe reformat layout. Otherwise a change in INSTALL.EXE required > > [4.] (see shot) many packages need multiple reconfirmations per piece ??? Numerous ENTER and SPACE required with the old installer indeed. New installer will no longer be bothered by this issue. > [5.] (see crappy shot) about to reboot ... into "NTLDR missing" Ah that's a nice string to search for. I guess Eric's OSCHECK can help a bit as well. > [6.] about the bootsectors, it should tell me what OS I'm about to > kill (as far as guessable) and backup the original BS. Also, it should > tell me about installing onto a non-ZERO'th HD (needs to adjust > BIOS boot settings) or non-ZERO'th partition (needs to adjust the > $80-boot flag in boot sector) I've no idea what that last bit means, but your initial part looks good. I'd assume it's perfectly safe to overwrite/update a FreeDOS installation while having to ask around for the other options. Alternatively I'll be real annoying and simply install SYSLINUX and let its multiboot capabilities sort things out. Thanks for your feedback, the screenshots help quite a lot in visualising what flaws might be experienced. ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
