Re: [Unattended-gui-users] bug in the 01install

[Mario G. <mar...@te...>]

Am Mittwoch, den 20.12.2006, 12:10 +0100 schrieb Juan Jose Pablos:
> Mario Gzuk escribi=F3:
> > Thank you for this report. Its up to date in svn. Are the profiles
> > working for you? Any other hints?
>=20
> I have not got time to test the profiles stuff. I know that it uses the=
=20
> old method. As soon as I can, I would test the profiles.
>=20
> I am testing this new stuff in this barebone:
> http://eu.shuttle.com/es/DesktopDefault.aspx/tabid-72/170_read-13029/
>=20
> The issue I have is that I am able to install the system when in the=20
> bios I change the sata hd to ahci instead of IDE.
>=20
> When the  windows instalation start the process stops because is not=20
> able to lod a AHCI driver, I added on the $oem$/$1$/ directory, but=20
> still fails.
>=20
> I am able to start the process if in the bios setup I change from ahci=20
> support to IDE.
>=20
> My solution would be to force the IDE mode for this system, but I do no=
t=20
> know how.
>=20

So the current state is that the bootcd is not working with the IDE
setting? Have you try the forcemodules=3Dyes
(http://unattended.technikz.de/index.php/Bootcd:options#forcemodules)
kernel option?

If you want to add the driver to the text mode setup you have to do some
other steps to. You might want to search the internet with the keywords:
txtsetup.oem or txtsetup.inf or "windows txtsetup drivers". Maybe you
find a howto in your language ;-)
The $oem$\... has also some limitations (And it is ONLY for the GUI
installation part of your windows installation). If you need help here
let me know.

greetings mario