Hi Eric, 2006/7/31, Eric Auer <[EMAIL PROTECTED]>: > > Hi Aitor, > > > (3) Once I create the partition with FDISK under WMWARE, I get the > > "usual" message: Partition signature != 55AA > > and PC locks. I have to FORMAT and SYS manually to avoid this. > > It took a while to find that string, but basically it means > that you did something like FDISK /MBR - because the message
Well, in that case INSTALL did this for me, which is OK. I just say it is a bit surprising for the user to come up with this message. > is from MBR code version of our FDISK - and then tried to > boot from harddisk, from the marked-as-active/bootable but > not-yet-formatted DOS partition. I would vote them for replacing the message with "Attempted to boot from an unformatted partition" > > (4) I can't remember the reason why the graphical installer was > > abandoned. We get to the old text installer, and get to the usual > > problems or uneasiness: > > The GUI installer worked pretty unstable and needed a 32bit CPU > with floating point unit and quite some RAM. Plus it cloned the Wrong, if a floating point is not present, it is emulated. However I thought there was a code to load the test installer if the computer is below 386 or did not have enough memory. > installshield looks and had a klikthru GPL thing which was > nonsense and raised wrong expectations... Raised wrong expectations? > > (4a) When a package set is required, it simply asks me to press a key, > > not very intuitive > > (4b) I wish there was an option which says "install everything" and never > > asks > > Not sure what you did, but only the "custom" option should ask > anything... When I installed the smallest CDROM, I just selected > "all base binaries" and then all unzipping whooshed by in FDPKG. I meant doing a FULL install of EVERYTHING. > > (4c) I get random failure when installing packages. I couldn't find a > > common feature. It might be that they are using the CD-ROM driver > > which has some kind of bug. > > Did you boot from CDROM? Then it would be a bug in ELTORITO or > in SHSUCDX. I could not boot from CDROM, so the problem would > be XCDROM related, but then, it did work fine on the 2nd attempt. I did install from the CD-ROM, yes. > > (4d) Suppose I cancel the install (e.g. I am tired of waiting till the > > VI runtime library gets installed and reboot). I press reset and > > there's no way to run POSTSET or POSTINST... > > Actually the whole sys / copy appropriate localized freecom / > create config and autoexec / ... thing happens as the very > last step before rebooting. This is done to delay making the > previous operating system unbootable as long as possible... > Or, of course, "moving" that system to a menu option, in the > case of a boot menu install. I am not saying to do it earlier. I just say: how about installing this all as the FIRST package? > But... That is about aborting install... What you mean are > the things which happen after the first reboot after DOS > is more or less completely installed: The POST... scripts. > I think I also had similar problems to yours - postinst and > postset trying to run things which are not in the default PATH... This makes sense, yes. > > (8) INSTALL never asked me about my keyboard configuration: thus > > I get no KEYB (but curiously enough with CP 858) > > The installer has a big language / country selection menu > which sets all of that... But for example the livecd did > not have a keyboard menu - when I checked the small livecd. > > At the moment, I would have to use the maximum cdrom with > all sources and stuff which would take far too long to > download. I hope the livecd will be available in the > "base with sources" cdrom again. The big livecd could > be moved from "full with sources" to "full binary". I was using the biggest available CD. I remember being asked that BEFORE installing the system. I just thought I would be asked that just as postinst or something like that. I remember Joe or Bernd did that in previous versions and it was nice. > > (11) CWSDPMI was NOT configured, even if I was requested to in the > > post-install. > > Why does cwsdpmi need a configuration? Just put it in the path... The problem is that I was asked if I wanted cwsdpmi, but then I didn't see it in the path automatically. Or perhaps it was just asking me if I wanted to have it installed. In that case, Blair, how about adding this line?: ECHO "CWSDPMI -P" >> AUTOEXEC.BAT The problem is that it could be added several times, so there should be a way to control that (maybe through environment variables). Aitor ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Freedos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freedos-devel
