Jump to content

Marztabator

Member
  • Posts

    481
  • Joined

  • Last visited

  • Donations

    $0.00 
  • Country

    United Kingdom

Everything posted by Marztabator

  1. I was just wondering if there'll be any compatibility problems from installing a product that came out before the service pack, that's all.
  2. I see. It's just that I don't like the idea how mobiles save a message for only '7 days'. To me that isn't really saving it as such, more like keeping it company for a while then kicking it back out into the rain again. Do Carphone Warehouse sell things like these, or is there a high-quality and detailed (while still easy to understand for a dummy like moi) webpage somebody could link?
  3. ....your mobile phone answerphone messages? For archival purposes, naturally. Is there any software that will allow me to do this? What link-up cable of sorts would I require?
  4. Regarding bundling matters for your customised XP setup CD that is?
  5. Ooops. I guess the overlong length of it kinda irritates a few peeps. Sorry guys. Might change it later if you really wish... Anyways, I believe I've found a workaround for this 828035/Messenger-service problem. If you have a copy of your XP CD with MSGSVC.DL_ still in the i386 directory, extract that and copy/move the dll file into $OEM$\$$\System32. So long as WU can detect the file, the hotfix will no longer be listed on the Critical Updates table. What's more, the service won't be fully installed, leaving the DLL pretty dormant and unattached. Neat eh? Oh, and I must add, compliments to nuhi for solving the zipfldr.dll/WU problem! Wonder how you cracked it, boyo?
  6. I removed a few needless services using nLite - I'm not sure if KB828035's probs are to do with services??? The log in the Windows directory is as usual overlong and hard to decipher, haha. Here it is in full: [KB828035.log] *** 2004/7/6 23:47:1.578 *** Exe = update.exe, Version = 5.4.1.0 *** ================== Update.exe started at 7/ 6/2004 at 23:47: 1 ================== *** Service Pack started with following command line: /O /U /N /Z *** ---- Old Information In The Registry ------ *** Source:D:\WINDOWS\System32\SETA71.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\ddraw.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA7C.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dplayx.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA85.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dsound.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETD6C.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbcint.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDBB.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbc32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDC8.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbccp32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETE13.tmp Version: 2.575.1022.0 *** Destination:D:\WINDOWS\System32\msorc32r.dll Version: 2.0.573.0 *** Source:D:\Program Files\Common Files\System\OLE DB\SETE16.tmp Version: 2.80.1022.0 *** Destination:D:\Program Files\Common Files\System\OLE DB\msdaorar.dll Version: 2.0.70.0 *** Source:D:\WINDOWS\System32\SETEEE.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\msjava.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETEF6.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\vmhelper.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETF31.tmp Version: 5.131.2600.1243 *** Destination:D:\WINDOWS\System32\cryptui.dll Version: 5.0.131.0 *** Source:e:\4051f2b904de4cabe8 Version: *** Destination: Version: *** Source:e:\d1520f8aa26d660bb371 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000002_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000003_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:e:\f731d066794cf07a36ce85abb42510f3 Version: *** Destination: Version: *** Source:e:\4ce34a628064d05bca0eb82609 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000001_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000004_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\SETF69.tmp Version: 5.131.2600.1123 *** Destination:D:\WINDOWS\System32\crypt32.dll Version: 5.0.131.0 *** Source:D:\WINDOWS\System32\SETF6B.tmp Version: 5.1.2600.1190 *** Destination:D:\WINDOWS\System32\cryptsvc.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF73.tmp Version: 5.1.2600.1164 *** Destination:D:\WINDOWS\System32\newdev.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF75.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\ole32.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF79.tmp Version: 5.1.2600.1254 *** Destination:D:\WINDOWS\System32\rpcrt4.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7B.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\rpcss.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7F.tmp Version: 6.0.2800.1233 *** Destination:D:\WINDOWS\System32\shell32.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\System32\SETF85.tmp Version: 6.0.2800.1143 *** Destination:D:\WINDOWS\System32\urlmon.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\AppPatch\SETF93.tmp Version: *** Destination:D:\WINDOWS\AppPatch\sysmain.sdb Version: 0.0.2.0 *** Source:e:\68a8798849478b603d Version: *** Destination: Version: *** Source:e:\7c1782e8be67eda630db0baa44 Version: *** Destination: Version: *** ---- New Information In The Registry ------ *** Source:D:\WINDOWS\System32\SETA71.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\ddraw.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA7C.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dplayx.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA85.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dsound.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETD6C.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbcint.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDBB.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbc32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDC8.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbccp32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETE13.tmp Version: 2.575.1022.0 *** Destination:D:\WINDOWS\System32\msorc32r.dll Version: 2.0.573.0 *** Source:D:\Program Files\Common Files\System\OLE DB\SETE16.tmp Version: 2.80.1022.0 *** Destination:D:\Program Files\Common Files\System\OLE DB\msdaorar.dll Version: 2.0.70.0 *** Source:D:\WINDOWS\System32\SETEEE.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\msjava.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETEF6.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\vmhelper.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETF31.tmp Version: 5.131.2600.1243 *** Destination:D:\WINDOWS\System32\cryptui.dll Version: 5.0.131.0 *** Source:e:\4051f2b904de4cabe8 Version: *** Destination: Version: *** Source:e:\d1520f8aa26d660bb371 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000002_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000003_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:e:\f731d066794cf07a36ce85abb42510f3 Version: *** Destination: Version: *** Source:e:\4ce34a628064d05bca0eb82609 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000001_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000004_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\SETF69.tmp Version: 5.131.2600.1123 *** Destination:D:\WINDOWS\System32\crypt32.dll Version: 5.0.131.0 *** Source:D:\WINDOWS\System32\SETF6B.tmp Version: 5.1.2600.1190 *** Destination:D:\WINDOWS\System32\cryptsvc.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF73.tmp Version: 5.1.2600.1164 *** Destination:D:\WINDOWS\System32\newdev.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF75.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\ole32.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF79.tmp Version: 5.1.2600.1254 *** Destination:D:\WINDOWS\System32\rpcrt4.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7B.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\rpcss.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7F.tmp Version: 6.0.2800.1233 *** Destination:D:\WINDOWS\System32\shell32.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\System32\SETF85.tmp Version: 6.0.2800.1143 *** Destination:D:\WINDOWS\System32\urlmon.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\AppPatch\SETF93.tmp Version: *** Destination:D:\WINDOWS\AppPatch\sysmain.sdb Version: 0.0.2.0 *** Source:e:\68a8798849478b603d Version: *** Destination: Version: *** Source:e:\7c1782e8be67eda630db0baa44 Version: *** Destination: Version: *** SetAltOsLoaderPath: No section uses DirId 65701; done. *** FetchSourceURL: SetupOpenInfFile Failed to open file: e:\762b13c832c75f62c2258e5595bccc\sp2\update\update.url *** DoInstallation: FetchSourceURL for e:\762b13c832c75f62c2258e5595bccc\sp2\update\update.inf Failed *** CreateUninstall = 0,Directory = D:\WINDOWS\$NtUninstallKB828035$ *** LoadFileQueues: SetupGetSourceFileLocation for halaacpi.dll failed: 0xe0000102 *** BuildCabinetManifest:SetupOpenInfFile failed with error INVALID_HANDLE_VALUE *** AnalyzePhaseZero used 0 ticks *** No d:\windows\INF\updtblk.inf file. *** User specified '-o'; ignoring any OEM driver files. *** AnalyzePhaseOne: used 16 ticks *** AnalyzeComponents: Hotpatch analysis disabled; skipping. *** AnalyzeComponents: Hotpatching is disabled. *** AnalyzePhaseTwo used 0 ticks *** AnalyzePhaseThree used 0 ticks *** AnalyzePhaseFive used 0 ticks *** AnalyzePhaseSix used 0 ticks *** AnalyzeComponents used 47 ticks *** Downloading 0 files *** bPatchMode = FALSE *** Inventory complete: ReturnStatus=0, 47 ticks *** Num Ticks for invent : 47 *** Allocation size of drive D: is 4096 bytes, free space = 8411840512 bytes *** Drive D: free 8022MB req: 6MB w/uninstall 0MB *** Num Ticks for download : 16 *** CabinetBuild complete *** Num Ticks for Cabinet build : 0 *** Registering Uninstall Program for -> KB828035, KB828035 , 0x0 *** LoadFileQueues: SetupGetSourceFileLocation for halaacpi.dll failed: 0xe0000102 *** SfcTurnOff: System is not Win2k < SP2; Not turning off SFC. *** SfcTurnOff: SFC was not turned off; using MakeSfcFileException. *** MyMakeSfcFileExceptionA: MakeSfcFileException failed; error=0x6ba. *** AtomicReplaceFile: Calling HpReplaceSystemModule( D:\WINDOWS\System32\wkssvc.dll, HFXFB3.tmp, _1992235283_.tmp, FALSE ). *** AtomicReplaceFile: HpReplaceSystemModule failed; status=0xc0000003, location=684. *** DoNoDelayReplace: Atomic replace support not implemented; disabling. *** MyMakeSfcFileExceptionA: MakeSfcFileException failed; error=0x6ba. *** MyMakeSfcFileExceptionA: MakeSfcFileException failed; error=0x6ba. *** Copied file: D:\WINDOWS\System32\wkssvc.dll *** Num Ticks for Copying files : 1281 *** Num Ticks for Reg update and deleting 0 size files : 0 *** UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do. *** ---- Old Information In The Registry ------ *** Source:D:\WINDOWS\System32\SETA71.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\ddraw.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA7C.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dplayx.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA85.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dsound.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETD6C.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbcint.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDBB.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbc32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDC8.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbccp32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETE13.tmp Version: 2.575.1022.0 *** Destination:D:\WINDOWS\System32\msorc32r.dll Version: 2.0.573.0 *** Source:D:\Program Files\Common Files\System\OLE DB\SETE16.tmp Version: 2.80.1022.0 *** Destination:D:\Program Files\Common Files\System\OLE DB\msdaorar.dll Version: 2.0.70.0 *** Source:D:\WINDOWS\System32\SETEEE.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\msjava.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETEF6.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\vmhelper.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETF31.tmp Version: 5.131.2600.1243 *** Destination:D:\WINDOWS\System32\cryptui.dll Version: 5.0.131.0 *** Source:e:\4051f2b904de4cabe8 Version: *** Destination: Version: *** Source:e:\d1520f8aa26d660bb371 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000002_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000003_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:e:\f731d066794cf07a36ce85abb42510f3 Version: *** Destination: Version: *** Source:e:\4ce34a628064d05bca0eb82609 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000001_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000004_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\SETF69.tmp Version: 5.131.2600.1123 *** Destination:D:\WINDOWS\System32\crypt32.dll Version: 5.0.131.0 *** Source:D:\WINDOWS\System32\SETF6B.tmp Version: 5.1.2600.1190 *** Destination:D:\WINDOWS\System32\cryptsvc.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF73.tmp Version: 5.1.2600.1164 *** Destination:D:\WINDOWS\System32\newdev.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF75.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\ole32.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF79.tmp Version: 5.1.2600.1254 *** Destination:D:\WINDOWS\System32\rpcrt4.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7B.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\rpcss.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7F.tmp Version: 6.0.2800.1233 *** Destination:D:\WINDOWS\System32\shell32.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\System32\SETF85.tmp Version: 6.0.2800.1143 *** Destination:D:\WINDOWS\System32\urlmon.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\AppPatch\SETF93.tmp Version: *** Destination:D:\WINDOWS\AppPatch\sysmain.sdb Version: 0.0.2.0 *** Source:e:\68a8798849478b603d Version: *** Destination: Version: *** Source:e:\7c1782e8be67eda630db0baa44 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000005_.tmp Version: 5.1.2600.0 *** Destination: Version: *** ---- New Information In The Registry ------ *** Source:D:\WINDOWS\System32\SETA71.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\ddraw.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA7C.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dplayx.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETA85.tmp Version: 5.3.0.900 *** Destination:D:\WINDOWS\System32\dsound.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETD6C.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbcint.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDBB.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbc32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETDC8.tmp Version: 3.525.1022.0 *** Destination:D:\WINDOWS\System32\odbccp32.dll Version: 3.0.520.0 *** Source:D:\WINDOWS\System32\SETE13.tmp Version: 2.575.1022.0 *** Destination:D:\WINDOWS\System32\msorc32r.dll Version: 2.0.573.0 *** Source:D:\Program Files\Common Files\System\OLE DB\SETE16.tmp Version: 2.80.1022.0 *** Destination:D:\Program Files\Common Files\System\OLE DB\msdaorar.dll Version: 2.0.70.0 *** Source:D:\WINDOWS\System32\SETEEE.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\msjava.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETEF6.tmp Version: 5.0.3810.0 *** Destination:D:\WINDOWS\System32\vmhelper.dll Version: 5.0.0.0 *** Source:D:\WINDOWS\System32\SETF31.tmp Version: 5.131.2600.1243 *** Destination:D:\WINDOWS\System32\cryptui.dll Version: 5.0.131.0 *** Source:e:\4051f2b904de4cabe8 Version: *** Destination: Version: *** Source:e:\d1520f8aa26d660bb371 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000002_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000003_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:e:\f731d066794cf07a36ce85abb42510f3 Version: *** Destination: Version: *** Source:e:\4ce34a628064d05bca0eb82609 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000001_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\_000004_.tmp Version: 5.1.2600.1106 *** Destination: Version: *** Source:D:\WINDOWS\System32\SETF69.tmp Version: 5.131.2600.1123 *** Destination:D:\WINDOWS\System32\crypt32.dll Version: 5.0.131.0 *** Source:D:\WINDOWS\System32\SETF6B.tmp Version: 5.1.2600.1190 *** Destination:D:\WINDOWS\System32\cryptsvc.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF73.tmp Version: 5.1.2600.1164 *** Destination:D:\WINDOWS\System32\newdev.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF75.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\ole32.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF79.tmp Version: 5.1.2600.1254 *** Destination:D:\WINDOWS\System32\rpcrt4.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7B.tmp Version: 5.1.2600.1263 *** Destination:D:\WINDOWS\System32\rpcss.dll Version: 5.0.1.0 *** Source:D:\WINDOWS\System32\SETF7F.tmp Version: 6.0.2800.1233 *** Destination:D:\WINDOWS\System32\shell32.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\System32\SETF85.tmp Version: 6.0.2800.1143 *** Destination:D:\WINDOWS\System32\urlmon.dll Version: 6.0.0.0 *** Source:D:\WINDOWS\AppPatch\SETF93.tmp Version: *** Destination:D:\WINDOWS\AppPatch\sysmain.sdb Version: 0.0.2.0 *** Source:e:\68a8798849478b603d Version: *** Destination: Version: *** Source:e:\7c1782e8be67eda630db0baa44 Version: *** Destination: Version: *** Source:D:\WINDOWS\System32\_000005_.tmp Version: 5.1.2600.0 *** Destination: Version: *** IsRebootRequired: d:\windows\system32\wkssvc.dll was no-delay replaced; reboot is required. *** DoInstallation: IsRebootRequired returned TRUE. *** RebootNecessary = 1,WizardInput = 0 , DontReboot = 1, ForceRestart = 0 *** Could anyone translate this log for me in the simplest terms, lol? Need to know what I've done wrong.
  7. Hmmm, this section hasn't been touched in a good while.... I still want to know whether the whole order thing in my question above is important or not?
  8. Well I've just tried out nLite but, upon examining the created ISO in IsoBuster, it appears none of the content has been modified whatsoever. ZIPFLDR.DL_ still exists. No matter how many times I check the content I want gone and build the image, this does not change. And before you ask: a) Yes, I did copy the contents of the CD onto HD first. I also tested this ISO out on Virtual PC. All the content I asked be removed was still present and active. Does this app still need a lot of work?
  9. Amen! i know exacly what you mean! I have been irritated by the very same thing. also, this: Question: This is a new feature in windows xp where in the folder tree in windows explorer when you expand a folder you see subfolder AND compressed files, I don't want the compressed files to be shown, only folders like the eariler windows version. Solution: it is a feature of XP as well as Me, but it can be disabled. Go to Start, Run, and type the following: regsvr32 /u zipfldr.dll That stops working sometimes and i hafto it all again. AND the "view as list" remember settings for all folders sometimes doesn't work, it shows folder 1 as list, i enter folder 2 and then go back to folder 1 which has changed to view as large icons, it's like it forgetts settings sometimes. I also disable zipfldr.dll after a fresh installation, although if you try double-clicking on a zip file afterwards it magically re-enables the bloody DLL again without your consent. Therefore you should remember to install a third-party compression app after deregistering the dll to truly get rid of the association once and for all (in a way). I did try to alter the i386 setup to not install the DLL at all once but this only led to the Rollup being eternally listed on Windows Update, because unfortunately WU relies on reading actual individual system files to see if they exist before deciding upon the status of the Rollup, rather than, say, a simple log file to let it know what's there and everything. Meh. Microsoft sure love to shove unecessary things down your throat. Like DRM, for example.
  10. Ok, I found out it only seems to happen if I open a new window in the background when using MyIE2, particularly if I enable the "middle-mouse-button-to-open-new-window" feature. A bug in MyIE2 specifically perhaps? Perhaps I should use something else instead, lol?
  11. Is there a tweak to change the shortcut arrow from the big boxy default to the small, non-boxed grey/white alternative, like with TweakUI? The problem with doing it under TweakUI is that it seems to alter another registry setting in HKCU/Control Panel/Desktop/WindowMetrics, meaning when the icons are reloaded they are in their downgraded and rather grotty 8-bit form. Indeed, it seems this happens also when you simply rebuild the cache with TweakUI. Microangelo can rebuild the cache and keep the icons the same as before, btw.
  12. Just wanted to ask - is it safe to list Q831167 directly under Q832894 in svcpack.inf? Or should I allow a couple of other updates to go by first before letting the former install, to allow time for the latter's updating to have fully finished?
  13. Thanks for the registry trick, neo! I think I've actually seen this one before in the Registry Hacks thread or elsewhere, but I must have swiftly forgotten it eventually. I shall test it out with a fresh copy of Windows to see whether it really does solve the trick from the off.... While we're on the subject of pictures, has anyone ever had the problem where IE (or an IE-based browser such as MyIE2 or Avant) seems to always try to download PNG files rather than display them like pictures? I know this happens at least when opening them in new windows. If I cancel the download, then refresh the window, only then does IE execute the correct instruction (displaying it onto the window, that is). Is there a registry hack to sort this out perhaps?
  14. Before you ask, yes, I tried unregistering it with regsvr32. Although it seemed to work, it unfortunately seems to be linked to part of the Display properties, meaning the preview wallpaper function will not work properly unless the dll is properly registered again. But the problem I find with Windows Picture & Fax Viewer is that it seems so greedy and obsessed with being top dog for viewing jpgs, gifs, pngs and the like. Even if I, for example, associate ACDSee (or ACDSee Classic) with the aforementioned formats, double-clicking on a picture seems to bring up WPFV instead of the desired third-party app I so wanted to utilise. Rather scarily, I checked the internal file type settings, and it appears the options specific to WPFV do not appear in the list of commands accustomed to any of the picture formats, meaning you cannot disable them. It's as if they're hard-coded into the system and hidden away! So yeah, I want WPFV to take a hike and never darken my tower again, but at the same time I don't want my Preview Wallpaper/Desktop Theme function to go all tits-up because its ever-so-dependant bloody DLL isn't in service. Perhaps hex-editing needs to be the order of the day? Comments if you will, thank ye.
  15. Simply put, I wanted to know if there was any way of converting hex code settings in .reg files to a more understandable format, or at least "decode" (is that the right word?) them in some way or other? Cheery cheers.
  16. Ok, maybe "threatened" was sort of jumping the gun a bit. And it's true that the trick lives on in some of our systems, yay. Anyhoo, if anyone can help translate the registry settings into the CMD format (REG ADD etc., as demonstrated with RunOnceEx), as I'm having quite a handful of trouble translating it meself, could they PM me with details/listings/whatever? Cheers.
  17. Christ, so they were threatened then? Despite the positivity that is sleeker, nicer CPU movement by having only the light scanner on board your system? Perhaps if they completely fixed the resource problems with their software as a whole then tricks like this might not have to exist...
  18. Firstly, I couldn't find it in the News Archive. Looked really closely as well. Next my thread regarding the McAfee trick has also done a runner, possibly been deleted. Was the trick a real bummer flop if you had to get rid of it all?
  19. I think my NVIDIA GeForce 2 MX/MX 400 could be the culprit here. Have any NVIDIA users here managed to fix this annoying problem?
  20. Looks like the KB828026 hotfix got changed recently. But what exactly are the differences this time? And why does the download page name it as "KB828026" yet the file name features a "Q828026" bit? Does anyone remember the filename of the original 828026 hotfix?
  21. http://www.MSFN.org/comments.php?shownews=6989 Well this is just bloody wonderful is it? Sorry if I'm being too upset about this, but I do like to avoid more problems whenever I can. Has anyone here actually experienced web page problems from installing this hotfix?
  22. Okay then. Now, has anyone else noticed the IE Cumulative Update compromise "IEAccess=off" and create the shortcuts anyway? I'd like to know if this can be prevented in any way.
  23. WAIT!!!! It's starting to all piece together now.... I actually built my svcpack.inf out of the original unmodified one, which for reference is laid out like this: [Version] Signature="$Windows NT$" [SetupData] CatalogSubDir="i386\hotfixes" [ProductCatalogsToInstall] [SetupHotfixesToRun] As you can see, the [Version] info only contains the Signature by default! I did not realise before that the other three lines had to be manually added yourself afterwards. Perhaps this is something that should be stressed to all newcomers to prevent similar posts?
  24. Woah. How peculiar. I honestly can't remember how my [Version] section ended up being short and incomplete like that. What I do remember is that I copied the general text of it from here, and modified where necessary. I doubt that the highlighted page ever had a short [Version] part in the past, did it? Anyways, thanks for informing me about this very simple and silly little error. @killerbee: Thanks for trying to help, but I already tried the slipstreaming trick before and while it worked out okay, I'm now trying to install it like a normal hotfix as you can see above. Now that just leaves the shortcut/cumulative situation. Will I have to do it the dirty way and setup a batch to manually delete the extra shortcuts, or is there a cleaner way about it?
  25. Two things for you lot, and one of them be a mysterious problem! 1) I made a new CD and recently reinstalled XP again, only to discover that it installed approximately zero of the contents in the 'update' directory! So all the critical updates appear on WU, qfecheck reports 'no hotfixes found on system' and I still have DX8.1 and WMP8 active. This is despite the following svcpack.inf (cabbed on the CD): [Version] Signature="$Windows NT$" [SetupData] CatalogSubDir="i386\update" [ProductCatalogsToInstall] [SetupHotfixesToRun] DX9NTopk.exe WMP9.exe MDAC.exe js56nen.exe /Q:U /R:N MSJavWU.exe /Q:U /R:N Q330994.exe /Q:U /R:N KB823182.exe /O /U /N /Z KB824105.exe /O /U /N /Z KB824141.exe /O /U /N /Z Q824145.exe /Q:U /R:N KB825119.exe /O /U /N /Z KB826939.exe /O /U /N /Z KB828026.exe /O /U /N /Z KB828035.exe /O /U /N /Z KB832353.exe /O /U /N /Z Q832483.exe qchain.exe And my dosnet.inf definitely has this bit at the bottom: [OptionalSrcDirs] Update So I really don't get it. Thing to add is, I didn't watch GUI Setup all the way through, so something may have gone wrong there, but then I probably wouldn't be able to see what seeing as it all flys by too quickly anyway (and the setup wasn't halted by any error in particular). 2) I previously remember that installing the IE Cumulative Update would ensure that the IE shortcuts get created on the desktop, Start Menu and Quick Launch bar even if you set "IEAccess=off" in winnt.sif. Which kinda defeats the point really. Any of you lot know a way of getting round this? Funnily enough, installing the OE Cumulative Update doesn't circumvent the "OEAccess=off" tag, so the shortcuts remain uncreated.


×
×
  • Create New...