Jump to content

xian7479

Member
  • Posts

    28
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    New Zealand

About xian7479

xian7479's Achievements

0

Reputation

  1. Look at txtsetup.oem, under those [Files.XXXX] sectors, find those lines start with "driver", you'll get all the files you need.
  2. Do you have an IDE HDD pluged? If so, unplug it first. If you are using the mobo built-in nvraid controller, you can just boot from the installation DVD 'cause it has nvraid driver integrated, you do not need to load nvraid driver, and see if this solves the problem. If all the above do not work, unplug your sata150 array, boot from DVD, do a clear installation on your sata300 array and it will definitely work unless your SATA array or the physical disk is damaged.
  3. Had a look inside IE7, it looks like a normal Windows update. but when I tried to use my samll windows update integration tool (which is mainly an inf parser) to integrate it, I run into a problem. The IE7 inf file has a section called DynamicStrings I never seen before, it contains following entries BRANDGUID = InstallPathRegistryKey,"SOFTWARE\Microsoft\Internet Explorer","BrandGUID" DownloadedProgramFiles = CustomStringTable,DownloadedProgramFiles ProductIDCode = CustomFunction,iecustom.dll,GetProductIDCode SystemTools = CustomStringTable,SystemTools those variable have to be converted to something that setupapi.dll can understand in order to integrate IE7 into Windows installation source but I've no idea how to do it.
  4. I have tested that before T-9 there are only a few .cat files inside dllcache folder so a command executed before T-9 won't delete system files from dllcache. @Takeshi More precisely, I wanna delete files from dllcache before first reboot. In fact I'm writing a small utility to integrate windows updates, as the Cumulative Security Update for IE6 does delete file, so I think it's more appropriate to delete this file before or during windows installation. If I delete the file directly from installation source, I would get a error message in setuperr.log since SETUPAPI.DLL cannot register the file specified in SYSSETUP.INF which I've deleted. SYSSETUP.INF is digital signed, in order to modify it, I have to modify SETUPAPI.DLL and SFCFILES.DLL to disable digital signature verification, but I still got some problem as sometimes wrong sections in INf file without digital signature get installed. Finally, I think it should be easier to just delete this file during windows installation, but I don't wanna use HKLM RunOnce and RunOnceEx as end user may also use those keys and there is possibility to have some conflict. Currently I'm using HKLM RunOnce as an alternative method but I still wanna find a way to delete this file before first reboot.
  5. @Takeshi Thanks for your reply but as I mentioned above that I'd like those files to be deleted BEFORE first time user login, so RunOnce and RunOnceEx are not what I'm looking for, is there some methods we can execute a command at or after T-9 but not the SetupParams from WINNT.SIF?
  6. I wanna delete some file from both system32 folder and dllcache folder before first time user login, without using WINNT.SIF and/or $OEM$. Currently, I run a CMD file from svcpack.inf (at T-13) to delete those files, but after first time user login, I find that files in system32 folder were deleted but files in dllcache folder are still there. If I run the same CMD file after user login, files in both system32 folder and dllcache folder are deleted. Does anyone know when the dllcache folder is created and is there any method to delete files from dllcache before first time user login? Thanks!
  7. Create a folder parallel to i386 called $OEM$, create a file called cmdlines.txt inside $OEM$, add following content [COMMANDS] "RunOnceEx.cmd" then put RunOnceEx.cmd in $OEM$. You don't need to add anything to winnt.sif, this will get executed at T-12 even if you set OemPreinstall to No.
  8. Tried to add some reg entries to HKLM RunOnce key by installing an INF file yesterday during UA installation of WinXP SP2, instead of adding those reg entries, Windows executes the commands (which are the values of thoes entries) immediately. Also tried to install this INF file on a working WinXP SP2 system, got the exactly same result. If those entries are added to some key else, it works properly. Does anyone has some ideas on this? Is there some motheds we can add RunOnce entries by using INF files? Thanks.
  9. Does anyone know how to midify SETUPAPI.DLL so system files like LAYOUT.INF can be edited? The only info I've found till now is from HFSLIP help, but the method only work for Win2k3 SP1 English version. Is there a version independent solution? Thanks in advance.
  10. extract the MSI first, then using switchs PIDKEY=*****-*****-*****-*****-***** /qn /norestart replace *****-*****-*****-*****-***** with your serial number.
  11. I've moved this file offline 'cause I found a bug. Last week I used this program to integrate drivers into my Windows source (though this tool is not designd for driver integration, I personally integrate drivers by calling fonctions inside this program), I found it didn't write unicode inf file properly. I'll put it back when I fix this bug along with some other issues.
  12. Have you tried to change the entry in SourceDisksFiles section to [sourceDisksFiles] percsas.sys = 1,,,,,,4_,4,1,,,1,4 'cause you current entry won't copy percsas.sys to the boot folder.
  13. The GUI is very simple, just locating the Windows installation source and where are the updates you wanna integrate, after press the process button, it minimises to system tray, after the integration process finishes, it will popup a message box to notify that the process has finished.
  14. Recently I wrote a small tool for Windows updates integration. Basicly speaking, it's similar to the hotfixes integration function of nlite. Though nlite is a great tool in modifying Windows installation source, it has some weakness in integrating Windows updates, for example, it modifies some unnecessary files even if people only use it for Windows updates integration, it fails to delete the files and reg entries that should be deleted on updates installation, and it can integrate hotfixes that should not apply to the Windows installation source, e.g. integrate a WMP10 hotfix to a Windows installation source which only has WMP9. Based on those, I decided to write this tool. Currently, the tool is partially working (tested on Windows XP Professional SP2 X86 source for hotfixes listed in HOTFIXES: Win2000 SP4 – WinXP SP1 – WinXP SP2, that KB917734 cannot be process). I've a few questions and need some help. First, does anyone know the syntax of "Prerequisite" directive in an INF file, I've searched msdn site but haven't found anything useful, I need more info to finish the condition check part of the tool. Second, in my knowledge, Windows Server 2003 has 4 editions: Web Server, Standard Server, Enterprise Server and Datacenter. But in Win2K3 updates INF files, there are directives for DataCenterFiles, BladeFiles, BusinessFiles, AdvancedFiles, ServerFiles, ProfessionalFiles. Could anyone piont out which directive applies to which edition of Win2k3. Third, how to determine that a Windows XP Windows installation source is Professional or Home Edtion, and a Windows Server 2003 installation source is Web Server, Standard Server, Enterprise Server or Datacenter Edition, excepting for looking at the EULA.txt. (Solved) The tool is available HERE, any contribution and feedback are welcome.
  15. I think that WMP10 has more codecs than WMP9 thus surpport more media formats.
×
×
  • Create New...