> I have several questions: - I have a small problem - when I change my > password to lenght about 8 characters, then instead: (15 seconds...) boot > I receive something like that: (15 seconds. boot Is there way how to > correct it? - What should I edit to change to reduce the time for waiting > before selecting default video mode and where edit the message about it Um... I hadn't thought this through, I'm surprised you are the first to hit it. The settings.s file is *both* executed as a script (to set the password, for example), *and* is the lilo message file. Well, when you edit the lilo message file, you have to re-run lilo, since lilo puts the actual sectors and length into the boot map file. So, you really should run unpack.s/buildit.s which will re-run lilo, or else delete enough that it is the same length. There is no way without re-running lilo to tell it that the message file is different. The lilo config parameters are in the buildit.s file, you could extract those into a lilo.conf file and just re-run lilo without running all of buildit.s, if you are comfortable with that. The video selection pause thing and its message may be hard compiled into the kernel source. You can change the time it sits at the "boot:" prompt by editing the lilo configuration in buildit.s, but the actual 30 second wait for video selection and the message are probably in the kernel source. You can disable it or force selection of a video mode via lilo. > (Press <RETURN> to see ....) - Where can I download rawr1722.exe > (anonymous access isn't allowed to ftp.clark.net) or could you send it to > me, please? Thank's No. It does not exist. There is no rawr1722.exe, because fdform18.zip never worked correctly, so I abandoned that approach. You will have to get rawrite2 and edit the source code to check for 21 sectors before it checks for 18 sectors. I am happy to say I abandoned rawr1722.exe so successfully that it no longer exists. The problem, you see, is that before you can rawr1722, you have to low-level format to 1722, which I used to do with a dos fdformat in fdform18.zip, which I didn't write, which never worked, and caused all kinds of support headaches. Since there is no way (especially under windows???) to reliably format a floppy (low level) to 1722, I dropped and removed and denied the raw writer. The good news is that it is easy for you to fix rawrite to do it, as long as you are warned that that DOES NOT do a low level format, feel free to do it. I will not be distributing rawr1722.exe in any form or under any conditions, because I think it is a flawed approach compared to my current installer process. Besides, given that the current approach works better,_why_ do you want it? -Tom
