Re: [Unattended] Trying out unattended. First impressions and wishlist
Thanks Marcus, This worked for me too :) ( http://www.mail-archive.com/unattended-info@lists.sourceforge.net/msg06842.html ) Thanks again, Paul On 27/11/2007, Markus Busche <[EMAIL PROTECTED]> wrote: > > Hello Paul, > > this worked for me... > > Bye, > > Markus > > 2007/11/27, paul kelly <[EMAIL PROTECTED]>: > > > > Hi - I am about to try out this driver pack method also. > > However with all the traffic on the subject I've become confused on best > > approach. > > Can any one who understands this better give me a condensed (simple) > > version of how best to implement ... apologies I'm fairly new to much of > > this :) > > > > Thanks again > > Paul Kelly > > > > On 23/11/2007, Michael De Groote < [EMAIL PROTECTED]> wrote: > > > > > > SO, the way i tried from here is: > > > > > 1. unpack driverpacks to /z/drivers > > > > > 2. link /z/os/winxp/$oem$/$1/D to /z/drivers/D and do the same > > > > for win2k > > > > > -> driver will be placed in "C:\D" > > > > > 3. generate devicepath using either setdevicepath.exe (from pyron) > > > > (can also > > > > > be done by using a "find ./ -type d" + some extra commands) and > > > > put that in > > > > > the file hivesft.inf (it contains a 'key' named DevicePath, and is > > > > > apparently used as part of a template for the registry > > > > > > > > I did that. It becomes a total nightmare if you got some variation > > > > in > > > > your hardware (lots of directories: the driverpath becomes too > > > > long). > > > > > > > > > > uhm.. i'm using all the driverpacks... it doesnt complain yet about > > > the devicepath being too long (but ok i modified the registry template > > > instead of putting it in a var in the unattended.txt or winnt.sif or > > > whatever, maybe that helps?) > > > > > > The reasons i chose this path are > > > 1. all paths (meaning all .inf files, and thus all drivers) are > > > available > > > 2. no %systemdrive% in DevicePath, but a hardcoded "c:\" (and come > > > on, who installs on a different drive than a c:\ drive, especially in a > > > business/school scenario?)... that gets you a LOT of chars down > > > 3. c:\D\G\I\1 and the like are also (in total) a lot shorter than > > > z:\drivers\G\I\1 and friends. (Doenst look like much, but that is 6 chars > > > less... do that a 150 times and that is 900 chars !) > > > > > > I think i'll include a call to setdevicepath.exe, but then for a > > > mapped network drive, so when a machine is installed, the drivers can be > > > removed locally, but are still available on network > > > Still need to keep the LAN driverpack tho... that's an absolute > > > requirement here :) but hey, what is a pc without being connected to a > > > network? Lonely (ok, and more secure too :) ) > > > > > > > > > > > So the Pyrons method definitely is your only choice. I think I'm > > > > past > > > > the driver hurdle now; tomorrow or next week I'll also try a more > > > > varied range of machines. > > > > > > > > > > Michael > > > > > > > > > - > > > This SF.net email is sponsored by: Microsoft > > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > > ___ > > > unattended-info mailing list > > > unattended-info@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/unattended-info > > > > > > > > > > > > - > > This SF.net email is sponsored by: Microsoft > > Defy all challenges. Microsoft(R) Visual Studio 2005. > > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > > ___ > > unattended-info mailing list > > unattended-info@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/unattended-info > > > > > > > -- > > XMPP: [EMAIL PROTECTED] > ICQ: 101900957 > http://exilostfriesen.de > - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Wed, 2007-11-28 at 09:18 +0100, Mario Gzuk wrote: > We are currently working on the Vista installation, this will only > available on NTFS Yes. Vista would be good. Maybe 64 bit support too... Currently, only a small minority of staff here use Vista (the preference is still to replace Vista with XP on new computers), and I don't think anyone uses 64 bit XP either. However, I expect it will only be a matter of time before all of this changes. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Tirsdag 27 november 2007 23:41, skrev Brian May:
> On Mon, Nov 26, 2007 at 01:18:39PM +0100, Nils Olav Fossum wrote:
> > Mandag 26 november 2007 12:22, skrev Brian May:
> > > My assumption (correct me if I am wrong) was that by default the user
> > > would get prompted to add these directories to OemPnPDriverPath.
> >
> > Yes, correct
> >
> > > So if you have same copies of winxpsp2 that use driverspack and some
> > > which do not, this might be an issue.
> >
> > No, by default you can choose the OS you want.
> > It does not mather what the OS directory under z:\os is named.
> > So it should be no problem to have nearly identical OS-trees.
>
> No, I meant if you tried to hide the prompt. You could hard code the
> OemPnPDriverPath in unattend.txt, but then the user will never get prompted
> even if installing from an OS which requires the prompt.
Yes, I see what you mean :-)
And I sometimes do just that (see below)
>
> A better solution might be to set both OemPnPDriverPath and OS as per
> computer settings, maybe in unattend.csv (or whatever you use).
Yes, I have something like this (this is simplifyed) in my site/config.pl:
sub ask_hwprofile_preseed () {
print "\nChoose Machine Hardware preseed setup.\n";
my $ret = menu_choice
('No pre-setup for this hardware (continue)' => undef,
'Dell Optiplex 745', => 'z:\\site\\preseed\\dello745.txt',
'Fujitsu Siemens E3500' =>'z:\\site\\preseed\\fsce3500.txt',
'HP DC-5750 AMD FylkesavtPC' =>'z:\\site\\preseed\\hpdc5750.txt',
);
defined $ret
or return undef;
return $ret;
} # sub ask_hw_preseed
sub ask_swprofile_preseed () {
print "\nChoose Software preseed setup.\n";
my $ret = menu_choice
('No Software pre-setup for this machine (continue)' => undef,
'Internsone Standard (domene)', => 'z:\\site\\preseed\\mgkisone.txt',
'ExternPC No Domain', => 'z:\\site\\preseed\\externpc.txt',
'minimal test', => 'z:\\site\\preseed\\minitest.txt',
'Testinstall :-) ', => 'z:\\site\\preseed\\test-sw.txt',
);
defined $ret
or return undef;
return $ret;
} # sub ask_sw_preseed
my $hw_preseed = ask_hwprofile_preseed ();
if (defined $hw_preseed) {
print $hw_preseed;
$u->read (dos_to_host ($hw_preseed));
my $sw_preseed = ask_swprofile_preseed ();
if (defined $sw_preseed) {
print $sw_preseed;
$u->read (dos_to_host ($sw_preseed));
}
}
Basically:
First ask witch hw settings I want added to unattend.txt
Then ask witch software script(s) to run.
The generation of the final unattend.txt is as follows:
1: read the default unattend.txt
2: add or override the settings from site/unattend.txt
3: add or override the settings from the hw-select menu
4: add or override the settings from the sw-select menu
5: write the final unattend.txt to disk
as an example, the dello745.txt:
[_meta]
fdisk_cmds = "fdisk /clear
1;fdisk /pri:12288;fdisk /pri:100,100 /spec:7;fdisk /delete /pri:1;fdisk
/pri:4000;fdisk /activate:1"
fdisk_confirm=0
edit_files=0
OS_media = Z:\os\winxpsp2
[Unattended]
OemPnPDriversPath = "drv-dell\opti-745;drv-chip\wdm_178;drv-misc\kb888111"
and a example from the sw menu:
(mostly settings for skipping questions)
[Identification]
JoinDomain = my_domain
[GuiUnattended]
AdminPassword=secretpasswd
[_meta]
ntp_servers=""
local_admins=""
edit_files = 0
top = mgk-internsone.bat
middle = ""
;bottom = ""
Works for me :-D
-
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Am Mittwoch, den 28.11.2007, 11:58 +1100 schrieb Brian May: > On Mon, Nov 26, 2007 at 12:54:41PM +0100, Mario Gzuk wrote: > > Hi, > > as I wrote months before there is all ready a way: > > http://unattended-gui.svn.sourceforge.net/viewvc/unattended-gui/z/etc/init/profiles/unattended-nodosemu/01install?view=markup > > > > You should also read: > > http://unattended.technikz.de/index.php/Win:installation_process > > Is there any hope doing something like this to install directly onto NTFS? Or > is read/write NTFS support in Linux still considered to risky? Hi, read/write NTFS support in Linux is supported with the unattended-gui bootcd, but the installation scripts doesnt support this (but you can write your own: http://unattended.technikz.de/index.php/Unattended-gui:Create_profile). We are currently working on the Vista installation, this will only available on NTFS greetings mario - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Mon, Nov 26, 2007 at 12:54:41PM +0100, Mario Gzuk wrote: > Hi, > as I wrote months before there is all ready a way: > http://unattended-gui.svn.sourceforge.net/viewvc/unattended-gui/z/etc/init/profiles/unattended-nodosemu/01install?view=markup > > You should also read: > http://unattended.technikz.de/index.php/Win:installation_process Is there any hope doing something like this to install directly onto NTFS? Or is read/write NTFS support in Linux still considered to risky? -- Brian May <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Tue, Nov 27, 2007 at 06:13:51PM +1100, paul kelly wrote: > Hi - I am about to try out this driver pack method also. > However with all the traffic on the subject I've become confused on best > approach. > Can any one who understands this better give me a condensed (simple) version > of how best to implement ... apologies I'm fairly new to much of this :) Steps 1: 1. Download all driverpack files. 2. Run the program and give it the directory, I will assume z:\os\winxpsp2. Use method 2. Method 1 is cleaner but won't work (at least not for all drivers). This directory should contain the i386 directory from a clean copy of the Windows CD. The process must have write permissions. 3. Ensure z:\os\winxpsp2\OEM (created in above step) is copied to c:\OEM during installation. Apparently this can be done by copying/moving to i386\$oem$\$1\OEM (not tested personally). 4. I had do some additional black magic to get it to work. In particular, I had to copy presetup.cmd and setuporg.exe from z:\os\winxpsp2\i386 to z:\os\winxpsp2\i386\$OEM$\$$\System32, and delete the entries for these files in z:\os\winxpsp2\txtsetup.sif 5. Apparently on startup, by default, it will ask you if you want to add the OEM directory (and directories under it) to OemPnPDriverPath; say no. Step 4 is ugly. Solutions welcome! -- Brian May <[EMAIL PROTECTED]> - SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Mon, Nov 26, 2007 at 01:18:39PM +0100, Nils Olav Fossum wrote: > Mandag 26 november 2007 12:22, skrev Brian May: > > My assumption (correct me if I am wrong) was that by default the user would > > get prompted to add these directories to OemPnPDriverPath. > > Yes, correct > > > > So if you have same copies of winxpsp2 that use driverspack and some which > > do not, this might be an issue. > > No, by default you can choose the OS you want. > It does not mather what the OS directory under z:\os is named. > So it should be no problem to have nearly identical OS-trees. No, I meant if you tried to hide the prompt. You could hard code the OemPnPDriverPath in unattend.txt, but then the user will never get prompted even if installing from an OS which requires the prompt. A better solution might be to set both OemPnPDriverPath and OS as per computer settings, maybe in unattend.csv (or whatever you use). -- Brian May <[EMAIL PROTECTED]> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Hi - I am about to try out this driver pack method also. However with all the traffic on the subject I've become confused on best approach. Can any one who understands this better give me a condensed (simple) version of how best to implement ... apologies I'm fairly new to much of this :) Thanks again Paul Kelly On 23/11/2007, Michael De Groote <[EMAIL PROTECTED]> wrote: > > > SO, the way i tried from here is: > > > 1. unpack driverpacks to /z/drivers > > > 2. link /z/os/winxp/$oem$/$1/D to /z/drivers/D and do the same for > > win2k > > > -> driver will be placed in "C:\D" > > > 3. generate devicepath using either setdevicepath.exe (from pyron) > > (can also > > > be done by using a "find ./ -type d" + some extra commands) and put > > that in > > > the file hivesft.inf (it contains a 'key' named DevicePath, and is > > > apparently used as part of a template for the registry > > > > I did that. It becomes a total nightmare if you got some variation in > > your hardware (lots of directories: the driverpath becomes too long). > > > > uhm.. i'm using all the driverpacks... it doesnt complain yet about the > devicepath being too long (but ok i modified the registry template instead > of putting it in a var in the unattended.txt or winnt.sif or whatever, > maybe that helps?) > > The reasons i chose this path are > 1. all paths (meaning all .inf files, and thus all drivers) are available > 2. no %systemdrive% in DevicePath, but a hardcoded "c:\" (and come on, > who installs on a different drive than a c:\ drive, especially in a > business/school scenario?)... that gets you a LOT of chars down > 3. c:\D\G\I\1 and the like are also (in total) a lot shorter than > z:\drivers\G\I\1 and friends. (Doenst look like much, but that is 6 chars > less... do that a 150 times and that is 900 chars !) > > I think i'll include a call to setdevicepath.exe, but then for a mapped > network drive, so when a machine is installed, the drivers can be removed > locally, but are still available on network > Still need to keep the LAN driverpack tho... that's an absolute > requirement here :) but hey, what is a pc without being connected to a > network? Lonely (ok, and more secure too :) ) > > > > > So the Pyrons method definitely is your only choice. I think I'm past > > the driver hurdle now; tomorrow or next week I'll also try a more > > varied range of machines. > > > > Michael > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > unattended-info mailing list > unattended-info@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/unattended-info > > - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Mandag 26 november 2007 12:22, skrev Brian May: > My assumption (correct me if I am wrong) was that by default the user would > get prompted to add these directories to OemPnPDriverPath. Yes, correct > > So if you have same copies of winxpsp2 that use driverspack and some which > do not, this might be an issue. No, by default you can choose the OS you want. It does not mather what the OS directory under z:\os is named. So it should be no problem to have nearly identical OS-trees. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Mandag 26 november 2007 12:54, skrev Mario Gzuk: > Hi, > as I wrote months before there is all ready a way: > http://unattended-gui.svn.sourceforge.net/viewvc/unattended-gui/z/etc/init/ >profiles/unattended-nodosemu/01install?view=markup > > You should also read: > http://unattended.technikz.de/index.php/Win:installation_process > > greetings mario Yes, I have finally found some time to go thru it :-) A big thankyou to Mario! - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Mandag 26 november 2007 12:17, skrev Frank Van Damme: > On Nov 26, 2007 11:42 AM, Nils Olav Fossum > > so if I get this right: > > Drivers are copied to c:\oem and Windows pick them up and uses them? > > Yes. Interesting, I wonder if its the installer (running under dosemu) that picks it up or if its picked up after the first restart... > > make a sensible directory structure under > > z:\os\winxpsp2\$oem$\$1 > > Yes, you can also also copy/move the OEM folder to i386\$oem$\$1\OEM, > so Windows Setup will copy it to the C: drive; this way you can avoid > messing with doit_cmds parameter. So, it is a documention issue .. > I slipstream my drivers with method > 2 btw (so I don't have to care too much about the max. length of > OemPnPDriverPath). It works well. yep, that is another method :-) - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Hi, as I wrote months before there is all ready a way: http://unattended-gui.svn.sourceforge.net/viewvc/unattended-gui/z/etc/init/profiles/unattended-nodosemu/01install?view=markup You should also read: http://unattended.technikz.de/index.php/Win:installation_process greetings mario Am Montag, den 26.11.2007, 22:25 +1100 schrieb Brian May: > On Mon, Nov 26, 2007 at 11:42:50AM +0100, Nils Olav Fossum wrote: > > Actually, Im trying to get away from the windows-installer, > > ie: the whole dosemu thing. > > I will post more in -devel soon. > > Sounds good to me. Look forward to reading the details. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Mon, Nov 26, 2007 at 11:42:50AM +0100, Nils Olav Fossum wrote: > Actually, Im trying to get away from the windows-installer, > ie: the whole dosemu thing. > I will post more in -devel soon. Sounds good to me. Look forward to reading the details. -- Brian May <[EMAIL PROTECTED]> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Mon, Nov 26, 2007 at 12:17:30PM +0100, Frank Van Damme wrote: > Yes, you can also also copy/move the OEM folder to i386\$oem$\$1\OEM, > so Windows Setup will copy it to the C: drive; this way you can avoid > messing with doit_cmds parameter. I slipstream my drivers with method > 2 btw (so I don't have to care too much about the max. length of > OemPnPDriverPath). It works well. My assumption (correct me if I am wrong) was that by default the user would get prompted to add these directories to OemPnPDriverPath. So if you have same copies of winxpsp2 that use driverspack and some which do not, this might be an issue. -- Brian May <[EMAIL PROTECTED]> - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Nov 26, 2007 11:42 AM, Nils Olav Fossum <[EMAIL PROTECTED]> wrote: > Søndag 25 november 2007 23:03, skrev Brian May: > > On Fri, 2007-11-23 at 11:27 +0100, Nils Olav Fossum wrote: > > > Onsdag 14 november 2007 17:08, skrev Maurice Libes: > > > > i make this copy in the UNATTEND.TXT file here: > > > > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; > > so if I get this right: > Drivers are copied to c:\oem and Windows pick them up and uses them? Yes. [SNIP] > > Anyway, hard coding the above is kind of ugly, especially as the os > > directory is hard coded ( z:\os\winxpsp2 ) - which might be OK if you > > have only one OS, but probably won't work if you have multiple OS in > > z:\os. > > Yep, this should be automated, and I believe it is already done, > but a little handwork is needed: > > make a sensible directory structure under > z:\os\winxpsp2\$oem$\$1 Yes, you can also also copy/move the OEM folder to i386\$oem$\$1\OEM, so Windows Setup will copy it to the C: drive; this way you can avoid messing with doit_cmds parameter. I slipstream my drivers with method 2 btw (so I don't have to care too much about the max. length of OemPnPDriverPath). It works well. -- Frank Van Damme A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mails or on usenet? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Søndag 25 november 2007 23:03, skrev Brian May: > On Fri, 2007-11-23 at 11:27 +0100, Nils Olav Fossum wrote: > > Onsdag 14 november 2007 17:08, skrev Maurice Libes: > > > i make this copy in the UNATTEND.TXT file here: > > > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; so if I get this right: Drivers are copied to c:\oem and Windows pick them up and uses them? > > hm, I wonder if this is just a documentation problem, and what we can do > > better.. > > ..Im starting a new thread.. > > If you started a new thread, I apologise, as I must have missed it. hehe, I tried to, but the message is a bit unclear, my bad. see 'Driver install fuzz'. Im trying to get more info to make documentation and I hope to automate the driver install process a bit more, if needed. But, Im not the best doc writer, or in other words: I can do it much better in Norwegian :-) > > Anyway, hard coding the above is kind of ugly, especially as the os > directory is hard coded ( z:\os\winxpsp2 ) - which might be OK if you > have only one OS, but probably won't work if you have multiple OS in > z:\os. Yep, this should be automated, and I believe it is already done, but a little handwork is needed: make a sensible directory structure under z:\os\winxpsp2\$oem$\$1 Lets say you have a HP dc 5750, create a directory 'hpdc5750' In this directory you put the drivers needed for this machine. And nothing more. file name crashes are rare. ATI/AMD, Intel, Broadcom and Realtek all have drivers for download you can use. So has HP, Dell, FujitsuSiemens, IBM, Lenovo ++ I use a combination of drivers from chipmakers and computermakers. Yes, this is a little more work, but the upside is controll over youre drivers. > > Maybe if you have a setting that gives a list of commands to execute > before doit_cmds - that way you wouldn't have to hard code the winnt > command either... But the list of commands to execute could vary > depending on the OS you want installed - e.g. if you want a copy of > winxp with and without the driver packs for some reason. > > In fact I almost did just this myself, but fortunately woke up to the > problem with unattend.cmd before I got myself too confused. Actually, Im trying to get away from the windows-installer, ie: the whole dosemu thing. I will post more in -devel soon. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Fri, 2007-11-23 at 11:27 +0100, Nils Olav Fossum wrote: > Onsdag 14 november 2007 17:08, skrev Maurice Libes: > > i make this copy in the UNATTEND.TXT file here: > > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; > > winnt /rx: > > lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt" > > hm, I wonder if this is just a documentation problem, and what we can do > better.. > ..Im starting a new thread.. If you started a new thread, I apologise, as I must have missed it. Anyway, hard coding the above is kind of ugly, especially as the os directory is hard coded ( z:\os\winxpsp2 ) - which might be OK if you have only one OS, but probably won't work if you have multiple OS in z:\os. Maybe if you have a setting that gives a list of commands to execute before doit_cmds - that way you wouldn't have to hard code the winnt command either... But the list of commands to execute could vary depending on the OS you want installed - e.g. if you want a copy of winxp with and without the driver packs for some reason. In fact I almost did just this myself, but fortunately woke up to the problem with unattend.cmd before I got myself too confused. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Onsdag 14 november 2007 17:08, skrev Maurice Libes: > i make this copy in the UNATTEND.TXT file here: > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; > winnt /rx: > lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt" hm, I wonder if this is just a documentation problem, and what we can do better.. ..Im starting a new thread.. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
> > > SO, the way i tried from here is: > > 1. unpack driverpacks to /z/drivers > > 2. link /z/os/winxp/$oem$/$1/D to /z/drivers/D and do the same for > win2k > > -> driver will be placed in "C:\D" > > 3. generate devicepath using either setdevicepath.exe (from pyron) (can > also > > be done by using a "find ./ -type d" + some extra commands) and put that > in > > the file hivesft.inf (it contains a 'key' named DevicePath, and is > > apparently used as part of a template for the registry > > I did that. It becomes a total nightmare if you got some variation in > your hardware (lots of directories: the driverpath becomes too long). > uhm.. i'm using all the driverpacks... it doesnt complain yet about the devicepath being too long (but ok i modified the registry template instead of putting it in a var in the unattended.txt or winnt.sif or whatever, maybe that helps?) The reasons i chose this path are 1. all paths (meaning all .inf files, and thus all drivers) are available 2. no %systemdrive% in DevicePath, but a hardcoded "c:\" (and come on, who installs on a different drive than a c:\ drive, especially in a business/school scenario?)... that gets you a LOT of chars down 3. c:\D\G\I\1 and the like are also (in total) a lot shorter than z:\drivers\G\I\1 and friends. (Doenst look like much, but that is 6 chars less... do that a 150 times and that is 900 chars !) I think i'll include a call to setdevicepath.exe, but then for a mapped network drive, so when a machine is installed, the drivers can be removed locally, but are still available on network Still need to keep the LAN driverpack tho... that's an absolute requirement here :) but hey, what is a pc without being connected to a network? Lonely (ok, and more secure too :) ) > > So the Pyrons method definitely is your only choice. I think I'm past > the driver hurdle now; tomorrow or next week I'll also try a more > varied range of machines. > Michael - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Nov 22, 2007 10:09 PM, Michael De Groote <[EMAIL PROTECTED]> wrote: > ok, just some following up on this trail: > > at the moment, i dont think it's stable enough to be useful, at least not in > an environment where you need to install more than one machine. Why? > A) because depending on the situation, it throws errors (on eg win2k, it > complains about some weird "COM error with using DOM" > B) the 'add new hardware wizard' is not suppressed. Author claims it is > being suppressed on his system (as far as i can tell from his posts), but i > haven't experienced that yet => you have to click your way through Have had problems with this too, by wisely clicking through the wizard it turned out that it was a piece of hardware that I dod not provide drivers for in my custom driver pack. Tomorrow I will re-try the installation. > C) it fracks up something in that wizard, making it act strange when trying > to locate driver files... even tho i point it at the correct file, it still > cant find it, again on win2k. On WinXP it seems to behave better, tho you > still have to click your way thru the wizard > > SO, the way i tried from here is: > 1. unpack driverpacks to /z/drivers > 2. link /z/os/winxp/$oem$/$1/D to /z/drivers/D and do the same for win2k > -> driver will be placed in "C:\D" > 3. generate devicepath using either setdevicepath.exe (from pyron) (can also > be done by using a "find ./ -type d" + some extra commands) and put that in > the file hivesft.inf (it contains a 'key' named DevicePath, and is > apparently used as part of a template for the registry I did that. It becomes a total nightmare if you got some variation in your hardware (lots of directories: the driverpath becomes too long). So the Pyrons method definitely is your only choice. I think I'm past the driver hurdle now; tomorrow or next week I'll also try a more varied range of machines. > 4. install using unattended... seems to work > > At least it works better than without step 3, since i have a gut feeling > that the thing that constructs the devicepath omits any directory that has > subdirectories... which is annoying since there are a lot of drivers in the > driverpacks that have .inf files in their main dir AND in a subdir, but the > .inf files in the main dir are not visible to the setup process since they > are not put in the devicepath value. Also, it seems that (but i need to test > this further) that pregenerating that key and putting it in the hivesft.inf > file bypasses the 4000byte limit for the OemPnPDriverPath thing... I'm not sure about that thing. As I see it, Pyrons method will basically do an equivalent of find -type d and add each of these to the registry (possibly excluding the directories with no .inf files). Anyhow, creating my own DriverPack works fine for me now, I might have a directory for a certain mobo with directories for the lan, audio etc drivers, I'll probably also testing that later. > The reason i think it might remove the restriction is info in the following > link : > http://vernalex.com/tools/spdrvscn/index.shtml > > > > anywayz, typing with an 8-month old is kinda difficult, so i'm gonna leave > it at this :) Cute :) -- Frank Van Damme A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mails or on usenet? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
ok, just some following up on this trail: at the moment, i dont think it's stable enough to be useful, at least not in an environment where you need to install more than one machine. Why? A) because depending on the situation, it throws errors (on eg win2k, it complains about some weird "COM error with using DOM" B) the 'add new hardware wizard' is not suppressed. Author claims it is being suppressed on his system (as far as i can tell from his posts), but i haven't experienced that yet => you have to click your way through C) it fracks up something in that wizard, making it act strange when trying to locate driver files... even tho i point it at the correct file, it still cant find it, again on win2k. On WinXP it seems to behave better, tho you still have to click your way thru the wizard SO, the way i tried from here is: 1. unpack driverpacks to /z/drivers 2. link /z/os/winxp/$oem$/$1/D to /z/drivers/D and do the same for win2k -> driver will be placed in "C:\D" 3. generate devicepath using either setdevicepath.exe (from pyron) (can also be done by using a "find ./ -type d" + some extra commands) and put that in the file hivesft.inf (it contains a 'key' named DevicePath, and is apparently used as part of a template for the registry 4. install using unattended... seems to work At least it works better than without step 3, since i have a gut feeling that the thing that constructs the devicepath omits any directory that has subdirectories... which is annoying since there are a lot of drivers in the driverpacks that have .inf files in their main dir AND in a subdir, but the .inf files in the main dir are not visible to the setup process since they are not put in the devicepath value. Also, it seems that (but i need to test this further) that pregenerating that key and putting it in the hivesft.inffile bypasses the 4000byte limit for the OemPnPDriverPath thing... The reason i think it might remove the restriction is info in the following link : http://vernalex.com/tools/spdrvscn/index.shtml anywayz, typing with an 8-month old is kinda difficult, so i'm gonna leave it at this :) Michael On Nov 15, 2007 9:43 AM, Michael De Groote <[EMAIL PROTECTED]> wrote: > i'm currently trying to do the following for driver-stuff: > > 1. only integrate the BTS LAN-driverpack (these are absolutely necessary) > (if i come across probs in the future i might integrate massstorage > textmode drivers too, but havent figured that part out yet :) ) > > 2. rest of the driverpacks goes into z:/drivers > > 3. then try using this : > http://www.msfn.org/board/lofiversion/index.php/t70209.html > => all drivers except network drivers remain on network share, which is > nice for old machines with small disks, and saves setup time since not ALL > have to be copied > => no more problem with limit on length of oempnpdriverpath > > hopefully i can report later today that this approach works > > Michael > > > > > > > On Nov 14, 2007 5:08 PM, Maurice Libes <[EMAIL PROTECTED] > wrote: > > > Frank Van Damme a écrit : > > > Hello, > > > > > > I am currently trying out Unattended. Depending on which PC I try it > > > on, it works nice... > > > > > > My biggest problem up to now has been pre-installing drivers. We have > > > very diverse hardware, and the first system I tried it on (an Asus > > > Pundit PH3, Intel-based) has an elaborate directory structure for the > > > device drivers (totalling 92 directories and subdirectories). > > > Apparently it is necessary to add all these directories to the > > > OemPnPDriverPath (why can't windows setup just copy it all to hard > > > disk, and then seek the correct .inf file in that tree?). I ended up > > > with a totally-unconfigured system with no support for the usb > > > controller, video chip, ethernet,... > > > > > > I also tried generating the OemPnPDriversPath by adding all these > > > subdirs in a string and putting that in unattend.txt (just so > > > Unattended would skip asking which driver folders to add). Didn't seem > > > like a very good idea, the path became pages long and > > > Unattended/Windows Setup mangles the entire directory structure > > > anyway. I would prefer not having to wory about the correct hardware > > > drivers and to just let Windows Setup figure out what drivers to > > > install. > > > > > > > > i don't know if i understand your problem > > but in case of limited string length from OemPnPDriversPath I suggest > > you to use > > the 2nd method proposed by the DPS_base installation program from > > DriverPack > > http://driverpacks.net/DriverPacks/ > > > > this method known as Pyron's method can solve this length problem > > > > All the driver are put in 7z format in a C:\OEM directory > > Then this method create a presetup before the Windows setup > > This presetup launch a programm DevPath.exe which scan the OEM directory > > searching for ".inf" driver files, and modify the > > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ DevicePath > > register > > > > th
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Nov 16, 2007 3:52 PM, Maurice Libes <[EMAIL PROTECTED]> wrote:
>> Never mind, I'm trying the driverpack stuff out now and it seems to
>> run place itself before the windows setup program.
>
>
> yes that's right
>
> > Apparently, you can put ("slipstream") drivers into the windows media
> >(read: z:\os\winspn or something), so you don't need to copy them
> >manually, as far as I understand.
>
>
> yes this is quite automatic modulo a little hack
>
> the method #2 from DPS_Base.exe (driverpack.net) do all the job
> but you have to do some hack with the unattended method from sourceforge,
> in order to make it work
>
> I try to resume:
> let's say your master Windows stays on D:\WXP
>
> 1. with method #2 from driverpack the drivers are put in 7zip in a
> directory called OEM
> so at the root file system in D:\WXP\OEM
> this method also generate the presetup.cmd file (look into this file you
> will understand what it is done)
>
> 2. as sourceforge-unattended works on the I386 directory you must copy this
> OEM driver directory to I386/OEM
> copy D:\WXP\OEM D:\WXP\OEM\I386
>
> 3. copy the entire I386 to your NTinstall unattended server by instance
> ~/os/winxpsp2/
>
> 4. as the Pyron method works on C:\OEM , at install time (more exactly
> before install time) you have to copy back the I386\OEM driver directory
> from the unattended server to C: on the client PC
>
> we do this action by the way of the unattend.txt file
> just like that, at this stage
>
> doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; winnt
> /rx:
> lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt"
Hmm, normally everything in the $oem$\$1 directory is copied to the
root of c:. I'm going to try copy (or symlink on my samba server) that
i386\OEM directory to $oem$\$1. It'll probably take away the need to
hack unattend.txt.
> seems to work here
>
>
> hope this helps
>
> M
>
>
>
>
>
>
> --
> Maurice Libes
> Tel : +33 (04) 91 82 93 25 Centre d'Oceanologie de Marseille
> Fax : +33 (04) 91 82 93 03 UMS2196CNRS- Campus de Luminy, Case 901
> F-13288 Marseille cedex 9
>
> Veuillez noter ma nouvelle adresse ==> [EMAIL PROTECTED]
>
>
>
--
Frank Van Damme A: Because it destroys the flow of the conversation
Q: Why is it bad?
A: No, it's bad.
Q: Should I top post in replies to mails or on usenet?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Fri, 2007-11-16 at 13:53 +1100, Brian May wrote: > More errors. It reboots once then complains it can't copy setupORG.exe, > presetup.cmd, etc . > > I am guessing that somewhere these files were suppose to be copied from > z:\os\winxpsp2\i386 to c:\...\i386, but this doesn't appear to be > happening. I ended up following the instructions I found on some dodgy website. Copy presetup.cmd and setuporg.exe from /os/winxpsp2/i386 to /os/winxpsp2/i386/$OEM$/$$/System32 (need to make this directory). Remove these files from txtsetup.sif Now it works. Yes, this seems ugly; however it is the only way I have got to to work. Otherwise windows won't copy the files to the C:\ drive in the initial installation stage, and can't access them later. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
Frank Van Damme a écrit :
On Nov 16, 2007 1:37 PM, Frank Van Damme <[EMAIL PROTECTED]> wrote:
When and where do you call devpath.exe then? I only see you copy the directory.
in the presetup.cmd which is generated by the #2 method
look into the presetup.cmd file
%CDDRIVE%\OEM\bin\DevPath.exe %SystemDrive%\D
I also see one problem with putting this in doit_cmds; normally (as
far as I see it) doit_cmds is being generated by unattended if there
is no value pre-defined, and what ends up in it depends on which OS
you chose to install (winxpsp2 in your case). Is there not something
that is executed before the setup (something that is not doit_cmds)?
Never mind, I'm trying the driverpack stuff out now and it seems to
run place itself before the windows setup program.
yes that's right
Apparently, you can put ("slipstream") drivers into the windows media
(read: z:\os\winspn or something), so you don't need to copy them
manually, as far as I understand.
yes this is quite automatic modulo a little hack
the method #2 from DPS_Base.exe (driverpack.net) do all the job
but you have to do some hack with the unattended method from
sourceforge, in order to make it work
I try to resume:
let's say your master Windows stays on D:\WXP
1. with method #2 from driverpack the drivers are put in 7zip in a
directory called OEM
so at the root file system in D:\WXP\OEM
this method also generate the presetup.cmd file (look into this file
you will understand what it is done)
2. as sourceforge-unattended works on the I386 directory you must copy
this OEM driver directory to I386/OEM
copy D:\WXP\OEM D:\WXP\OEM\I386
3. copy the entire I386 to your NTinstall unattended server by instance
~/os/winxpsp2/
4. as the Pyron method works on C:\OEM , at install time (more exactly
before install time) you have to copy back the I386\OEM driver directory
from the unattended server to C: on the client PC
we do this action by the way of the unattend.txt file
just like that, at this stage
doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;/*xcopy OEM c:\OEM /Y /E /I*/;
winnt /rx:
lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt"
seems to work here
hope this helps
M
--
Maurice Libes
Tel : +33 (04) 91 82 93 25Centre d'Oceanologie de Marseille
Fax : +33 (04) 91 82 93 03UMS2196CNRS- Campus de Luminy, Case 901
F-13288 Marseille cedex 9
Veuillez noter ma nouvelle adresse ==> [EMAIL PROTECTED]
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Nov 16, 2007 1:37 PM, Frank Van Damme <[EMAIL PROTECTED]> wrote:
> When and where do you call devpath.exe then? I only see you copy the
> directory.
>
> I also see one problem with putting this in doit_cmds; normally (as
> far as I see it) doit_cmds is being generated by unattended if there
> is no value pre-defined, and what ends up in it depends on which OS
> you chose to install (winxpsp2 in your case). Is there not something
> that is executed before the setup (something that is not doit_cmds)?
Never mind, I'm trying the driverpack stuff out now and it seems to
run place itself before the windows setup program.
Apparently, you can put ("slipstream") drivers into the windows media
(read: z:\os\winspn or something), so you don't need to copy them
manually, as far as I understand.
--
Frank Van Damme A: Because it destroys the flow of the conversation
Q: Why is it bad?
A: No, it's bad.
Q: Should I top post in replies to mails or on usenet?
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
unattended-info mailing list
unattended-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Nov 14, 2007 5:08 PM, Maurice Libes <[EMAIL PROTECTED]> wrote: > i don't know if i understand your problem > but in case of limited string length from OemPnPDriversPath I suggest > you to use > the 2nd method proposed by the DPS_base installation program from DriverPack > http://driverpacks.net/DriverPacks/ > > this method known as Pyron's method can solve this length problem > > All the driver are put in 7z format in a C:\OEM directory > Then this method create a presetup before the Windows setup > This presetup launch a programm DevPath.exe which scan the OEM directory > searching for ".inf" driver files, and modify the > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ DevicePath > register > > this method works great and you can have as many drivers as you want > without problem > > with the unattended sourceforge project there is just a hack to do in > order to make this method functionnal > > 1. you have to copy the OEM Directory containing the drivers, into your > I386 Directory > 2. then at install time you MUST copy backward the I386\OEM directory to C: > > i make this copy in the UNATTEND.TXT file here: > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; > winnt /rx: > lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt" > > > hope it can help When and where do you call devpath.exe then? I only see you copy the directory. I also see one problem with putting this in doit_cmds; normally (as far as I see it) doit_cmds is being generated by unattended if there is no value pre-defined, and what ends up in it depends on which OS you chose to install (winxpsp2 in your case). Is there not something that is executed before the setup (something that is not doit_cmds)? -- Frank Van Damme A: Because it destroys the flow of the conversation Q: Why is it bad? A: No, it's bad. Q: Should I top post in replies to mails or on usenet? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Wed, 2007-11-14 at 17:08 +0100, Maurice Libes wrote: > All the driver are put in 7z format in a C:\OEM directory > Then this method create a presetup before the Windows setup > This presetup launch a programm DevPath.exe which scan the OEM directory > searching for ".inf" driver files, and modify the > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ DevicePath > register I have tried this, but as soon as winnt is called (as per command line before), I start getting the "Setup was unable to copy the following file" error. I started writing a list until I get sick of it: dac960nt.sys mraid35x.sys ql12160.sys ultra.sys These files all seem to come from DPM7092.7z. The things I checked: * 7z Archive is not corrupt. * heaps of disk space Any more ideas? It would be nice if it would tell you more details, or even if the problem was in the source file or destination file. > i make this copy in the UNATTEND.TXT file here: > doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; > winnt /rx: > lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt" Hmmm. For some reason the GUI created the OEM directory at Z:\os\winxpsp2\OEM, not at Z:\os\winxpsp2\i386\OEM Or was I meant to move Z:\os\winxpsp2\OEM to Z:\os\winxpsp2\i386\OEM manually? I had to modify the above command to suit. Maybe I was suppose to enter ...\winxpsp2\i386 in the GUI, not ...\winxpsp2 ? It seemed happy with ...\winxpsp2 . Still, the fact it is coming up with the file names would seem to imply it is finding the source files OK. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Fri, 2007-11-16 at 11:52 +1100, Brian May wrote: > That seems to have fixed my problems. At least installation is now past > that point. More errors. It reboots once then complains it can't copy setupORG.exe, presetup.cmd, etc . I am guessing that somewhere these files were suppose to be copied from z:\os\winxpsp2\i386 to c:\...\i386, but this doesn't appear to be happening. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Fri, 2007-11-16 at 11:27 +1100, Brian May wrote: > I will redo the the process again, from a fresh copy of XP SP2. Maybe > the fact I changed from method 1 to method 2 confused things. Sorry for the noise here. That seems to have fixed my problems. At least installation is now past that point. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
On Fri, 2007-11-16 at 11:09 +1100, Brian May wrote: > Still, the fact it is coming up with the file names would seem to imply > it is finding the source files OK. Hmm. Looks like the GUI renamed some of the files in my i386 directory, but these are still referenced in the initial installation. adpu160m.org: Microsoft Cabinet archive data, 50331 bytes, 1 file ALIIDE.org: Microsoft Cabinet archive data, 2839 bytes, 1 file dac2w2k.org: Microsoft Cabinet archive data, 29302 bytes, 1 file dac960nt.org: Microsoft Cabinet archive data, 8001 bytes, 1 file dosnet.org: ASCII text, with CRLF line terminators DPTI2O.org: Microsoft Cabinet archive data, 10997 bytes, 1 file mraid35x.org: Microsoft Cabinet archive data, 9785 bytes, 1 file ql12160.org: Microsoft Cabinet archive data, 25938 bytes, 1 file txtsetup.org: ASCII text, with CRLF line terminators ultra.org:Microsoft Cabinet archive data, 15864 bytes, 1 file winnt.org:ASCII text, with CRLF line terminators I will redo the the process again, from a fresh copy of XP SP2. Maybe the fact I changed from method 1 to method 2 confused things. -- Brian May <[EMAIL PROTECTED]> Victorian Partnership for Advanced Computing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
i'm currently trying to do the following for driver-stuff: 1. only integrate the BTS LAN-driverpack (these are absolutely necessary) (if i come across probs in the future i might integrate massstorage textmode drivers too, but havent figured that part out yet :) ) 2. rest of the driverpacks goes into z:/drivers 3. then try using this : http://www.msfn.org/board/lofiversion/index.php/t70209.html => all drivers except network drivers remain on network share, which is nice for old machines with small disks, and saves setup time since not ALL have to be copied => no more problem with limit on length of oempnpdriverpath hopefully i can report later today that this approach works Michael On Nov 14, 2007 5:08 PM, Maurice Libes <[EMAIL PROTECTED]> wrote: > Frank Van Damme a écrit : > > Hello, > > > > I am currently trying out Unattended. Depending on which PC I try it > > on, it works nice... > > > > My biggest problem up to now has been pre-installing drivers. We have > > very diverse hardware, and the first system I tried it on (an Asus > > Pundit PH3, Intel-based) has an elaborate directory structure for the > > device drivers (totalling 92 directories and subdirectories). > > Apparently it is necessary to add all these directories to the > > OemPnPDriverPath (why can't windows setup just copy it all to hard > > disk, and then seek the correct .inf file in that tree?). I ended up > > with a totally-unconfigured system with no support for the usb > > controller, video chip, ethernet,... > > > > I also tried generating the OemPnPDriversPath by adding all these > > subdirs in a string and putting that in unattend.txt (just so > > Unattended would skip asking which driver folders to add). Didn't seem > > like a very good idea, the path became pages long and > > Unattended/Windows Setup mangles the entire directory structure > > anyway. I would prefer not having to wory about the correct hardware > > drivers and to just let Windows Setup figure out what drivers to > > install. > > > > > i don't know if i understand your problem > but in case of limited string length from OemPnPDriversPath I suggest > you to use > the 2nd method proposed by the DPS_base installation program from > DriverPack > http://driverpacks.net/DriverPacks/ > > this method known as Pyron's method can solve this length problem > > All the driver are put in 7z format in a C:\OEM directory > Then this method create a presetup before the Windows setup > This presetup launch a programm DevPath.exe which scan the OEM directory > searching for ".inf" driver files, and modify the > HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ DevicePath > register > > this method works great and you can have as many drivers as you want > without problem > > with the unattended sourceforge project there is just a hack to do in > order to make this method functionnal > > 1. you have to copy the OEM Directory containing the drivers, into your > I386 Directory > 2. then at install time you MUST copy backward the I386\OEM directory to > C: > > i make this copy in the UNATTEND.TXT file here: >doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; > winnt /rx: > lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt" > > > hope it can help > > > Currently I'm having another test system on my desk which is between > > its 15th and 16th reboot for installing updates, or so it seems :-) > > I'd like to draw your attention to C't offline update: a small GPL > > program written by the dutch computer magazine C't. It produces update > > cdroms for chosen windows versions and languages of Windows; the > > updates are installed with MS's update agent, it's got its own system > > for automatic reboot and recall and support for service pack releases. > > Maybe it's worth considering to integrate this in Unattended? > > > > Some download links in the scripts are dead. This probably because my > > scripts are outdated - I tried updating them but always got a "no > > route to host" error to the sourceforge cvs. Pretty annoying. I'll go > > on without pe windows messenger for now. > > > > Then, on the Pundit (after I'd thrown some cruft out of the drivers > > directory, and removed the OemPnPDriversPath from unattend.txt), about > > half of the drivers got installed - just not the usb ones and the > > network. For some reason I just couldn't get the thing to work > > afterwards too. Weird. I'll try Xp instead of 2000 and let know how it > > went. > > > > Also: the system currently installing is a win2k. I have an > > unattend.csv which worked nice for the pundit and the windows Xp key, > > but for this system Unattended still asks me for a product key. Which > > is weird since the product key is in the database. Or is the key not > > "Windows 2000 Professional ProductKey"? > > > > Another thing I'm a bit (...) concerned about is security. The default > > settings are guest:guest, so everyone can read unattended.txt and the > > admin passwords therein. Would it
Re: [Unattended] Trying out unattended. First impressions and wishlist
Frank Van Damme a écrit : > Hello, > > I am currently trying out Unattended. Depending on which PC I try it > on, it works nice... > > My biggest problem up to now has been pre-installing drivers. We have > very diverse hardware, and the first system I tried it on (an Asus > Pundit PH3, Intel-based) has an elaborate directory structure for the > device drivers (totalling 92 directories and subdirectories). > Apparently it is necessary to add all these directories to the > OemPnPDriverPath (why can't windows setup just copy it all to hard > disk, and then seek the correct .inf file in that tree?). I ended up > with a totally-unconfigured system with no support for the usb > controller, video chip, ethernet,... > > I also tried generating the OemPnPDriversPath by adding all these > subdirs in a string and putting that in unattend.txt (just so > Unattended would skip asking which driver folders to add). Didn't seem > like a very good idea, the path became pages long and > Unattended/Windows Setup mangles the entire directory structure > anyway. I would prefer not having to wory about the correct hardware > drivers and to just let Windows Setup figure out what drivers to > install. > > i don't know if i understand your problem but in case of limited string length from OemPnPDriversPath I suggest you to use the 2nd method proposed by the DPS_base installation program from DriverPack http://driverpacks.net/DriverPacks/ this method known as Pyron's method can solve this length problem All the driver are put in 7z format in a C:\OEM directory Then this method create a presetup before the Windows setup This presetup launch a programm DevPath.exe which scan the OEM directory searching for ".inf" driver files, and modify the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\ DevicePath register this method works great and you can have as many drivers as you want without problem with the unattended sourceforge project there is just a hack to do in order to make this method functionnal 1. you have to copy the OEM Directory containing the drivers, into your I386 Directory 2. then at install time you MUST copy backward the I386\OEM directory to C: i make this copy in the UNATTEND.TXT file here: doit_cmds = "Z:;cd Z:\os\winxpsp2\i386;xcopy OEM c:\OEM /Y /E /I; winnt /rx: lang /s:Z:\os\winxpsp2\i386 /u:C:\netinst\unattend.txt" hope it can help > Currently I'm having another test system on my desk which is between > its 15th and 16th reboot for installing updates, or so it seems :-) > I'd like to draw your attention to C't offline update: a small GPL > program written by the dutch computer magazine C't. It produces update > cdroms for chosen windows versions and languages of Windows; the > updates are installed with MS's update agent, it's got its own system > for automatic reboot and recall and support for service pack releases. > Maybe it's worth considering to integrate this in Unattended? > > Some download links in the scripts are dead. This probably because my > scripts are outdated - I tried updating them but always got a "no > route to host" error to the sourceforge cvs. Pretty annoying. I'll go > on without pe windows messenger for now. > > Then, on the Pundit (after I'd thrown some cruft out of the drivers > directory, and removed the OemPnPDriversPath from unattend.txt), about > half of the drivers got installed - just not the usb ones and the > network. For some reason I just couldn't get the thing to work > afterwards too. Weird. I'll try Xp instead of 2000 and let know how it > went. > > Also: the system currently installing is a win2k. I have an > unattend.csv which worked nice for the pundit and the windows Xp key, > but for this system Unattended still asks me for a product key. Which > is weird since the product key is in the database. Or is the key not > "Windows 2000 Professional ProductKey"? > > Another thing I'm a bit (...) concerned about is security. The default > settings are guest:guest, so everyone can read unattended.txt and the > admin passwords therein. Would it be possibly/easy to remaster the > boot disk with some real user and real password? > > > -- Maurice Libes Tel : +33 (04) 91 82 93 25Centre d'Oceanologie de Marseille Fax : +33 (04) 91 82 93 03UMS2196CNRS- Campus de Luminy, Case 901 F-13288 Marseille cedex 9 Veuillez noter ma nouvelle adresse ==> [EMAIL PROTECTED] - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
Re: [Unattended] Trying out unattended. First impressions and wishlist
For the drivers, search the list for driver-packs by driverpacks.net. For security, you can edit the isolinux.cfg on the boot cd. regards - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ ___ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
