Jump to content

erik_demon

Member
  • Posts

    419
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

Everything posted by erik_demon

  1. Hey guys I am going to test the DP tonight. I already slipstreamed the DP's and I noticed 3 small things (very non-critical ) 1. quote from Installation_Instructions.htm (DP BASE) It should not be renamed to BTS_DPs_auto.cmd because in the BTS_DPs_Slipstreamer_V506.cmd the line is like this: %IE% BTS_DPs_autocopy.cmd START BTS_DPs_autocopy.cmd So the file should be renamed to BTS_DPs_autocopy.cmd 2. The file cmdlines_fix.exe is left on the root of the CD. This should be added to the RUN_ME.cmd: %IE% cmdlines_fix.exe DEL /Q cmdlines_fix.exe 3. DP CPU is not added to the DP readme file (I know, this has nothing to do with the slipstreaming but I just mention it anyway ) The rest of the slipstream went fine. I will post the results of my format tonight. EDIT: Oh yeah, almost forgot to mention I use method 2 with KtD and I choose to use GuiRunOnce
  2. @DigeratiPrime I don't think that this will work for (intel) Chipset drivers aswell When slipstreaming the drivers, a $OEM$\$$\INF folder is created with the latest Intel inf files. So if you don't reslipstream this DP, you won't have the newest (intel)chipset drivers available. For all other DP's it should be fine EDIT: Unless your DP is very old, and you still have the DP folder instead of the D folder
  3. Hey Welcome to MSFN This is not entirely correct. If you want to copy some files to the root of the drive where windows is installed (for you is that the C drive), you have to create a folder inside the $OEM$ folder. This folder is called $1. Your structure should now look like this: $OEM$\$1\install\enz for more info about this, please check-out this page For more info about the RunOnceEx, look here and if you want to install directly from the CD, look here (this however is a bit more diffecult, I would recommend you to start with the link above first. Good luck!!
  4. It is strange, for some people (like me) [Components] is working, for other people, it does not. Is [Components] depending on another alue in the winnt.sif in order to work?
  5. Could you please check if this ... [OptionalSrcDirs] SVCPACK ... is in your dosnet.inf? EDIT: I believe Nlite does this automatic, and I think the /intergrade switch does this aswell, but it is just to be on the safe site
  6. It doesn't work for me Bastian_W, what is download.exe? It doesn't seem to be in winxp.
  7. @Nois3 This is great thanks I do have a question now Could you please explain this, does this mean that after 30 days, your windows stops functioning, and you need to reaply your serial? EDIT: or does this mean that in 30 days your CD won't accept the code?
  8. hey I believe you can put it every where between... REM Example, how to look for CDROM-drive. Must have a file to identify in its root (like WIN51 or WPI.ico). for %%i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%i:\win51 set CDROM=%%i: echo Found CD-Rom as drive %CDROM% and... REM Start WPI and wait for its end start /wait \wpi\WPI.hta If you would like to, you could even start it from inside your WPI
  9. Hi First things first, please remove your serial key (I already collected two keys on this board today ) I don't know much about network installs but i will try to help Do you get any errors? Maybe this topic can help you out
  10. Hey this is why it doesn't work: OemPreinstall=No should be OemPreinstall=YES EDIT IMPORTANT: Please remove your serial key
  11. Glad I was able to help about the winnt.sif creation thing, I updated my method so that it now creats a (simple) winnt.sif Check it out here If you want it to work on a floppy disc, select from line 142 to 195, and replace all %CDROM% to A:\ EDIT: line 142 should be ECHO;SetupMgrTag >>%CDROM%WINNT.SIF and line 195 should be SET answerfile_name=winnt.sif
  12. Hey Welcome to MSFN Your winnt.sif is okay When you install from a CD, your $OEM$ has to be parallel to your i386 folder. When you install by using winnt.exe or winnt32.exe your $OEM$ for has to be inside the i386 folder (like you have now) EDIT: a tip: You are using $OEM$\C\firstrun Using $OEM$\C is only intersting if you want to copy specific things to specific drives, like for instance: $OEM$\C\firstrun and $OEM$\D\Other_crap. Instead of $OEM$\C you could also use $OEM$\$1 because $1 will copy everything inside to the drive where windows is installed
  13. Thank you for your efforts Although I do not have a TV card, i'm sure that it will come in handy someday. Also thanks for the other packs!
  14. Note that these driver are for Windows MCE. They should work okay on Windows XP though. I don't believe that these drivers are WHQL for all Nvidia card Quote from guru3d
  15. New version available (see first post) This version is written for my system, so if you want to use it, you need to modify it. Since my batch skills are not that great, it may be that parts of the script can be optimized. If you see such a part, please comment I tested it and for my system it works great EDIT: For the winnt.sif creator, credits go to gunsmokingman who designed it (see the link in post nr. 6 ) Thanks
  16. Hey If you want to do this, you need to change some values in the txtsetup.sif aswell Please check-out this topic for more info about this
  17. New updates available, check out this page I can see the downloads with windows updates v6, but the manual download links aren't working yet EDIT: Since I have some problems with the DL links, here's a screenshot with all updates EDIT2: KB893066 is upgraded to version 2
  18. I don't know what's the problem, but you don't need to double post it
  19. About the removal tool: Remove the Malicious Software Removal Tool v1.5 from windows updates(KB890830) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RemovalTools\MRT] "Version"="63C08887-00BE-4C9B-9EFC-4B9407EF0C4C" And for MS Office 2003 KB896999 is available (Outlook spam filter)
  20. I agree and maybe the same can be done for the "applications database"
  21. REG ADD %KEY%\100 /VE /D "Registry Changes and Tweaks" /f REG ADD %KEY%\100 /V 1 /D "REGEDIT /S %systemdrive%\install\tweaks.reg" /f I do it like this (no REGEDIT32.EXE but just REGEDIT) I would recommend to this at the end of the RunOncEx, but before your clean-up. If you do it afterwards, tweaks.reg doesn't exist anymore EDIT: by the way, I also use "REGEDIT /S tweaks.reg" in my cmdlines.txt. (I don't know if it matters, I only know that it works )
  22. It is correct that not all tweaks work when excecuted during cmdlines.txt (some current user tweaks I believe) If you want to apply your tweaks a second time, you can do it during GuiRunOnce or RUnOnceEx (be adviced that most reg changes only work after a reboot)
×
×
  • Create New...