Benjamin Burton wrote:
I'm trying to run some updates as executables, but I'm getting a failed
status 246 error.
You can download every single hotfix and apply it in the cmdlines.txt
file. Just remember to convert the files to a 8.3 file format.
--
mvh
Jørgen Hovelsen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 8 Dec 2006, Arrance, Jonathan wrote:
There are comments on how to change the initrd command line from the ready
ISO somewhere in the archive.
I used to do it with the attached script. However, I now prepare the ISO
myself now, so I don't
hello
when I boot up this machine I get this error:
Unrecognized interface type in
/sys/firmware/edd/int13_dev80/interface
unable to determine boot device at /usr/bin/find-boot-device line
212
*** find-boot-device failed
The file /sys/firmware/edd/int13_dev80/interface contains with an
optiplex
Hi,
I will release the unattended-gui boot-cd 0.2 this week, maybe you can
try this one for the optiplex 745?
If you want feel free to contact me directly because you have to setup
some little things in your network share and the documentation for that
is not ready yet
greetings mario
Am
Anders Nyström wrote:
thank you
Marios boot cd works fine with lenovo T60
and the old boot cd works with the older computers
Could some one tell me what has changed with the T60? and/or what has to
be modified in the kernel config..?
thanks
Am Montag, den 11.12.2006, 15:03 +0100 schrieb Christian Fischer:
Anders Nyström wrote:
thank you
Marios boot cd works fine with lenovo T60
and the old boot cd works with the older computers
Could some one tell me what has changed with the T60? and/or what has to
be modified in the
Is there a way to specify an unattend.txt file the same way, or do you
need to put it someplace on your cifs share and then modify one of the
scripts?
Thanks for all of the help
Jon
-Original Message-
From: Ben Walton [mailto:[EMAIL PROTECTED]
Sent: Friday, December 08, 2006 3:15 PM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 11 Dec 2006, Arrance, Jonathan wrote:
Is there a way to specify an unattend.txt file the same way, or do you
need to put it someplace on your cifs share and then modify one of the
scripts?
Check out the power of site/config.pl.
The
Hi All,
I'm interested to know how all you folks out there store your drivers in
i386\$oem$\$1\
I am having the following problems:
1 - The 64 charachter path size runs out pretty quick, and many driver paths
are too long. This makes it difficult to give logical and recognizable names
to the
Alon Lutzker wrote:
Hi All,
I'm interested to know how all you folks out there store your drivers in
i386\$oem$\$1\
I am having the following problems:
1 - The 64 charachter path size runs out pretty quick, and many driver
paths are too long. This makes it difficult to give
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 11 Dec 2006, Alon Lutzker wrote:
1 - The 64 charachter path size runs out pretty quick, and many driver paths
are too long. This makes it difficult to give logical and recognizable names
to the drivers. I manage to get it to work by just
My os\os\i386\$oem$ are symlinks. You probably need to allow wide
symlinks in Samba.
...and if you're using Windows to host the install share, you can use
Junction Points to achieve the same result (Junction Points are - from my
basic understanding of these things - equivalent to symlinks in
12 matches
Mail list logo
