drivers integration

wardenik
Beiträge: 65
Registriert: 27 Okt 2008, 12:22

drivers integration

Beitrag von wardenik »

depotserver.pdf p.90 section "drivers integration" says about modyfing unattended.txt
when I checked the unattend.txt however, i can see there #oempnpdriverspath# that is being set probably in winxppro.py

so, should I modify it or not?
Benutzeravatar
wolfbardo
uib-Team
Beiträge: 1354
Registriert: 01 Jul 2008, 12:10

Re: drivers integration

Beitrag von wolfbardo »

Hi wardenik
wardenik hat geschrieben:depotserver.pdf p.90 section "drivers integration" says about modyfing unattended.txt
when I checked the unattend.txt however, i can see there #oempnpdriverspath# that is being set probably in winxppro.py

so, should I modify it or not?
Recommended is using
"Simplified driver integration with symlinks"

and not modifying unattend.txt

regards

Bardo Wolf


OPSICONF 2024
https://opsi.org/en/opsiconf/

Basisworkshop Mainz :

17. - 20. 06. 2024


opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.

http://www.uib.de
wardenik
Beiträge: 65
Registriert: 27 Okt 2008, 12:22

Re: drivers integration

Beitrag von wardenik »

whoops, missed that part :D
sorry.

anyway, that works like a charm. But I still have (for an unknown reason) the problem with "setup cannot copy hraidsk1" ...
why the hell is it searching for this.
anybody had that?

thanks
Benutzeravatar
wolfbardo
uib-Team
Beiträge: 1354
Registriert: 01 Jul 2008, 12:10

Re: drivers integration

Beitrag von wolfbardo »

wardenik hat geschrieben:But I still have (for an unknown reason) the problem with "setup cannot copy hraidsk1" ...
mmh, for each Client or some Clients installing winxppro?

regards

Bardo Wolf


OPSICONF 2024
https://opsi.org/en/opsiconf/

Basisworkshop Mainz :

17. - 20. 06. 2024


opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.

http://www.uib.de
Benutzeravatar
j.schneider
uib-Team
Beiträge: 1801
Registriert: 29 Mai 2008, 15:14

Re: drivers integration

Beitrag von j.schneider »

Hi wardenic,

sounds like a problem with an Adaptec SCSI-Controller driver.
Do you get any results if you run the following command?

Code: Alles auswählen

find /opt/pcbin/install/winxppro/drivers/drivers -iname txtsetup.oem -exec grep -Hi hraidsk1 {} \;
wardenik
Beiträge: 65
Registriert: 27 Okt 2008, 12:22

Re: drivers integration

Beitrag von wardenik »

Nope, that's the problem.
I've already checked that...

The problem appears on VMPlayer PXE image and on a standalone machine as well...
Benutzeravatar
wolfbardo
uib-Team
Beiträge: 1354
Registriert: 01 Jul 2008, 12:10

Re: drivers integration

Beitrag von wolfbardo »

Hi wardenik,

seems to be a problem with your
i386-directory.

Whats your source for your i386-Directory ?

regards

Bardo Wolf


OPSICONF 2024
https://opsi.org/en/opsiconf/

Basisworkshop Mainz :

17. - 20. 06. 2024


opsi support - uib gmbh
For productive opsi installations we recommend maintainance + support contracts which are the base of opsi development.

http://www.uib.de
wardenik
Beiträge: 65
Registriert: 27 Okt 2008, 12:22

Re: drivers integration

Beitrag von wardenik »

hmm, I've found that one in i386:

opsi:/opt/pcbin/install/winxppro/i386# grep -ir hraidsk1 *
a320mgt.inf:1 = %FLOPPY1_DESCRIPTION%,hraidsk1,,
aichmgt.inf:1 = %FLOPPY1_DESCRIPTION%,hraidsk1,,
TXTSETUP.SIF:hraidsk1 = 1,,,,,,,303,0,0
TXTSETUP.SIF:hraidsk1 = 1,,,,,,,301,0,0
Benutzeravatar
j.schneider
uib-Team
Beiträge: 1801
Registriert: 29 Mai 2008, 15:14

Re: drivers integration

Beitrag von j.schneider »

You should use an i386 from an original Microsoft Windows XP CD.
wardenik
Beiträge: 65
Registriert: 27 Okt 2008, 12:22

Re: drivers integration

Beitrag von wardenik »

On the contrary.
I have a DELL-prepared windows XP CD that I am using for the installation process with the drivers integrated inside.
The weird thing is that hraidsk1 is there in i386 and in *.inf files and also in TXTSETUP.sif.
but anyway, i get this message.
So, now I'm investigating if opsi is not overwriting TXTSETUP.sif or some other data, that might be the problem
Antworten