Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About oao

  1. I 've run into a weird problem. I've been running MS Office 2000 SR-1 Premium (Word only) on Windows XP64. I've recently installed Windows Live Writer which I use to publish my Blogger blog. Every time WLW loads IE8 to access the blog, Windows installer pops up and tries to install something from the Office disc. Suspecting that the Office was configured to install some function on request, I went through the Office components and uninstalled everything that was not necessary for my use of Word, but this failed at the end of the process with error 1919: Error 1919. Error configuring ODBC data source: MS Access Database, ODBC error 6: Component not found in the registry. Verify that the file MS Access Database exists and that you can access it. I then decided that when WLW popped the installer, to let it demand all the MDAC files that it needed, I collected them and made them available to it and it looked like it installed whatever it needed. Yet WLW continues to pop up the installer and to issue the 1919 error. I turned on verbose logging for the installer and it produced some logs, one of which I am attaching to this message. I have another log which is probably important, but it is long and the system does not let me attach it. Perhaps somebody can figure out what's going on here and can advise on a solution. Thanks. Office 2000 SR-1 Premium Setup(0002)_MsiExec.txt
  2. elite 64 not available?

    I was referring to the RAR files listed here: http://www.msfn.org/board/topic/137765-windows-7-rtm-3264-bit-updated/ Some of these files are necessary together with the vLite in order to customize Win7. Or are you saying that only vLite is now necessary, without those files?
  3. elite 64 not available?

    I tried to download the elite 64 rar from both sites. The mediafire says file is no longer available, and the other site is not available itself. What gives?
  4. OEM Windows 7

    It is my understanding that you need a retail Windows 7 install to apply vLite to. Is there some way that it can be done with Windows 7 that comes preinstalled on laptops? There is a way to create an install disc for OEM version: http://thecustomizewindows.com/2010/11/create-a-bootable-windows-7-dvd-for-oem-pcs-not-supplied-with-installation-disk Would that be usable? It's not very clear and I would prefer not to have to go through it, though.
  5. Integration of Intel's SATA AHCI and RAID drivers

    Fernando, Yes, everything is clear now, thanks. I had realized all that by the time you gave your clarification.
  6. I communicated with Stebner on this and he tells me that at the time when people were having problems trying to install the .Net via SVCPACK.INF during T-13 he found a workaround which he posted here: http://blogs.msdn.com/astebner/archive/200.../06/591694.aspx The x64 version of the modified SVCPACK.INF file would look like this: [CatalogHeader] [Version] Signature="$WINDOWS NT$" [setupData] CatalogSubDir="\amd64\SVCPACK" [setupHotfixesToRun] reg delete HKLM\Software\Microsoft\PCHealth\ErrorReporting\DW /f reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 0 /f Net20SP2.exe /Q /C:"install.exe /Q" reg add HKLM\SYSTEM\Setup /v SystemSetupInProgress /t REG_DWORD /d 1 /f KB958481.exe /Q /C:"install.exe /Q" KB974417.exe /Q /C:"install.exe /Q" KB968930.exe /Q /C:"install.exe /Q" [ProductCatalogsToInstall] which assumes the installers are in the AMD64 folder of the source. Note that I have included not just the SP2 install but also the 3 fixes. I am not sure whether they will work the same, so maybe somebody knows.
  7. well, that's what I was referring to initially: confusion about the term add-ons and where should they be added in nLite. I am interested only in x64 addons that can be added at Hotfix and don't require any switches/commands. those that require the latter and which are added at RunOnce don't matter much -- I prefer to install them myself manually after windows. the only issues I came to were (1) the .NET, 2SP2 now, 3 and 3.5 later, if I ever need them; and (2) one posted online, TweakUI, which Kurt attached to his guide. what I need to know is can either be added at Hotfix? if not, can the method posted by Aaron Stebner that I posted in the other thread be modified to create a Hotfix addon for (1)? Here's what Stebner replied when I asked him: > I'm not familiar with nLite, so I'm not sure how well I'll be able to answer this question. Does nLite prevent you from being able to pass command line parameters to the installer when you run it? If so, can you write a wrapper script that would not require command line parameters but that can launch the .NET Framework setup with the required command line parameters?< That's essentially what I was asking as I am not technical enough to know the answer.
  8. kurt, the tweakui x64 addon you list in the guide -- does it require the bat file to be integrated, or can it be integrated as a hotfix by nLite? I see that inside the archive is an exe file and no entries file -- hence my question. Thanks.
  9. Add-ons, RunOnce and Installers

    Thanks. The 2 of the sites that do have a ,NET addon include 2, 3 and 3.5. I am interested only in 2 SP2 and its hotfixes. I will install the later versions only as needed. One of theaddons was inspired by these instructions: ====================================================== To create an administrative install point for the .NET Framework 2.0 SP2 x64: 1. Download the package named netfx20sp2_x64.exe from http://www.microsoft.com/downloads/details...1d-10e506da9d0f and save it to your local hard drive 2. Extract the contents of the setup package by running this command: netfx20sp2_x64.exe /x:c:\netfx20sp2\x64 3. Stage the base MSI by running this command: msiexec /a "c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\netfx20a_x64.msi" TARGETDIR="c:\netfx20sp2\x64\AIP" 4. Apply the patches to the staged base MSI by running this command: msiexec /a "c:\netfx20sp2\x64\AIP\netfx20a_x64.msi" PATCH="c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\ASPNET_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\CLR_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\CRT_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\DW_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\NetFX_Core_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\NetFX_Other_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\WinForms_64.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\ASPNET.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\CLR.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\CRT.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\NetFX_CA.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\NetFX_Core.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\NetFX_Other.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\PreXP.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\WinForms.msp;c:\netfx20sp2\x64\wcu\dotnetframework\dotnetfx20\DW.msp" With these steps, you will have an administrative install point for the .NET Framework 2.0 SP2 x64 located at c:\netfx20sp2\x64\AIP. You can then install the MSI directly using a command line like the following: msiexec.exe /i c:\netfx20sp2\x64\AIP\netfx20a_x64.msi /l*v %temp%\netfx20sp2x64log.txt /qb VSEXTUI=1 You can adjust the parameters as needed if you want a fully silent install instead of basic UI, or want to use any other standard Windows Installer command line parameters. ========================================== What modifications if any can be made to make it a Hotfix addon? Thanks.
  10. Add-ons, RunOnce and Installers

    Thanks. Do I understand you correctly that the silent .NET maker synthesized creates addons which can be added during Hotfix? I would like to make sure before I try to read about it, which is quite long and involved. The RunOnce option does not seem more useful to me than just running the .NET installer after Windows install. Nothing that I found online indicates that .NET addons for Hotfix integration are possible -- only explanations of why they are not possible and workaround e.g. via RunOnce. There is one exception -- a .NET 2SP2 addon in .7z format -- without any explanation as to how it was created. Alas, it is x86 and I need a x64. It seems to me that with so many asking for it, if it were possible and easy there would have been such addons available online. But there aren't.
  11. Add-ons, RunOnce and Installers

    It does -- the ENTRIES.INI was what I was missing. I've been reading info on unattended but it's been discouraging -- it just takes more than I am willing to invest.
  12. Add-ons, RunOnce and Installers

    I already got you on that. I was just trying to explain why I posted the questions and what was unclear to me.
  13. Add-ons, RunOnce and Installers

    Well, I think my point was that I am not inclined to try to figure out the details. Consequently, I need to be told what update is an addon which can be added in Hotfix and which must be added in RunOnce with a command. And sometimes this information is provided and clear, sometimes is not. It may be also scattered in many place and sometimes varies. Now, if "you know what you are doing" then my questions woud have not been posted. I was asking as somebody who does not and, nor am I interested in figure out the details. I tried and it was too much for the time and effort I wanna put into it. So, not knowing those details and having been warned not to apply updates to a modified CD, I stick by this and use only nLite on a fresh CD. I cannot be aware of T-13, because I don't really know what that is and how to know when it's relevant or not, that's the whole point. I already said I am not interested in making addons and that I must use what I can find. And what I could find was instructions by another to add the .NET updates in RunOnce with commands, the synthesized maker is not an option. What I could not tell was whether TweakUI and Silverlight addons were good for Hotfix or needed the RunOnce. I think the issue here is that we vary in terms of how much we want to invest in understanding the process of slipstreaming and, therefore, how much we want to learn about it. Some of us want to just do the maximum we can without becoming fully knowledgeable about the details. And we dk what the maximum is without asking all sorts of questions which for knowledgeable users may be trivial. In this particular case I went thru the docs on addons and addon makers and I decided it's something I am not interested in. So I tried to figure out the maximum I could do by posting the questions. I hope this makes sense.
  14. Integration of Intel's SATA AHCI and RAID drivers

    I think the confusion here was that I thought that the UltraATA showed by Device Manager represents the IASTOR. But as I understand from you now, it reflects PCIIDE. So while I expected both drivers to be updated, only the SATA was, which is apparently correct. But where does the PCIIDE and its updates come from -- are they usually issued separately/
  15. Integration of Intel's SATA AHCI and RAID drivers

    This is your "last post" that you refer me to to respond. I don't see any questions here, so I am not sure what you want me to say. What I did was Device Manager|Properties|Update Driver, point to the 64 folder extracted from the executable file downloaded, and select the IAHCI.INF file, I had to force it to install. I am running XP64. At the time I was under the impression that both drivers listed by Device Manager -- SATA and UtraATA would be updated to the new version. When I looked at both drivers listed, the UltraATA was not updated, only the SATA, so I thought there was something wrong and posted the question. But then I used the executable installer directly and it did the same thing, so I figured it was OK. You also seemed to be saying that only the SATA was updated. Is this what you wanted?