Seem to be is it the best suggestion what I have from this thread :)
- In this case please give me some idea, why we need to give a so ugly
argument list for cmd.exe to simopky start the drivers.exe?
- Why we need to chunk file names to 8.3, I think winnt.exe and setup.exe
can handle long
Hi,
the 8.3 is limited by windows setup. After the setup you can play with
file names longer than 8.3.
One suggestion: Integrate the drivers for mass staroage directly into
the PNPDriverPath, install the driverpacks as first script after the setup.
I have no solution for you because we only work
Hi
Success! :D
[GuiUnattended]
DetachProgram=cmd.exe
Arguments=/Q /C START /MIN %SYSTEMDRIVE%\$win_nt$.~ls\$OEM$\Drivers.cmd
I'm used untouched files from DriverFiles.zip and whole bunch of drivers
compressed into one file Drivers.7z (mass storage also included).
Decompress drivers as in the
I have decided to debug the situation.
1. Step
[GuiUnattended]
DetachedProgram=cmd.exe
Arguments=/K echo %SYSTEMROOT% C:\NETINST\bubu.txt
It's working, after installation process c:\netinst\bubu.txt is created,
and
contain C:\WINDOWS. That means (for me) that cmd.exe was called
Hi,
sometimes it is better to dont ask why it is not working... Try this:
create a script which does the work you want to do and call this script
You can place it in $OEM$ so it will be on the hard disk after the first
step of installation.
(my 2 cents)
Greetings mario
tovis schrieb:
I
