Jump to content

dev.man

Member
  • Posts

    5
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    France

About dev.man

Contact Methods

  • Website URL
    http://

dev.man's Achievements

0

Reputation

  1. @Bâshrat the Sneaky What is odd is the ATTRIB behavior/syntax when you write "ATTRIB -A -R -S -H I386 /S /D": It will remove the attributes only for the files and directories named "I386", in this case only THE directory I386 because there is no file or sub-directory named like that inside I386. In the file RUN_ME.CMD you should write: REM ### Removes attributes of some files we're going to overwrite. ### ATTRIB -A -R -S -H I386\*.* /S /DThis will remove all attributes for all the files and directories inside the directory I386, thus avoiding all the error messages "Error: Could not write to file" when you run RUN_ME.cmd (for example in M2 method, STEP 3, B- slipstreaming DriverPacks, trying to write in TXTSETUP.SIF and other files) Although I don't think "-A" is useful, it does not hurt. By the way, GREAT JOB! you are doing and... good luck for your exams.
  2. Ok I found a solution: In Microsoft DDK there is a tool named snetcfg.exe (source file that you must compile). Unattended installation of Qos Packet Scheduler is done like this: snetcfg.exe -v -c s -i ms_psched
  3. @xtp183, I think you are right, Qos Packet Scheduler is installed when you install with an original XP CD. @cumminbk, you are right, it is possible to install Qos Packet Scheduler with winnt.sif. But I currently have a lot of running machines, XP or 2000, without Qos Packet Scheduler because they were installed a long time ago with an unattended process (winnt.sif or Unattended.txt). Now I must deploy Qos Packet Scheduler on these existing machines because it's required by a new software (to deploy too). I have existing deployments means, logon scripts or other deployment software, but I don't have an unattended installation package to install Qos. So I'm searching a way to deploy it in an attended way on already existing running machines, something like a command line with silent switches, a batch, a script, or whatever... Many thanks for your replies.
  4. /integrate is faster than manual process, and more reliable (no typo errors, normally...). A good example is "Windows 2000 SP4 Update Rollup 1" which is a cumulative patch that contains 49 hotfixes: despite some few changes that must be manually made in svcpack.inf (erroneous subdirectory entries...), the /integrate option is really time-saving. (Remark: /integrate is not available for old hotfixes. )
  5. Hello, I am searching for a way to install the Windows Network Service "QoS Packet Scheduler" in an unattended way. The target computers are running Windows 2000 or XP and have access to a Windows installation source share via network (if needed). I failed with MS devcon.exe tool, may be I do not know how to use it... Thanks.
×
×
  • Create New...