• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About johann83

  1. Heres a batch file that does something like what you are trying to do. It looks at a three digit number in a text file (file path/name specified in batch) and increments it and then writes it back out to the file. In the mean time the old and new values are stored in two variables which could be used elsewhere in the script (e.g. in your CDIMAGE commands). I hope this helps you. @ECHO OFF CLS SETLOCAL ENABLEEXTENSIONS ENABLEDELAYEDEXPANSION :: Define the name of the file containing the version number SET VERFILE=VER.TXT :: Make sure the version file exists IF NOT EXIST %VERFILE% GOTO ERROR :: Check current version (from file) FOR /F "delims=" %%F IN (%VERFILE%) DO SET CURRVER=%%F :: Increment the version number IF "%CURRVER%" LSS "009" ( SET /A TMP1=%CURRVER:~-1%+1 SET NEWVER=%CURRVER:~0,-1%!TMP1! ) ELSE IF "%CURRVER%" EQU "009" ( SET /A TMP1=%CURRVER:~-1%+1 SET NEWVER=%CURRVER:~0,-2%!TMP1! ) ELSE ( SET /A TMP1=%CURRVER:~-2%+1 SET NEWVER=%CURRVER:~0,-2%!TMP1! ) :: Write the new version number to a temporary file ECHO %NEWVER%>>%VERFILE:~0,-4%.TMP :: Update the version file with the temporary one XCOPY /Q /Y %VERFILE:~0,-4%.TMP %VERFILE% >> NUL DEL %VERFILE:~0,-4%.TMP >> NUL :: Done, exit the script GOTO END :ERROR ECHO An unexpected error occured during this operation. :END ECHO. PAUSE EXIT Regards, Matt
  2. I believe the correct spelling is "intrigues" At any rate, if you hex edit the sfcfiles.dll file you will find a lengthy list of file names as wamatt says. However, it doesn't seem to me like this list is long enough to contain all the files that are protected by SFC, and one would think that there should be an easier way for MS to add something to SFC protection (besides updating the DLL, obviously). I'd be interested to hear anyone else's thoughts on the matter... Matt
  3. I was thinking more along the lines of if someone wanted to disable SFC for other files, besides those in %ProgramFiles%. Such as uxtheme.dll perhaps... It would make it tremendously more user friendly to allow some sort of user control over what files are removed from protection. I am by no means saying that what you did is no good, I was just trying to make a suggestion. Regards, Matt
  4. Just curious which folders this removes from SFC? Is it only things in %ProgramFiles% or are there others? Do you have a list? I know you are doing this as a (free) service to others, but I think it would be nice to allow the user to select which items to be removed from SFC. I'm not entirely sure how you did this, so I don't know if that could be done easily, but maybe you could extract the list of protected files from the DLL and then allow the user to specify which ones to disable via an INI (or similar). Just a thought... Regards, Matt
  5. Try this: ;Set the temp directory to C:\Temp [HKEY_CURRENT_USER\Environment] "TEMP"="C:\\Temp" "TMP"="C:\\Temp" But just like all HKCU tweaks, it will need to be applied via cmdlines.txt to take effect for all users... Hope that helps. Matt
  6. I have the same problem with the same mobo. I guess we'd need to take up the issue with Abit really. In reality, since I don't reinstall all that often (hopefully) I just open the case and disconnect the PATA drive. I have also noticed that if I have a bootable OS on both the SATA and PATA drives, the PATA one boots no matter what I set in the BIOS. Of course, I haven't checked it lately and there have been a couple of BIOS updates, so maybe they fixed that one. Matt
  7. I have something in my REG files that seems to work for this. I'll look it up when I get home and post back... Regards, Matt
  8. Install them using the /SAVEINF="filename" option to record an install INF file (InnoSetup equivalent to an ISS file). Then in your unattended use the /LOADINF="filename" option to install unattended. InnoSetup switches are available here. I have not tried the components option, but if you create an INF it has a list of components in it. The components list from my install INFs are below. I don't know if I selected everything though, so something may be missing. QuickTime Alternative Components=mpclassic,qtcodec,qtdirectshow,qtplugins,qtcpl Real Alternative Components=mpclassic,realcodec,realdirectshow
  9. Looks like you don't really want an answer then, because what you want to do cannot be done. Sorry...
  10. UPDATE This version works exactly as expected.
  11. I'm trying that now, thanks. I also noticed one other thing (unrelated to SATA). With this new DirectX hotfix the *.CAT file that ends up in the SVCPACK.INF file does not conform to the 8.3 convention that everything else does. Is this by design? As a side note, it seemed to work fine with the long file name... Regards, Matt
  12. I'm having a problem with the SATA integration with the latest "test" version of XPCREATE. I'm using the SI3112R controller on my motherboard and have included the drivers in the $OEM$/$1/Drivers directory. XPCREATE says that it located the drivers and integrated them, but the entries in TXTSETUP.SIF are not there. The SI3112R.SY_ file is correctly added to the I386 directory and the headings for the entries in TXTSETUP are there (i.e. [sourceDisksFiles] etc) but the contents for each heading are not there. Log files are attached. If I need to send the SATA drivers, I can do that too. For now, I manually added the entries, but thats not really an optimal solution. Thanks. Matt
  13. GM, I know you don't/won't support this method, but I was able to get Windows Update to report it as installed by first slipstreaming DX9 into the XP source using batches from jdeboeck. I then put the DirectX90-KB839643-x86-ENU.EXE file in the HF1 directory for XPCREATE. Even if you don't support this method, perhaps it will help you figure out the Windows Update problem. Regards, Matt
  14. Found something interesting about this problem. It goes away if I install windows "attended" (i.e. the normal install works perfectly). For debugging the unattended, all I did was take the attended install source and added a stripped down WINNT.SIF file. The contents of this file are below, it came directly from setupmgr.exe and I added the UnattendSwitch=Yes line. Any thoughts? ;SetupMgrTag [Data] AutoPartition=1 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=No UnattendSwitch=Yes TargetPath=\WINDOWS [GuiUnattended] AdminPassword=361902e619afae135e34749e73fa9c64c37021a83fcd318d220b82eb191a53dd EncryptedAdminPassword=Yes OEMSkipRegional=1 TimeZone=35 OemSkipWelcome=1 [UserData] ProductID=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX FullName="Matthew J. Volkar" OrgName="" ComputerName=JOHANN83 [Display] BitsPerPel=32 Xresolution=1280 YResolution=1024 Vrefresh=75 [Identification] JoinWorkgroup=WORKGROUP [Networking] InstallDefaultComponents=Yes Again, the normal ("attended") XP install works as expected, while the same source with the above WINNT.SIF file added exhibits the IE/OE problems discussed in my first post. Any thoughts would be appreciated. Thanks, Matt
  15. From my original post... Which is exactly what is recommended in the link you provided.