Jump to content

Grope For Luna

Member
  • Posts

    95
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Canada

About Grope For Luna

Profile Information

  • OS
    Windows 8.1 x64

Recent Profile Visitors

1,298 profile views

Grope For Luna's Achievements

0

Reputation

  1. I did a system restore and it works now. I think it had something to do with Acronis True Image that I installed and uninstalled.
  2. The Windows6.1-KB2487335-x64 "Important Update" gives me a Bad Pool Caller bluescreen when I try to integrate it into my WIM. It only applies to Windows Live Family so it's useless to me anyway (like a few other updates that deal with Indian rupee symbols, Canon printers, Russian/Chinese characters in Media center, etc.) Edit: Never mind... the bluescreen issue was apparently with the Online Armor beta I was using.
  3. Actually, if you look in winsxs it might already be there. It doesn't show in the Start Menu in my new install but the files are there... c:\Windows\winsxs\amd64_microsoft-windows-stickynotes-app_31bf3856ad364e35_6.1.7600.16385_none_493ba8a4d2fc9697\StikyNot.exe c:\Windows\winsxs\amd64_microsoft-windows-stickynotes.resources_31bf3856ad364e35_6.1.7600.16385_en-us_567f6e855a658d02\StikyNot.exe.mui You can copy them to a new folder and place the mui in an en-us subfolder.
  4. Open the install.wim and look for StikyNot.exe in system32. You will also need StikyNot.exe.mui from system32\en-us (or whatever language you are using). Other libraries might be needed so no guarantee it will work.
  5. VLite appears to be useless for the integrated SP1 isos. Some of the files in the oobe folder get replaced with HP printer xml files. This happens in at least 1 more folder in system32 so there may be more. They're still listed as dlls but the content is xml and installation fails when oobe starts.
  6. Most of the file links in the x64 list are for the x86 versions. A quick search & replace in notepad does the trick (x86->x64). The link for KB968537 was wrong entirely. windows_2008_server_sp2_x64_enu.ulz Excluding the IE updates which are outdated by now there are only 7 potentially useful updates so it's barely worth the effort.
  7. I hate to break it to you, but Quicktime Alternative is still Quicktime. It doesn't have the QuickTime Player (<1MB ?) or the language files but everything else is basically the same. What's the big fuss anyway? You don't have to use quicktime if you don't want.
  8. Edit: Oops... nevermind. The addon is here: http://www.codecpackguide.com/quicktimealt.htm and here ftp://ftp.ku.lt/pub/Windows/audio/K-Lite/...es_addon270.exe Is this addon still required for 2.80?
  9. You can deal with some of the dependencies by deleting some of the dependency sections of the manifest files. That should allow you to remove some of the unused folders, and maybe a few unneeded components. Right now I have a combined Nero Burning Rom / Recode installation that takes up ~90MB.
  10. I also don't have BluRay, so I can't test it. I'll check SMC folder. You did not answer me. Do you mean on NScCoreComponents folder? Cheers Yes, I meant the NScCoreComponents. I just deleted the files (except for the manifest) from my installation and it works fine. Which files could you not delete? Most everything in the SMC folder can be deleted. If you plan on making audio cds from mp4/m4a files, you will need to keep ndaudio.dll (and APM_NeroDigital.dll in AudioPlugins). Otherwise, you can delete that too. I just discovered that you also need NeESParser.ax (not included in your Lite distro) and NeAudio2.ax if you want to burn FLAC files to an audio CD. Unlike Nero v8, most of the dlls don't need to be registered. Only advrcntr4.dll appears to be necessary so you can save a lot of registry clutter by registering only the essentials. Even NeroAPI doesn't need registration, unless you want to use it for burning with third party apps like UltraISO.
×
×
  • Create New...