Jordan Share wrote:
Rather than change the config files (if that is indeed what you need to
do), you might consider changing the IP addresses handed out to the
various MAC addresses. pxelinux.0 will get its config file based on
what IP address it was given. So you could dynamically
Jordan Share writes:
Patrick J. LoPresti wrote:
He asked a question about dealing with .dll files; I have tried the
method documented in KB275334 and it seems to work:
http://support.microsoft.com/?id=275334
It should be possible to automate these steps, but not at install time
Dag Nummedal wrote:
Jordan Share writes:
I'd like to find out if anyone has a pointer to the breakdown of what
each numeric code means.
The destination is defined by the [DestinationDirs] section in the inf file.
You can find the information you're looking for here:
Hi,
For number 4, I have a small hack in install.pl that replaces the tftpboot
file from booting from the network to booting from the local disk.
It does this once the machine has repartitioned etc, right before it starts
to copy files.
Brad
-Original Message-
From: Max Lovius
Hi!
Im currently also looking into a completly unattended installation for
our local schools.
The idea is that a teacher or student should be able to reboot the computer
and reinstall it by choosing INSTALL instead of LOCAL from the pxelinux
prompt.
My idea for a solution is to have a
Title: Message
I wrote a script
that use Unattended::Inifile to grab a value out of the unattend file.
However, this does not take place until fairly late in the install after perl
and windows have been installed.
When the script executes, I get the following message:
"Can't locate
Dag Nummedal [EMAIL PROTECTED] writes:
Jordan Share writes:
Yes, I have read that KB article. It says, The correct OEMDIR
destination can be found by searching the INF file used to install
the device or driver.
Ah. Well, that is embarrassing.
Would you believe I treated OEMDIR as a
Max Lovius [EMAIL PROTECTED] writes:
What I want to do is :
(1) remotely reboot a computer.
(2) have the first boot, partion hard drive.
(3) have the second reboot, continue the unattended installation.
Easy enough.
(4) have a system that will then change automatically unattended
(in
Harder. You need a way for the install.pl on the client machine to
indicate a state change back to the TFTP (or maybe DHCP) server.
The easiest approach, I think, is to export the pxelinux.cfg directory
inside the TFTP root as a Windows share, modify the boot disk to mount
it as P: or
Tyler Hepworth [EMAIL PROTECTED] writes:
I wrote a script that use Unattended::Inifile to grab a value out of
the unattend file. However, this does not take place until fairly
late in the install after perl and windows have been installed.
When the script executes, I get the following
10 matches
Mail list logo
