drivers integration
drivers integration
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?
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?
Re: drivers integration
Hi wardenik
"Simplified driver integration with symlinks"
and not modifying unattend.txt
regards
Bardo Wolf
Recommended is usingwardenik 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?
"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
Re: drivers integration
whoops, missed that part
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
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
Re: drivers integration
mmh, for each Client or some Clients installing winxppro?wardenik hat geschrieben:But I still have (for an unknown reason) the problem with "setup cannot copy hraidsk1" ...
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
- j.schneider
- uib-Team
- Beiträge: 1801
- Registriert: 29 Mai 2008, 15:14
Re: drivers integration
Hi wardenic,
sounds like a problem with an Adaptec SCSI-Controller driver.
Do you get any results if you run the following command?
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 {} \;
Re: drivers integration
Nope, that's the problem.
I've already checked that...
The problem appears on VMPlayer PXE image and on a standalone machine as well...
I've already checked that...
The problem appears on VMPlayer PXE image and on a standalone machine as well...
Re: drivers integration
Hi wardenik,
seems to be a problem with your
i386-directory.
Whats your source for your i386-Directory ?
regards
Bardo Wolf
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
Re: drivers integration
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
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
- j.schneider
- uib-Team
- Beiträge: 1801
- Registriert: 29 Mai 2008, 15:14
Re: drivers integration
You should use an i386 from an original Microsoft Windows XP CD.
Re: drivers integration
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
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