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 <[EMA
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 Vis
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 O
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/01inst
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.techn
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
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
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 a
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 migh
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/ind
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
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, d
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]>
-
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'
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:
>
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
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:\netins
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
>
> > 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 u
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 si
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
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
> >(r
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
> happ
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\DevP
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
>
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/
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 modi
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 copie
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.
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.
a
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
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
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
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 f
34 matches
Mail list logo
