Low RAM Option 1 : Use UltraISO to reduce the size of the ISO by deleting all folders from the ISO except \i386 folder, also delete all files >1MB in the i386\LANG folder. Then use the default Firadisk option and load ISO into RAM (use default options).Low RAM Option 2: Use DPMS option 3 (WinvBlock) for STEP 1, and use Step 2 (
There have been some issues with running SFC.EXE /SCANNOW that this article doesn't address. They are:1) The system won't accept the original installation disk because it doesn't have Service Pack 2 on it.2) You don't have a Windows installation CD - only a restore CD from the manufacturer.Here's how to deal with them:__________________________________________________________________________To fix the SP2 issue, you'll have to "slipstream" SP2 along with your installation CD. Rather than going through all the gory details here, just visit this link: _slipstream.asp It provides a detailed explanation of how to slipstream SP2 along with your Windows installation CD.__________________________________________________________________________To fix the problem when you only have a restore CD you'll have to search for a folder on your hard drive (or on the restore CD) that's named "i386" (without the quotes). Once you find that, copy it to your hard drive at the root (C:\i386). Make sure that the directory is located at the root of your C: drive (C:\i386) - if not, then you'll need to change the path to the proper entry in the registry edit.Then perform this registry edit to point SFC.EXE at it:So, the first step is to backup your registry. The easy way to do this is to set a System Restore point ( )Next, go to Start...Run...and type in "regedit.exe" (without the quotes) and press enter. You'll see a folder-like view on the left, and entries on the right.Navigate down the folder view on the left to: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup Just click on the + sign to expand the view of the next level - so, to start, you'll click on the + next to HKEY_LOCAL_MACHINE and look for the SOFTWARE entry.Then you'll click on the + next to SOFTWARE and look for Microsoft, and so on until you get to the Setup key. Then just click once on the Setup key. Look in the right hand pane and double click on the entry that says "SourcePath".In the box that pops up, type in "C:\" (without the quotes) and press Enter. Then close regedit and reboot your computer. SFC.EXE /SCANNOW should now run without problems for you.___________________________________________________________________________If you're unable to find the i386 folder, it may be that it's on a hidden partition on your hard drive or that the restore CD has been created in a different way and you can't view the directories.If so, there's a couple of more things to try (please post your question in the forums) or you can look to see if your system has a repair or a non-destructive recovery option. This option will leave your programs and data intact while replacing all of the Windows files. This is also the next step if SFC.EXE /SCANNOW doesn't fix the problem.
windows xp sp3 i386 lang folder 54
Hello, all If you run Windows XP SFC and it asks for your "Service Pack 3 Disk", you can extract the service pack 3 files as follows:Download the standalone windows XP SP3 package from here: ;displaylang=enand save it to your desktop.Then extract the files from the package by going to Start -> Run and entering:"%userprofile%\Desktop\WindowsXP-KB936929-SP3-x86-ENU.exe" -x:C:\xpsp3This will place the service pack 3 updates to the i386 folder into your C drive under the folder "xpsp3".You should then be able to point SFC at this folder for the files it can't find from your windows disk or i386 folder.Hope that helps,Billy3
mahamori 19191a764c -xp-sp3-i386-lang-folder-18[ -xp-sp3-i386-lang-folder-18 ][ -xp-sp3-i386-lang-folder-18 ][ -xp-sp3-i386-lang-folder-18 ]link= -xp-sp3-i386-lang-folder-18link= -xp-sp3-i386-lang-folder-18link= -xp-sp3-i386-lang-folder-18
If you have the i386 directory then you should check out a program called nLite. You put the i386 path in nLite, make any tweaks you desire within the program, then it can create a burnable cd image for you. Using this method you can make a new XP cd. I do recommend, however, to make a copy of the i386 folder and use that as the path since nLite makes the modifications directly to the folder you provide. So if any mistakes are made you will still have a clean i386 directory to work with.
When I tried selecting my folder in nLite, it gave me an error "Make sure that the selected folder or drive contains the 'i386' or 'AMD64' directory and proper Windows installation files." I had the exact same files in the directory as listed in the guide so I am rather confused. Thanks for any help.
Eric wrote: [When I tried selecting my folder in nLite, it gave me an error "Make sure that the selected folder or drive contains the 'i386' or 'AMD64' directory and proper Windows installation files." I had the exact same files in the directory as listed in the guide so I am rather confused. Thanks for any help.]
my question is how can i install/integrate this files to make my pc updated even without using windows update..& can you teach me hoe can i make a boot cd after the process of integration.. ..as of now i recieved error "Make sure that the selected folder or drive contains the 'i386' or 'AMD64' directory and proper Windows installation files" . can you give me a step by step guide. sorry for my question..
11-04 07:12 INFO root: === wubi 9.10ubuntu1 rev160 ===11-04 07:12 DEBUG root: Logfile is c:\docume1\shree\locals1\temp\wubi-9.10ubuntu1-rev160.log11-04 07:12 DEBUG root: sys.argv = ['main.pyo', '--exefile="H:\\wubi.exe"', '--cdmenu']11-04 07:12 DEBUG CommonBackend: data_dir=C:\DOCUME1\shree\LOCALS1\Temp\pyl118.tmp\data11-04 07:12 DEBUG WindowsBackend: 7z=C:\DOCUME1\shree\LOCALS1\Temp\pyl118.tmp\bin\7z.exe11-04 07:12 DEBUG CommonBackend: Fetching basic info...11-04 07:12 DEBUG CommonBackend: original_exe=H:\wubi.exe11-04 07:12 DEBUG CommonBackend: platform=win3211-04 07:12 DEBUG CommonBackend: osname=nt11-04 07:12 DEBUG CommonBackend: language=en_US11-04 07:12 DEBUG CommonBackend: encoding=cp125211-04 07:12 DEBUG WindowsBackend: arch=amd6411-04 07:12 DEBUG CommonBackend: Parsing isolist=C:\DOCUME1\shree\LOCALS1\Temp\pyl118.tmp\data\isolist.ini11-04 07:12 DEBUG CommonBackend: Adding distro Xubuntu-i38611-04 07:12 DEBUG CommonBackend: Adding distro Xubuntu-amd6411-04 07:12 DEBUG CommonBackend: Adding distro Kubuntu-amd6411-04 07:12 DEBUG CommonBackend: Adding distro Mythbuntu-i38611-04 07:12 DEBUG CommonBackend: Adding distro Ubuntu-amd6411-04 07:12 DEBUG CommonBackend: Adding distro Ubuntu-i38611-04 07:12 DEBUG CommonBackend: Adding distro Mythbuntu-amd6411-04 07:12 DEBUG CommonBackend: Adding distro Kubuntu-i38611-04 07:12 DEBUG CommonBackend: Adding distro KubuntuNetbook-i38611-04 07:12 DEBUG CommonBackend: Adding distro UbuntuNetbookRemix-i38611-04 07:12 DEBUG WindowsBackend: Fetching host info...11-04 07:12 DEBUG WindowsBackend: registry_key=Software\Microsoft\Windows\CurrentVersion\Uninstall\Wubi11-04 07:12 DEBUG WindowsBackend: windows version=xp11-04 07:12 DEBUG WindowsBackend: windows_version2=Microsoft Windows XP11-04 07:12 DEBUG WindowsBackend: windows_sp=Service Pack 311-04 07:12 DEBUG WindowsBackend: windows_build=260011-04 07:12 DEBUG WindowsBackend: gmt=511-04 07:12 DEBUG WindowsBackend: country=US11-04 07:12 DEBUG WindowsBackend: timezone=America/New_York11-04 07:12 DEBUG WindowsBackend: windows_username=shree11-04 07:12 DEBUG WindowsBackend: user_full_name=shree11-04 07:12 DEBUG WindowsBackend: user_directory=C:\Documents and Settings\shree11-04 07:12 DEBUG WindowsBackend: windows_language_code=103311-04 07:12 DEBUG WindowsBackend: windows_language=English11-04 07:12 DEBUG WindowsBackend: processor_name=Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz11-04 07:12 DEBUG WindowsBackend: bootloader=xp11-04 07:12 DEBUG WindowsBackend: system_drive=Drive(C: hd 12176.7734375 mb free ntfs)11-04 07:12 DEBUG WindowsBackend: drive=Drive(C: hd 12176.7734375 mb free ntfs)11-04 07:12 DEBUG WindowsBackend: drive=Drive(D: cd 0.0 mb free cdfs)11-04 07:12 DEBUG WindowsBackend: drive=Drive(E: hd 18042.3164063 mb free ntfs)11-04 07:12 DEBUG WindowsBackend: drive=Drive(F: hd 30439.8554688 mb free ntfs)11-04 07:12 DEBUG WindowsBackend: drive=Drive(G: hd 997.30078125 mb free ntfs)11-04 07:12 DEBUG WindowsBackend: drive=Drive(H: cd 0.0 mb free cdfs)11-04 ...
> Date: Thu, 10 Dec 2009 23:44:39 +0000> From: > To: > Subject: [Bug 383752] Re: "Cannot download the metalink and therefore the ISO">> I'm receiving this error as well.>> I downloaded the latest 9.10 netbook remix, today, and am trying to> install via USB to an ASUS EEE pc running windows XP SP3.>> --> "Cannot download the metalink and therefore the ISO"> > You received this bug notification because you are a direct subscriber> of the bug.>> Status in Wubi, Windows Ubuntu Installer: Fix Committed>> Bug description:> I downloaded ISO image of Kubuntu 9.04 (and Ubuntu 9.04) and burned CD... When i try to install Kubuntu or Ubuntu from CD i get an error "Cannot download the metalink and therefore the ISO". Wubi creates folder "ubuntu", size 697 Mb.. I don't know what to do..>> To unsubscribe from this bug, go to:> +bug/383752/+subscribe
2ff7e9595c
Comments