Op 15-1-2012 3:56, dos386 schreef: >> [Freedos-kernel] FreeDOS 1.1 released > > COOL :-)
thanks, worked hard for it :) > http://jafile.com/uploads/dos386/freeds11.png I like your style of coming up with screenshots, it clarifies issues quite nicely. I wish VMware's video feature would use standard codecs so something could be posted to Youtube or something. There's other software likely anyway, so no big deal. > Problems: > > - What's the purpose of the menu item "Pasquale" (see top shot) ? It serves as a dedication to the late DOS-C (FreeDOS kernel origin) developer Pat. However if you press TAB there you might find the Isolinux/Memdisk parameters used. If I remember correctly it functions as a hidden way to remaster the ISO, and does so by hiding all physical disks (the "nopassany" on commandline). Unfortunately, this also hides the (El-Torito) CD-drive as it's presented as drive E0 (or F0 or whatever). If there could be a custom modified version of the FreeDOS kernel that doesn't return C:..Z: at boottime, but only at runtime when adding disk drives (ramdisks, usb drives, perhaps some PARSEHDD.SYS based on UIDE etc) I could remove the NOPASSANY parameter and thus keep CD-ROM access intact for ELTORITO.SYS. Right now you're forced to load UIDE driver to gain access to IDE/SATA CD drive (it does hardware detection, doesn't rely on BIOS hooks removed by "nopassany"). Thus, this option is selectable but not intended for end-users. No end-user will select beyond first few options (install, or fdisk to speed up things a bit if already experienced with DOS) anyway. > - It fails to find any HD (see middle shot) In the normal configurations or the dedication one? The copyright one serves as a hidden option to load an ISO file, except that I omitted it for the official 1.1 release (unlike the earlier binary release that Michael Brutman tested and found buggy). It's intended to get rid of CD access times by loading the ISO into RAM. > - Using the menu item "install to harddisk", it starts installing but > hangs at "commandx" (see bottom shot) I don't think it hangs, just takes ages and ages to decompress COMMANDX as it's a big file. For most compatibility, memory managers were disabled. This means kernel and shell are loaded in conventional memory and thus buffer space for UNZIP is tiny, making things take much longer. > - CWSDPMI, VSM, DOSNTLFN, ... are in Yeah I've got reasons for adding them (default \AUTOEXEC.BAT, as well as for running MKISOFS and in my working copy, 7ZDECWAT). > - INFOPAD, 7-ZIP, UNTGZ, HX/HDPMI32, MPXPLAY, FASM, CC386, FREEBASIC, > ARACHNE, ... are NOT in ... what can you do with it when installed ? Nothing much yet, I'll admit that. I wanted to release a basic updated set first, and afterwards add back the Live/Net functionality that 1.0 base had, and yet even later add back most stuff that was in the big 1.0 CD-image. And there's other stuff to add, as you mention already. I'd like to have that PDF reader in at least, and NASM/Openwatcom plus some of Japheth's tools. Finding goals and then finding the most suitable corresponding tools can be quite challenging already. Only imagine all kinds of software related to CD-drives. I've not had much luck with Arache, OBW and Dillo in VMware. ------------------------------------------------------------------------------ RSA(R) Conference 2012 Mar 27 - Feb 2 Save $400 by Jan. 27 Register now! http://p.sf.net/sfu/rsa-sfdev2dev2 _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
