mazin

I think that "Default User" is not usable/effective at other times than T-13 and T-12! When I want to apply something to the "Default User", hence any user afterwards; I do it at T-13 via SVCPACK.INF! I, then, use %UserProfile%!

Thanks.

I use this to register WinZip v9.0! I hope it works for v10, too. BTW, I HATE autoit.

I'm sorry for that. But since some of your apps install correctly under your SVCPACK.INF, then I think your INF is good. You may want to check your HotFixes. I mean if all other apps install well except HotFixes, then there's something wrong with them. This is just a thought.

I wonder if that reg file used for v9.0 works.

@ totoymola I enjoyed your ResEdit.msi! Thanks!

Oh, I forgot your request! Look, here, please.

Your XISTA is a very attractive theme, especially, if applied with ColorStyle=NormalColor! Also, ColorStyle=Aero is very nice. One thing, however, is why my mouth stops for a while when the pointer touches an object? For UXTHEME, is it important for your theme, specifically? The pic, on the top right corner in your first post, is for autorun SETUP.EXE! Will you please say how can it be replaced in my SETUP.EXE? Ah, and you used some foreign fonts in your pics. Adobe Photoshop 7.0 asked if I wanted to replace some fonts. Can you please upload those fonts, too? What's new.psd for? I like your GRFX so much. Keep up the good work. Thanks.

They are not in the same file. logonon screen = logonui.exe boot screen = NTOSKRNL.exe

Nice GFX. I can't wait!

Does your CAB contain foldres/ubfolders?

@ _sergio_ I integrated SP1 into my XPCD; and when SP2 released I integrated it, too. So, I have both SP1.cab and SP2.cab (plus Driver.cab, of course!) in .\i386\ Each one of those three CABs contains four files: 1- ntoskrnl.exe 2- ntkrnlmp.exe 3- ntkrnlpa.exe 4- ntkrpamp.exe Also, there's another instance of ntoskrnl.exe (actually: ntoskrnl.ex_) in .\i386\ I extracted each CAB. I changed the boot screen (image) in each EXE. I re-cabbed the CABs again. I replaced the original CABs with the newly re-cabbed ones. Also, I MakeCabbed the edited ntoskrnl.exe (to: ntoskrnl.ex_) and replaced the one in .\i386\ So, whatever KRNL is your processor, no worry. Hope it helps.

@ Yurek3 Thank you for your feedback.

HUH! That easy?

Actually, I used attrib -r -a -s -h with /S to remove attributes from files in the main directory and subdirectories. attrib -r -a -s -h /S /D "%TEMP%" I added /D to remove attributes from subdirectories, as well. This will make it be easy for rd /S /Q "%TEMP%\" to delete all subdirectories without leaving some ones behind. It could be good if /A (your idea) is functioning the same with directories. I mean something like this: rd /A /S /Q "%TEMP%\" If it could be, then three lines of code can be shrinked to one. My TEMP is now clean; so I can't test it, however. Thanks for the tip anyway.

T D has got a nice one there. However, there are different scenarios. I don't know yours, specifically! I'm going to list what in mind for cleaning up a user's TEMP directory, leaving %SystemRoot%\Temp as it is. I'll assume that your PC has a single user or multiple users with the same preference of cleaning up their TEMP directory. Scenario 1: CleanUp on demand. Inside any batch file you use during Windows Setup, add the following lines: echo @ECHO OFF>%SystemRoot%\CL.CMD echo echo.>>%SystemRoot%\CL.CMD echo echo.>>%SystemRoot%\CL.CMD echo echo Cleaning Up My %TEMP%>>%SystemRoot%\CL.CMD echo attrib -r -a -s -h /S /D "%%TEMP%%">>%SystemRoot%\CL.CMD echo del /F /S /Q "%%TEMP%%\*.*">>%SystemRoot%\CL.CMD echo rd /S /Q "%%TEMP%%\">>%SystemRoot%\CL.CMD That script can be put in a batch file running at T-39, T-13, T-12, T-9, and actually at any stage. The script creates CL.CMD in Windows folder. And, when run, CL.CMD cleans the user's TEMP directory. Being in Windows folder, CL.CMD can be called anytime by any user to do its job. A user can just go to Start-->Run and type CL, then press ENTER. And VOILA! Scenario 2: CleanUp on demand and at System StartUp. We use the same script above with extra one line (REG ADD HK..): REG ADD HKLM\Software\Microsoft\Windows\CurrentVersion\Run /v "TEMP CleanUp" /d %SystemRoot%\CL.CMD echo @ECHO OFF>%SystemRoot%\CL.CMD echo echo.>>%SystemRoot%\CL.CMD echo echo.>>%SystemRoot%\CL.CMD echo echo Cleaning Up My %TEMP%>>%SystemRoot%\CL.CMD echo attrib -r -a -s -h /S /D "%%TEMP%%">>%SystemRoot%\CL.CMD echo del /F /S /Q "%%TEMP%%\*.*">>%SystemRoot%\CL.CMD echo rd /S /Q "%%TEMP%%\">>%SystemRoot%\CL.CMD Same as above, the script creates CL.CMD in Windows folder. Additionally, it puts a call for it in HKLM\Run making it be run at every system startup, whatever the user account being logged in. Same as above, CL.CMD cleans the user's TEMP directory. Being in Windows folder, CL.CMD can be called anytime by any user to do its job, and not only at system startup. A user can just go to Start-->Run and type CL; then press ENTER to run CL.CMD! One thing I'm not sure of is wether REG ADD works at T-39! Surely, REG ADD works at the other stages. Note: In the second scenario, if the PC is a multi-user machine where each user wants to control his own TEMP, then we just replace HKLM with HKCU. This requires a user to log in using his own account, then apply the script. In such a case, we add that script to a batch file running at T-13. I haven't tested it at T-12, however. The script, in that case, will be slightly different as follows: echo @ECHO OFF>"%UserProfile%\Desktop\DELifNO.CMD" echo REG ADD HKCU\Software\Microsoft\Windows\CurrentVersion\Run /v "TEMP CleanUp" /d %%SystemRoot%%\CL.CMD>>"%UserProfile%\Desktop\DELifNO.CMD" echo del %%0>>"%UserProfile%\Desktop\DELifNO.CMD" echo @ECHO OFF>%SystemRoot%\CL.CMD echo echo.>>%SystemRoot%\CL.CMD echo echo.>>%SystemRoot%\CL.CMD echo echo Cleaning Up My %TEMP%>>%SystemRoot%\CL.CMD echo attrib -r -a -s -h /S /D "%%TEMP%%">>%SystemRoot%\CL.CMD echo del /F /S /Q "%%TEMP%%\*.*">>%SystemRoot%\CL.CMD echo rd /S /Q "%%TEMP%%\">>%SystemRoot%\CL.CMD So, when a user logs in using their account, they will find "DELifNO.CMD" on their desktop. If a user wants a cleanup on demand, they just delete the file "DELifNO.CMD"! Otherwise, ie both cleanups, they run "DELifNO.CMD". Ah, and "DELifNO.CMD" is self-deleted. I hope I was clear and well understood.

I think it should be [... and thereby going directly into the second phase of copying...?] I hope I am correct..

Yes, that's what MS says. This is what I say: RD command is ABLE to delete a bunch of directories even without wildcards . Also, the back slash ensures that the TEMP folder itself is not removed. It's not documented, but just a brain HARSH! Then, the whole %TEMP% clean-up is solved, this way: attrib -r -a -s -h /S /D "%TEMP%" del /F /S /Q "%TEMP%\*.*" rd /S /Q "%TEMP%\" Hope you like it. B)

It's not a good idea to use HKLM if the computer is a multi-user environment. B) You'd better use HKCU, instead; so that every user can be able to control their %TEMP%. However, DEL command does not delete directories, but files only. So, what about directories inside %TEMP%?

I use install.ins to slipstream my Favs. Look in my signature.

Thank you very much. I made some more editing for even my original explorer.exe! It looks like I , accidentally, deleted those strings from the dialog!

@ cancerface Tested! SWEET! No errors! Thanks!

I think you mean WINNT.BAT!

ONCE in all my life, and it was a bloody day, when I tried to upgrade from Win2000 to WinXP. I received tons of those messeges, not only against system files; but also against some software drivers. I think UPGRADE needs deep and careful preparation. I can understand why some of us need UPGRADE not fresh install. But, unfortunately, I can't help you in practical manner. Just a thought, if you have any hacked system files on your system; try to restore the original files prior to upgrading. Plus, if you have software drivers (was the scanner in my situation) that are not compatible with WinXP; uninstall them first while running your old system (Win2000 in my situation). You'd better even unplug them unless you get XP-compatible software for them. May GOD be with you!

You may search for CDBURN.exe (.zip).