Chameleon I386 Folder Icon

I can laugh at myself.I will also allow others to poke fun at me, especially in this situation.but.How dare you ask me to use the 'search' function!!!Actually, I don't play well with forum search engines. Just one of those things.Luckily, you guys were here to help. I really do appreciate it.It has been a while since I did a clean install, etc. So maybe this was just thething to get me back in step. Good thing it was only a 'semi', and not 'full blown' emergency.I'll try REFIT, once I get done with formatting a spare drive.Also, it may be a good idea to create a program called 'UnFuckIt'. It could undo thethings people like me have done.

You could charge for it. You would be able to retire earlyOne last thing. Chameleon 1.0.11 works great with the MSI OSX install.

2.0 gets stuck will not work. That may be why I made this large mistake.

Logic seems to have 20/20 vision in these situations. Either way, great work guys! If you need help breaking anything, let me know. I really shouldn't have, but for some reason I installed Chameleon RC1 on my macbook (really should read what something does before installing) and now the machine does not boot. I get a flashing question mark on top of a folder icon when trying to boot the machine.Running Disk Utility with an installer DVD and verifying the disk shows no errors, nor does the 'repair disk' help.You can believe I'm sorry to take anybody's time with this problem, just hoping that someone in the know might be able to tell me where to go looking next, or what to do.many many thanks! Had the same problem this week.REFIT did not work for me. I had to use a spare drive and Carbon Copy my'screwed up' drive to it.It boots fine now.

This is a very time consuming fix. It was relatively easy using my Mac pro but you might have some difficulty using a laptop. If you have a large enough external drive, you can CC your HDD there, format your Macbook drive, then transfer it back to the Macbook drive.I'm sure there is an easier way to fix this but the people on this forum don't really care.

I understand their position but with this many people making a simple mistake, it only makes sense to include an 'un-install' utility.I guess what troubles me most is the fact that no one could tell me how to undo what had been done. This is computer science, not pharmacology, the way it works should not be such a mystery.I'll try to help the best I can, so just post as many details as possible. Okay, just in case this is useful for someone else in the future, I managed to fix this just with fdisk. It turned out that either there was no boot record whatsoever, or no partition marked active. Setting the booting drive via nice GUI tools that come with the OS X installation media were no good, but with running this I'm back to normal:use Terminal on the installation DVD / media and.fdisk /dev/disk0 (should list partitions on the disk, unfortunately I got a lot of zeros)fdisk -u /dev/disk0 (creates the new MBR record, apparently )fdisk -e /dev/disk0 (or whatever the drive is that you're wanting to play with)Mine complained: 'could not open MBR file /usr/standalone/i386/boot0: No such file or directory'. I ignored this as I was partly following instructions on this page:I knew that my disk only had one visible partition (except for the EFI one), so what I then did was:fdisk: 1 flag 2Partition 2 marked active.fdisk:.1 quitWriting current MBR to disk.

Rebooting machine as normal.Please note that this may not work in your case and at any rate remember that using fdisk can erase ALL your data on the drive you're operating on so count me lucky as I didn't really know what I was doing! Hey All,First of all, I'd like to say thanks for the great Chameleon software. Im triple booting XP, Debian, and OS X on my Asus eee 1000HE, and I couldn't be happier.However happy I may be now, I hit a few snags along the way, and chameleon wouldn't install on many of my flash drives (e.g, Corsair Flash Voyager 16GB) and while trying to figure out what would work and what wouldn't, I ran the cameleon installer 20+ times (from my Macbook Pro), and one time I accidentally ran the install onto my OSX partition on the Macbook Pro. Well, I was a bit frightened, but a reboot let me back into OS X no problems at all, but later when I tried using boot camp to boot into Windows XP it wouldn't work at all. Sad, I know, and fairly expected, I know.Any suggestions would be appreciated, Thanks.EDIT: I'm aware of the standard solution relying on refit, but I'd like to avoid that if at all possible. I'm also about to upgrade the Hard drive in my MBP tomorrow, so I'll be using Carbon Copy Cloner, maybe if I dont copy over the extra partition?

(Beyond the OS X and the WinXP Partitions). Chameleon screwed up my mac too, took about 8 hours to repair (requires an external hard drive):1. Take your OS X cd and put it into your mac.2. Power up and hold down the 'c' key.3.

When the apple appears, release the c key.4. When the install screen appears go to utilities (located on the bar on the top of the screen) and select the 'disk utilites'.5. Click on your mac hard drive and click on the 'repair' tab.6.

Click on your hard drive as the source and an external hard drive as the destination, this will back up your files on an external hard drive, and click the option below, I believe it's 'restore'.7. Click on your mac hard drive and click erase, and erase your hard drive.8. Go to the utilities option and click 'start up disk'.9. Select your OS X disk.10.

Restart and reinstall your OS X disk.Hope that helps!!!

If it exists C:I386 (the folder 'I386' at the root of your 'C:' drive) mostlikely contains an image of the installation copy of Windows. It's often placedon your hard drive as a way to avoid having to ask for a CD when Windowsdecides it needs some file that hasn't yet been installed.It's also used as one of the repositories for the original files used bySystem File Protection and the System File Checker.

If Windows determines thatone of its files has been replaced with an unrecognized copy, perhaps due to avirus, then the System File Checker will restore the file to its originalversion from C:I386. (It actually uses additional repositories as well, incase service packs and other updates have legitimately updated the file.)In an attempt to answer the question 'I wonder what happens if.' , Icarefully 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 updateto let Windows know where it is.' Windows File Protection had attempted to check my system files. I'm fairlycertain that the error message it technically incorrect.

No files had beenreplaced by unrecognized versions. Rather, the error was simply that thereference 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 afolder 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 simpleregistry setting. Specifically the keyHKEYLOCALMACHINESoftwareMicrosoftWindowsCurrentVersionSetupSourcePath.Firing up regedit, locate that key:Note how it's set to 'C:' by default.

The folder must be named I386, andthis setting tells Windows where to find that folder. Double clicking onSourcePath, you can then change it to be the full path to theI386 folder:Note that it doesn't include the 'I386', it just points to where I386 can befound.

In my case it's freenasnotenmaxmachinespecificleoi386, but theregistry setting is freenasnotenmaxmachinespecificleo. (In my case'freenas' is the server, 'notenmax' is the share, and then 'machinespecific'and 'leo' are just folders within that share. NotenboomAugust 5, 2007 8:17 AM-BEGIN PGP SIGNED MESSAGE-Hash: SHA1David: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 canoften be pointed a the CD or DVD drive, and hence requires you to insert the CDor DVD on which you have Windows. Pointing it at C:I386,.if it's the sameas on your CD. is a convenience to avoid having to load the CD when it'sneeded.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+BgKiG315wcMGHakmfSBsiIACcCKVeGKf8X3uwvPmczmMSf/sQEYAK5Wy-END PGP SIGNATURE. LarryAugust 17, 2007 4:50 PMThe 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).

Chameleon I386 Folder Icons

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. NotenboomAugust 19, 2007 12:51 PM-BEGIN PGP SIGNED MESSAGE-Hash: SHA1I would leave the contents of the I386 folder alone. It represents a snapshotof the I386 folder from your install CD. If things are updated, they'll bereflected in other directories (like the SP2 related I386) elsewhere on yourmachine. I would expect modifying the contents of I386 to have unpredictableresults.Leo-BEGIN PGP SIGNATURE-Version: GnuPG v1.4.7 (MingW32)iD8DBQFGyJ9NCMEe9B/8oqERAgVTAJ9yTpEx2/DtDKqmaTFt2Szzdis4OQCfZbP7wEgzlessStPbw3GIBWg+1fwRXfB-END PGP SIGNATURE. Craig DavidsonMarch 22, 2008 11:40 AMI'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 SJune 8, 2008 7:48 AMI 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. MorganDecember 6, 2008 7:20 AMHi LeoI followed the instructions above as my SR has simply dissappeared!When i do the HKEYLOCALMACHINESoftwareMicrosoftWindowsCurrentVersionSetupSourcePath. 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! BAW30sJanuary 5, 2009 5:12 AMI 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 subjectthat 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 wazzleSeptember 23, 2011 1:10 AMIm running xp pro sp3, Ive tried changing that registry location to my I386 folder(correctly) but sfc still demands the cd. Why?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? PattyNovember 28, 2011 11:39 AMDear 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 KightleyOctober 17, 2012 2:51 AMHaving 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. & SettingsAll UsersApp. 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! I did manage to delete them. Mark JOctober 17, 2012 11:25 AM@TonyNone 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 thetop of the page - there's a very good chance thatyour question has already been answered on Ask Leo!If you don't find your answer, head out toto ask your question.