Ok, I realise I am starting to sound boring here, so skip the technical crap and we move on to the next part. You see it does not really what file system is used as the controller 'translates' it fit for the memory type used. When you start writing to it the first block is being filled, once full the second is being filled and so on. See it as a tower with the controller at the bottom and the memory blocks on top of it. Here is also the point where all the fakes fool you. So you have the controller taking your data and shifting it onto the actual memory chips. This is one reason why a 16GB chip never can take the full 16GB, usually between 14.5 and 15.8GB. Some areas of the memory can't be accessed with normal tools as they contain the actual info on the addressing and type of memory. Like a hard drive each flash memory not only contains a memory chip but also a controller to transfer the data.

It does not matter if you have a USB stick or SD card, the only difference is the connection type and the way it is addressed, in most cases you can find the same memory chips in both types. These additional log files will enable us to further troubleshoot why this is happening.Let me tell you a bit about the way these memory devices actuall work (in simple terms).

While in Finder, look for the FlashPlayerInstallManger.log file, in the same User's Library/Logs directory, upload this file.

Finder will open to this location, upload the two files (Adobe_ADM.log and Adobe_GDE.log).

Select the Adobe_ADMLogs directory and then CTRL+Click on the directory and then select 'Reveal in Finder'.

Look for ~/Library/Logs and expand it, if it isn't expanded.

Launch the Console app and on the left side there will be a list of log files.

You can use the Console app (/Applications/Console.app) to view all log files. Depending on your OS X version, the user's Library folder may be hidden. In the meantime, what does ' I have tried the Flash Uninstaller as well and that does not do anything.' mean?įor the installer log files, I've been informed that they are created as soon as the installer is launched, can you please look again.

Fakeflashtest stuck at 90