Messages - brahman [ switch to compact view ]

Pages: prev1 ... 37 38 39 40 41 [42] 43 44 45 46 47 48next
206
Hello,

in my experience with USB sticks a brand new purchase may have a problem right away. If so immediately return it and do not use it. There were also a lot of fakes on the markets, which had a real size  of only 512MB, but made Windows think successfully that the size was several GB. It also allowed Windows to copy data in that amount (built the Fat with the filenames so that the files appeared to bo on the stick even when searchng for them later, but all the data went into the toilet WITHOUT ANY ERROR MESSAGE WHILE COPYING). These fakes can only be detected with special tools, since the controller is adjusted to show let's say 8GB, but there is only 512MB memory in it. Worse, problems will only show up, if you try to put more than 512MB of data on this stick and afterwards check all the data with a compare utility, since the file is registered in the file system and any file commander shows it to be on the disk, though it is not.

Because of wear leveling (the controller switches data to different sectors to increase life expectancy of the memory chips on write operations) USB sticks cannot be easily handled by standard hard drive diagnostic utilities. One give away for a fake stick though is a GRAPHED speed bench mark test: The REAL chip will be slow, and then the rest of the test will show unrealistically FAST results.

Like this fake 1 GB USB drive with only 256MB on board where the real chip is about 12,5MB/sec but the stick controller lets the data pass for the non-existent chips at 25MB/sec.:

http://img49.imageshack.us/img49/9814/hdtunebenchmarkgenericu.png


There is one free utility specially for USB sticks which a big German software magazine developed after they sent out a few hundred (at least) of those fake sticks to their users as gifts for subscribing to their magazine (and subsequently had to replace them all!).

I run this tool on all my USB sticks when first purchasing them.

It works best when the stick is formatted but completely empty, since it fills the stick up to capacity with its own data and then makes a byte by byte comparison. This way it bypasses the wear leveling and caching of the USB stick and can test every single sector. I would recommend to format the stick as Fat/Fat32 for testing, and only after first testing format to NTFS if so desired.

The program itself can be switched from German to English when started, but the web site is German only.

Here is the link to the website translated by google:

http://translate.google.com/translate?prev=hp&hl=de&js=n&u=http%3A%2F%2Fwww.heise.de%2Fsoftware%2Fdownload%2Fh2testw%2F50539&sl=de&tl=en&history_state0=&swap=1

Here is the original German link:

http://www.heise.de/software/download/h2testw/50539

Here is the link for directly  downloading the utility (which is a bit difficult to find):

http://www.heise.de/ct/Redaktion/bo/downloads/h2testw_1.4.zip

If you do have data problems on a stick already in use, I would recommend the excellent free Testdisk and Photorec. Run Photorec first to lift any problem data from the flash memory before starting the Testdisk repair procedure, since sometimes any repair attempt could theoretically make things work, so it is best to always do a recovery first.

Also another highly recommended program for most data recovery problem (USB stick use for free, hard disk use you need to buy the program) is Zero Assumption Recovery, which you can buy on a weekend with their special weekend discount for $29.95, but as said: Recovering photos from flash is free.

I have all of them in my tool kit, and they are must have for me.
 
One last piece of advice: Windows Checkdisk in error correct mode should only be run as a routine maintenance tool for very minor problems related to the file system. Do not run chckdsk if there is already a hardware or more serious data integrity problem, it can make things considerably worse and potentially unrecoverable. Always lift the data off first ( ... on a USB stick, slightly different story on a dying mechanical hard drive, but that would be another topic ...).

Hope this helps some.

Regards,

Brahman

207
Hi Mouser,

could it be that Total Commander and FARR interfere with hotkey assignments in a subtle way (using latest releases of both)?

Please see my thread here:

http://ghisler.ch/board/viewtopic.php?p=177052#177052

Regards,

Brahman

208
Hi,

I am late to the party, but can I make a drink request?  :)

I don't like when too  much stuff is running in the background and keep my system very clean. FARR is an exception, because it is such a great app.

Therefore would it be possible to make Tineev start "Everything" when invoked by FARR hotkey, and close "Everything" when the FARR window is hidden again?

Could you add a path entry in the ini file where the "Everything" path can be entered, in case "Everything" does not run in the background, so it can be started automatically.

And another ini option to close "Everything" when FARR goes to sleep - please, pretty please!?  ;)

That would be cool!  :Thmbsup:

Regards,

Brahman

209
There is another FF extension which forces HTTPS and has the additional feature of setting SECURE cookies. The authors have a very good paper  :up: on their site explaining a lot of details of how to secure your site and your browser. The use of secure cookies in this process is very important.

Here is the site for "Force HTTPS" extension:
https://crypto.stanford.edu/forcehttps/

and here are the changes I made to the .js file of the extension in the following folder location
..\extensions\[email protected]\defaults\preferences\forcehttps.js
in order to connect to Donationcoder securely:

Spoiler
// Rewriting rules (client-side)
pref("forcehttps.rewriting.rules.^http://(([^/]+[.])?donationcoder[.]com)/",
    "https://$1/");

// Full ForceHTTPS cookie protection
pref("forcehttps.blocking.rules.(^|[.])donationcoder[.]com$", true);

// Partial ForceHTTPS cookies (only allowed client-side)
pref("forcehttps.stripcookies.rules.(^|[.])donationcoder[.]com$", true);



If anybody knows a simple way (i.e. not sniffing) of determining if a cookie has been set securely or not, I would appreciate if (s)he could share that information with me.

The use of Force HTTPS seems to be even more secure than noscript because of the secure cookie setting feature.

I have noscript permanently deactivated, because I think it is almost impossible (at least for my surfing habits) to browse the web without the use of java script. So it is too much of a nuisance for me  :huh:. FF3.5 will hopefully make the possibility of cross scripting attacks more remote, FWIU.

Regards,

Brahman

210
@lanux128:
Thanks for your help. You know why I wasn't able to find it? My dpi, resolution, and font settings are a bit unusual, so the box never showed the "Add Exception" button, which is the one I was looking for. I only needed to expand the dialogue size and there it was tucked away on the far right corner ;D!

@f0dder:
It would be. Guess I was not clear: Not accept faulty certs globally, but allow to accept them with a confirmation click (i.e. old FF2 default behaviour is wanted here) instead of going through the rigamarole. But after I found again my "Add Exception" button, I guess that won't be necessary so much any more :Thmbsup:.

Regards,

Brahman

Pages: prev1 ... 37 38 39 40 41 [42] 43 44 45 46 47 48next
Go to full version