On Tuesday 24 April 2007 11:05:16 Jordi Massaguer i Pla wrote:
I am asking you some testing and feedback about it.
You can download the
latest builds from:
Sascha and me have done some basic testing of your test builds. instlux works
quite well so far. We can also verify that it is working for SATA harddisks.
We discovered only some minor issues:
#1 Find Windows partion
find --set-root /autoexec.bat
This would break on several windows installation on different partions. Even
on windows installation which don't have a "autoexec.bat" file in place. (At
least one box i tested with a vendor customized Windows XP doesn't have one.)
We enhanced your nsis script so it create a "stamp file" to mark the Window
partition which triggered the instlux installation:
find --set-root /instlux-hitme.txt
... should be very unique :)
(Feel free to rename the file in something more unique)
Updated the German translation ... not quite sure about the quality of the
other translations. Maybe you should make a call for proof reading.
#3 Use system screen resolution and selected language
instlux should now start the installation in the user chosen language. The
installation system gets booted with vga=0xXXX parameter and splash=silent.
The screen resolution from the Windows installation is used to determine the
vga value. For some reason the splash screen is not working .. but i guess
your initrd is customized and not the original one - right?
The nsis system plugin is required to get the system resolution
TODO: Some languages aren't handled yet in the nsis script.
#4 instlux grub - timeout 0
The grub of instlux boots know the installation immediately. No need to bother
the user two times with different boot managers.
#5 Check minimum amount of RAM / Harddisk free space (TODO)
For the network installation builds instlux should check if the minimum amount
of RAM is avaliable. If not instlux should give a warning. Maybe we could do
something similar to check if enough harddisk space is left and give
#6 make_instlux.py changes
Don't call makensis with absolute path, my version is very very customized.
Maybe we should provide a nsis package with all the required plugins in the
All changes are attachted as patch from the latest revision of SVN. I hope you
could commit them upstream. Beside the background color change to #7ac142
this should be still distribution independent...