Lwde, The i386 folder contains the Windows XP system files. It is present on your Windows XP CD-ROM. Portions of it are installed on your system when you do a clean install. On my system I have a 73.1MB folder in C: WINDOWS Driver Cache and two 2.3+ MB folders in C: Windows System32 Reinstall Backups 0000 (and 0001) DriverFiles and a 72.6MB folder in C: Windows System32 Reinstall Backups 0002 DriverFiles. The Windows XP put them there either during installation or during operation. There is no need to back them up on your current system before the clean install. Sorry, your browser doesn't support Java.
Driver Cache I386 Windows Xp 10
Are you a new computer owner, or simply new to Delltalk? You may find some helpful information on how best to use this forum. Want to make a hyperlink in your post, want to add a graphic or sound file, need to troubleshoot a non-working Java applet, want to build an attractive signature? These capabilities can be yours if you visit. For help in deciding what can be eliminated from your Startup list, take a look. Want to get rid of Network Neighborhood, change your Registered Owner name? Check out the little utilities at.
Ready to sign up for Web server space? Want to learn FTP? For new users (or veterans who would like to help a new user), a number of basic Windows tasks are illustrated in. Note: I do not answer Instant Messages but I do answer email.
Archived from groups: microsoft.public.windowsxp.printfax Our printer driver installation utility seemed to work till the 64-bit XP Beta version. Our setup wizard has always worked thinking that the OS known driver files would be lying in IA64 path. Now, In the final version of 64-bit XP service pack 1, It seems that the driver.cab file is lying in I386 directory. I have few questions related to it and hope someone will help me out here. Is the driver.cab file destination would be based on whether the system is a x86 based system or amd64 based one? Has the destination files of drivers also changed in the release? I tried changing the source path to where my driver.cab is residing currently on my machine, Now its looking for sp2.cb.
My system doesn't have a sp2.cab but it has a sp1.cab (its service pack 1). Can someone explain what could be the reason here. Thanks a lot, Ashish. Archived from groups: microsoft.public.windowsxp.printfax The driver cab in i386 are for 32bit drivers.
These are not printer drivers. Uncab the file if you want to see what types of drivers are included in this file. The spooler will only load 64bit drivers. Question 1 Not sure what you are asking.
Windows driver cache amd64 is the path to the x64 driver.cab file Q3 do not use ntprint.inf from XP. X64 requires decorated infs. Check - Alan Morris Windows Printing Team Search the Microsoft Knowledge Base here: wrote in message [email protected]. Our printer driver installation utility seemed to work till the 64-bit XP Beta version. Our setup wizard has always worked thinking that the OS known driver files would be lying in IA64 path. Now, In the final version of 64-bit XP service pack 1, It seems that the driver.cab file is lying in I386 directory. I have few questions related to it and hope someone will help me out here.
Is the driver.cab file destination would be based on whether the system is a x86 based system or amd64 based one? Has the destination files of drivers also changed in the release? I tried changing the source path to where my driver.cab is residing currently on my machine, Now its looking for sp2.cb. My system doesn't have a sp2.cab but it has a sp1.cab (its service pack 1). Can someone explain what could be the reason here. Thanks a lotAshish.
Archived from groups: microsoft.public.windowsxp.printfax I cannot comment on much you ask except to say that: the driver 32.cab and driver.cab files are in C:: windows Driver Cache i386 and C: Windows Driver Cache amd64 respectively; there is no sp2.cab file for Windows 64 bit (It is released with what are regarded as equivalent to Windows XP 32 bit SP2-level files as part of the initial release.); Other drivers might be present in system, system64, or systemWOW32 directories. Windows XP 64 bit and Server 2003 64 bit will not use 32-bit printer drivers. Note: These comments represent the best of my present understanding. That understanding might be incomplete or erroneous. Tom MSMVP Windows Shell/User wrote in message [email protected].: Our printer driver installation utility seemed to work till the 64-bit: XP Beta version. Our setup wizard has always worked thinking that the: OS known driver files would be lying in IA64 path. Now, In: the final version of 64-bit XP service pack 1, It seems that the: driver.cab file is lying in I386 directory.
I have few questions: related to it and hope someone will help me out here.: 1. Is the driver.cab file destination would be based on whether the: system is a x86 based system or amd64 based one?: 2. Has the destination files of drivers also changed in the release?: 3. I tried changing the source path to where my driver.cab is residing: currently on my machine, Now its looking for sp2.cb. My system doesn't: have a sp2.cab but it has a sp1.cab (its service pack 1). Can someone: explain what could be the reason here.:: Thanks a lot,: Ashish.
Archived from groups: microsoft.public.windowsxp.printfax Tom, thanks for your help. But just found out that and it seems files lying in I386 directory won't be accepted by the Addprinter. It returns me 'NOT A VALID IMAGE' kind of error. I guess, the Add printer wizard would only use C: Windows Driver Cache amd64 driver.cab for its installation purpose. If you can point me out to any MSKB, it will be of greta help. I tried googling but couldn't find something which can help me Thanks a lot, Ashish.
Archived from groups: microsoft.public.windowsxp.printfax I can possibly account for two of the three locations: one is the copy-in-use. Another is a backup. The system keeps copies of all essential files so it can replace any that are overwritten by an errant install. Contents will differ.
There might be a MSKB article or other public resource on it but I don not have the reference at hand. Tom MSMVP Windows Shell/User wrote in message [email protected].: Tom,: Thanks a lot for your reply?: One more basic question.: I have driver.cab and NTPRINT.INF files on 3 places in my system, why: they should be at so many places?: Are the contents of driver.cab in c: I386 and C: Windows Driver: Cache amd64 same?:: I am running Windows XP 64-bit SP1 on xeon.:: Thanks,: Ashish. Archived from groups: microsoft.public.windowsxp.printfax the spooler recognizes x64 print drivers as 'Windows x64', x86 drivers are 'Windows NT x86' Use your own inf file but add the proper decorations. If you need all the devices listed in ntprint.inf you will need to use correct OS version of the inf. Just grab ntprint.inf from a x64 system and compare it to ntprintinf from an x86 system.
Alan Morris Windows Printing Team Search the Microsoft Knowledge Base here: wrote in message [email protected]. HI AlanThanks for your help.
Question 1 - i read somewhere as the machines and drivers have been identified as x86 and amd64 ones. So when looking for cab files, do i ever need to worry about this, in my code for these parameters.
If i dont use ntprint.inf, what should i use. I have an UI which repeats the steps done by AddPrinter Wizard. ThanksAshish.
Gm.dls cache file ‹ ‹ Author Message Husky Posted: Tue Nov 09 05:24:15 CST 2004 Windows XP Setup gm.dls cache file I'm trying to get around Windows File Protection (which I only learned about in an earlier post here). I want to replace the gm.dls sound file supplied by Microsoft with one of my own.
I had done this, and used it successfully for a while, but suddenly WFP stops me from making any changes and has reverted to the original file. One way suggested was to change the cached version of this file, which is not protected.
But I can't find it. It's not in any of the.cab files in windows driver cache I386 (where one source suggests) and I can't find a folder called dllcache (which another source suggested). Does anyone know where to find it? Will Posted: Tue Nov 09 05:24:15 CST 2004 Windows XP Setup gm.dls cache file Hi You may find you'll have problems if you replace, amend etc. An MS file that is protected by WFP. Will Denny MS-MVP - Windows Shell/User Please reply to the News Groups I'm trying to get around Windows File Protection (which I only learned about in an earlier post here). I want to replace the gm.dls sound file supplied by Microsoft with one of my own.
I had done this, and used it successfully for a while, but suddenly WFP stops me from making any changes and has reverted to the original file. One way suggested was to change the cached version of this file, which is not protected.
But I can't find it. It's not in any of the.cab files in windows driver cache I386 (where one source suggests) and I can't find a folder called dllcache (which another source suggested). Does anyone know where to find it? Vanguard Posted: Tue Nov 09 08:17:51 CST 2004 Windows XP Setup gm.dls cache file I'm trying to get around Windows File Protection (which I only learned about in an earlier post here). I want to replace the gm.dls sound file supplied by Microsoft with one of my own. I had done this, and used it successfully for a while, but suddenly WFP stops me from making any changes and has reverted to the original file. One way suggested was to change the cached version of this file, which is not protected.
But I can't find it. It's not in any of the.cab files in windows driver cache I386 (where one source suggests) and I can't find a folder called dllcache (which another source suggested). Does anyone know where to find it? What happens if you use Start - Run to enter 'C: Windows System32 dllcache'?
Does Explorer then open to show that.hidden. folder? You won't see hidden or system folders in Explorer unless you configure its options to do so. Post replies to newsgroup - Share with others.
![]()
Email: lh811newsATyahooDOTcom and append '=NEWS=' to Subject. Wesley Posted: Tue Nov 09 11:28:20 CST 2004 Windows XP Setup gm.dls cache file gm.dls is in both of these folders C: WINDOWS system32 dllcache and C: WINDOWS system32 drivers C: WINDOWS system32 dllcache is a Hidden folder. Gm.dls DLS Designer Default GM Sound Set - Hope this helps. Wes I'm trying to get around Windows File Protection (which I only learned about in an earlier post here). I want to replace the gm.dls sound file supplied by Microsoft with one of my own. I had done this, and used it successfully for a while, but suddenly WFP stops me from making any changes and has reverted to the original file. One way suggested was to change the cached version of this filewhich is not protected.
But I can't find it. It's not in any of the.cab files in windows driver cache I386 (where one source suggests) and I can't find a folder called dllcache (which another source suggested). Does anyone know where to find it? Sebastian Posted: Tue Nov 09 17:03:02 CST 2004 Windows XP Setup gm.dls cache file I'm not quite there yet but I'll get there eventually. Thanks for all the help/suggestions/links. Sebastian Posted: Thu Nov 11 05:29:01 CST 2004 Windows XP Setup gm.dls cache file Actually I'm less close than I thought.
I've started a new thread about this, but in case that gets lost or overlooked, what I said was: I'm trying to replace the Microsoft default sound file c: windows system32 drivers gm.dls with another file. I ussed to be able to do this, but since SP2 it is automatically replaced by a copy, apparently from C: windows system32 dllcache. I was suggested I could delete that copy of the file, but I can't - it too gets replaced almost immediatley - from where???? Also, it was suggested I use the program 'Replacer.com' but it says gm.dls is 'not in the database' Any other suggestions gratefully received. Sky Posted: Thu Nov 11 08:08:26 CST 2004 Windows XP Setup gm.dls cache file Actually I'm less close than I thought.
I've started a new thread about this, but in case that gets lost or overlooked. Best idea is to maintain a thread until the problem is resolved.
Creating a new thread daily won't make fixing the problem easier. I'm trying to replace the Microsoft default sound file c: windows system32 drivers gm.dls with another file. I ussed to be able to do this, but since SP2 it is automatically replaced by a copyapparently from C: windows system32 dllcache. The resolution remains the same as it was in your first thread on the 8th. Rename the file you wish to replace in the dllcache folder, the i386 folder if it is there, in the lastknowngood folder if it exists, and in the system32 drivers folder. Then copy the new one to the drivers folder.
You will have to do this each time you wish to replace that file.Sky Sebastian Posted: Thu Nov 11 14:03:02 CST 2004 Windows XP Setup gm.dls cache file Best idea is to maintain a thread until the problem is resolved. Creating a new thread daily won't make fixing the problem easier. Quite right - but I'm new to all this and couldn't, at that moment, find my earlier post.
We learn from our mistakes, and I'm learning a lot. Rename the file you wish to replace in the dllcache folder I've done that - it just gets replaced. the i386 folder if it is there That's where it used to live before SP2. It's not there now, nor is it in the.cab files now in that directory.
Dec 23, 2017 - AAA Driver Training AAA.com. • Final Exam Booklet #3138 • Exam Answer Sheet #3145. The AAA Driver Improvement Program™ includes two. Jan 27, 2018 - Driver Improvement Courses for Seniors. AAA's safety experts provide reliable and accessible answers to your questions about aging. Dec 25, 2017 - Ohio driver's license test/exam. Aaa Driver Improvement Final Exam Answers. High schools have offered AP classes that can be eligible for. Aaa driver improvement final examination.
in the lastknowngood folder if it exists I've never heard of this. I'll see if I can find it.
Thanks Sebastian Posted: Fri Nov 12 04:09:01 CST 2004 Windows XP Setup gm.dls cache file.in the lastknowngood folder if it exists and I said: I've never heard of this. I'll see if I can find it. Thanks But I can't find it. Where should I look? Sky Posted: Fri Nov 12 07:08:59 CST 2004 Windows XP Setup gm.dls cache file.in the lastknowngood folder if it exists and I said: I've never heard of this. I'll see if I can find it.
Thanks But I can't find it. Where should I look?
As I said 'if it exists'. It may not exist on your system. That folder only gets created if multiple backups are needed for protecting system-level files, for example during the installation of several updates. When you Restart the system those files are synched with the dllcache folder and then the 'lastknowngood' folder is removed.Sky Sebastian Posted: Sat Nov 13 13:28:02 CST 2004 Windows XP Setup gm.dls cache file I'm still in the dark about a lot of this but I've learned a lot. One way or another I've managed to get my file back where I wanted it. Thanks for all the information and tips. Sebastian Posted: Sun May 14 08:41:01 CDT 2006 Windows XP Setup gm.dls cache file I'm still in the dark about a lot of this but I've learned a lot.
One way or another I've managed to get my file back where I wanted it. Thanks for all the information and tips. I did recently find the real answer and I'm putting it here in case anyone with the same problem ever reads this:- I simply had to change the pointer in the Registry which points to GM.DLS and change it to point to the file I wanted. HKEYLOCALMACHINE Software Microsoft DirectMusic GMFilePath=SystemRoot% SYSTEM32 drivers GM.DLS Simple when you know how.
I am running Win XP Pro SP3. Last installed with slipstreamed SP2.
Trying to install a Logitech MK320 wireless keyboard and mouse. They use a USB HID Receiver. Inserting the receiver causes Windows Found New Hardware which errors installing the drivers with the message 'the data is invalild'. Followed instructions to make setupapi.log verbose. I find the first error message to be @ 22:10:56.015 #V180 Verifying file 'C: WINDOWS system32 DRIVERS hidusb.sys' (key 'hidusb.sys') against catalog ' failed. Error 2: The system cannot find the file specified. Verified that this file is in Driver Cache i386 Driver.cab.
What do I need to do to get windows XP SP3 to extract the file and put it in System32 Drivers folder? Or may I manually extract and just put it there? Note I am upgrading from a PS2 Keyboard and Mouse and have never used a USB Keyboard nor mouse. Plugging in a USB Mouse gives me the same error message. I have tried to update all of my USB drivers.
Windows Device Manager states that they are the newest available though online the correct versions are later. These versions match the versions in the Drivers.cab file. I found one place to download a newer set but it won't run under SP3. My usb drivers are more up to date than I thought.
They are all from sp2. Now I need to figure out how to start hid stuff. There is no current hid keyboard or mouse. A system at work, winxp sp3, with a usb keyboard, and a usb mouse, installed the hid receiver and the wireless keyboard and mouse work fine. My system at home with a ps2 keyboard and a ps2 mouse will not correctly install a usb keyboard, a usb mouse, nor the usb receiver for a wireless keyboard and mouse. All three devices end with the same error message. Data Invalid.
An Operating System should not interrupt the user; nor require updates, antivirus, or firewalls. Please answer all of the following diagnostic questions by number in your very next reply (no need to quote this post): 1a. Are you still getting the 'hidusb.sys is not found' errors? Are you still getting ' errors?
When did you last install slipstreamed WinXP SP2? When (approx.
Date) did you last install SP3 and did you install it manually or via Windows Update? What is the full name of your installed anti-virus application or security suite and is your subscription current? What anti-spyware applications (other than Defender)? What third-party firewall (if any)? Has a(nother) Norton application or a McAfee application EVER been installed on this computer since the last install of slipstreamed WinXP SP2? Assuming you used the OEM disc that came with the computer-in-question to create the WinXP SP2 slipstream, did a Norton free-trial or a McAfee free-trial pick one come preinstalled on the computer when you bought it? (Doesn't matter if you never used or Activated it.) 7.
Open Add/Remove Programs & make sure the Show Updates box at the top is checked. Now scroll down & tell me if ALL of the following updates are listed?. KB2559049, KB2567680; KB2555917; KB2544521, KB2544893, KB2476490; KB2393802 & KB971029 Most will be displayed as 'Security Update for Windows XP' followed by the KB number in parentheses.
If IE8 is installed, two will be displayed as 'Security Update for Windows Internet Explorer 8' followed by the KB number in parentheses. Robear Dyer (PA Bear) Microsoft MVP (Windows Client) since October 2002. An error 2 is DOS speak for file not found. A 'hid' means Human Interface Device (like a mouse). I don't know what all those other messages mean, but if you are missing hidusb.sys, you can download one. The hidusb.sys file should be in the following folders (assuming XP in installed on your C drive): c: windows system32 drivers c: windows system32 dllcache (that is where XP keep backup copies of important files) I uploaded a copy of the XP Pro SP3 file you need to my SkyDrive (everybody has a SkyDrive for sharing files). You can download it and when you do, put a copy of the file in these two folders (assuming Windows is installed on your C drive): c: windows system32 drivers c: windows system32 dllcache (that is where XP keeps backup copies of important files).
Here is the link to my SkyDrive and you can look for the file you need there: When you see the files available for download, you may not see the file extension (.exe,.dll,.cpl,.sys, etc.), but when you download them they will have the correct extension. You need to put the downloaded files in the correct folders on your system. That may not solve all your issues, but you will at least be past that part and then we can fix the rest. Yes I'm still geting hidusb.sys not found.
Did a clean install with Win XP and slipstreamed SP2 about 4 years ago when I updated the hard drives to raid 0. I've recently updated the bios for the ASUS A7n8X deluxe motherboard. Their site states that earlier versions 'fixed' a large file transfer problem for WinXP with Raid0. Another updated 'fixed' driver install errors for usb keyboards and mice. I still have a problem after this update. SP3 download now runs. I get the same errors trying to install the usb wireless keyboard and mouse, or a usb keyboard.
SP3 was an automatic update. Don't know when and do not remember if this was a one time update or many small ones.
In Ad/Remove it shows SP3 Version 20025. I'm curently using Microsoft Security Essentials with Microsoft Firewall.
I have a purchased copy of Win XP when I built my system to which I slipstreames SP2 when I updated the hard drives. I never used Norton or MacAfee after the update. Just AVG and Avast.
Now Microsoft. All updates you mentioned were installed. KB2559049 on 8/11/2011 KB2544521 on 8/11/2011 KB2393802 on 2/22/2011 KB971029 on 3/20/2011 KB2544893 on 8/11/2011 KB2555917 on 8/11/2011 KB2567680 on 8/11/2011 KB2476490 on 8/11/201 I use IE7. Mostly I use firefox and never use IE unless I'm on MS site.
An Operating System should not interrupt the user; nor require updates, antivirus, or firewalls.
![]()
If it exists C: I386 (the folder 'I386' at the root of your 'C:' drive) most likely contains an image of the installation copy of Windows. It's often placed on your hard drive as a way to avoid having to ask for a CD when Windows decides it needs some file that hasn't yet been installed.
It's also used as one of the repositories for the original files used by System File Protection and the System File Checker. If Windows determines that one of its files has been replaced with an unrecognized copy, perhaps due to a virus, then the System File Checker will restore the file to its original version from C: I386. (It actually uses additional repositories as well, in case service packs and other updates have legitimately updated the file.) In an attempt to answer the question 'I wonder what happens if.'
, I carefully backed up the contents of my C: I386 folder, and then deleted it. The next morning I woke up to this error message.
You can move your I386 folder to wherever you like, as long as it remains visible to your machine, and you make the registry update to let Windows know where it is.' Windows File Protection had attempted to check my system files.
I'm fairly certain that the error message it technically incorrect. No files had been replaced by unrecognized versions. Rather, the error was simply that the reference copy it expected in C: I386 was no longer there. I restored the copy of my machine's C: I386 folder to another machine, on a folder that had been shared and that was visible on my local network. The 'trick' to telling Windows where to look turns out to be a simple registry setting. Specifically the key HKEYLOCALMACHINE Software Microsoft Windows CurrentVersion Setup SourcePath.
Firing up regedit, locate that key: Note how it's set to 'C: ' by default. The folder must be named I386, and this setting tells Windows where to find that folder. Double clicking on SourcePath, you can then change it to be the full path to the I386 folder: Note that it doesn't include the 'I386', it just points to where I386 can be found. In my case it's freenas notenmax machinespecific leo i386, but the registry setting is freenas notenmax machinespecific leo. (In my case 'freenas' is the server, 'notenmax' is the share, and then 'machinespecific' and 'leo' are just folders within that share. I386 does not have to be at the root of the share.) Once updated, the setting does not take effect until you reboot. After rebooting I opened up a command prompt window and forced Windows File Protection to check all my files by running the System File Checker ( SFC /scannow): It completed normally, indicating that all files were good, and that the I386 folder had been accessed successfully from its new location.
The bottom line: you can move your I386 folder to wherever you like, as long as it remains visible to your machine and you make the registry update to let Windows know where it is. Article - August 2, 2007. Notenboom August 5, 2007 8:17 AM -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 David: My general philosophy is 'if it ain't broke, don't fix it'.:-) But you point out something I overlooked in the article: the SourcePath can often be pointed a the CD or DVD drive, and hence requires you to insert the CD or DVD on which you have Windows. Pointing it at C: I386,.if it's the same as on your CD. is a convenience to avoid having to load the CD when it's needed. But I'd leave it alone until or unless it became a nuisance.
Leo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGteojCMEe9B/8oqERAv3VAJ4iAv+BgKiG315wcMGHakmfSBsiIACcCKVe GKf8X3uwvPmczmMSf/sQEYA= =K5Wy -END PGP SIGNATURE. Larry August 17, 2007 4:50 PM The new Secunia Personal Software Inspector (www.secunia.com) is a program that looks for old versions of programs that have been superceded and contain holes that can be exploited by virii or malware.
It reports old versions with known holes in my i386 folder (such as an old Flash player). I know that I'm not running these versions from i386 on a routine basis, but I would like to delete them to prevent them from being loaded in the future, or prevent the module from being loaded by a malevalent program. However, removing them (assuming that I could find them among the compressed files in i386) might cause errors that could prevent Windows from using other information in the i386 folder. Notenboom August 19, 2007 12:51 PM -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I would leave the contents of the I386 folder alone. It represents a snapshot of the I386 folder from your install CD.
If things are updated, they'll be reflected in other directories (like the SP2 related I386) elsewhere on your machine. I would expect modifying the contents of I386 to have unpredictable results. Leo -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) iD8DBQFGyJ9NCMEe9B/8oqERAgVTAJ9yTpEx2/DtDKqmaTFt2Szzdis4OQCfZbP7 wEgzlessStPbw3GIBWg+1fw= =RXfB -END PGP SIGNATURE.
Craig Davidson March 22, 2008 11:40 AM I've moved my I386 file from my C drive to my E drive (my second hard drive). Now whenever I try to copy the I386 file to a dvd, it won't let me. I haven't deleted the file from my C drive yet (basically I have an I386 on both my C and E drives), and neither will copy to a dvd. I get the message 'Windows has encountered a problem when trying to copy this folder. What do you want Windows to do?'
-Retry- -Skip- -Cancel- I don't want to delete it from my C drive until I have a physical copy, in case there was a problem. What can I do? Mark S June 8, 2008 7:48 AM I have a somewhat related problem. I inserted a card into a hub/combo card reader and windows crashed and then rebooted. Since then, all my USB devices have been acting erratically. I've tested them with another computer and they work fine.
My guess: some files were corrupted in the crash. I got the 'Files that are required to run.' Windows properly error box that you reference above. However, it demands an XP Professional SP2 CD rom.
I upgraded to SP2 over the web. I have no CD rom to give it. It doesn't care about my original windows Home disk.
I ran the system file checker and it too asked me to insert the SP2 Pro disk I don't have. So apparently there are some files that need to be fixed or replaced. But I have no way to do this. Any tips, other than buying another copy of Windows? Thanks in advance.
Morgan December 6, 2008 7:20 AM Hi Leo I followed the instructions above as my SR has simply dissappeared! When i do the HKEYLOCALMACHINE Software Microsoft Windows CurrentVersion Setup SourcePath. Search I find my 'source path' is shown as D: when, having searched, it (I386 folder) is actually in C: I have no idea why the discrepancy as I certianly didn't move it! My question is, in order to fix my problem do I simply change the source path back to C: (as per instructions above) and then reboot and run SFC/SCANNOW? I hope so because other wise I'm lost! BAW30s January 5, 2009 5:12 AM I was trying this today and initially failed because I didn't know that it was necessary when editing the registry to put file paths in inverted commas whenever a space is present.
I had copied my I386 directory to C: Win2kP setups and the space had prevented the registry change from being effective; I then found in a blog on this subject that I should have written 'C: Win2kP setups'. Now SFC works properly.
So either don't use a file or folder name with a space or put the path in inverted commas. I hope this helps someone.
D wazzle September 23, 2011 1:10 AM Im running xp pro sp3, Ive tried changing that registry location to my I386 folder(correctly) but sfc still demands the cd. Another problem lately, is when i run sfc /scannow it doesnt replace any of the files it finds is corrupted. Sfc used to run and each time it found a file it said 'retry'. When it would finish and i would run it again it no longer came up with the 'retry' so I knew it had replaced them.
Now it just shows the same retry demands as it did the 1st time and I can tell that the Op system is slowly getting more corrupted. Why is it no longer replacing files? Is there a public software that can replace sfc? Patty November 28, 2011 11:39 AM Dear Leo, I knew 'SFC / scannow' allready by a moderator who helped me.
I have the problem too of a pop-up that asks me a cd of XP with SP3 for all the dll's. I have burned a cd with the iso of SP3, also I have tried several other things.till I formatted my HD and installed it allover, a new install.the 1st thing is that I did 'SFC / scannow', on the installment of how i bought the pc brand new in the shop.there was the same question about the cd!
Was it corrupt when I bought it? The weird thing is, my sister, my father, and brother of my sisters husband all have the same pc, and with all the 'SFC / scannow' isn't working and there is asked for a cd of XP for SP3 to load all the dll's. On Microsoft is nothing to find yet that helped. I know XP is old and antique in the world of pc's, maybe that's the crucial factor. Though i like XP.
Do you recognise the problem? I read somewhere about the i386, that's a part of SP3 too, that it has a shadow file somewhere.when rebooting, it wouldn't be the same in both files, the shadow file is recovering to the previous status, so they are not the same, that would cause this? I couldn't find the page anymore where i read it unfortunately.
Thank you for you site with info&suggestions, i like it. Best regards. Tony Kightley October 17, 2012 2:51 AM Having read your article about telling Windows where to find the I386 folder, I did not remember seeing I386 in the C: directory on my Laptop, so I checked and, then, did a search. I found 50 folders entitled I386 or i386, varying from a few Kb to 113Mb! Most were associated with ParetoLogic Anti Virus, apparently, and were in the Docs.
& Settings All Users App. As I do have a CD for the Win XP OS on the Laptop, the fact that an I386 folder is not in C: should not be a problem. Is it normal or common for proprietary programs to use i386 folders? However, what did puzzle me was several i386 folders in the a C/Windows directory such as Driver Cache and ServicePackFiles, although the corresponding C: Windows folders were, also, present. These rouge folders were, all, dated May 2011 and contained 0kb of data, so what I did to get them is a mystery - unless you have any ideas!
________________________________________ How to make STK amplifier dual power supply board making video link. 5.1 dolby digital tamil songs free download.
I did manage to delete them. Mark J October 17, 2012 11:25 AM @Tony None of the things you mentioned is of any particular concern, unless you are having other problems with your computer. It's not unusual for a proprietary program or driver to have a /i386 folder. I386 is sometimes used as a designation for 32 bit applications or drivers to distinguish it from x64 drivers which are 64 bit apps or drivers. I386 refers to the Intel 386 (or 80386) processor, the first 32 bit processor. The i386 processor hasn't been produces in the last 18 years, but the i386 designation is used to refer to all 32 bit processors. Comments on this entry are closed.
If you have a question, start by using the search box up at the top of the page - there's a very good chance that your question has already been answered on Ask Leo! If you don't find your answer, head out to to ask your question.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |